Subject: Re: Fw: Re: tcp connections lost on interface down
To: Michael van Elst <mlelstv@serpens.de>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: tech-net
Date: 08/24/2003 16:32:08
On Sun, Aug 24, 2003 at 11:03:14AM +0000, Michael van Elst wrote:
> bouyer@antioche.eu.org (Manuel Bouyer) writes:
> 
> >> In my opinion, reconfiguring the network is an exceptional event too.
> 
> >No. laptop users do it several times a day, when switching between
> >wireless and ethernet.
> 
> Well, I switch between wireless and ethernet and I can't even use that
> approach because the wireless connection is IPSEC while the ethernet
> connection isn't.

None are ipsec here, and dhcp is configured to give the same static IP
for both the wireless and ethernet adapter of a laptop.

> 
> 
> >> Dropping a connection when the address becomes invalid still sounds
> >> reasonable to me. I'd rather add methods for "moving" an address
> >> between interfaces that would not be seen as an exception. Providing
> 
> >This won't work, because there can be a window in which you don't have
> >an interface at all (for example if you have to remove your ethernet
> >PCMCIA adapter to plug in the wireless one).
> 
> Sure it would :) Use a virtual interface that maps to the real interface
> that is plugged in with automated failover.
> 
> Ah yes, someone has to write a driver that does this.

And it looks really overkill for something that already works.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 24 ans d'experience feront toujours la difference
--