Search
Results (402)
- Bug #12075 (Resolved): Changes to an existing ... not applied on HA secondary after XMLRPC sync
- When synchronizing settings over XMLRPC, the ... ter but that could be prone to timing issues.
- Bug #12071 (Closed): Responder Only IPsec tun ... secondary node when a failover happens in HA
- Normally with an IPsec tunnel on a pfSense HA ... n 21.05 nodes, and a remote pfSense instance.
- Feature #12055 (Closed): Option to disable XMLRPC Sync for Loopback Virtual IPs
- According to this pfSense doc, Loopback IPs a ... ific virtual IPs so that they don't conflict.
- Todo #12025 (New): Add 1:1 Validation to Notify Someone They are 1:1 NAT'ing an Interface Address
- Although it is VERY rarely necessary, we shou ... verify against an HA member as well or CARP VIP as it can sometimes be easy to forget that y ... ateway monitoring to fail on that interface).
- Bug #12006 (Duplicate): CARP IP sometimes doesn't apply to CARP member
- I noticed this when a CARP member had no CARP status. I was told that this can happen if the VIP address isn't applied to a member. I sa ... er which had a blank CARP status didn't have VIP IP applied to it. In this case, it was the ... aded the VM. I saw it on: 2.5.1-RELEASE
- Feature #11957 (Resolved): XMLRPC synchronization for DHCP relay settings
- Configuration synchronization (XMLRPC) does n ... dary box… I have two other personal examples.
- Feature #11954 (New): Multicast limits
- On my two XG-1541, I have configured 1 LAGG, ... n igmpproxy. Cause: igmpproxy sees each CARP VIP as a network interface so it tries to bind() on it and reaches MAXVIFS. * The more VIP we add on multicast-enabled interfaces, the ... t-enabled interface can't have more than six VIPs on it. Otherwise igmpproxy refuses to start ... n all of our VLANs, XX = 21 (obviously, only VIPs on multicast-enabled VLANs are counted). Wi ... tination NAT, XX = 20. If we add additionnal VIPs on these multicast-enabled VLANs, XX = 19. ... is my justification for this feature request.
- Bug #11864 (Resolved): OpenVPN stays bound to previous IP address after interface changes
- Setup: OpenVPN listening on UDP IPv4 on a VIP or physical interface. Steps to recreate: ... ted: https://redmine.pfsense.org/issues/9660
- Bug #11816 (Resolved): RFC 2136 Dynamic DNS client uses IPv6 alias VIP instead of Track IPv6 address for AAAA records
- https://forum.netgate.com/topic/163023/ddns-r ... iven instead of the GUA." see also #5999
- Regression #11805 (Resolved): Port forward ru ... ly-to`` does not work for Multi-WAN (CE Only)
- Port forwards coming into the firewall from a ... ly on WAN2, not via port forwarding, works.