Remote management of WAX214 Access Point

In response to your comments, I have to agree that in general the idea of using a VPN may seem the best approach for remotely managing the WAX214 on the local LAN but there is also the point that opening a VPN session to the clients LAN opens a hole for the purpose of capture or sniffing of those private packets on the clients LAN without the knowledge or permission of the client.

Now whilst the VPN maybe a de-facto method client Data or access to that client Data should be our greatest concern hence using HTTPS on a Web browser to a public facing TCP port on a router (which only points to the AP on the local LAN via port forwarding) shouldn't pose an issue especially if it is only allowed from a known public IP source address, further more using this method does not allow the remote engineer direct access to the clients Data stream.

We only enable this method of access to overcome the simple local management from the local LAN on the AP as it does not support the Insight portal method, as such the router is locally managed on our NMS which is on a private subnet and the example of using it across the Internet was only used as a general example of traversing from one IP subnet to another across a NAT'd gateway.

We have already tried your suggested method using simple port-forwarding and although in principle it should work (and does on the WAC50x series of AP's) on the WAX214 it appears to fail when accessed from another IP subnet other than the Local LAN IP subnet, in true reality the AP does respond but gives you the URL of the Netgear main site and not the view to the Login page on the AP itself.

So if you test this and come back with a solution I'll be surprised as I have already logged this with Netgear and they have confirmed it isn't possible hence my request for a product enhancement and not a comment of should work.

Best regards.