On Sun, 7 Apr 2013, Edward Ned Harvey (lopser) wrote:
Date: Sun, 7 Apr 2013 12:03:24 +0000
From: "Edward Ned Harvey (lopser)" <lop...@nedharvey.com>
To: David Lang <da...@lang.hm>, Frank Bulk <frnk...@iname.com>
Cc: "tech@lists.lopsa.org" <tech@lists.lopsa.org>
Subject: RE: [lopsa-tech] Wifi
From: tech-boun...@lists.lopsa.org [mailto:tech-boun...@lists.lopsa.org]
On Behalf Of David Lang
Ahh, but if they keep the same SSID, and the APs are bridged with DHCP being
handled at some central server (not on the individual APs, then moving from
one AP to another is just dis-associating andassociating to the new one. No
need to change IP addresses, no need to re-establish the VPN.
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'm pretty sure that I've actually (accidently) tested this while reprogramming
APs on one interface of my laptop while being connected to the network on
another interface. I've downed the interface or changed the IP and then fixed it
and telnet/ssh connections have come back to life.
I've also had active connections on my laptop and moved around the building from
one APs coverage zone to another without loosing the connection.
David Lang
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
