WG Interface 23.7.9

[kozistan]

Hello! Got issue after 23.7.9 updat. Wireguard interfaces appear unassigned. As they've been created and configured before the update, they are up and running, so it's kinda cosmetic issue. Just wonder if i need to create new one i won't be able to assign it to interface. Am i the only one with this one?

[franco]

"interfaces" appear "unassigned"? First things first WireGuard instances do not have to be assigned as interfaces per se. Can you qualify your report a bit?


Thanks,
Franco

[kozistan]

I'm using 5x WG connection as gateway for different departments, so i've been assigning WG devices to interfaces as gateway. Now, as u can see at the screenshot, they are not available at the device list and you can see WG connections are UP.

[franco]

This is the wireguard-go plugin I guess?

[kozistan]

correct Franco, is there another way how to use it?

[franco]

Ok that should be it then:

https://github.com/opnsense/plugins/commit/837b403b
https://github.com/opnsense/plugins/commit/2c2644e5

# opnsense-patch -c plugins 837b403b 2c2644e5

Sorry about that. The wireguard-go is not on our radar anymore and this looked innocent enough...

https://github.com/opnsense/core/commit/b4cfc0da9


Cheers,
Franco

[kozistan]

Thanks Franco, really appreciate!

btw, is there another way how to make my situation different? Just wondering you're complaining about this plugin, so i'm curios .

[franco]

The os-wireguard-go plugin will be removed in 24.1 and the upgrade will ship with a standard install of the wireguard kernel module. You could also switch to the kernel module plugin (os-wireguard). But I don't know the exact reason for you using go. There are a a few loose ends like Zenarmor support.


Cheers,
Franco

[kozistan]

I have purchased business subscription of Zenarmor, means i can not move to os-wireguard. Anyway, will test a bit.

Thanks again for your support!