- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Orbi Firmware 2.3.1.60
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
@thombe wrote:
on rbk50 - in AP mode
here is my latest log..
[WLAN access rejected: incorrect security] from MAC address 20:39:56:59:8f:ee, Wednesday, May 15, 2019 21:51:12
[WLAN access rejected: incorrect security] from MAC address 04:f1:28:2f:b0:6a, Wednesday, May 15, 2019 20:16:46
[UPnP set event: del_nat_rule] from source 192.168.1.188, Wednesday, May 15, 2019 16:30:59
[UPnP set event: add_nat_rule] from source 192.168.1.188, Wednesday, May 15, 2019 16:29:48
@thombe, do you know if that MAC address belongs to your Satellite? If yes, then you'll need to generate a new backhaul password to avoid WiFi instability. Also, please disable UPnP as it's a security risk. Since your Orbi is in AP mode, there shouldn't be any NAT rule either. If everything is working properly, there shouldn't be anything in your log when your Orbi is in AP mode, except for local admin login/NTP time sync info.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
@FURRYe38 wrote:
You don't have to update. The updates are just there and available for you. You have to make the update happen. NG no longer forces auto FW updates.
What will invariably happen is the security fixes card will get played and will essentially force the end user to apply the update. And until the update process is improved, the risk of having to perform a factory reset is high.
The main value of the policy change is to give the end user choice of when to apply the update. And it is appreciated.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
@SW_ wrote:
@thombe wrote:
on rbk50 - in AP mode
here is my latest log..
[WLAN access rejected: incorrect security] from MAC address 20:39:56:59:8f:ee, Wednesday, May 15, 2019 21:51:12
[WLAN access rejected: incorrect security] from MAC address 04:f1:28:2f:b0:6a, Wednesday, May 15, 2019 20:16:46
[UPnP set event: del_nat_rule] from source 192.168.1.188, Wednesday, May 15, 2019 16:30:59
[UPnP set event: add_nat_rule] from source 192.168.1.188, Wednesday, May 15, 2019 16:29:48
@thombe, do you know if that MAC address belongs to your Satellite? If yes, then you'll need to generate a new backhaul password to avoid WiFi instability. Also, please disable UPnP as it's a security risk. Since your Orbi is in AP mode, there shouldn't be any NAT rule either. If everything is working properly, there shouldn't be anything in your log when your Orbi is in AP mode, except for local admin login/NTP time sync info.
Hi, no it's not, both those rejected mac addresses are both Nokia android phones.
in addition the .188 up address that is upnping is one of those androids, so not sure what is causing that, but will look further, as i don't want any upnp on my setup.
Can I ask, about NG no longer forcing updates, is this from this firmware onwards, or is this from the server push. i.e. if i choose to run a specific earlier firmware will it remain on that firmware, e.g. .210. ??
i shall also be taking a look at netspot later.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
I believe it came in on v32 or v44. Not sure if you downgraded to v210 if it would auto update or not.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
@thombe wrote:
in addition the .188 up address that is upnping is one of those androids, so not sure what is causing that, but will look further, as i don't want any upnp on my setup.i shall also be taking a look at netspot l
@thombe, UPnP can flood your WiFi network with its broadcast traffic about its UPnP services every 30mins to all UPnP clients. UPnP is not applicable to AP mode and it should be the first thing to disable.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
@thombe wrote:... if i choose to run a specific earlier firmware will it remain on that firmware, e.g. .210. ??
If you want to stay with v210, you could try Disable Orbi Auto Firmware Update.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
I believe uPnP is disabled on the Orbi when in AP mode...?
@SW_ wrote:
@thombe wrote:
in addition the .188 up address that is upnping is one of those androids, so not sure what is causing that, but will look further, as i don't want any upnp on my setup.i shall also be taking a look at netspot l
@thombe, UPnP can flood your WiFi network with its broadcast traffic about its UPnP services every 30mins to all UPnP clients. UPnP is not applicable to AP mode and it should be the first thing to disable.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
@gr8sho wrote:
Why would I want UPnP on at all?
It's one of those fancy features that try to simplify home network management via auto-discovery and IoT automation. Because of that trust between devices, hacker can take over and control all those devices discovered via UPnP, which is the main reason why it's a major security risk. The risk outweigh the benefit. To be safe, it's best to disable UPnP even if you think you want it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
This firmware is no different than the previous one .48
Half of my Nest protects and a couple of my Nest Outdoor Cams cannot connect to the wifi. And all of my TP-Link smart plugs cannot connect.
I'm reverting back to .44 again
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
@jodax wrote:
Half of my Nest protects and a couple of my Nest Outdoor Cams cannot connect to the wifi. And all of my TP-Link smart plugs cannot connect.
This could happen if Orbi WiFi network is influx due to frequent/random reboots. Before reverting, might want to give network cold boot a shot. For example, shutdown all Orbi/Satellites for 15mins, then bring them back online one by one, starting with Orbi, then followed by each Satellite. If you've already done that, please ignore.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
I don't have NEST protect or cams howver have two NEST thermostat controllers. I have had no issues connecting them to a Orbi RBK50 system.
I run manual channels 1 or 11 on 2.4Ghz, WPA2 and AES only. Beamforming and uPnP is enabled. 20/40Mhz is set for 40Mhz only. Daisy Chain and Fast roaming are disabled.
@jodax wrote:
This firmware is no different than the previous one .48
Half of my Nest protects and a couple of my Nest Outdoor Cams cannot connect to the wifi. And all of my TP-Link smart plugs cannot connect.
I'm reverting back to .44 again
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
Possible those devices that can not connect may have problems themselves.
Try turning OFF ALL devices that can connect. Then try to connect the others that can't and see. Also placement and distance from RBR or RBS is key.
You can temporarily disable the 5Ghz SSID from broadcasting while you set up 2.4Ghz only devices with Orbi. Under Advanced Tab/Advanced Settings/Wireless Settings
@jodax wrote:
I also have a nest thermostat and somehow that is not affected too, just a couple of the nest cam (the nest doorbell is also unaffected), 3 out of 6 nest protects, and 3 tp-link plugs cannot connect. But the rest of my devices have no issues.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
Just reverted to .44, everything is working fine again. No additional actions needed. So, no, I don't accept the idea that the devices themselves have issues when the changes that triggered the problem was the firmware (and reverting fixes it)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
Would have to factory reset the system after loading v60 and setup from scratch to confirm that v60 is working or not for your devices.
For now, go with what works. Enjoy.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
@FURRYe38 is probably right on that you might benefit from a reset in this case. Given both v48 and v60 had shown similar problem with your network devices, it could be a result of improperly initialized variables/configurations that are required by the newer firmwares. A factory reset might be in order in this case. With that said, if you're happy with v44, there's no reason to upgrade.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
@SW_ wrote:
It's one of those fancy features that try to simplify home network management via auto-discovery and IoT automation. Because of that trust between devices, hacker can take over and control all those devices discovered via UPnP, which is the main reason why it's a major security risk. The risk outweigh the benefit. To be safe, it's best to disable UPnP even if you think you want it.
DNK. I didn't like the potential performance hit and it seems it could interfere with IGMP transmission. Just conjecture on my part. During the process of disabling it, Wi-Fi became unstable temporarily. I'm hoping some of the glitches I'm seeing controlling one of my STBs settles down. In particular the DVR controls.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
@jodax wrote:
This firmware is no different than the previous one .48
Half of my Nest protects and a couple of my Nest Outdoor Cams cannot connect to the wifi. And all of my TP-Link smart plugs cannot connect.
I have several smarthome devices including tplink smartplug, Amazon cloudcam, blink xt, all of which run off 2.4 band. It all hangs together. I've gone through the factory reset ritual as is often prescribed.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
so I need some help I think.
I looked at this mornings log files and I'm getting loads of upnp, which might well explain why my system is pretty unstable..
however I use the orbi in ap mode, so can't enable or disable upnp, I'm not sure where to look now.
see below..
[UPnP set event: del_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 20:25:30
[UPnP set event: del_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 20:24:06
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 20:24:02
[UPnP set event: add_nat_rule] from source 192.168.1.79, Tuesday, May 21, 2019 20:23:59
[UPnP set event: add_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 20:23:56
[UPnP set event: del_nat_rule] from source 192.168.1.79, Tuesday, May 21, 2019 20:23:33
[UPnP set event: del_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 20:23:15
[UPnP set event: add_nat_rule] from source 192.168.1.79, Tuesday, May 21, 2019 20:23:12
[UPnP set event: add_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 20:23:11
[UPnP set event: del_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 20:01:58
[UPnP set event: add_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 20:01:01
[UPnP set event: del_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 19:18:31
[UPnP set event: add_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 19:17:31
[UPnP set event: del_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 19:16:50
[UPnP set event: add_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 19:15:25
[UPnP set event: del_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 19:08:24
[UPnP set event: add_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 19:04:28
[UPnP set event: del_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:59:46
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:52:41
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:52:35
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:52:07
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:52:03
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:52:00
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:51:43
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:51:02
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:50:58
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:50:49
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:50:42
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:50:16
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:50:13
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:48:25
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:48:21
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:47:15
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:47:11
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:46:57
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:46:53
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:46:30
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:46:24
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:45:45
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:45:41
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:42:50
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:42:46
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:42:20
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:42:16
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:41:51
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:41:44
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:40:28
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:40:25
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:40:07
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:39:41
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:39:23
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:39:12
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:38:40
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:38:33
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:38:28
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:38:22
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:38:13
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:37:49
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:37:31
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:37:11
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:37:07
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:36:54
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:36:19
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:36:12
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:36:08
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:36:04
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:34:42
[UPnP set event: del_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:12:52
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:12:15
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:12:11
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:11:43
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:11:39
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:10:01
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:09:58
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:09:46
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:09:42
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:08:36
[UPnP set event: add_nat_rule] from source 10.208.22.216, Tuesday, May 21, 2019 18:08:28
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 18:07:37
[UPnP set event: del_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 17:08:25
[UPnP set event: add_nat_rule] from source 192.168.1.102, Tuesday, May 21, 2019 17:07:59
[UPnP set event: del_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 16:20:53
[UPnP set event: add_nat_rule] from source 192.168.1.188, Tuesday, May 21, 2019 16:07:35
[UPnP set event: del_nat_rule] from source 192.168.1.76, Tuesday, May 21, 2019 14:23:24
[UPnP set event: add_nat_rule] from source 192.168.1.76, Tuesday, May 21, 2019 14:23:12
[Time synchronized with NTP server] Tuesday, May 21, 2019 11:31:38
[email sent to: 8mundania@gmail.com] Tuesday, May 21, 2019 09:00:03
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
What are these devices seen at these IP addresses?
What is the IP address pool size of on the RBR? default?
If the AP mode, the Orbi shouldn't be logging any UPnP events for devices. That should be done on your host router.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
Why does Sattalite show me the exact same attached devices list as main unit? anyone else experiencing this issue? It was not like this before taking 60 Firmware. I have done multiple factory resets with nvram wipe on both main and satellite and multiple reboots and manually input all info. absolutely nothing else has changed in my setup or environment other than taking 60 Firmware and additionaly sattalite shows as 5g which is incorrect as it is wired. Reverted to previous Firmware and none of the above mentioned issues encountered so what has changed in 60 to cause these issues? Using AP mode. Have wasted hours!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Orbi Firmware 2.3.1.60
Daisy chain disabled?
What is the Mfr and model# of the ethernet switch if one is in the configuration.
@JMU1998 wrote:Why does Sattalite show me the exact same attached devices list as main unit? anyone else experiencing this issue? It was not like this before taking 60 Firmware. I have done multiple factory resets with nvram wipe on both main and satellite and multiple reboots and manually input all info. absolutely nothing else has changed in my setup or environment other than taking 60 Firmware and additionaly sattalite shows as 5g which is incorrect as it is wired. Reverted to previous Firmware and none of the above mentioned issues encountered so what has changed in 60 to cause these issues? Using AP mode. Have wasted hours!
• Introducing NETGEAR WiFi 7 Orbi 770 Series and Nighthawk RS300
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more