AP ONE "handoff" to another AP ONE in local network not working well


Let us further check on that and update you shortly

1 Like

Thank you for your reply @sitloongs. We already enabled the Fast Transition setting as soon as it was available, but it did not seem to make any difference.

Can you confirm if this setting is supposed to work with iOS and Mac OS devices?

@mldowling, thanks for highlighting to us, we have updated the user manual and changed it to “dBm”.


There is another thread that helped me with my similar handoff problem (between my Surf Soho Router and my AP One Rugged as well as an Actiontec access point). Apparently there is a known handoff issue in the Soho router if you have created a VLAN and assigned a LAN port to be an Access Port (instead of a Trunk). I removed my VLAN and voila, all our iOS devices are now handing off seamlessly to the access points. Perhaps this also affects your Balance? Here is the other thread: Trouble with WiFi handoff on AP One Mini

1 Like

Thanks @peppypeplink for the suggestion and the link to the thread. I am not sure if the suggested solution is applicable to my situation as my AP’s are all connected to our LAN switch (Cisco) and controlled by a Balance One Core which is on the WAN side. There are no VLANs defined on the BOC and it has no problem managing the AP’s, so I would assume that the Hand Off and Fast Transition should work reliably. If not, I do not clearly understand what changes are required.

I am also not sure your post was describing the same issue I am having. In your case you mentioned problems connecting to a different AP and getting a new IP in the case of moving from one location to another. However, you did not make it clear if the device fell outside of the signal range of the original AP before the switchover happened.

In my case, I have identified two general patterns:

  1. If the original AP signal is lost completely (regardless of the Client Signal Strength Threshold or Fast Transition settings), then devices do connect successfully to the nearest available AP. However, if the signal is just weak and another AP with a stronger signal is closer, the device does not automatically switch over.

  2. Even if an apple device is in the same location for an extended period of time, the internet connection seems to get dropped even though the wifi signal is almost at full strength. I am facing this on a daily basis. This may be due to a problem with the DHCP lease recycle/refresh and the process may be taking a very long time. I have never tried to intentionally wait it out, but manually toggling my wifi gets the internet working again within seconds.

Hi Adeebag.
My solution is likely not for you, unfortunately. But just to clarify my setup for others:

My Pepwave Soho MK3 serves as both a router and an AP. I also have a Pepwave AP One Rugged (for coverage in a different part of the building) which just relays IP addresses from the Soho (which serves as the DHCP server).

Without a VLAN enabled and port assigned as “access”, the iOS devices handoff between APs perfectly upon leaving signal range. However, with a VLAN enabled and port assigned as “access”, the iOS devices that go out of range of the Soho will connect to the Rugged AP but drop the DHCP relayed IP address. The iOS device will then self-assign an internal IP number (i.e. 169.254.xxx.xxx) about 6 times over the course of ten minutes before finally obtaining its correct original IP address relayed from the Soho DHCP server through the AP One Rugged, once again establishing network/internet access.

Again the workaround for this issue is to disable VLANs with ports assigned as “access” (it’s possible that ports assigned as “trunk” may be OK).

The actual fix is available in beta firmware 8.0.2s005, and Pepwave support messaged me today that it will be included in the next G.A. firmware.

I’m sorry I wasn’t able to help your situation Adeeebag as I now know how frustrating handoff problems can be! Anyway, I hope this helps someone.