psychopomp1
Senior Member
If ‘NETGEAR Guy’ is reading this, I hope you can get the NG firmware developers to sort these bugs out on your flagship router as the Netgear staff/mods are blatantly ignoring these on the official NG forums.
From stock firmware 1.0.2.40 onwards, the LEDs on the router don’t behave the way they’re supposed to in the cases below – doing factory resets and re-flashing firmware makes no difference at all so its clearly firmware bugs:
1) When switching off the 60ghz (802.11ad) radio , its LED goes off and then comes on again a few mins later – despite 60ghz radio still being off. It should stay off permanently once the radio is disabled…period.
2) When changing the LED state from flashing to solid, the LEDs do indeed stop flashing and stay lit solidly. But what happens after a while (could be hours/days/weeks), any one of the 2.4ghz and 5ghz radio LED goes off – despite the radio in question still working.
Others are also reporting these bugs, so its not just me. I’m also getting these bugs on a brand new X10.
Just to re-iterate, the above bugs were NOT occurring in firmware 1.0.2.32 or earlier so I’m sure the NG developers can easily fix these.
Cheers
psycho
From stock firmware 1.0.2.40 onwards, the LEDs on the router don’t behave the way they’re supposed to in the cases below – doing factory resets and re-flashing firmware makes no difference at all so its clearly firmware bugs:
1) When switching off the 60ghz (802.11ad) radio , its LED goes off and then comes on again a few mins later – despite 60ghz radio still being off. It should stay off permanently once the radio is disabled…period.
2) When changing the LED state from flashing to solid, the LEDs do indeed stop flashing and stay lit solidly. But what happens after a while (could be hours/days/weeks), any one of the 2.4ghz and 5ghz radio LED goes off – despite the radio in question still working.
Others are also reporting these bugs, so its not just me. I’m also getting these bugs on a brand new X10.
Just to re-iterate, the above bugs were NOT occurring in firmware 1.0.2.32 or earlier so I’m sure the NG developers can easily fix these.
Cheers
psycho
