On 26 Apr 1998 at 18:22:06, Dave Freeman wrote:
>> What I would like to do now is change the default route so that the
>> ppp link on the RH5 box is the default route for the RH5 box
>
>Thanks to all those who pointed me in the right direction. I have
>managed to get the default route situation fixed up and my RH5 box
>now dials up, establishes a connection and also establishes a default
>route.
>
>>From this RH5 box I can actually ping/traceroute to internet systems
>just fine.
>
>Flushed with my success I then changed the default route on one of
>the other machines on my LAN so that it would now point to the
>gateway on the RH5 box.
>
>Unfortunately, this other box cannot make use of the gateway on the
>RH5 box. I can ping the RH5 box from the other box so I know the
>network connection exists. From looking at the LED's on my hub it
>looks like the other box is sending tcp packets to the RH5 box.
>Unfortunately they seem to go no further than that.
>
>I am guessing this is tied up in IP forwarding or routing configs.
>
>Can anyone point me in the right direction for fixing up this side of
>things?
>
>FWIW, when the ppp connection is up my 'route -n' looks like this:
>
>Destination Gateway Genmask Flags Metric Ref Use Iface
>203.58.22.3 0.0.0.0 255.255.255.255 UH 0 0 1 ppp0
>203.57.10.0 0.0.0.0 255.255.255.0 U 0 0 7 eth0
>127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 3 lo
>0.0.0.0 203.58.22.3 0.0.0.0 G 0 0 28 ppp0
I think I've got the same problem you have -- the problem is that the machine
at the other end of your ppp connection only has a single host route back to
your machine's ppp0 IP address and does not have a network route for your
local network.
If you were to look at the routing table on the other machine, you'd see:
203.58.22.2 0.0.0.0 255.255.255.255 UH 0 0 1 ppp0
(I'm assuming 203.58.22.2 is the IP address of YOUR end of the ppp0 connection
-- it could be something else, of course) as the only route using the ppp0
interface -- it does not have a route like:
203.57.10.0 203.58.22.2 255.255.255.0 U 0 0 7 ppp0
(Again, I'm assuming your end of the ppp0 interface is 203.58.22.2 -- it could
in principle be anything -- and I'm assuming your other LAN hosts are on the
same network that your eth0 interface is)
So what happens is your machine happily sends out packets from your other LAN
hosts out the ppp connection, but the other side of your ppp connection doesn't
know what to do with the incoming packets destined for these machines and
probably tries to send them back out it's default gateway.
I have not found an answer to this -- I have to log on to my ppp server and
manually create the network route.
I suppose you could do IP masquerading on your ppp box and masquerade all
IP addresses from your 203.57.10.x network:
ipfwadm -F -i accept -P all -S 203.57.10.0/24 -D 0.0.0.0/0 -m
You have to have your kernel built with IP forwarding and IP Masquerading for
this to work -- I think the default kernels have them built, not sure. I'm
already masquerading on my ppp server and don't want to add another masquerade
on my local ppp machine.
>
>(Yes, I have had a look thru the stuff on redhat.com but most of the
>network config stuff refers to using netcfg and I don't have X
>installed on _any_ computer on my LAN at the present time.)
>
>Thanks for any help you can offer...
>
>Dave.
Dirk
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
