-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
net/wireguard: use stock rc script, rename server #1049
Conversation
|
good for an unreleased 12.0 it seems ;) merged, thanks! |
|
@fichtner I now also have a report that it works on stock FBSD 11.2, but 19.1b image crashes :/ |
|
dirty programming vs hardening features :> |
|
cc @lattera |
|
This is the stack trace, something with UFS: Thx to @decke for debugging .. |
|
This will warrant longer debugging. Do you have steps to reproduce? |
|
On OPNsense: opnsense-code plugins Via UI: VPN -> WireGuard -> Local: Add a new instance, leave pub and private empty, Tunnel Address 10.10.61.10/24, Save Go to Endpoints, add an endpoint, give pubkey
Shared secret empty, endpoint se1.wg.azirevpn.net, port 51820. Go back to Local, open your instance and on dropdown Endpoints choose the one and save. Then go to General and enable WireGuard. Now when you restart (just hit Apply/Save) for a couple of times you'll get a stacktrace .. sometimes it takes 20 restarts, sometime only 2. Tested with 18.7 and 19.1b. |
|
I installed FreeBSD 11.1 with ZFS and bootstrapped to OPNsense .. error seems to be gone but with exactly every second restart of wireguard I get the following (and wireguard doesn't start): |
|
Have you tried running Wireguard on stock HardenedBSD? I'm thinking of filing a bug report with Wireguard. |
|
@lattera: You probably haven't noticed that wireguard is a pure userland (Golang) implementation. From the stacktrace it seems that removing a pidfile or unix socket ends in a UFS kernel panic. I don't see how filing a wireguard bug would help here. |
|
@decke Ah. I don't know anything about Wireguard, other than it's a new VPN tech. @mimugmail That makes sense. HardenedBSD hasn't made any changes to the filesystems supported by FreeBSD. Thank you for trying to reproduce with stock HardenedBSD. @fichtner How does OPNsense use tunefs? Perhaps @mimugmail can try running tunefs on his HardenedBSD setup then starting Wireguard. FreeBSD did introduce changes to UFS between 11.1 and 11.2. |
|
same as FreeBSD simply to enable softdep... need to run a side by side test and isolate the cause... it all revolves around https://github.com/WireGuard/WireGuard/blob/master/src/tools/wg-quick/freebsd.bash IMO |
|
We got a bugreport with a stock FreeBSD 11.2 that seems to trigger a similar or the same issue. |

Finally found the time to move to stock rc script. I renamed Server to Local as it confused many users coming from OpenVPN not understanding why configure server when using as client.
Still stack traces with 11.1 and 11.2 HBSD, reported from port maintainer that it's stable in 12.0 :(