Hi all,
I have a *Really* weird networking problem - and I'm hoping it is
something obvious that I have missed.
I have an ISDN interface dialed into work. This is authenticating
correctly and seems to be correct. The following extract from ifconfig
shows the interface setup:
ippp0 Link encap:Point-to-Point Protocol
inet addr:10.254.254.4 P-t-P:10.254.254.1 Mask:255.255.255.0
UP POINTOPOINT RUNNING NOARP MTU:296 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:30
where my local IP address is 10.254.254.4, and the remote access server is
10.254.254.1. With the routing table as follows (no default route):
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
storm.localnet * 255.255.255.255 UH 0 0 0 eth0
10.254.254.0 * 255.255.255.0 U 0 0 0 ippp0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
I can ping the local ISDN interface (10.254.254.4) and the remote ISDN
interface (10.254.254.1).
However, if I add ANY routes through the interface as follows:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
storm.localnet * 255.255.255.255 UH 0 0 0 eth0
10.254.254.0 * 255.255.255.0 U 0 0 0 ippp0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
172.16.0.0 10.254.254.1 255.255.0.0 UG 0 0 0 ippp0
I can not ping the local interface (10.254.254.4)
I can not ping the remote interface (10.254.254.1)
I can not ping any hosts on the target network.
It is possible that there are routing issues in the remote network
preventing the ping responses returning from the 172.16.0.0 network -
however I should still be able to ping the local and the remote interface.
(note - the same behaviour occurs with a default route instead of the
172.16 network).
This seems really strange and not what I expect to see.
Any ideas ?
Jason.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
