[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Modem and NIC Gateway



On Thu, Feb 5, 2009 at 2:02 PM, Zanga Chimombo <z.chimombo@admarc.co.mw> wrote:
> Aneurin Price wrote:
>>
>> You shouldn't need to set a gateway in order to ping 172.21.0.1 because
>> you should have a direct connection to it. Your initial routing table
>> looks like it should work so I'd suspect another problem. That said, the
>> final line isn't right if you want to contact the outside world.
>> 0.0.0.0         0.0.0.0         0.0.0.0         U         0 0          0
>> ppp0
>> should be:
>> 0.0.0.0         172.21.0.1      0.0.0.0         U         0 0          0
>> ppp0
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt
> Iface
> 172.21.0.1      0.0.0.0         255.255.255.255 UH        0 0          0
> ppp0
> 192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0
> eth0
> 0.0.0.0         172.21.0.1      0.0.0.0         UG        0 0          0
> ppp0
> 0.0.0.0         0.0.0.0         0.0.0.0         U         0 0          0
> ppp0
>
> yeah, the final line looks dubious to me too, but i wasn't sure. however, if
> i make the changes u r suggesting surely the 3rd and 4th lines will only
> differ on the "G" flag? that doesn't look right either!?
>

My apologies, that should indeed have the 'G' flag, so the modified version
is correct aside from the addition of the extra line with no gateway set.

>> You said you can connect fine using ppp alone - what does the routing
>> table look like then?
>
> i can connect fine to the internet from the gateway. This is what it looks
> like.
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt
> Iface
> 172.21.0.1      0.0.0.0         255.255.255.255 UH        0 0          0
> ppp0
> 192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0
> eth0
> 0.0.0.0         0.0.0.0         0.0.0.0         U         0 0          0
> ppp0
>

You said 'i am able to ping 172.21.5.136 but not 172.21.0.1' and 'i can
connect fine to the internet from the gateway'.
So you can ping, say google.com from your gateway machine correctly? But
you can't ping 172.21.0.1 from your gateway? If that's the case, then maybe
172.21.0.1 is simply set not to respond to ping requests.

Since you can get to the internet from your gateway, then its routing should
be fine, and the next thing is to configure IP masqurading to allow your
internal network to connect via that machine.

Nye


Reply to: