I have the BR500 VPN Router, connected to the outside world through a Motorola MB8611. Wireless networking is provided by Netgear WAC devices situated throughout the house. All the WAC devices are wired (Ethernet) to the router, some via switches and some direct. All has worked well and still basically is. Problem is that the BR500 is at end of life and no longer supported. Although it has never been completely essential for me to do so, I have used Insight to manage all my devices.
As of yesterday, looking at the network through my Insight app, the BR500 is shown as disconnected, and if I log directly onto the router from my PC on the same internal network, it also has a banner that says "Access to cloud is not available." I guess that message is consistent with the lack of ability to see the router via Insight. My home network seems to be otherwise working, but I cannot get the BR500 to show as connected in Insight. I have rebooted the modem, followed by rebooting the router, but to no avail.
I'm guessing the Netgear is basically phasing out the BR500 and this symptom is just the first of many that I will experience.
Since Netgear doesn't seem to have a replacement for the BR500, and seems to only push the Orbi systems for home use, I'm kinda inclined to go elsewhere like Ubiquiti.
I received the attached email from Netgear ... But, the BR500 Firmware V5.10.0.6 isn't available on the support page (only V5.10.0.5). AND, there's no way to upgrade the BR500 through Insight because it has been disconnected because of the expired SSL certs.
I assume that since Insight won't work with the BR200 router going forward without the updated firmware, we must have the firmware to get the BR200 connected back to Insight ... and this MUST be done direct on the BR200 UI (not through insight).
When can we expect to see the updated Firmware loaded to the support page above?
The following firmware is available to upgrade your device:
Firmware Details:
Model BR200
Firmware Version: 5.10.0.6
Release notes:
Insight Managed Business Router BR200 Firmware Version 5.10.0.6
Bug Fix
This firmware addresses the following bug:
Fixes the issue where SSL certificate for cloud connection has expired. Please follow the local GUI firmware update instructions to update to this firmware.
Known Issues
This firmware contains the following known issues:
The BR200 UI cannot be reached through VPN, through a static route from a different subnet, or by LAN users from a VLAN other than the default management LAN (VLAN 1). Workaround: Access the local browser UI from the BR200 default management LAN.
NAT loopback does not work in this release. NAT loopback is useful for accessing internal resources by public domain name. Workarounds: Use one of these workarounds:
o Change device hosts file to map public domain name to local IP when working on the same subnet as a public server.
o Use a separate DNS server that can handle accessing public resources from an internal network.
o Downgrade to a previous released firmware with NAT loopback support.
IPsec issues
o Different IPsec policies (Rules) have to use the same Pre-Shared Key (PSK).
o When applying the Disable, Enable, and Add IPsec policy features to a new routing table and firewall rules, an established IPsec connection briefly disconnects.
Workaround: Change the IPsec policy only when a brief disconnect is acceptable.
o NAT-T cannot be disabled with IPsec IKEv1.
o Wrong subnet is displayed in the IPsec VPN log.
o Some supported IPsec policies (Rules) are not available in the local browser UI.
Workaround: Use Insight to choose from all supported policies.
OpenVPN is missing the remote-cert-tls server in the client.opvn export.
Workaround: If “No server certificate verification method has been enabled' error is shown in the Open VPN client status window, add a new line at the end of the client.ovpn configuration file with this text:
remote-cert-tls server
DHCP server max client limited to 254 addresses.
DHCP reservation for non-default subnet may be lost after power cycle.
IPv6 passthrough doesn't work.
Unable to change name in IP/MAC Reservations or on Insight Cloud Portal.
After the firmware update, GUI access through the Firefox browser is slow. The root cause of this issue is that Firefox does not update the certificate properly.
After updating to the latest firmware, make sure to update to the latest version of the NETGEAR Insight app for the best functionality and user experience.
Sincerely,
The NETGEAR Insight Team
Do not reply to this message. This message is automatically generated.
You are receiving this e-mail because of your notification settings in NETGEAR Insight. To manage your Insight notification settings, visit How do I view and manage Insight notifications?
After trying to upload the new 5.10.0.6 firmware using browsers Brave and Firefox, I successfully updated it using Edge.
Now I am having a problem with the router showing "CPU Occupancy Rate is high. Check the Router." The CPU usage is 57.36%. I will reboot it to see if it settles down.
After reboot, CPU usage is back down to 14.8%. Maybe all is well again. Yes, now cloud access and Insight Management app recognizes it as alive. yeah! Thank.
I upgraded to the latest FW and while that resolved my insight connection, it broke my ipsec setup between two BR200 routers. The ipsec makes a connection but I can no longer map drives via their local subnet. I can ping the other subnets ip addresses, but cant access, map, or connect to network shares on the other subnet.
This use to work with the 5.0.7.10.4 fw. If I downgrade, again, I will lose insight connection!
Are you setting IPsec tunnel through Insight, or GUI? The new firmware should not change IPsec settings, would you please open support ticket with NETGEAR support and enable SDM for both sites, so that we can debug why working IPsec broken after firmware update. Thanks.
Setting IPsec in GUI. IPsec connects green on both ends and log shows connection. The issue is with fw newer than 5.07.10.4. I have tried each as they are released. While the routers connect they don't allow lan access to each subnet. Downgraded fw and I can browse subnets with no issues. This is a known Netgear issue, I was hoping this release fixed it but once again Netgear let me down!
