NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

FloBer's avatar
FloBer
Aspirant
Mar 16, 2021

RAX80 nightmare

When Netgear is going to deliver a working and stable firmware for this top-end priced router ? 

 

A week ago I realised that all the ports forwarding rules I used to set and then deleted were still alive thus not showing in the web UI !

Meaning my NAS that I once temporarly setted up on to be reachable on port 80 weeks ago for testing purpose was still reachable from internet on this port even if the rules is long time gone in my UI !

What a f*cking shame is that ?! A basic security feature with flaws like this is unacceptable, this was with FW RAX80-V1.0.3.106_1.0.50 

 

Of course I resetted my router and set it again manualy only to get a router that drop the WAN connection several times a day. 

I downgraded the FW to RAX80-V1.0.3.88_1.0.41 and the WAN wass still dropping, so I dowgraded to RAX80-V1.0.2.76_1.0.35 with a full configuration again and now the connexion seams a little more stable but severals features are missing or not working like the logs not showing the ports forwarding or duplicated local IP.

What the heck ?

 

400$ is a price tag i can't understand for an expensive piece of garbage like this. 

Bye Netgear, it's over for me, if your 400$ products can't be reliable and safe to use I can't trust any of your products again, I'm ordering a new Asus router. 

2 Replies

  • > [...] my NAS that I once temporarly setted up on to be reachable on
    > port 80 weeks ago for testing purpose was still reachable from internet
    > on this port even if the rules is long time gone in my UI !

     

       Did you run that test from a system which was really in the outside
    world, or did you simply specify the router's WAN/Internet address from
    a system on your LAN?  NAT loopback can be misleading in such a case.

    • FloBer's avatar
      FloBer
      Aspirant

      From my phone by LTE, no WIFI, no loopback here. 
      I've realised the rules were still working by looking at the router logs.