NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WAX610 - blank admin page
Hi all, Does anyone have any experience with a WAX610? It's my first Netgear WiFi product so I'm not sure if this is how they are meant to work or not. I added the MAC to my DHCP server and boo...
Malvineous wrote:
But if I access it via its FQDN (as in http://hostname.mydomain.example) then the admin page is blank.
Is this expected behaviour? Is everyone just using raw IPs instead of DNS?
Reads like you have not configured the FQDN on the LAN settings.
Crux is that they are comparing the FQDN with the referrer URL, kid of a security (or security by obscurity) feature, without any warning as you experience. Yes, I don't get warm with this ****, as it's different from any other business vendor product implementation.
Ok, I made a little progress. It turns out if I access the AP via its IP address (as in https://1.2.3.4) then I get the admin page working. But if I access it via its FQDN (as in http://hostname.mydomain.example) then the admin page is blank.
Is this expected behaviour? Is everyone just using raw IPs instead of DNS?
Malvineous wrote:
But if I access it via its FQDN (as in http://hostname.mydomain.example) then the admin page is blank.
Is this expected behaviour? Is everyone just using raw IPs instead of DNS?
Reads like you have not configured the FQDN on the LAN settings.
Crux is that they are comparing the FQDN with the referrer URL, kid of a security (or security by obscurity) feature, without any warning as you experience. Yes, I don't get warm with this ****, as it's different from any other business vendor product implementation.
Ohh that did fix the problem! I've never had to enter that into a device before to get it to work! Definitely a firmware bug because it doesn't even come up with an error, just a completely blank page. Weirdly when I put in the FQDN a popup came up saying "invalid IP address" and then the UI buttons stopped working, but after reloading the page it had saved the FQDN and immediately accessing the admin web page by https://fqdn worked. Of course accessing it via https://hostname still gives a blank page, you have to include the domain as well. What a terrible design!
So how can I get that set automatically from the DHCP server? I'm already passing "host-name" and "domain-name" options, do I have to pass another option as well? It will be annoying having to remember to log in and update the FQDN if the AP is ever moved to a different location and it picks up a new IP address and hostname.
Indeed, it's a strange design to say it this way, very uncommon for normal IT and network admins. Looks like they followed some strange security design wishes by one early customer.
Malvineous wrote:
So how can I get that set automatically from the DHCP server? I'm already passing "host-name" and "domain-name" options, do I have to pass another option as well? It will be annoying having to remember to log in and update the FQDN if the AP is ever moved to a different location and it picks up a new IP address and hostname.
No, this would require a change in the DHCP client, automatically updating the config in this aspect. These DHCP options would help for the device when doing DNS queries, without the need for defining the domain part of the DNS search path. Last but not least, this would not change or enhance the usability in my opinion.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
