GL-AXT1800 4.1.0 - OpenVPN server - local LAN not accessible

nickyz · 2022-12-09T11:36:36.905Z

I have set up OpenVPN server with the standard settings, and Client-to-Client Option enabled.

I can connect to the server with the generated client config file. The traffic is router trough the VPN server which is fine. However, the devices on the local network are not accessible (and visible).

Client to Client option does not seem to work. As well the option “Allow access to local network” in the server settings is gone in firmware version 4.x?! Access to local network worked on firmware 3.x.

What to do to enable the visibility and access to local resources when connected to the OpenVPN server? This is a crucial feature and without it, there is no point to use the server at all!

yuxin.zou · 2022-12-10T03:19:13.581Z

nickyz:

Client to Client option does not seem to work. As well the option “Allow access to local network” in the server settings is gone in firmware version 4.x?! Access to local network worked on firmware 3.x.

It has been modified into the VPN Dashboard, please refer to VPN Dashboard - OpenVPN Server Options.

alzhao · 2022-12-10T03:25:40.412Z

Maybe you mean this option.

It allows that you still be able to access the local WAN network when connected to a VPN server.

image730×390 37.4 KB

nickyz · 2022-12-10T05:04:51.730Z

This option is checked as well on my side, and has no effect on accessing the local LAN devices.

alzhao · 2022-12-10T06:08:05.165Z

Can you draw a diagram to clarify how do you want to which subnet.

nickyz · 2022-12-10T06:55:36.949Z

the router is directrly connected to WAN with DHCP.
The internal network is:

Router IP Address 192.168.31.1
Start IP Address 192.168.31.100
End IP Address 192.168.31.249

OpenVPN server:
Tunnel Address: 10.8.0.0

I want to access a device with IP 192.168.31.170

in the Vpn dashboard:
OpenVPN Server Options:

Allow Remote Access LAN is enabled
IP Masquerading is enabled (disabling - no effect)

wcs2228 · 2022-12-10T18:32:34.304Z

What kind of device is at IP address 192.168.31.170 (Windows PC, Mac, NAS, etc)? What protocol do you want to access it (SMB, http, ftp, etc.)? Are you able to ping the 192.168.31.170?

In terms of visibility, LAN devices would not be able to broadcast across subnets and need to be accessed by IP address.

I do not work for and I do not have formal association with GL.iNet

alzhao · 2022-12-12T03:52:48.371Z

nickyz:

Allow Remote Access LAN is enabled

If you want to access the LAN network (192.168.31.0/24) network from the vpn client, this should be the only option needed, supposing you are using ovpn client on your pc/smartphone directly.

Pls check @wcs2228’s questions.

nickyz · 2022-12-12T17:28:23.677Z

alzhao:

192.168.31.0/24

I appears it was Windows firewall problem on the device. This topic helped
https://forums.openvpn.net/viewtopic.php?t=21887

Consider this topic closed and I am sorry for wasting your time. It is not a router problem!

wcs2228 · 2022-12-12T18:32:11.460Z

That was what I suspected (applies to both OpenVPN and WireGuard):

LAN remote access via WireGuard connection Technical Support for Routers

I have WireGuard VPN Server running on my GL-MT300N-V2 (Mango) router at home. I now abroad and use WireGuard VPN Client software on my laptop and it works fine (IP check shows that I’m in my home place). But the problem that I can’t access the shared drive on my home PC (\192.168.2.116), which is connected via WiFi to the Mango router (LAN). At the same time, I can ping that PC: Reply from 192.168.2.116: bytes=32 time=93ms TTL=127 Also, I can ping the Mango router itself in both WireGuard a…