NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Intermittent internet connectivity outage with Orbi?
I just installed my new Orbi router yesterday, replacing a Nighthawk R8500. I believe that overall wireless coverage has improved, though top-end performance is not quite as high (measured via fast.com). That's fine for me, and the only router feature I miss is being able to have separate 2.4Ghz vs. 5Ghz SSIDs (so I'm grudgingly switching to the new-fangled way of naming the two wireless networks the same),
I've upgraded the Orbi firmware to the latest available - V1.2.0.6. What's concerning is that my 2 Nest cameras (Dropcam Pros) have individually reported going offline today at 7:12am, 10:58am, 1:12pm. I didn't notice any internet outage myself today. Each time I receive the offline email I check and the camears are online again. I never received these before today while using my R8500 or older wireless routers, so it's not Nest/Dropcam.
I looked at the Orbi admin website Interrnet Port... Show Statistics and it shows WAN/LAN/WLAN up time for the entire day (i.e., no reset and up times > 14 hours). I also looked at Advanced... Administration... Logs during the offline times and other than spurious [DoS Attack: RST Scan] entries (that normally appear throughout the logs), nothing seems to indicate an outage.
Has anyone else notice camera outages? Thoughts on what this might be? I'm hoping that a firmware update will iron out these intermittent outages.
I read in the other "Ring Door Bell" thread that a customer had better results after disabling "Enable Implicit BEAMFORMING". So I tried that just to see what happens. It's probably too early to tell yet, but my 2 Nest cameras have only disconnected once in the past 2 days and I think that's because there was a power outage at my house today (I wasn't home and both cameras went out at the same time, something the intermittent outages haven't done).
245 Replies
- Thanks Mikey94025. I just unchecked that option and will keep an eye out for the next few days to see if it helped. Thanks for the suggestion.
My nest cam's continue to disconnect. I had to deactive the beamforming. Argh. Where's the fix, Netgear?!
Deactiving implicit beamforming shouldn't have any effect on newer ac devices which are supported with explicit beamforming. It sucks that we have to use a work around but it doesn't look to be that impactful to performance. But I totally agree this should have worked out of the box.
While I have been mostly happy with Orbi I intend to make to clear in my Amazon product review that Orbi does have issues.true but disabling implicit does effect the coverage and performance of those non ac devices that do support beamforming , disabling explicit makes no sense
So has ther been an official ticket logged with Netgear for this? Or any confirmation from Netgear that this is an issue they will be addressing?
I turned off the beamforming feature and so far I have not seen data drops, I do however see slower speeds (though that could be caused by anything) and not as good coverage.
I actually do not ever have a full signal anymore, no matter the distance fro mthe router or satellite. It is slightly frustrating that we can't use the system as intended and advertised.
Add me to the list as someone who has a new Orbi system and a Nest Cam, and had drops every few hours on the Nest Cam until I disabled the beamforming feature. 18 hours and no drops.
Netgear, you responded to some earlier messages. Can you provide an update?
Looks like I will be holding off on purchasing Orbi till I see this get fixed (hopefully). Netgear are we working on a fix yet?
- I ended up getting an eero for comparison testing as I was going crazy with satelite placement and not being sure if anything connected to satellite.
Glad I did because I have had zero issues with the eero setup. So I'm going to forget about the mu-mimo support and the triband theory for a mesh network that actually works. Netgear rushed the release of this product and that is simply unacceptable for a large company, this is more of a beta or alpha product that needs a lot more work to be ready.
There is also amplifi hd I want go try for comparison once it ships. But as of now the eero has a much wider range, much faster speeds, and a real app that goes with it. Sorry to say but Orbi is going back because it couldn't do the one thing I needed it to, provide reliable wifi.
nitrogen1 wrote:
I ended up getting an eero for comparison testing as I was going crazy with satelite placement and not being sure if anything connected to satellite.
Glad I did because I have had zero issues with the eero setup. So I'm going to forget about the mu-mimo support and the triband theory for a mesh network that actually works. Netgear rushed the release of this product and that is simply unacceptable for a large company, this is more of a beta or alpha product that needs a lot more work to be ready.
There is also amplifi hd I want go try for comparison once it ships. But as of now the eero has a much wider range, much faster speeds, and a real app that goes with it. Sorry to say but Orbi is going back because it couldn't do the one thing I needed it to, provide reliable wifi.you might want to look at the Cnet review of the orbi and specifically the wifi testing
https://www.cnet.com/products/netgear-orbi-wifi-system/review/2/
the orbi system is far better wifi wise when compared to the eero
the amplifi hd review below
http://www.digitaltrends.com/router-access-point-reviews/ubiquiti-amplifi-hd-review/
doesnt excite ether
- No parental controls or QoS
- No remote access or active USB port yet
No MU-MIMOand its mesh system flood smaller apartmentsand it overall only gets a 6 / 10 for its reviewthe only real upside to the amplifi hd is its 1300M wifi
- You can't really say that the orbi system is better when out of the box it simply didn't work. It drops data out of the box, it's ridiculous to have to scan the Internet to get your $400 router to work.
And I'm aware that is is the only one of those that has mu-mimo and beam forming ( that doesn't work) but most client devices don't have mu mimo support so it only works one way. And it really doesn't do me any good when the non mumimo devices have performed (at least thexpensive eero) much faster consistently. The orbi simply does not compare for me even with the extra features. I also feel the satelite for the orbi is very buggy. I was not able to get a full wifi signal being 2 feet away from it.
Can't always trust what you read online. Just because a spec sheet looks good doesn't mean the execution was good.
I'm not steering people away from it, but I did want to share my finding in a head to head comparison. Maybe in 15 firmware updates from now I'll take another look, but these new technologies in the orbi are simply not well executed. It might work in a easy to network home, but it doesn't solve the problem it promises to solve for difficult homes with dead spots. And as mentioned earlier, thus type of execution is not acceptable from a large company. Those are just my personal views and experiences.works here mate . have the best wifi i have ever had and the whole family is happy with it , it is a possibility you have a faulty unit
I have several nest cams that are constantly loosing connection with my Orbi. Once I disabled beam forming, I have not had a single disconnect. Netgear needs to address this pronto. Where is the next firmware update already.
I too have had random disconnects off the network, the laptop is hard wired to the router, the disconnects to appear for some reason late morning, and some times at night. May be other times, but just haven't noticed.
Just adding log lines, the time stamps appear to be 4 hours off, not sure where to fix that.
Not sure if the 'attacks' are causing issues.
[DoS Attack: ACK Scan] from source: 31.13.69.226, port 443, Friday, October 14, 2016 07:33:21
[DHCP IP: 192.168.1.12] to MAC address f8:f1:b6:d9:b2:ce, Friday, October 14, 2016 07:30:43
[DHCP IP: 192.168.1.10] to MAC address ac:3c:0b:38:44:07, Friday, October 14, 2016 07:30:28
[admin login] from source 192.168.1.112, Friday, October 14, 2016 07:23:36
[DoS Attack: ACK Scan] from source: 199.4.160.29, port 443, Friday, October 14, 2016 07:12:55
[DoS Attack: SYN/ACK Scan] from source: 206.190.57.61, port 443, Friday, October 14, 2016 07:12:45
[DoS Attack: ACK Scan] from source: 199.4.160.29, port 443, Friday, October 14, 2016 07:10:53
[DoS Attack: SYN/ACK Scan] from source: 92.222.85.168, port 80, Friday, October 14, 2016 06:49:30
[DoS Attack: ACK Scan] from source: 31.13.69.195, port 443, Friday, October 14, 2016 06:43:12
[DHCP IP: 192.168.1.112] to MAC address ec:f4:bb:1b:19:82, Friday, October 14, 2016 06:42:35
[DoS Attack: ACK Scan] from source: 31.13.69.195, port 443, Friday, October 14, 2016 06:41:57
[DHCP IP: 192.168.1.4] to MAC address a0:04:60:0e:a9:b4, Friday, October 14, 2016 06:11:21
[DHCP IP: 192.168.1.22] to MAC address 90:02:a9:69:d6:09, Friday, October 14, 2016 06:00:33
[DoS Attack: TCP/UDP Chargen] from source: 185.94.111.1, port 58473, Friday, October 14, 2016 05:56:28
dsc_dewain wrote:Just adding log lines, the time stamps appear to be 4 hours off, not sure where to fix that.
Not sure if the 'attacks' are causing issues.
[DoS Attack: ACK Scan] from source: 31.13.69.226, port 443, Friday, October 14, 2016 07:33:21
[DHCP IP: 192.168.1.12] to MAC address f8:f1:b6:d9:b2:ce, Friday, October 14, 2016 07:30:43
[DHCP IP: 192.168.1.10] to MAC address ac:3c:0b:38:44:07, Friday, October 14, 2016 07:30:28
[admin login] from source 192.168.1.112, Friday, October 14, 2016 07:23:36
[DoS Attack: ACK Scan] from source: 199.4.160.29, port 443, Friday, October 14, 2016 07:12:55
[DoS Attack: SYN/ACK Scan] from source: 206.190.57.61, port 443, Friday, October 14, 2016 07:12:45
[DoS Attack: ACK Scan] from source: 199.4.160.29, port 443, Friday, October 14, 2016 07:10:53
[DoS Attack: SYN/ACK Scan] from source: 92.222.85.168, port 80, Friday, October 14, 2016 06:49:30
[DoS Attack: ACK Scan] from source: 31.13.69.195, port 443, Friday, October 14, 2016 06:43:12
[DHCP IP: 192.168.1.112] to MAC address ec:f4:bb:1b:19:82, Friday, October 14, 2016 06:42:35
[DoS Attack: ACK Scan] from source: 31.13.69.195, port 443, Friday, October 14, 2016 06:41:57
[DHCP IP: 192.168.1.4] to MAC address a0:04:60:0e:a9:b4, Friday, October 14, 2016 06:11:21
[DHCP IP: 192.168.1.22] to MAC address 90:02:a9:69:d6:09, Friday, October 14, 2016 06:00:33
[DoS Attack: TCP/UDP Chargen] from source: 185.94.111.1, port 58473, Friday, October 14, 2016 05:56:28the dos attacks are more than likley dead torrents you have downloaded then closed , if there is lots it could swamp the nat table
Any update from Netgear regarding when Orbi will support the Indoor Nest Cam item model #NC1102ES with beamforming enabled? I have had to disable beamforming to prevent all of my Indeoor Nest Cam's from constantly disconnecting.
Can someone from Netgear please chime in on this thread?
- Has everybody opened a ticket with Netgear? I did and they asked me a couple of questions over email.
They followed up with a phone call. They said there will be a firmware update this month and they hope it will fix this issue.
Fingers crossed.I had a ticket open for the last three weeks I think. It ended with something to the effect of, "above tier 2 has analyzed it and hopes the next firmware release will help" and "turn off beamforming and tell us if that seems to make any difference" I turned off beamforming, but still have a ton of quick disconnects and reconnects. Overall, it still works very well, just not the most reliable for most devices. Big problem is one of those devices is the laptop my wife programs on and no matter where she uses it (same room as router, or same room as satellite), she gets the most noticeble disconnects and reconnects many times a day.
verdugan wrote:
Has everybody opened a ticket with Netgear? I did and they asked me a couple of questions over email.
They followed up with a phone call. They said there will be a firmware update this month and they hope it will fix this issue.
Fingers crossed.i think you find its early november b4 its released
- That sucks about your wife's laptop.
When I turned off beamforming, I haven't experienced disconnects in any other devices and my cameras are ok. - Wow, not just wireless issue, I'm hardwired and every day got disconnected.
> Wow, not just wireless issue, I'm hardwired and every day got disconnected.
Do you get router log entries indicating these disconnects? I haven't received any more dropcam disconnects (they get flagged) since disabling implicit beamforming, but maybe the dropcams don't alert if the disconnect is very brief. So I'd like to see if any of your specific log entries appear in my router log.
I don't see disconnects but this morning when I checked i did see an Internet Connection logged between 4 hour window I hadnt used it, and my work vpn was disconnected again. Work VPN has never been an issue with connectivity. Only since I installed this new router.
