@netnerdy Looks like this isn't completely true. Authentication seems to go away if I kill and restart wpa_supplicant. Instead I tried reruning the whole script (pfatt.sh) after the boot sequence. When I do that, I get a hard crash and the firewall reboots.

@jimp I am seeing that my sg-3100 on reboot is stuck at the blue lights (circle) flashing in a fast mode. None of the other lights flash either. This is a working device that has caused issue on reboot. Any ideas? Thanks in advance

@jimp I'm fine with the update freeze, but I wanted to try wireguard on my 7100, and it isn't showing up on the 27 Nov build of 2.5. Is that a bug in my upgrade or a difference between CE and Netgate builds?

Can confirm this is fixed. Just ran the 5th Feb 2021 ISO and it works. Thanks for the quick fix!

@viktor_g i done it. https://redmine.pfsense.org/issues/11369

https://redmine.pfsense.org/issues/11365

Thanks for the quick response. Will create a thread as suggested. Thanks.

@quarkz thanks, i didn't find that on a previous search

@qsystems said in From 2.4.5_1 to 2.5.0.a.20210115.2350 - ipsec mobile client vpn certificate based no longer working: Deleted all mobile configs and put back in the active config, unchecked group authentication under mobile client - extended configuration. It now works. Could be related to group authentication, see https://redmine.pfsense.org/issues/10748

@viktor_g Oh many thanks, removing all the P521 CAs, now Squid sees another type! Thanks a lot for your help! Best,

[image: dav.jpg] [image: dav.jpg] [image: sdr.jpg] [image: sdr.jpg] [image: sdr.jpg] [image: sdr.jpg] [image: sdr.jpg] [image: sdr.jpg] [image: sdr.jpg] [image: sdr.jpg] [image: sdr.jpg] [image: sdr.jpg] [image: sdr.jpg]

If you're just testing now (in the current snapshot) it should be in there already. You can check /etc/inc/util.inc on line 2363. Should include ^wg. Steve

@jegr Seems already be fixed. https://redmine.pfsense.org/issues/11249

@kiokoman said in Remove VMware MSI-X from the PCI blacklist.: @Cool_Corona it work ok with hw.pci.honor_msi_blacklist=0 the problem is that there should be no more need for it Just to chime in here: setting it to 0 did help a lot in my ESXi deployment by bringing down IRQ CPU utilisation by ca factor 10 (with passed through Intel NICs). It should be made the default or at least added to the tuning section in the docs not only for vmxnet NICs (already in there since some weeks ago) but also intel NICs passed through to a virtual pfsense.

@impatient 2.5.0.a.20201231.0250 is fine.

@techlw Seems so, tested it shortly four months ago and it seemed fine then.