Hello,
I'm trying to get a s2s working. One at the moment does not have a public port, but I don't think it is the culprit here.
On siteA(vb) wireguard starts normally, config below
interface: wg0
public key: xxx
private key: (hidden)
listening port: 51821
peer: xxx
endpoint: publicIP:46107
allowed ips: 10.50.20.0/24, 10.100.0.0/24
latest handshake: 9 minutes, 41 seconds ago
transfer: 328 B received, 25.38 KiB sent
persistent keepalive: every 15 seconds
SiteB (cp) screenshots
and from shell /usr/local/etc/rc.d/wireguard start gives
#] ifconfig wg create name wg0
[!] Missing WireGuard kernel support (ifconfig: SIOCIFCREATE2: Invalid argument). Falling back to slow userspace implementation.
[#] wireguard-go wg0
┌──────────────────────────────────────────────────────┐
│ │
│ Running wireguard-go is not required because this │
│ kernel has first class support for WireGuard. For │
│ information on installing the kernel module, │
│ please visit: │
│ https://www.wireguard.com/install/ │
│ │
└──────────────────────────────────────────────────────┘
[#] wg setconf wg0 /dev/stdin
[#] ifconfig wg0 inet 10.50.20.2/24 alias
[#] ifconfig wg0 mtu 1420
[#] ifconfig wg0 up
[#] route -q -n add -inet 10.20.50.0/24 -interface wg0
[#] route -q -n add -inet 10.20.0.0/16 -interface wg0
[#] rm -f /var/run/wireguard/wg0.sock
This issue happened on both instances, following previous discussions I reinstalled wireguard and site vb at least has it configured now (or so it seems), but site B has issues.
Any help appreciated
It's not an error. The WireGuard authors can be pretty weird... their kernel module is still experimental and we have used the Go implementation since 2019.
Cheers,
Franco
Thanks for the insight!
So then what could I possibly go about and troubleshoot on site B that does not start the service (even from the dashboard)?
Remove .50.0/24 from the endpoint