Paul Hinker wrote: > Miles, > > After snooping the interface a bit, I thought the problem must be coming > from the wireless bridge between my U27 and the router. I removed that but > I'm still seeing the same high latency. When pinging another machine on the > same network and snooping the interface I'm seeing the following: > > $ pfexec snoop -tr -d e1000g0 -P > Using device e1000g0 (non promiscuous) > 0.00000 192.168.1.100 -> 192.168.1.130 ICMP Echo reply (ID: 937 Sequence > number: 3) > 0.99997 192.168.1.100 -> 192.168.1.130 ICMP Echo reply (ID: 937 Sequence > number: 4) > 2.00004 192.168.1.100 -> 192.168.1.130 ICMP Echo reply (ID: 937 Sequence > number: 5) > 2.04618 ns7.skybeam.com -> 192.168.1.130 DNS R Error: 3(Name Error) > 2.07063 192.168.1.1 -> 192.168.1.130 DNS R Error: 2(Server Fail)
That sure looks like DNS trouble. Try doing "ping -n" and see if the apparent delays go away. If they do, then that's the problem: your RFC 1918 addresses aren't being resolved properly back in to host names, and that's causing ping to get hung up. A "simple" fix is to run a caching DNS server, and map the 168.192.in-addr.arpa domain into your own local set of definitions. The good news is that it doesn't represent any sort of real performance problem. ;-} -- James Carlson 42.703N 71.076W <[email protected]> _______________________________________________ networking-discuss mailing list [email protected]
