On Wed, 2007-08-15 at 17:34 +0100, Roy Marples wrote: > On Wed, 2007-08-15 at 17:07 +0100, Graham Murray wrote: > > To avoid that problem, do not stop net.ethN when the cable is > > pulled. When the cable is re-inserted then (if it has not been left > > disconnected for too long) if the services have not stopped, TCP > > sessions may still be active. > > So what do you think would happen if I unplug cable A and plug in cable > B? Both are on separate networks.
I would expect it to act like any other Linux box and get a new address via dhcp, or, if I wasn't using dhcp, sit on the old address, even though it is now incorrect, until I changed it. A netplug event should trigger dhcp events, but not necessarily the services all dropping. After all, I've seen netplug do some funny things, like false positives on disconnection and such. I'd much rather my connection drop for a second and come back up, so all my packets can simply retransmit and everything continues, than have the services also decide to go down and refuse to resume any open connections when the connection comes back up. TCP has retransmission for a reason. Let's not break it if we don't have to do so. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation
signature.asc
Description: This is a digitally signed message part
