First of all, I don’t allow WAN-side Admin access. That’s foolish in any scenario.
Secondly, um…yes, the setting affects LAN side access. If I restrict it to a single network (or VLAN) then in fact I am only able to access the Administration from said network or VLAN. It also locks out the app, unless it is sitting on the specified network or VLAN (as I would expect it to, appropriately.) So here we have a very basic feature and a very important one which apparently even Peplink staff aren’t familiar with or have a misunderstanding of the functionality.
This needs to be addressed, along with the other major issue I’ve raised numerous times that still hasn’t been resolved. Namely, setting the Admin to HTTPS and using a port other than 443. Immediately, I lose any and all access (from any network) to the Administration. The only way in is via InControl which has no problem bringing up the WebUI (interesting, eh?). I’m not doing it wrong and my equipment works. The problem lies with the Pepwave product and/or the firmware. This is a serious oversight and it needs to be addressed.