Orbi RBR350 in AP mode - not always getting DHCP IP when roaming

Question

Hi folks,&nbsp;I have a frequent issue with my Orbi setup in AP mode which is quite annoying. When roaming around with my device throughout the house, I often find that I get no connectivity, while the WiFi signal is still great. When I check the DHCP status of my device in this situation, I often find it resorted to a 169.254.x.x (link-local, autoIP) address. The only possible reason for this IMO is that the DHCP request, which the device did after roaming to the other AP, timed out. I've actually verified this in the macOS logs on my MacBook (there was a request, but no timely reply, making it go into autoIP).&nbsp;This usually recovers when I completely disable and re-enable the WiFi on my device, but of course, this is only a workaround and something which should not be required to do.&nbsp;Below is a schematic of my setup. It seems to me that I encounter the issue the most when I'm getting closer to my 2nd floor station, which might indicate it's an issue with the wireless backhaul, because the other stations are wired.&nbsp;The cause is not 100% certain to blame Orbi of course (especially with the smart switches in between), but my reasons why I think the chances are high that it is Orbi:I didn't have this issue yet before I got Orbi (I was using the builtin FR!TZBox WiFi, together with a wired FR!TZ repeater in the attic, connected via the same switch path)I seem to have the issue when nearing the only Orbi station which has a wireless backhaulTo make this even more evident: before I reduced the Orbi's TX power to 50% I often had the issue in the attic as well. Afterwards much less often, which indicates that my device probably likes to switch to the attic station sooner (because the 2nd floor becomes too weak) and gets back on wired backhaul which doesn't have this issue.The issue occurs after roaming, but can be workaround by toggling the WiFi on the client (why would a switch block a 1st DHCP request, but shortly thereafter allow the 2nd one...?) so this could indicate that the Orbi station handles roaming clients differently than "freshly" connecting clients (turning their wifi on)Roaming with the previous FR!TZ wifi system worked fine with the same clients and network setupI've disabled IGMP / MLD snooping, DHCP proofing and any other feature which I suspect of interfering with multicast on the smart switchesI've installed the latest firmware on everythingOne of the changelogs of the GS108Tv3 firmware indicated fixing an issue related to passing DHCP when there's an extra device in between, but apparently this fix didn't helpAny ideas?&nbsp;Orbi setup

danielschenk · Answer

Thanks for the tip. I'll first do a test by powering off the 2nd floor satellite, and to make up for the lost coverage, put the system back to 100% TX power, because I think I can survive with that. I think this is a better test for isolating the issue than using a bad powerline adapter or finding a better backhaul spot.&nbsp;After I've isolated the issue to the 2nd floor satellite this way I can start trying the other things. I will keep you posted.

Garwoofoo · Answer

This sounds a lot like the problem that's been reported in a few threads here where iPhones especially are losing connection when roaming between satellites.&nbsp;I don't think the precise reason has been identified yet and it looks like an Orbi bug for sure but it does seem to occur more in setups that have a mixture of wired and wireless satellites. Since I moved both of my satellites to wireless I haven't seen the issue.

ekhalil · Answer

Garwoofoo&nbsp;wrote:This sounds a lot like the problem that's been reported in a few threads here where iPhones especially are losing connection when roaming between satellites.&nbsp;I don't think the precise reason has been identified yet and it looks like an Orbi bug for sure but it does seem to occur more in setups that have a mixture of wired and wireless satellites. Since I moved both of my satellites to wireless I haven't seen the issue.It looks like an old issue from 2019 is back now again. I see few people reporting issues with wired backhaul. That issue was caused by loops when a satellite is paired with both wired and wireless backhaul. There was a workaround for that issue at that time:https://community.netgear.com/t5/Orbi/Wired-backhaul-configured-but-still-shows-WLAN-Backhaul/m-p/1791580/highlight/true#M68964&nbsp;

danielschenk · Answer

I've encountered the issue several times now without the wireless satellite. This means that either the wireless satellite wasn't the cause, or it wasn't the only one.&nbsp;ekhalil&nbsp;wrote:Can you please try this procedure in the wired satellite:1. Switch off the Satellite2. Go to Attached Devices in the web GUI and click on the "Disconnect" button beside the Satellite in questions3. Turn on the Satellite and use a paper clip to factory reset the Satellite4. When the Satellite is up after factory reset, press the Sync button on the Satellite (while the Ethernet cable to the Router is connected) and then on the Router5. When the Satellite is added it should behave correctly.I'm currently away from home for a little while but will try this as soon as I get back.

ekhalil · Answer

How good is the wireless backhaul to the “bad satellite”? Can you please check this in the web GUI, under “Attached Devices “, do you see that satellite connected to the router over 2.4 or 5 GHz?
Does thing become better if the satellite is brought closer to the router?

Forum Discussion

Orbi RBR350 in AP mode - not always getting DHCP IP when roaming

10 Replies