NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR750 Shows Offline After FW Update
I just updated the FW on my RBR750, and now I am unable to access the orbi via the app, or by IP (192.168.5.1). I have deleted and re-installed and logged back into the app, still unable to conne...
- NG must have pushed the update to me. I can now access everything via the browser. App just spins when I put in the password in and I assume times out, but I may need to delete and reinstall. But that will be a tomorrow project.
Just excited that I got a win!
Ports are not blocked by NG or by any NG services. If ports are blocked, users would be doing this and it's up to them to un-block these ports if they are purposefully blocking them. Otherwise, users can manually update FW as well which some of us did before this event happened and didn't have system wide problems when the event first started.
Tnknights wrote:
If all the ports are blocked, how can they push an update? To me, it is scary that if they can push something with all ports blocked, what kind of back door do they have?
A simple port scan showed all ports to the router was blocked. After the fix, ports 80 and 443 are open. A more intense scan show more ports open.
There is no logic behind the statement saying that if ports were blocked, users did it. Why would everyone do it that had issues? Why would I have done that in the middle of the night, at the same time the update happened? It makes complete sense that the update blocked the ports with a bad setting. They should’ve included a failsafe like we do in the enterprise world.
There is no logic behind the statement saying that if ports were blocked, users did it. Why would everyone do it that had issues? Why would I have done that in the middle of the night, at the same time the update happened? It makes complete sense that the update blocked the ports with a bad setting. They should’ve included a failsafe like we do in the enterprise world.
Tnknights wrote:
A simple port scan showed all ports to the router was blocked. After the fix, ports 80 and 443 are open. A more intense scan show more ports open.This illustrates how terminology affects discussions. Ports being blocked and ports being open are two different concepts.
In general, the term "blocked" means that the router has prevented data from passing through the router. Netgear routers do not block attempts to reach other devices unless the user has deliberately created blocks using the Security "Block Services" menu.
Ports are described as being open, closed, or stealth depending on how the router treats a connection attempt to itself.
- open generally means that the router accepts a connection attempt to the router.
- closed means that the router actively rejects the connection attempt by sending back a rejection message.
- stealth means that the router does not respond at all to a connection attempt.
There is an excellent discussion of these descriptions at Gibson Research: https://www.grc.com/su/portstatusinfo.htm
You are entirely correct that the router is supposed to accept connections on a number of ports:
- Port 53 because it is a DNS server
- Port 80 for the unsecured web interface
- Port 443 for the secured version of the web interface (with that damn self-signed SSL Certificate)
- Port 631, the Internet Printing Protocol - which "beats me" because I do not think printers can be attached to Orbi routers.
- Port 20005, which has something to do with German Telecom.
The problem that caused so much discussion on the forum is that Netgear's firmware update made the router stop accepting connections on ports 80 and 443.
- I had no idea whether the ports were blocked or closed as the router did not respond to any query on the port. I used blocked as I didn’t do any troubleshooting. As soon as I saw 80 and 443 not respond, I stopped. I had other things to do! LOL!
