Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-04 Thread Marc G. Fournier
On Thu, 4 May 2006, Gavin Atkinson wrote: On Thu, 2006-05-04 at 12:27 -0300, Marc G. Fournier wrote: On Thu, 4 May 2006, Gavin Atkinson wrote: On Thu, 2006-05-04 at 11:30 -0300, Marc G. Fournier wrote: On Thu, 4 May 2006, Rutger Bevaart wrote: Technically it's not routes that are not being

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-04 Thread Gavin Atkinson
On Thu, 2006-05-04 at 12:27 -0300, Marc G. Fournier wrote: > On Thu, 4 May 2006, Gavin Atkinson wrote: > > > On Thu, 2006-05-04 at 11:30 -0300, Marc G. Fournier wrote: > >> On Thu, 4 May 2006, Rutger Bevaart wrote: > >> > >>> Technically it's not routes that are not being updated, but a stale > >>

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-04 Thread Marc G. Fournier
On Thu, 4 May 2006, Gavin Atkinson wrote: On Thu, 2006-05-04 at 11:30 -0300, Marc G. Fournier wrote: On Thu, 4 May 2006, Rutger Bevaart wrote: 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

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-04 Thread Marc G. Fournier
On Thu, 4 May 2006, Rutger Bevaart wrote: On May 4, 2006, at 4:30 PM, Marc G. Fournier wrote: This is what we end up having to do ... but, unfortunately, that means getting ahold of our co-lo provider and asking them to do it ... they have always been most accomodating, its just one of those

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-04 Thread Gavin Atkinson
On Thu, 2006-05-04 at 11:30 -0300, Marc G. Fournier wrote: > On Thu, 4 May 2006, Rutger Bevaart wrote: > > > 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

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-04 Thread Rutger Bevaart
On May 4, 2006, at 4:30 PM, Marc G. Fournier wrote: This is what we end up having to do ... but, unfortunately, that means getting ahold of our co-lo provider and asking them to do it ... they have always been most accomodating, its just one of those things that I shouldn't *have* to do :(

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-04 Thread Marc G. Fournier
On Thu, 4 May 2006, Rutger Bevaart wrote: 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 t

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-04 Thread Antony Mawer
On 4/05/2006 6:20 PM, Rutger Bevaart wrote: 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

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-04 Thread Rutger Bevaart
) From: "Marc G. Fournier" <[EMAIL PROTECTED]> Subject: Re: em(4) device still 'freezes' on latset CVSup'd 6.x ... To: freebsd-stable@freebsd.org Message-ID: <[EMAIL PROTECTED]> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Also, as an aside ... 6.x em

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-03 Thread Marc G. Fournier
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 insta

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-03 Thread Mark Linimon
On Wed, May 03, 2006 at 05:42:41PM -0700, David Kirchner wrote: > I don't know the protocol for this -- would the old PRs be re-opened, > or should a new PR be filed for 6.x? I'd recommend filing a new PR but reference the older ones in case it is indeed the same problem. mcl

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-03 Thread David Kirchner
On 5/3/06, Marc G. Fournier <[EMAIL PROTECTED]> wrote: I just upgraded one of my old 4.x server to 6.x, and the one annoying problem that I've experienced with 4.x persists in 6.x ... ... when you ifconfig alias a new IP onto an em(4) device, the tcp/ip stack (I'm guessing) hangs for a period o

Re: em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-03 Thread Steven Hartland
Marc G. Fournier wrote: I just upgraded one of my old 4.x server to 6.x, and the one annoying problem that I've experienced with 4.x persists in 6.x ... ... when you ifconfig alias a new IP onto an em(4) device, the tcp/ip stack (I'm guessing) hangs for a period of time, while my 6.x/bge0 server

em(4) device still 'freezes' on latset CVSup'd 6.x ...

2006-05-03 Thread Marc G. Fournier
I just upgraded one of my old 4.x server to 6.x, and the one annoying problem that I've experienced with 4.x persists in 6.x ... ... when you ifconfig alias a new IP onto an em(4) device, the tcp/ip stack (I'm guessing) hangs for a period of time, while my 6.x/bge0 servers don't hang at all,