NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Many ISPs have begun blocking outbound UDP connections on port 123, the common port used for NTP (network time synching). Because of this, the Orbi router (and other Netgear routers) have crippled functionality related to scheduling and OpenVPN - they simply can't get an accurate time synch after rebooting.
There is a trivial fix though: simply use a port other than 123. This would literally be one line of code change in a firmware update. Making this change will allow the Orbi to again function correctly.
In summary:
Changes desired:
- Sync time via a port other than 123.
Broken functionality, until fixed:
- Scheduling access and blocking services
- Wifi power on/off on schedule
- OpenVPN server (cannot connect if timestamp disagrees between client/server).
Thanks for your consideration.
4 Comments
I think the orbi could do with perhaps the ability to choose what ntp server you wish to connect to as well as port.
What ISPs are these? This would break functionality on almost any embedded device.
An alternative would be to run your own NTP service.
- I know of AT&T blocking for certain. Googling "port 123 blocked" leads to many results of various ISPs doing the same. I believe Comcast will be doing the same shortly as well.
It has become more common after recent DDoS attacks utilizing port 123 as a vector.
I've had to set up another router as an NTP server solely for the purpose of making my Or I function semi-correctly in AP mode. It's able to grab the correct time, but even the timezones don't appear to function correctly in the latest firmware. - I'm in Australia and my ISP is mate communicate (which I think resells M2). Previously I had another router (Fritzbox 7490) connected and it's time server functioned perfectly. I wish Netgear would take a leaf out of Fritzbox and provide the same level of functionality, especially in Advanced mode. I think that is absurd that the Orbi router provides a function that seems to not work for all. I had placed a call with support who told me reverse the firmware back to v1.5.0.12. This lead to me bricking the "bricking" the router and I had have it replaced (and 5 days without internet!!!). I then tried to check the time server on the firmware the device came with (1.3.0.26) then upgraded it to v1.5.0.12 and checked, then upgraded it to the latest, v1.8.0.6 and experienced the same problem each time, i.e . time wont sync. This really should be an easy fix by allowing the router admin to choose an ntp server pool and port.
