Messages

i monitore wireguard now via monit, works fine for me

waiting for "vpn hook" ;-)

thx

thx a lot and sorry for not finding it

nobody?

/usr/local/opnsense/scripts/Wireguard/wg-service-control.php stop

does also not work

/usr/local/sbin/configctl -dq wireguard stop

does not stop my wireguard service

/usr/local/sbin/configctl -dq wireguard restart

does not restart

also do not get an error message?

How to restart Wireguard VPN Service via commandline

/usr/local/sbin/configctl wireguard stop/start

does not do the job

thanks a lot for your input.

Looking good for now, that the remote site initiates the vpn connection!!

thx

ok, good idea to restart, maybe i can use monit as well

If one end has a fixed IP address let the other one initiate the connection. You can leave the peer IP address field empty or set to 0.0.0.0 - don't exactly remember which. If both ends have dynamic addresses, bad luck. I don't work with anything but fixed for site 2 site VPNs.

The problem is that WG starts before your uplink and DNS is ready ...

ok, i'll try this. The central Opnsense has an fixed address, the S2S peers are "FritzBox" i'll put a persistant keepalive to conf

Let's see if this works

but peer has an dynamic ipadress

after reboot of my opnsense 23.7.3, wireguard does not come up, it shows green in dashboard but is not working

log shows following entry:
/usr/local/opnsense/scripts/Wireguard/wg-service-control.php: The command '/usr/bin/wg setconf 'wg0' '/usr/local/etc/wireguard/wg0.conf'' returned exit code '1', the output was 'Name does not resolve: `xxxyyy.com:53956' Configuration parsing error'

manually restarting wireguard helps and wireguard is running again.
I assume it is a timeing problem, because wireguard starts and at this point i do not have an official IP adress on WAN interface, because DHCP takes some time.

how can i solve this issue?

I have the kernel modul and it worked until upgrade to 23.7.2
23.7.1 everything was fine

After upgrade to 23.7.2 Wireguard is not working anymore (wg0 interface missing)

I found the problem, because i configured the wireguard tunnel network also as local network in openvpn, in order to be able to route traffic from wireguard to openvpn and vice versa.
this worked perfect until 23.7.2

With 23.7.2 it doesen't work anymore until i
1. stop openvpn
2. restart wireguard
3. restart openvpn
then it is working again.

any Ideas?

Hi,

do i unterstand it right, that the Wireguard (Group) rules are for all instances (wg1, wg2, ...) and interface rules is for the related instance wg1, wg2?

thx

i only installed os-wireguard plugin and then upgraded to 23.1.
Everything seams to work fine, but services monitor shows red for wireguard-go

hard to accept the red entry at the top of plugin List :-)