aric wrote: >> --On December 4, 2009 7:35:57 AM -0500 James >> Carlson<[email protected]> wrote: > [snip] >> It may be ossible to hack the system so that it "ignores" the >> conflicts ("set arp:arp_no_defense = 1" in /etc/system may do it), >> but then you're just a sitting duck. > > Interestingly, I did do this on build 121 and left it running for the last 7 > days. I have since updated to build 129 where this hack is NOT in place, and > I am now receiving an IP address. The same that I was assigned when I put > this hack into /etc/system last week on build 121. > > I suspect that somehow the arp table got messed up on my machine and changing > /etc/system temporarily fixed the problem. I wonder if arp -d would have been > sufficient?
Having the ARP table messed up on your machine wouldn't cause the symptoms you described. However, having someone else's ARP table somewhere on your local network messed up -- such that it answers for the IP address that you're being assigned -- would explain the problem. I still think you've got either a broken piece of equipment on that network, or perhaps a DHCP server that has bugs. It's good to hear that it's working for you now, but I wouldn't be surprised to find that you come back later with more trouble. -- James Carlson 42.703N 71.076W <[email protected]> _______________________________________________ networking-discuss mailing list [email protected]
