Technically it's not routes that are not being updated, but a stale
(outdated) ARP cache on the other hosts. The system with the new
alias'ed IP needs to do a gratuitous ARP (broadcast ARP for it's own
IP). As an intermediate solution you could flush the ARP cache on the
hosts with stale cache (usually a router or L3 switch on the subnet).
Sounds like a bug in the em driver. Anybody do sniffing to see if it
does send out ARPs? If not I can test on one of our Dell 2850's with
em's.
Regards,
Rutger Bevaart
Date: Wed, 3 May 2006 21:43:39 -0300 (ADT)
From: "Marc G. Fournier" <[EMAIL PROTECTED]>
Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Also, as an aside ... 6.x em(4) still isn't sending up the arp
broadcasts,
so IPs moved from one machine to this one aren't having their routes
appropriately updated ... again, please note, that moving an IP
from any
machine to a *non* em(4) interface does update the routes properly and
instantly ...
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
