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...
cheshbr wrote:
No, I can’t run my Orbis in router mode because I have a basic DSL service requiring a modem, and mine, a Billion 7800VDOX modem/router, handles the routing. I mearly disabled WiFi, hooked up the Orbis in AP mode and experienced a great outcome first time (although the wired backhaul fought me at first). I bought Netgear Orbi for its mesh and coverage functions, and when I do get some new high speed broadband (yes folks, we here in Australia are being dragged kickin’ and screamin’ into the 21st century with new fibre infrustructure to be made available across the nation by 2020) I may try the Orbis in router mode as I won’t need the Billion. I could still use the Billion as a router only, but it’s a bit dated, and I too like the sound of the Ubiquiti Edgerouter X. I’d love hear about your experience with it. Good luck.
Wanted to follow up. As I indicated earlier, I have a lot of devices and 4 kids thrashing the wireless. I experienced a lot of issues first with the satellite (devices were attaching but no active internet connection). Unplugging the satellite (wireless backhaul) and plugging back in or resetting the entire system was the only way I could achieve stability (which I don't really call stable). I RMA'd the satellite to no avail (still had the same issues with the new one). The longest I was able to run the system continuously was around 6 days before having to go through the unplug or reset. I also experienced the same issue with the main router at least 2 times (my son told me he unplugged and plugged back in to remediate).
I purchased the EdgerouterX, setup was fairly simple using the built in wizards. I won't know for a few more days, whether or not this has remediated the situation. I'm hopeful that it does and will report back in a few more days. If it does, I would think that perhaps the routing on these units is suspect and that perhaps less use (or light use), of the system doesn't manifest itself with all users (ie. some users experience these issues, and some do not).
More to follow.
So essentially Netgear Engineering has given up? Everything is resolved ? No Beta Firmware coming to test? Is this the finalized finished product we paid $400+ for?
- That's how i interpret it. No one from the company has chimed in here at all.
NG doesn't post when FW updates are forthcoming, nor when beta's are available. During the life span of the Orbi, FW update would be made available at NGs descression. Users will have to be patient for FW updates to be released and don't assume anything.
JMU1998 wrote:
So essentially Netgear Engineering has given up? Everything is resolved ? No Beta Firmware coming to test? Is this the finalized finished product we paid $400+ for?
- Point being nobody from ng has chimed in about anything for weeks. Like they are doa
- Netgear has seemed less and less involved in this community forum over time. They aren't really obligated and don't probably want to get into the minutae, after all it's a community forum.
All I know is that there is still betas going on with Orbis and netgear is planning on releasing even more new model of said Orbis. Whether we are going to see a v2 and a branch in firmware because of the hardware change, it's anybody's guess from the outside looking in.
For those of us who have used Netgear products forever, it's gotta be pushing close to 18 years for me, are used to v2 hardware that had same cases but tweaks under the hood. Maybe they are more reluctant to do that these days and prefer to launch a new model.
I'm fortunate that I haven't had that many problems, never master reset outside of a beta, have participated in numerous betas, and have been using my launch RBR50 as a router for almost two years. I wasn't involved in the beta for the initial product though, but did get a RBK50 set as soon as they were available. So with v2 hardware it will be same story new day...
To JMU1998, post 598, you have submitted a sentence that makes no sense in a public forum.
It makes sense to me with v2 hardware probably a different Firmware will be released which we will Beta test for NG for a year again?
To JMU1998, I still have no idea what you are on about. You say “it makes sense to me with V2 hardware”. What are you talking about? Forums are platforms for people with common interests to exchange ideas and tips and tricks, and share solutions, not meaningless, overly brief cryptic comments. And for clarity, punctuation is useful, too.
I apologize for my cryptic words and poor punctuation any other complaints?
What I am really frustrated about after a year is several issues remain unresolved. I have learned to live with them now mostly by using Orbi in AP mode. However, the issue of not being able to get the sattalite show up in the list other than as attached to main unit, is very bothersome. I have tried factory resets, nvram wipe no matter what I try. I do not have managed switches in my setup either.
No, JMU1998, no other complaints. Now back to Netgear Orbi, and the issues you are raising. Please elaborate
- What he said made sense to me. He was saying that when the next version of orbi is released we will still be beta testing it for them for $400 . I tend to agree with that statement. I had a Netgear wndr3700 v4 and it worked great. I can't believe this is the same company that made they great router because it's night and day difference
I too run my Orbis in AP mode, and I don’t have the issues you describe. I have mentioned before a beaut app called “Net Analyzer” that maps SSIDs when you roam between Orbi devices, lists all devices attached to the Orbi network (but not differentiating between router and satellite), and best of all, a direct route to the Orbi router and satellite web interfaces (open menu option LAN, then scan, and look for the small white “W” in a light blue box. Touch that, and the next screen shows “Web Interface Yes” with a green dot).
If you try this and still no success, try this. Download the firmware for 2.1.4.16 separately for each Orbi, and manually install the FW, Satellite first. Then power cycle them and see what happens.
Also, as you are in AP mode, how good is your primary router? Is it set up optimally, and have you configured DHCP? I have always reserved IP addresses in my primary router which are passed on to the Orbis, making device identification easier.
- Thats new products but not current orbi firmware.
