After updating to the development build and from there to the release candidate my wireguard vlan is no longer getting an internet connection. I have no idea why this is, but I saw that osfirewall and os-wireguard show as missing under plugins and this can't be resolved.
They're not missing, part of core now.
A screenshot from System-Gateways-Configuration please ?
Here you go, it shows working as before
Mkay...was expecting something else.
FW rules on the VLAN and NAT would be next ones to check
I think I found the problem, somehow the vpn gateway group got deleted but the rules still reference it.
I recreated the group and everything is working fine again.
Confirmed, mine are gone too. Didn't notice so far as I had some individual rules active since the last time I had to change servers
did you check for updates again after it updated? ignore my post next to yours, its a different weird issue.
I have Wireguard fully working on my box after updating
my gateway group was gone also
i posted it in the irc earlier
Do you have any <gateway_group> listed in /conf/config.xml or the only remnants of the name are in the rules section ?
Quote from: newsense on January 20, 2024, 09:18:03 PM
Do you have any <gateway_group> listed in /conf/config.xml or the only remnants of the name are in the rules section ?
I took a look at the configuration history, the entire gateways block was not there in the config before i added it back.
But I only had this one wireguard gateway group before the update.
+ <gateways>
+ <gateway_group>
+ <name>***</name>
+ <item>***|1</item>
+ <item>***|1</item>
+ <trigger>down</trigger>
+ <poolopts/>
+ <descr/>
+ </gateway_group>
+ </gateways>
It looks like the '/usr/local/opnsense/mvc/script/run_migrations.php' delete all gateways and the group, but only recreated the gateways withoutt the group
Same here. I lost all my gateway groups and they are not in the config file either. Only the references to the gw groups remain in the firewall rules.
Actually, everything (and including) under <gateways> is gone, including this tag itself.
@franco, not sure if you'll see this but I did notice the commit that fixes this issue. If I upgraded now that it's fixed, would I still encounter this issue? Just wondering since there won't be a RC2 and I'm itching to try it.
It's not fixed in anything that you can upgrade to until 24.1 is out next week. If you're on a VM you can try applying the patch after you land on 24.1.r1 but I doubt it would work retroactively.
The only possibility for this to work would be to export the config, upgrade to 24.1.r1, apply patch, reboot and import the config file again -- that is _if_ the GW migration script is triggered on import.
Thanks for the info. I bit the bullet and recreated my groups. No big deal.