Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
23.7 Legacy Series
»
os-wireguard 2.0[2]
« previous
next »
Print
Pages: [
1
]
Author
Topic: os-wireguard 2.0[2] (Read 808 times)
Zoltrix
Newbie
Posts: 6
Karma: 0
os-wireguard 2.0[2]
«
on:
August 31, 2023, 11:23:30 am »
Hi,
A silly question no doubt. But what does the [2] indicate in os-wireguard 2.0[2]?
I've just upgraded to OPNsense version 23.7.3, and under plugins, I have 2.0_1 listed for wiregauard. Should that be 2.0_2?
One of the reasons I ask, is that the upgrade seemed to hang on the checking repositories part. And when I refreshed, it indicated it was now up-to-date.
Cheers
«
Last Edit: August 31, 2023, 11:25:20 am by Zoltrix
»
Logged
tiermutter
Hero Member
Posts: 1099
Karma: 61
Re: os-wireguard 2.0[2]
«
Reply #1 on:
August 31, 2023, 11:45:14 am »
That's the reference in release notes to provided external sources, eg github
Logged
i am not an expert... just trying to help...
Zoltrix
Newbie
Posts: 6
Karma: 0
Re: os-wireguard 2.0[2]
«
Reply #2 on:
August 31, 2023, 11:51:26 am »
haha wow, I even looked in the announcements thread before I posted, and the reference links are right there
Logged
franco
Administrator
Hero Member
Posts: 17668
Karma: 1611
Re: os-wireguard 2.0[2]
«
Reply #3 on:
August 31, 2023, 02:19:33 pm »
In the cases of _1 and _2 it was hotfixes required to keep the IPv6 code of WireGuard working. It hasn't been otherwise documented as we don't annotate hotfixes for plugins much due to not being part of the default install/core features.
Similar policy applies to ports/packages updates in FreeBSD ports that have revision bumps for various minor reasons.
Cheers,
Franco
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
23.7 Legacy Series
»
os-wireguard 2.0[2]