Messages

Ok, I just applied the patch manually and ticked the require message authenticator box for my AP clients. Let me monitor the freeradius logs and get back to you.

Is this the correct command?

opnsense-patch -a punktDeForks -c plugins a1f6543

EDIT: Looks like it's downloading from the incorrect URL:

root@OPNsense:~ # opnsense-patch -a punktDeForks -c plugins a1f6543
fetch: https://github.com/punktDeForks/plugins/commit/a1f6543.patch: Not Found

How do I change the path to "opnsense-plugins" instead?

So just to be sure, when the primary WAN comes back, all new connections will go through that link and all established/old connections stay in the backup link, correct?

I don't. Is there an official guide for manually applying patches that I can follow?

Sure, let me know how I can help. FWIW, this option is a dropdown box (not a free form text field) in the pfsense freeradius package.

I'm receiving the same error in freeradius. How can we set this option? Why are there are no advanced options in the opnsense freeradius package?

Fair enough. However, I'm not insinuating anything. Again, this simply piqued my curiosity as, like you, I don't experience the issue.

Yes, AGH upstream. I don't have this problem too so I'm just curious what is causing it for others.

Is this fixed upstream yet?

Got it. Thanks.

No, I mean from the plugins page in opnsense that's on a proxmox vm. So that's a no then. I have the microcode updated on the host already.

Is this microcode update beneficial if opnsense is running on a proxmox vm?

For some reason, I have found nothing about this issue except this thread. It definitely worked prior to the upgrade to 24.7, and absolutely does not in 24.7, at least when I tried it last week.

As noted, I downgraded to 24.1.10, and it's back to working, but I was able to do so by rolling back to a snapshot.

One tip: If you downgrade manually to 24.1.10, make sure you have a config file ready that was created in 24.1.10 or earlier. At least in most similar setups (and I assume OPNsense is the same way), restoring from config only works if the config file was created from the same or earlier version to which it's restored.

Of course, downgrading is only a temporary solution. It's not feasible to remain with 24.1.10 permanently, so hopefully there is some interest in a workaround or patch in 24.7 for this, because it's beyond my technical skills to fix it on my own.

Well, here's my thread about it:

https://forum.opnsense.org/index.php?topic=42330.msg208973#msg208973

Sent from my SM-S916B using Tapatalk

All the OPNsense plugins will be reinstalled when you check for updates.

For the third party ones you'll have to reinstall, hopefully you have copies of the config files as they're not included in the OPNsense one.

To follow-up on this, the opnsense plugins do not get reinstalled when you "check for updates". They get reinstalled when you click on the "resolve plugins conflict" button under System -> Firmware -> Status.

Isn't that the question? I don't have all the answers.


Cheers,
Franco

It is. I just don't know if this issue can be considered a bug that needs to be in the opnsense team pipeline or not. Dors this mean that this also happens in pfsense? I don't remember having this issue when I was still using pfsense. No offense meant.