Well - Michael got me thinking in the right direction (replied to him
off-list by accident), and some googling and guessing seem to have got
me through.
I performed "route add" commands to add the networks in question; this
allowed me to reach them, and freed up the rest of my internet access,
too.
ie. (as root) route add -net 192.168.1.0 netmask 255.255.255.0 dev ppp0
I would have thought these would be picked up by the configuration I
did in the Routing tab in pptpconfig. I'll have to dig deeper to find
out whether my assumption is bad, or there's something else wrong.
(The routes are torn down when the tunnel is - so I'll have to add
them each time until I can find the correct incantation to get them
set up automagically.)
With that - I fired up rdesktop and connected to my work machine
successfully at half-past midnight.
Err...yay?
It's worth at least a little yay, I guess. My Windows machine has sat
forlornly powered down, called upon only to access into work. It
would seem those days are over.
Cheers.
On 22/03/07, C.T. Paterson <i [ dot ] adore [ dot ] my [ dot ] 64 [ at ] gmail [ dot ] com> wrote:
On 21/03/07, Michael P. Soulier <msoulier [ at ] digitaltorque [ dot ] ca> wrote:
> On 3/21/07, C.T. Paterson <i [ dot ] adore [ dot ] my [ dot ] 64 [ at ] gmail [ dot ] com> wrote:
> > At this point - I would appear connected. An "ifconfig -a" shows that
> > the ppp interface has the address 192.168.1.119. Nonetheless, I can
> > not ping/access the machines I would expect inside the corporate
> > network, and I can not access the internet.
>
> What networks are you trying to reach? Are you trying to resolve DNS
> at work? Have you updated your DNS config?
I've tried to ping machines in the 192.168.0 network (the DNS), and in
the 10.2.0 network (a lab machine). I don't know any pingable
machines in the 192.168.1 network - but that's where my workstation
is, and this all started when I tried to rdesktop to it, and it was
timing out.
I will eventually want to use work's DNS - but I'm not getting that
fancy yet. I've been using IP addresses to eliminate the possibility
this was a DNS problem.
> Lets see your routing table.
>
> route -n
With the address munging as mentioned in my previous mail - this is what I have.
# route -n (before pppd)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.256.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.256.1 0.0.0.0 UG 0 0 0 eth0
When the tunnel is established, there is also the line:
192.168.1.105 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
It, of course, is removed when the tunnel is taken down.
Cheers.
--
"My country is the world, and my religion is to do good."
-- Thomas Paine
--
"My country is the world, and my religion is to do good."
-- Thomas Paine