Posted: Wed Jul 21, 2010 6:31 Post subject: AP not releasing Mac Address wen roaming
hi guys this is my first post but here goes
currently we have 3vlans in our company with 7AP's split between floors
2 -3rd floor
3 -2nd floor
2 - ground floor
which is genius EAP-3660
now the problem i have is that as soon as i connect on a specific floor say for example 2nd floor
and i disable the wireless radio on my laptop and than walk to another AP on same floor and re inable the radio my mac is still on the previous AP i connected
and thus i get a time out with no ping and only wen i reboot the AP that the mac is stuck on I get ping and internet access on the AP i moved to ....
Q1. is the problem the arp table thats not releasing mac quick enough?if so how do i get rid of this problem?
Q2.can it be because WDS is disabled or was not config correctly?
thanks for the help in advance
What we have is the following:
Three Access Points running the same release of dd-wrt:
DD-WRT v24-sp2 std (c) 2009 NewMedia-NET GmbH
Release: 10/10/09 (SVN revision: 13064)
These are all running in bridged mode, shared SSID using WPA2 Personal (TKIP). The common VLAN they're on is linked to our Cisco core, which handles our traffic levels well.
We'd like to have users (95%+ Windows 7 Pro) roam with little to no network interruption.
We've run into the following snag:
1) Begin a continuous ping to an Internet host.
2) Connect to Access Point 1 (AP-1).
-> Ping flows normally.
3) Walk towards AP-3 past AP-2. Since the signal strength is sufficient to maintain AP-1, no handover is performed, even though the signal from both AP-2 and AP-3 is higher.
-> Ping flows normally, if somewhat erratic because of packet loss.
4) While standing under AP-3, toggle the Hardware Wifi Radio button. Now the web interface on AP-1 still notes that the relevant (notebook)'s MAC is associated with it.
5) Turn the Wifi Radio switch on. Since AP-3 is closest, the radio will associate with AP-3. But AP-1 still believes that the (notebook) is connected through it.
-> NO NETWORK CONNECTIVITY.
The APs are running in AP mode (not client_bridged), but the wireless and cabled interfaces are bridged (under the section looking like this:
Network Configuration ( ) Unbridged (o) Bridged
)
sorry for the confusion
