NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WAC540 ca. 5 Minute Delay on First Connection till PING start working
Dear Community, I have 2 WAC540 , both are configured for 5L and 5H only . Here I have "default" values : Wireless Mode : 11ac Output Power : 100% MCSI Index/ Data Rate : Best Guard Interval...
Hi vpk_kumar ,
thank you . Unfortunately I will have to wait till the weekend because the switch (in Office) is not a PoE switch , and I have only 1 Power Supply for the WAC540.
But I will try as you told me. I will :
1. Replace Office switch with PoE switch ( HP newer model ) .
2. Connect Office AP and another Production AP to the same switch , and try to roam .
Notice : I have googled yesterday and I found a post where some people where having the same problem with Wireless Roaming and MAC not beeing correctly updated .
Anyway if the above brings nothing , I have already devised a master plan :) I will order 2x TPLink 5 Port POE "dumb" switches . And will connect the AP to it , and then connect the TP Link to the switch . And will label the Switch ( Bugfix :) )
Regards
Robert
Hi vpk ,
thank you for the fast response. I just tried what you told me.
iPhone and Android simply pinging 192.168.0.202 (IP of AP) it worked instantly. Trying to ping 192.168.0.11 (IP) of Remote Computer ( Windows 10 ) 5 Minutes .
Also pinging from 192.168.0.202 the IP 192.168.0.11 works imediatelly, there are no drops .
There are also no drops from 192.168.0.11 to 192.168.0.202 .
To have the bigger picture both APs ( 192.168.0.203 and 192.168.0.202 ) are in a subnet with no gateway whatsoever ...
the Clients connecting them are all in the 192.168.0.x subrange. And the Server which then communicates with the Clients is also in the 192.168.0.x range . This is a Scanning Network .
Both APs are configured like this :
IP Address : 192.168.0.202 ( or 203 )
Subnetmask : 255.255.255.0
Gateway 192.168.0.1 ( does not exists )
DNS 192.168.0.1 ( does not exists )
Secondyary DNS 8.8.4.4 ( not reachable )
I do not wish to reach the Wireless APs and Clients from anywhere except the Server . But I suppose this is not the problem because it works instantly on AP 203 which is in my Office .
Any ideas what now ?
TThank you Robert
Found the Offending switch! :) But I don't know what on earth is wrong with it. It is not routing as far as I can tell, I also went trough all the switches widh show cdp neighbours to check if they are simple dumb switches and yes.
The offending swtich is a HP Procurve J9279A . I will replace it with a newer modell this weekend in the hopes that it might solve the problem. But I thought I'd ask here is there perhaps a magic switch which might be causing this ?
It looks like this :
I connect Office AP directly to this switch
Production AP is connected to another switch ( which is like this Dispatch Switch -> Midway Switch -> Offending Switch )
if I go to Production I have to wait 5 minutes until I am able ping anything other then the Production AP itself.
if I come back to the Office I have to wait 5 minutes until am ab able to ping anything other then the Office AP .
If the Office AP is connected to a cheap TP-Link switch which is then connected to this Offending Switch it works instantly. Sorry but WTF?
Is this perhaps some sort of ARP safety feature ...
Regards
Robert
UPDATE :
I have on all the Switches STP enable. So I did the same for the two APs . Unfortunately did not help.
I also tried what happens if I go back connect and start pinging then turn off device wait for 5-10 minutes. And turn it on again.
Strangely for both Office and Production if I connect once, and turn off wait and turn on it works instantly. Only if I go from AP Office to AP Production do I need to wait 5 minutes.
hi Robert,
Is it that your issue can happen on both the Ap's after you move the wireless client from 1 Ap to another AP and each Ap is under different switch?
#try : Will the issue happen if both the Ap's are under 1 switch( keep HP/Tplink at a time ) and remove the other switch from network. Move the client from 1 Ap to another AP.
Looks to be that the macadress of the client is not getting updated to the correct port of the the switch when you move the client to new Ap and hence packet wont reach to correct port. After the default aging time of 300secs , old entry for the client macaddress might be getting removed in switch table and then datapath resumes. Please check if you could isolate the isolate the issue with #try test.
Hi vpk_kumar ,
thank you . Unfortunately I will have to wait till the weekend because the switch (in Office) is not a PoE switch , and I have only 1 Power Supply for the WAC540.
But I will try as you told me. I will :
1. Replace Office switch with PoE switch ( HP newer model ) .
2. Connect Office AP and another Production AP to the same switch , and try to roam .
Notice : I have googled yesterday and I found a post where some people where having the same problem with Wireless Roaming and MAC not beeing correctly updated .
Anyway if the above brings nothing , I have already devised a master plan :) I will order 2x TPLink 5 Port POE "dumb" switches . And will connect the AP to it , and then connect the TP Link to the switch . And will label the Switch ( Bugfix :) )
Regards
Robert
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
