wireguard point to point guidance

Started by nikkon, February 09, 2022, 09:37:16 AM

Previous topic - Next topic
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
DEC750 Deciso


thanks for sharing this.
let me go through this and see how it turns out :)
DEC750 Deciso

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
DEC750 Deciso

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...
kind regards
chemlud
____
"The price of reliability is the pursuit of the utmost simplicity."
C.A.R. Hoare

felix eichhorns premium katzenfutter mit der extraportion energie

A router is not a switch - A router is not a switch - A router is not a switch - A rou....

Exactly. Should be like accessing it locally

February 10, 2022, 10:29:55 PM #6 Last Edit: February 11, 2022, 01:32:23 PM by nikkon
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?

DEC750 Deciso

It can be closed
I made a mistake when I added the route.
all works now
thank you
DEC750 Deciso