4.8.0 Wireguard client configuration issues

Routers VPN, DNS, Leaks
1

I'm connecting to a pfSense server via the MT3000's WireGuard client. MT3000 firmware version is 4.7.4. In the VPN dashboard, "Auto Detect" mode is selected, and devices on both LANs can access each other. When I upgraded the MT3000 firmware to 4.8.0, the VPN dashboard only has "Global" and "Policy" modes. While the MT3000 can access the pfSense LAN, pfSense cannot access the MT3000. The "Remote Access LAN" option is enabled in the MT3000's WireGuard client. What settings do I need to configure on the MT3000 client to allow access between the two LANs? I'm certain that the pfSense WireGuard settings are correct.

2

Adapt as appropriate:

3

Does this apply to 4.8, which is what OP asked about? And it doesn't address why you cannot access the router once the VPN is connected.

4

They (GL.iNet) could have reworked the GUIs given the newly included PBR feature.

Screenshot_20250816_001723
Screenshot_20250816_001723926×336 25.3 KB

5

This is from a Slate AX (GL-AXT1800) running v4.8.0-beta9 as a WG Client:

Screenshot_20250816_002847
Screenshot_20250816_002847591×399 24.2 KB

6

How does this address that you cannot connect to the router once the VPN is established?

To be clear, not from the upper or lower subnet.

7

The 'server' needs to serve a route back to the client for a S2S. That has not been determined to be configured.

8

Connect to the mt3000 on the IP the VPN server gave to the mt3000.

Eg
Mt3000 local Lan is 192.168.8.0/24
pfsense assigned mt3000 VPN connection 10.1.2.3/32

When connecting from pfsense side to mt3000 use IP 10.1.2.3.

The rest of 192.168.8.0/24 will work as expected

1 Like
9

If want to access from server router side TO client router LAN through client router LAN subnet, it required to add a route rule in server router.

Bruce_2025-08-20_11-10-22
Bruce_2025-08-20_11-10-221193×435 17 KB

If only access the client router GUI, not required to add the route, direct use client tunnel IP like 10.x.x.x.