Paul Parkyn wrote:
Hello Steve & Andy,
The result of route -n:-
[EMAIL PROTECTED] bin]# /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
202.0.46.87 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.42.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
eth0
0.0.0.0 192.168.42.12 0.0.0.0 UG 0 0 0
eth0
[EMAIL PROTECTED] bin]# ping 202.0.46.87
PING 202.0.46.87 (202.0.46.87) 56(84) bytes of data.
64 bytes from 202.0.46.87: icmp_seq=0 ttl=255 time=151 ms
64 bytes from 202.0.46.87: icmp_seq=1 ttl=255 time=143 ms
64 bytes from 202.0.46.87: icmp_seq=2 ttl=255 time=141 ms
64 bytes from 202.0.46.87: icmp_seq=3 ttl=255 time=139 ms
64 bytes from 202.0.46.87: icmp_seq=4 ttl=255 time=613 ms
64 bytes from 202.0.46.87: icmp_seq=5 ttl=255 time=132 ms
64 bytes from 202.0.46.87: icmp_seq=6 ttl=255 time=138 ms
--- 202.0.46.87 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6004 ms
rtt min/avg/max/mdev = 132.969/208.995/613.898/165.379 ms, pipe 2
[EMAIL PROTECTED] bin]#
What puzzles me is why the ISP assigns me this ip address.
I have tried with seLinux disabled and the firewall turned off and set kppp to
assign the default route.
Looks like it's pinging OK... Tell ya what, try this...
At a command prompt, type
route add default gw 202.0.46.87
...then see if you get traffic through. Maybe related, maybe not, Hows
the DNS setup?
