When in AP mode, the Orbi forces the 3rd octet to be .2 (xxx.xxx.2.xxx).
There is no configuration available for DHCP or to change any of the settings. It is also NOT documented anywhere.
For a $2k router, how could this even be possible? I have multiple VPNs and using the guest network crippled my network and it took hours to figure out what was happening.
Setting up an LAN address is Networking 101, how could something so fundamental be missing?
In AP mode, the only DHCP that can be active is the one in use for VPN clients connecting by TUN where different LAN subnet must be used than in TAP mode where the VPN client connecting is bridged (tap-bridge) to the usual LAN.
So if the OpenVPN is connecting in TUN mode, a dedicated IP subnet is used (likely in the OpenVPN config file, probably not click and pray control), the AP OpenVPN does some NAT then.. If the OpenVPN client is configured to connect by TAP, your usual LAN DHCP is typically active (unless some fixed address is assigned in the config).
The difference TAN vs. TUN is of course documented - in the OpenVPN documentation - (not in any Netgear router doc)
When in AP mode, the Orbi forces the 3rd octet to be .2 (xxx.xxx.2.xxx).
There is no configuration available for DHCP or to change any of the settings. It is also NOT documented anywhere.
For a $2k router, how could this even be possible? I have multiple VPNs and using the guest network crippled my network and it took hours to figure out what was happening.
Setting up an LAN address is Networking 101, how could something so fundamental be missing?
