Firmware Version 1.5.0.12 issues/fixes

---

anschmid wrote:

When I do a status update on Dynamic DNS I get this:

 

something.mynetgear.com updated successfully at 08:00 AM, 01/01/1970

 

Not sure what clowns are working at Netgear but this is a problem I dealt with 20 years ago when I studied computer science. You'd think by now people programming hardware would know how to probably pull a date from the system without using the default date when the first computer was created?

 

Amateurs at best but probable less than that!

---

I am pretty sure your router hasn't grabbed the Date/Time from the Netgear NTP server.  I have had that problem numerous times.  I have even had to Telnet into the router and set the date/time myself as I use the Block Services per Schedule.  Under Schedule you will see the current Date/Time of the router.  I wish Netgear would allow us to change the NTP server.

WOW, you are right. I missed that.

What a joke NETGEAR! Do you have any idea the problems this will create? Everything today requires a properly working DNS.

I am done. I have spent months trying to justify what should and could be a great product, but Netgear seems destined to make thier Orbi so STUPID that it should only be sold to poeple who have no idea, and no needs, of how I network should work.

1. They are forcing WPS - Major secirity concern.

2. No ehternet backhaul.

3. No method of stearing clients to specific satelites and/or router (I am sittng 10 feet from my Orbi rotuer, but its connecting to my Satelite 25 feet way and through a wall. My link speedis less than 100Mbps)

4. No method t change you IP in AP mode, must switch back to Router Mode to make any changes to IP.

5. No realtime client connect info to see what clients are doing, and no backhaul WIFI details to see the quality of that backhaul connection. You only get a list of clients and what radio they are connected to.

6. The Orbi app is USELESS. Who cares if it looks pretty. When I use ot to see connected clients I get ZERO.

7. And now this AP Guest Mode joke. Changing clients dns suffix....Are you kidding?

8. And no method to seperate the 2.4 and 5G SSIDs. I had to switch to debug mode to and sarch the itnrnet to find the command. Which will be undone if I make any change to the Orbi settings....Yes, I wnat control of what clients connect to what radio, and preferable which Orbi device.

The FACT every other OEM provides all fo the above abilty (if not half of it) is a major blow to Netgears arguement, "Customers dont want this stuff, they want easy". Yes, and customers also want an easy car to drive, so I guess that means bluetooth, HUD, manual shifting, BMW iDrive, Touchscreen, etc should be removed....it's too complicated...

Netgear, I understand you want simple for very low-tech customers who only know how to plugin to the power outlet. But this is INSANE.

I will give this Orbi one more firmware update. But if this is thier dirrection, well, I guess someone will buy my Orbi at a discount.

Thank God I still have my ASUS. Looks like I may be turing it back on.

---

anschmid wrote:

When I do a status update on Dynamic DNS I get this:

 

something.mynetgear.com updated successfully at 08:00 AM, 01/01/1970

 

Not sure what clowns are working at Netgear but this is a problem I dealt with 20 years ago when I studied computer science. You'd think by now people programming hardware would know how to probably pull a date from the system without using the default date when the first computer was created?

 

Amateurs at best but probable less than that!

---

I have to correct myself on this one. I checked this again today and now the status is working and is showing a correct time:

something.mynetgear.com updated successfully at 12:48 AM, 02/28/2017

All I can think of is that the router might have not gotten a time refresh after I did the udpate since checking Dynamic DNS working was one of the first things I checked after the update as I was waiting for it desperately! But router was up and I was using the web interface obviously!

Thanks Netgear folks, not that bad after all!