I own several Gli-net-MT300N GL-V2 in which they are all connected to openvpn server running on a local machine, the issue I have is they are able to connect no problem however they cant see the local LAN or ping any device
If i to take the same openvpn config and connect from a pc, I am able to see the full LAN and ping all devices so its not openvpn server issue or configuration
I wanted to reach and ask if there is a specific firewall rule or ip route I need to enable for it to be able to see the LAN on the openvpn server? as it does if I connect with the same openvpn profile from openvpn connect on a PC
Thank you
I want to ping devices on the openvpn lan, how i can setup the port forward I also have luci installed on the MT300N-GL v2, your help is highly appreciated
If you are referring to router port forwarding to the openvpn server, this is also working as I can access the openvpn no issue and can go out to the internet using the openvpn server public ip, my current issue is I cant see the LAN network of the openvpn server using the MT300N v2 , however If I to use the same openvpn config file on PC everything working flawless
Any help on this would be highly appreciated, thanks in advance
Sorry if i am miss described my issue, I have the openvpn server not running on MT300N GLv2 its running on a remote server (centos 7 machine), I just use MT300N-GLv2 as openvpn client, I can access the openvpn server which is running on centos 7 no problem and can browse internet using this machine VPN, the centos 7 machine is running on 192.168.1.x subnet ==> to a public ip
While the MT300N Glv2 is running on 192.168.8.x and connected using wan port to a router on 192.168.1.x subnet with different public ip
Now the issue i have that once I am conncted to open vpn, I cant see/ping any device(s) under the remote lan 192.168.1.x
here also my ip route
root@GL-MT300N-V2:~# ip route
0.0.0.0/1 dev tun0 scope link
default via 192.168.1.1 dev eth0.2 proto static src 192.168.1.123
4.2.2.1 via 172.27.232.1 dev tun0 metric 101
8.8.8.8 via 172.27.232.1 dev tun0 metric 101
x.x.x.83 via 192.168.1.1 dev eth0.2
128.0.0.0/1 dev tun0 scope link
172.27.224.0/20 via 172.27.232.1 dev tun0 metric 101
172.27.232.0/22 dev tun0 proto kernel scope link src 172.27.232.5
192.168.1.0/24 dev eth0.2 proto kernel scope link src 192.168.1.123
192.168.1.0/24 via 172.27.232.1 dev tun0 metric 101
192.168.8.0/24 dev br-lan proto kernel scope link src 192.168.8.1
Two things. First, by any chance are the clients connecting with the same credentials? That can require some fancier footwork.
Second, it sounds like you have two 192.168.1.xx networks in the mix here, once that the Mango is connected to and one that the openvpn server is connected to. Is that so? That is a major no-no.