All,
Am trying to setup a WireguardTunnel Server for our local mesh island infrastructure.
In reviewing my settings, i have come across what appears to be an anomaly on my setup.
Setup is a Mikrotik hAP AC Lite, RPI 3B+, Grandstream VoIP phone.
When running the below commands (in bold), the response is returned below. It looks like the Wireguard tunnel daemon is not operating.
root@N5TXZ-hAP1:~# ps | grep vtund
3531 root 1316 S grep vtund
root@N5TXZ-hAP1:~#
^^^This just shows my grep command, not the vtund daemon running.
root@N5TXZ-hAP1:~# logread | grep -i vtun
Tue Aug 6 13:07:12 2024 daemon.notice procd: /etc/rc.d/S19firewall: mesh-firewall: Executing /etc/local/mesh-firewall/02-vtund
Tue Aug 6 13:07:26 2024 daemon.notice procd: /etc/rc.d/S82vtundsrv: uci: Entry not found
Tue Aug 6 13:07:27 2024 daemon.notice procd: /etc/rc.d/S84vtund: uci: Entry not found
root@N5TXZ-hAP1:~#
^^^This looks like the daemon/service is either not in the rc.d file, or it is not running.
The Wireguard Tunnel Server and Client details have been vetted by others, and all looks to be in order. The Tunnel Server is ENABLED, but the Client cannot connect.
Any constructive input ideas?
73,
Mark
Am trying to setup a WireguardTunnel Server for our local mesh island infrastructure.
In reviewing my settings, i have come across what appears to be an anomaly on my setup.
Setup is a Mikrotik hAP AC Lite, RPI 3B+, Grandstream VoIP phone.
| 20240618-8d4eade MikroTik RouterBOARD 952Ui-5ac2nD (hAP ac lite) |
When running the below commands (in bold), the response is returned below. It looks like the Wireguard tunnel daemon is not operating.
root@N5TXZ-hAP1:~# ps | grep vtund
3531 root 1316 S grep vtund
root@N5TXZ-hAP1:~#
^^^This just shows my grep command, not the vtund daemon running.
root@N5TXZ-hAP1:~# logread | grep -i vtun
Tue Aug 6 13:07:12 2024 daemon.notice procd: /etc/rc.d/S19firewall: mesh-firewall: Executing /etc/local/mesh-firewall/02-vtund
Tue Aug 6 13:07:26 2024 daemon.notice procd: /etc/rc.d/S82vtundsrv: uci: Entry not found
Tue Aug 6 13:07:27 2024 daemon.notice procd: /etc/rc.d/S84vtund: uci: Entry not found
root@N5TXZ-hAP1:~#
^^^This looks like the daemon/service is either not in the rc.d file, or it is not running.
The Wireguard Tunnel Server and Client details have been vetted by others, and all looks to be in order. The Tunnel Server is ENABLED, but the Client cannot connect.
Any constructive input ideas?
73,
Mark
Have you checked your Internet router's port and port forwarding rules?
Do you know how I can check to determine if the Wireguard process(es) are running, or is it embedded in the kernel?
I have checked my router's rules,a nd they should be sufficient; however, I will make a separate post on that aspect as I have a FW in the mix, as well.
Scroll down a bit for Wireguard tunnels.