OpenVPN-Server
via https://openvpn.net/cloud-vpn/ ***
*
*
*
OpenVPN-Client *
PC "B" *
Windows **** PC LAN Interface *********
route ADD 192.168.1.0 *
_ MASK 255.255.255.0 100.96.1.YYY *
*
*
*****GL-MV1000_OpenVPN-Client 1 (192.168.1.0/24 e.g. OpenVPN IP 100.96.1.114)
* maquerade VPN to LAN ************ Device 192.168.1.11
* *
* *** Device 192.168.1.12
* *
* *** Device 192.168.1. ...
*
*
*****GL-MV1000_OpenVPN-Client 2 (192.168.1.0/24 e.g. OpenVPN IP 100.96.1.116)
* maquerade VPN to LAN ************ Device 192.168.1.11
* *
* *** Device 192.168.1.12
* *
* *** Device 192.168.1. ...
*
*
*****GL-MV1000_OpenVPN-Client 3 (192.168.1.0/24 e.g. OpenVPN IP 100.96.1.118)
* maquerade VPN to LAN ************ Device 192.168.1.11
* *
* *** Device 192.168.1.12
* *
* *** Device 192.168.1. ...
*****GL-MV1000_OpenVPN-Client n (192.168.1.0/24 )
* maquerade VPN to LAN ************ Device 192.168.1. ...
.
.
When using a Ubuntun Linux PC with OpenVPN-Client instead of Brume, everything works fine to route to the 192.168.1.0 when adding the manual route on PC “B”.
On another hacked WLAN Router OpenWRT + masquerade + openvpnClient, the setup worked.
The Brume, receives something, but packet must be blocked for any reason, and does route into 192.168.1.0/24.
Disabling Firewall did not help. Maybe deeper internal setting.