Search
Results (402)
- Bug #15500 (New): Hanging connections with fa ... ode when floating rule is matched in >= 2.7.1
- - Two freshly installed instances, both with ... es assigned, (WAN, LAN and PFSYNC). - CARP/VIPS are setup on the WAN and LAN. - pfsync an ... ang.* New connections can be made and the VIPs have failed over using CARP as expected and ... nnections to failover correctly and not hang.
- Bug #15428 (Not a Bug): UI appears to put inc ... ameters into the low level NIC configurations
- it appears that there is a bug with the UI an ... e. HA is therefore not working as intended.
- Bug #15361 (Resolved): Network and broadcast ... ut validation is incorrectly applied to IPv6 VIPs
- There is no network address in IPv6, nor broa ... "The network address cannot be used for this VIP" It happened on my pfSense+ box but it seems the CE 2.7.2 is also affected.
- Bug #15216 (New): captive portal zone name conflicts with existing interface name
- Customer reports intermittent issues with cap ... ssue. config for the parent interface, CARP VIP and zone are attached.
- Bug #15176 (Resolved): Change Mobile IPsec RADIUS accounting to use ``accounting_requires_vip`` so accounting will not activate for non-mobile VPNs
- At some point strongSwan's @eap-radius@ plugin gained a setting called @accounting_requires_vip@ which makes strongSwan only send accounting ... > plugins > eap-radius > accounting_requires_vip = yes@) and reword the note on @vpn_ipsec_mobile.php@ to account for the change.
- Bug #15148 (Resolved): OpenVPN Wizard fails when a VIP is used
- If you create a remote access server using the OpenVPN wizard and select a VIP as the interface it creates an invalid confi ... ncorrectly, for example: <pre> <interface>_vip5f14838faac2c|172.21.16.88</interface> </pre> That is using a CARP VIP on WAN. Resaving the server config creates the correct values: <pre> - <interface>_vip5f14838faac2c|172.21.16.88</interface> + <interface>_vip5f14838faac2c</interface> + <ipaddr>172.21 ... ace means it cannot be resaved in the webgui.
- Bug #15096 (Resolved): Interface subnet aliases do not contain IPv6 VIPs
- While the tables _NETWORK not reflecting any IPv6 ULA as VIP at all, an ULA IPv6 connection from LAN is w ... 1702635139798 CE and Plus are affected.
- Bug #15057 (Resolved): Router Advertisement daemon does not prioritize IPv6 GUA over ULA
- When saving or reloading radvd service, the c ... mistakenly chosen as the track interface IPv6
- Regression #14987 (Not a Bug): ``Interface Address`` is no longer an option for outbound NAT targets
- After upgrading to version 23.09, the option ... ose. !clipboard-202311150941-pz0q7.png!
- Regression #14966 (Resolved): DHCP WAN with multiple (2+) IP Alias VIPs may show ``0.0.0.0`` as an interface address at boot
- On a system with a DHCP WAN and more than one IP alias VIP on the same interface the firewall may end u ... d Plus 23.09 with as few as 2 (two) IP Alias VIPs. The VIPs do not need to be in the same subnet as the ... ains on the interface, but @0.0.0.0@ and the VIPs are removed. Though it seems like it mig ... same way in the script with and without the VIPs present. It does not appear to affect op ... but something we need to address either way.