Tony Battersby wrote: > "iperf -c 192.168.1.1" never finishes, but "iperf -c 192.168.2.1" does > finish. Press Ctrl-C to abort the hung iperf. Ping 192.168.1.1 does > not respond. Ping 192.168.2.1 does respond, but each ping has almost > exactly 1 second latency (the latency should be < 1 ms). > >
Update: after triggering the problem, the ping latency on the interface that still responds is the same as the ping interval. The default ping interval is 1 second, so in my initial test I was seeing a 1 second ping latency. If I do "ping -i 2 192.168.2.1", then each ping takes 2 seconds to receive the response. If I do "ping -i 5 192.168.2.1", then each ping takes 5 seconds to receive the response. This implies that the network stack doesn't realize that it received the ping reply until it goes to send another ping. Hope that helps. Tony Battersby Cybernetics -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
