OPNsense Forum

English Forums => Virtual private networks => Topic started by: nikkon on February 09, 2022, 09:37:16 am

Title: wireguard point to point guidance
Post by: nikkon on February 09, 2022, 09:37:16 am
Hello,

Did anyone managed to set a point-to-point Wireguard VPN?
Can you please point me to some docs (the one on opnsense is incomplete i believe)

Thanks
Title: Re: wireguard point to point guidance
Post by: Greelan on February 09, 2022, 10:01:58 am
https://www.thomas-krenn.com/en/wiki/OPNsense_WireGuard_VPN_Site-to-Site_configuration
Title: Re: wireguard point to point guidance
Post by: nikkon on February 09, 2022, 11:37:31 am
thanks for sharing this.
let me go through this and see how it turns out :)
Title: Re: wireguard point to point guidance
Post by: nikkon on February 10, 2022, 09:37:48 am
it works. the tunnel is up. the interface has been created.
Now I need to figure out how to route traffic through the tunnel

thank you
Title: Re: wireguard point to point guidance
Post by: chemlud on February 10, 2022, 09:51:47 am
The IP (-ranges) in the config will be accessed via the tunnel. try to reach a smb share or open ssh or whatever with the remote IP in the config and it should work...
Title: Re: wireguard point to point guidance
Post by: Greelan on February 10, 2022, 10:15:33 am
Exactly. Should be like accessing it locally
Title: Re: wireguard point to point guidance
Post by: nikkon on February 10, 2022, 10:29:55 pm
something doesn't match

the tunnel is up:
peer: VSS+lopy56*********
  endpoint: 24.4.223.185:51823
  allowed ips: 10.100.92.0/31, 192.168.123.0/24
  latest handshake: 23 seconds ago
  transfer: 2.88 MiB received, 2.87 MiB sent

Firewall A internal networks 172.16.10.0/24, 172.16.20.0/24
Firewall B internal network 192.168.123.0/24
Tunel network is : 10.100.92.0/31

without any additional fw rules ping fails

ping 192.168.123.1                                                       
PING 192.168.123.1 (192.168.123.1): 56 data bytes
Request timeout for icmp_seq 0

With the additional rule where I define the gateway same behaviour

Firewall A rules on Lan:
   IPv4 *   *   *   FirewallBLan    *   WIREGUARD_GW   *   FW B LAN access VPN
where FirewallBLan is Firewall B (192.168.123.0/24)

What am I missing?

Title: Re: wireguard point to point guidance - solved
Post by: nikkon on February 17, 2022, 03:12:28 pm
It can be closed
I made a mistake when I added the route.
all works now
thank you