@Beerman said in Netgate Releases pfSense Plus Software Version 26.07: How can I use the new GUI on a virtual machine? 400 Netgate Nexus is not supported on this sytem Nexus cannot be licensed on this system due to: serial number unavailable, unsupported virtualization. See this thread. Short version is that you must have a serial number and a UUID.

@chpalmer I ended up downloading the latest netgate installer and used that to directly download and install the 2.9 beta. That worked without issues and able to load my previous config file during the install. I've tried upgrading from 2.8.1 to 2.9 numerous times and it resulted the same thing so gave up using the upgrade path. Used the newest installer instead.

@dstacey147 said in A New Release Candidate for pfSense Plus Software Version 26.07 Available!: @patient0 It looks like they want to impose a yearly subscription for each instance using the new interface? If your only instance is the firewall itself, it should be free, otherwise it's a deal breaker for me. I'm not paying a yearly subscription for something I already own, when I bought my 6100 it was for the harware and all updates going forward. No, I’m pretty sure that is not the case - if it was, that would be the end of Netgate with most of its current customer base :-) The license that comes with Nexus for its hosting instance should be “perpetual” according to previously mentioned releases of nexus. The expirering license is probably some “built-in” motivator to make sure you update the nexus package every once in a while.

@stephenw10 yeah I’ve not seen that ever. It has a UPS though.

@Darkk said in OpenVPN Race Condition Remediation: Several of my pfsense 2.8.1 instances already updated themselves. Reinstall openvpn-client-export update it also.

Nice work, please add fine‑grained RBAC to Netgate Nexus. We need a way to allow operators to manage all registered pfSense instances (view instances, use remote GUI/console) without giving them access to any Nexus controller settings or menus. A separation of “Instance Management” and “Controller Administration” privileges would enable proper role separation and significantly improve security in multi‑team environments.

@dennypage Create an igmp rule on your floating rules, and do not set the direction to in. Set: Interface Leave: Direction to any Set: Protocol to IGMP only Set: Source to any Set: Destination to any Set: Quick Set: Adavanced Options, Allow IP options For example if you have pfblocker dnsbl auto rules (ping auto rule, permit auto rule) on top, it can cause trouble on the states. Check: the States of this rule. You should see tcp and upd packets as well, 443. If you set the direction on your lan intarfce to in, you should see igmp only, otherwise you have to place at the very top of all your other floating rules before everything else.