On Sun, Apr 7, 2013 at 7:22 AM, David Lang <[email protected]> wrote: > When the AP's don't support roaming, the client needs to dissociate from >> the original AP, give up its IP address and request again from DHCP. The >> fact that DHCP assigns the same IP again is largely irrelevant - the fact >> that the client needed to give up the IP in the first place means it dumped >> its TCP stack. Your UDP connections should remain connected just fine, but >> TCP gets dumped. >> > > actually, TCP connections don't get dumped when I've done this. I may be > getting lucky and not happening to send traffic in the small window when > it's down, but it doesn't automatically cut all connections. >
I will second this; moreover, in at least some cases I have had devices manage to recover existing connections even if they do try to send data. It depends on whether the OS actually tears down the interface while renegotiating or leaves it valid; the latter is more common these days, likely because of this + it's faster in general than knocking down the interface completely even though it requires more work on the part of the OS than a simple ifdown-renegotiate-ifup. -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
