Re: bsd: arp info overwritten for x.x.x.x by X:X:X:X:X:X on xl0

[Paul Greene <pauljgreene_(_at_)_comcast_(_dot_)_net>]

I have Comcast cable, which recently broke off from Excite_(_at_)_Home_(_dot_)_ Since the 
switch I've also been getting the same message, but it doesn't seem to affect 
anything. Everything works fine.

Paul Greene

On Thursday 07 February 2002 19:57, Ryan Lindsey wrote:
> well. i forced it to release using ipconfig at command line (tried to ping
> the released address and it wasn't there) and no one else had that ip. then
> i renewed it and got the same ip.  BSD box is still getting the 'arp info
> overwritten' stuff though.
>
> rbl
>
> ----- Original Message -----
> From: "David S." <davids_(_at_)_idiom_(_dot_)_com>
> To: "Ryan Lindsey" <rlindsey_(_at_)_austin_(_dot_)_rr_(_dot_)_com>
> Cc: <misc_(_at_)_openbsd_(_dot_)_org>
> Sent: Thursday, February 07, 2002 5:28 PM
> Subject: Re: bsd: arp info overwritten for x.x.x.x by X:X:X:X:X:X on xl0
>
> > > Normal set up for two ip addresses, cable modem to the uplink slot in
> > > my first hub and then
> > > both machines connected to hub recieves an ip address.  One machine is
> > > WinXP(66.68.195.49) and the other is OpenBSD(66.68.202.12).
> > >
> > > Feb  7 12:03:42 devin /bsd: arp info overwritten for 66.68.195.49 by
> > > 00:30:7b:ff:50:70 on xl0
> > > Feb  7 12:15:44 devin /bsd: arp info overwritten for 66.68.195.49 by
> > > 00:50:04:ce:cb:0d on xl0
> >
> > Try disconnecting your Windows box, and see if 66.68.195.49 answers
> > a ping.  If so, there's another machine on the subnet using that
> > address.  Windows DHCP clients cling rather tenaciously to an address
> > once assigned, or so I understand.  You may have to force yours to
> > give up its address.
> >
> > David S.