NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi firmware update v2.1.4.16 availability
We’ve been monitoring issues that some customers have experienced in OrbiOS 2.1.4. In response, we’re releasing firmware that provides a permanent fix for the homekit issue along with various other f...
I’m viewing this debate about the pros and cons of v2.1.4.16 in disbelief. How is it that I and others report that they have v2.1.4.16 working just fine, and there are probably hundreds of satisfied Orbi users who don’t need to engage in forum activity. This means those of you having difficulty are in the minority, so if you are in this category you have to try harder to get it working, and not throw in the towel.
Here’s a thought. If I can get my v2.1.4.16 Orbi RBK50 working with wired backhaul in AP mode, so can you unless your units are faulty (I have never tried Orbi in router mode) or your environment is not conducive to a mesh network.
So on the assumption that the Orbis work, the reason that you can’t get yours to work may rest with other factors in your environment.
I have always used reserved IP addresses in my internet gateway modem/router’s DHCP table. If you do this with all your household devices you want on WiFi, you will have a table that lists them and their fixed IP address. This will be passed on to the Orbi router in AP mode.
I have no evidence that doing this guarantees success, but I do it and it works so I wonder if contributes to the simplicity of AP mode.
It is stated in Orbi documentation that location is important. In that regard, here’s a tip for how to set up AP mode. Before anything else, disable WiFi on the internet gateway modem/router. Now back to the Orbis. On fist install, or after a reset, locate your router and your satellite side by side with no cable at this point on the satellite. Run through the initial setup wizard. Once the basic setup works, install previously downloaded FW v2.1.4.16 manually, satellite first. Then put it in AP mode and configure it. AP mode doesn’t give you lots of features so this can be quick.
This should give you a working Orbi environment. If so, then move the satellite to the desired location.
Lots of walls and obstacles will diminish a WiFi signal and metal objects may cancel It.
If the initial setup worked when the Orbis were together, then the location might be the reason if it no longer works satisfactorily.
If if after this you are still having difficulties, it may be the internet gateway modem/router that’s the problem
I have an AT&T Gateway with the orbi running in AP mode. I have an R6400 that was replaced by the Orbi. Since the Orbi is unable to operate in Router mode (still dont understand how that happens), is it overkill to connect the R6400 to the AT&T Gtaeway with all of the wireless radios cut off on the gateway and then connect Orbi to the R6400? (I'm assuming that's the proper way to set that up)?
Kev77 wrote:
I have an AT&T Gateway with the orbi running in AP mode. I have an R6400 that was replaced by the Orbi. Since the Orbi is unable to operate in Router mode (still dont understand how that happens), is it overkill to connect the R6400 to the AT&T Gtaeway with all of the wireless radios cut off on the gateway and then connect Orbi to the R6400? (I'm assuming that's the proper way to set that up)?
You'll have to be able put the AT&T gateway into "bridge" mode...so that it acts just as a cable/fiber modem. Assuming that you can do that, I'm not sure what firmware's available for the R6400...if you can get decent firmware for the R6400, then I'd give it a shot. But the for the R6400, the firmware needs to be live (currently supported) or you're setting yourself up for problems. On the other hand, if you're happy the way that it is now, that the AT&T gateway has a decent, currently supported router portion that gives you the routing functions that you need, then I'd stay with that.
I see that there is dd-wrt firmware for the R6400, so if you're up for that, you might give it a shot *smile*.
RogerSC wrote:
Kev77 wrote:
I have an AT&T Gateway with the orbi running in AP mode. I have an R6400 that was replaced by the Orbi. Since the Orbi is unable to operate in Router mode (still dont understand how that happens), is it overkill to connect the R6400 to the AT&T Gtaeway with all of the wireless radios cut off on the gateway and then connect Orbi to the R6400? (I'm assuming that's the proper way to set that up)?
You'll have to be able put the AT&T gateway into "bridge" mode...so that it acts just as a cable/fiber modem. Assuming that you can do that, I'm not sure what firmware's available for the R6400...if you can get decent firmware for the R6400, then I'd give it a shot. But the for the R6400, the firmware needs to be live (currently supported) or you're setting yourself up for problems. On the other hand, if you're happy the way that it is now, that the AT&T gateway has a decent, currently supported router portion that gives you the routing functions that you need, then I'd stay wtih that.
i have ro use DMZ to connect the gateway to the r6400. Main problem with the Orbi of course, constantly dropping the signal in router mode. This would at least give me customization and parental controls, which I can't do with the Gateway
My comments must be preceded by the disclosure that I am in Australia and don’t know what a AT&T Gateway is, nor have I had any experience with the Netgear R6400. Just Netgear Orbi.
So if you have connected the Orbis to the gateway in AP mode, and provided you have access to the internet, then the gateway is handling the routing, NAT, DHCP, firewall and security, isn’t it? If so then you don’t need to use the R6400. Does everything work in this setup? You don’t say.
Perhaps the reason you can’t get the Orbis to work in router mode is because it’s reacting to the AT&T Gateway also in router mode? If that’s the case then one of the two devices has to be in bridge mode to give the other the duties of the necessary router functions
