If you’re not sure what it is, you’re not using it. IGMP Proxy does not work with VLAN interfaces.Disable IPComp under VPN>IPsec, Advanced to work around if you’ve enabled IPComp. Make sure every virtual IP has something shown in the Interface column on firewall_virtual_ip.php. Go to Firewall>Virtual IPs, edit the affected IP alias, pick the appropriate CARP IP parent, then save and apply changes. IP aliases with CARP IP parent lose their parent interface association post-upgrade.

In the mean time, editing your OpenVPN server instance and setting the topology to “net30” there will accomplish the same thing and fix it. This is not working as intended in some cases, but has been fixed for 2.3.1. OpenVPN topology change - configuration upgrade code was intended to set upgraded OpenVPN servers to topology net30, rather than the new default of topology subnet.For those upgrading from a 2.3 beta or RC version to final. There are a few areas where additional caution should be exercised with this upgrade. The covers everything you’ll need to know for upgrading in general. Upgrade Considerations As always, you can upgrade from any prior version directly to 2.3. While the majority of these were related to the Bootstrap conversion, impacting 2.2.6 and earlier releases. Past blog posts have covered some of the changes, such as the, and the.

The webGUI rewrite brings a new responsive look and feel to pfSense requiring a minimum of resizing or scrolling on a wide range of devices from desktop to mobile phones. The pkg conversion enables us to update pieces of the system individually going forward, rather than the monolithic updates of the past. We are happy to announce the release of pfSense® software version 2.3! The most significant changes in this release are a rewrite of the webGUI utilizing Bootstrap, and the underlying system, including the base system and kernel, being converted entirely to FreeBSD pkg.

Pfsense 2.0.3 iso