OPNsense Forum
Archive => 23.1 Legacy Series => Topic started by: MCMLIX on January 15, 2023, 08:26:48 am
-
I'm using Wireguard. I install the os-wireguard plugin and then "pkg install wireguard-kmod".
To test 23.1 would I "# opnsense-update -ur 23.1.r1" then remove the plug-in or remove it from 22.7.10_2 before the update.
-
I have a similar question. I installed from CD. I preload all of my plugins including wireguard kernel. I then restored my config. Now I have the wireguard-go service showing as down but wireguard is working.
Great job by the way! you should also know that my strongswan config survived and works!
Thanks team!
-
If you use wireguard-kmod, there is no wireguard-go running. The services widget checks for wireguard-go and flags it as down.
I suggest you configure the services widget to ignore wireguard-go and place the dedicated wireguard widget on your dashboard.
-
Thanks, that worked. I am hoping that we will be able to see the kmod status at some point.
-
Question about default behavior:
Setting the widget in the services dashboard to be ignored is definitely a solution to this issue. However, the widget should be installed and uninstalled with the wireguard-go plugin, correct?
Checking the instance that I just upgraded: os-wireguard-go is not installed and os-wireguard is.
Shouldn't the dashboard widget follow the particular plugins that are installed rather than needing a user to disable/ignore the widget manually?
Perhaps this is actually a bug?
-
Both plugins (kmod and go) use the same code. It's as much as a bug as nobody contributing the change.
I'm unsure what all the fuzz is about.
Cheers,
Franco
-
I've made code contributions to the wireguard plugin in the past. I'm definitely willing to see how to fix this. I just wanted to check in here and discuss before going forward.
The problem is that if one had the os-wireguard plugin installed before this update, after the update, there is a new plugin named os-wireguard-go that is not installed. However, on the dashboard, there is a red stopped entry in the services pane. This indicates a problem. However, from what I gather in the discussion so far, this is not a problem, and the user should manually have that entry in the pane ignored.
Should that dashboard pane entry just be part of the os-wireguard-go plugin only and not appear at all if the os-wireguard plugin is installed alone?
-
Yes, the dashboard widget is still monitoring the wireguard-go service and not the kernel module. It would be nice if the dashboard widget monitored the kernel module and allowed us to start stop and restart the kernel module, if possible.
Thanks,
Al
-
Yes, the dashboard widget is still monitoring the wireguard-go service and not the kernel module. It would be nice if the dashboard widget monitored the kernel module and allowed us to start stop and restart the kernel module, if possible.
Thanks,
Al
The widget? Or the Services monitor?
-
The services monitor. I could be wrong but i thought the service monitor was widget. not to be confused with the wireguard widget.
Al
-
So I installed OPNsense 23.1 with Wireguard onto Proxmox 7.3-4 using a config.xml backup. I passthrough nics and the usb stick.I used pmhausen suggestion. I installed the Plugins (even the wireguard plugin, just the missing one) rebooted and all is good. os-wireguard-go shows as installable, so I think I'm using wireguard-kmod. I installed patch # opnsense-patch -c plugins 2ed1f987eb97d, don't know if i needed to. As it stands all is working great (touch wood). Thank you for the assistance and thank you for another great release!
-
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
-
The problem with the services widget is to be expected. See my explanation here:
https://forum.opnsense.org/index.php?topic=31889.msg154136#msg154136
And Franco's patch here:
https://forum.opnsense.org/index.php?topic=32110.msg155184#msg155184
Probably fixed in some hotfix early next week.
-
Just a quick semi off-topic question here.
Before update to 23.1
- WireGuard Go plugin installed (os-wireguard)
- WireGuard kmod package installed manually from cli
Are we supposed to uninstall the kmod package before applying the update to 23.1?
Or will the update replace/remove the WireGuard Go plugin and update the kmod package?
-
After upgrading to 23.1 my Wireguard service broke. I noticed that the WG interface (wg0) was down. After rebooting multiple times I tried
root:~ # service netif restart wg0
/etc/rc.d/netif: WARNING: wg0 does not exist. Skipped.
Starting Network: wg0.
ifconfig: interface wg0 does not exist
Any idea what might be going on? Otherwise the upgrade went fine.
Thank you
-
Is the native Wireguard widget on the dashboard supposed to look like this? Never used it before but enabled it as recommended in thread and this is what I get. Could it be related to a bug in the theme I'm using from the plug-ins? I am in the three-wide format.
-
Just a quick semi off-topic question here.
Before update to 23.1
- WireGuard Go plugin installed (os-wireguard)
- WireGuard kmod package installed manually from cli
Are we supposed to uninstall the kmod package before applying the update to 23.1?
Or will the update replace/remove the WireGuard Go plugin and update the kmod package?
Correct me if I'm wrong, but doesn't the OPNsense plugin system "track" / ignore manually installed packages? Maybe that was TrueNAS CORE?
I'm already on 23.1, but previously installed the wireguard-kmod package via pkg install.
Before following my tests blindly, please create a backup!
I just tested uninstalling the plugin. When doing so, the following packages were uninstalled:
- bash
- os-wireguard
- wireguard-tools
I then had to manually cleanup wireguard-kmod via pkg remove. Re-installing the os-wireguard plugin now adds the following packages:
- bash
- os-wireguard
- wireguard-tools
- -> wireguard-kmod <-
Uninstalling the os-wireguard plugin again now properly cleans up the wireguard-kmod package.
My conclusion is that it's cleaner to uninstall the os-wireguard plugin and wireguard-kmod package first, and then re-install the plugin.
My WireGuard config was untouched by this (please create a backup).
-
So I'm on OPNsense 23.1.3_4-amd64. I have been running with "schnerring" guide since it was posted. I substitute in Surfshark Wireguard. I followed "pmhausen" advice initially and that seem to work. I did try the above procedure and everything seems to work great (touch wood).
Thank you for the hard work on developing OPNsense. Thank you "schnerring" for the guide.
-
Correct me if I'm wrong, but doesn't the OPNsense plugin system "track" / ignore manually installed packages? Maybe that was TrueNAS CORE?
I'm already on 23.1, but previously installed the wireguard-kmod package via pkg install.
Before following my tests blindly, please create a backup!
I just tested uninstalling the plugin. When doing so, the following packages were uninstalled:
- bash
- os-wireguard
- wireguard-tools
I then had to manually cleanup wireguard-kmod via pkg remove. Re-installing the os-wireguard plugin now adds the following packages:
- bash
- os-wireguard
- wireguard-tools
- -> wireguard-kmod <-
Uninstalling the os-wireguard plugin again now properly cleans up the wireguard-kmod package.
My conclusion is that it's cleaner to uninstall the os-wireguard plugin and wireguard-kmod package first, and then re-install the plugin.
My WireGuard config was untouched by this (please create a backup).
I can confirm that this way is cleaner and that the config is indeed kept in place after reinstalling os-wireguard. Just did it on one of my firewalls.
However just uninstalling os-wireguard will not only leave wireguard-kmod but also wireguard-tools on my system.
So I think the best way to do this is to...
pkg remove os-wireguard wireguard-tools wireguard-kmod
reboot
Then just reinstall the os-wireguard package in the web ui.