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

Forum Discussion

Robion3090's avatar
Robion3090
Follower
Apr 17, 2021

Unable to Set Static ip, DHCP options, or anything in the web interface

To whom this may concern,

At this time I am continuing to use basic functionality of the device I have purchased. I would have assumed this device would have been competent enough for the higher pricepoint to accomidate DHCP options, Setting a Default LAN subnet customization or even having management features that functioned through the web UI.

Clearly I am mistaken, Is anyone else having these problems, and or have a solution or work around to better manage this device ? (AX80)

 

--- Edit  : After more research and digging through the logs, Along with discovering Telnet is responding on the WAN interface for whatever god unknowing reason. I am returning this product and avoiding all netgear devices like the black plauge in the future after dumping the debug.htm logs and discovering the chineese successfully authenticating to the device before I have even had a chance to set it up.

Netgear get your S*** together and test a product before you decide to sell it to people.

2 Replies

  • antinode's avatar
    antinode
    Guru
    Apr 17, 2021

    > Model: RAX80|Nighthawk AX8 8-Stream WiFi Router

     

       Firmware version?  Connected to what?

     

    > [...] Is anyone else having these problems, [...]

     

       What, exactly, are "these problems"?  "Unable" is not a useful
    problem description.  It does not say what you did.  It does not say
    what happened when you did it.  As usual, showing actual actions
    (commands) with their actual results (error messages, LED indicators,
    ...) can be more helpful than vague descriptions or interpretations.

     

       Which "DHCP options" would you like to control?  (Netgear firmware
    for its consumer-grade routers tends to offer very little in this
    neighborhood.)

     

    > [...] discovering Telnet is responding on the WAN interface [...]

     

       How, exactly, did you discover that?  If you're testing from a device
    on the router's LAN, using the router's WAN/Internet IP address, then
    NAT loopback could cause misleading results.


    > [...] after dumping the debug.htm logs and discovering [...]

     

       Thanks for including some actual evidence.

     

    > [...] I am returning this product [...]

     

       Perhaps there's no point, then, in providing a useful problem
    description.