I have been testing Wireguard on FreeBSD 11.2-RELEASE and ran into a problem.
The issue seems to occur when a Wireguard interface is brought online on a specific routing table with
If this routing table doesn't have a default route defined, the interface and the
process seem to go into a state where the interface can not be destroyed with
and the process can not be terminated with a
I am able to workaround this by renaming the interface with a
adding in a default route to the routing table and then starting the Wireguard interface.
1 - Is it possible to terminate the first wireguard-go process? It has a T in the STAT field in ps and does not terminate upon a 'kill -9'
2 - Is it possible to remove the first interface?
The issue seems to occur when a Wireguard interface is brought online on a specific routing table with
Bash:
setfib 1 wg-quick up wg0
Bash:
wireguard-go wg0
Bash:
ifconfig wg0 destroy
Bash:
kill -9 $PIDI am able to workaround this by renaming the interface with a
Bash:
ifconfig wg0 name wg9991 - Is it possible to terminate the first wireguard-go process? It has a T in the STAT field in ps and does not terminate upon a 'kill -9'
2 - Is it possible to remove the first interface?