Can anyone diagnose this for me?
I'm in the process of building up a firewall but at some stage I musta
messed up and am now getting really weird results.
This is the results of a ping from 192.168.0.1 to 192.168.0.1 (the box
which will become the fireawall).
# PING 192.168.0.1
PING 192.168.0.1 (192.168.0.1) from 192.168.0.1 : 56(84) bytes of
64 bytes from 192.168.0.1: icmp_seq=0 ttl=225 time=0.7ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=225 time=80001.0ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=225 time=160000.9ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=225 time=240000.8ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=225 time=320000.8ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=225 time=400000.7ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=225 time=480000.7ms
--- 192.168.0.1 ping statistics ---
509 packets transmitted, 8 packets received, 98% packet loss
round-trip min/avg/max = 0.7/280000.7/560000.6 ms
This also happens when I do it from other machines behind the firewall
but I was very surprised when it did it when pinging itself.
Theres a pattern of 80000ms increments between successful pings...
Can't figure out whats wrong though.
If I try to telnet or FTP, I have to wait for an eternity b4 the login
prompt appears after the initial "connected" msg. But once I login
there is no problem using the console or transferring files. Same
thing for other machines to 192.168.0.1. So the network is "working"
but its waiting for something.
Has anyone had this happen to them b4 and manage to solve it?
Any help appreciated