"
Hah, of course I get it working right after posting. The only thing missing now is getting clients on the LAN routing traffic through it.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
Virtual private networks / Wireguard: OpnSense as a client only
July 25, 2025, 07:32:44 PM
Hi all,
I can't seem to figure this out from the docs, as they all seem to focus on running a Wireguard server, not a Wireguard client. I run a non-OpnSense Wireguard server, and have a peer config of:
```
[Interface]
Address = 192.168.14.8
PrivateKey = aaa=
ListenPort = 51820
DNS = 192.168.3.202
[Peer]
PublicKey = bbb=
PresharedKey = ccc=
Endpoint = vpn.domain.ext:51820
AllowedIPs = 192.168.6.0/24
```
I would usually put this into client software, but I want to set up a client in OpnSense that will route any traffic to 192.168.6.x from my LAN net through the VPN. However, no matter what I try I never see a connection attempt from OpnSense on the remote endpoint.
I can't seem to figure this out from the docs, as they all seem to focus on running a Wireguard server, not a Wireguard client. I run a non-OpnSense Wireguard server, and have a peer config of:
```
[Interface]
Address = 192.168.14.8
PrivateKey = aaa=
ListenPort = 51820
DNS = 192.168.3.202
[Peer]
PublicKey = bbb=
PresharedKey = ccc=
Endpoint = vpn.domain.ext:51820
AllowedIPs = 192.168.6.0/24
```
I would usually put this into client software, but I want to set up a client in OpnSense that will route any traffic to 192.168.6.x from my LAN net through the VPN. However, no matter what I try I never see a connection attempt from OpnSense on the remote endpoint.
Pages1
