> Now, here's the kicker: the problem goes away if I run 'tcpdump': I do > tcpdump & > ping blarg.net > > and 'ping' responds correctly. I can then kill 'tcpdump', and until the next time I >boot, the network works fine. It's as if 'tcpdump' changed something, and that >change allows name resolution to work. > So that's the deal. Any ideas why my system is behaving this way, and what I can do >about it? > Thanks tcpdump put your NIC in promiscous mode, ie it allow your card get packets that have not your MAC address. I thought that recent kernels didn't hand off these packets to upper layers, but I'm not sure. So, i'ts possible that your cisco try to answer you with a wrong mac address because of DHCP misconfiguration. So you could have the same effect as tcpdump with ifconfig eth0 promisc To be sure of this you should try to see the result of tcpdump -e - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
