Search
Results (397)
- Bug #12227 (Resolved): Changing VHID on CARP VIP does not update VHID of related IP Alias VIPs
- 192.168.88.44 - CARP VIP (VHID: 1) 192.168.88.45 - IP Alias on CARP VIP: <pre> [2.6.0-DEVELOPMENT][root@pf100.home ... TO_LINKLOCAL> </pre> After changing CARP VIP VHID to 2, the IP alias remains on the old V ... options=21<PERFORMNUD,AUTO_LINKLOCAL> </pre>
- Regression #12217 (Resolved): Kernel panic in IPFW when using Captive Portal
- Starting around the 2.6.0 snapshot on August ... ap 0, rip = 0, rsp = 0, rbp = 0 --- </pre>
- Bug #12202 (Resolved): When a CARP VIP VHID change is synchronized to a secondary node, the CARP VIP is removed from the interface and the old VHIDs remain active
- Set up a CARP VIP between two nodes. Primary: <pre> vtnet4: ... MNUD,AUTO_LINKLOCAL> </pre> Hmm. The old VIP was also not cleared from the interface - CA ... INKLOCAL> </pre> Edit / Save / Apply the VIP on the secondary: <pre> vtnet4: flags=89 ... dmine any more. Sorry for any misformatting.)
- Feature #12169 (Resolved): IPsec keep alive option to initiate phase 2 without using ICMP
- Currently the IPsec GUI allows users to enter ... unction which likewise may be leveraged here.
- Bug #12132 (Duplicate): Port Fowards Using CARP VIP Form Validation on Source Broken
- With the interface address, you're able to de ... ce] address" such as "WAN Address" to a CARP VIP, when you go to save the second rule it will ... ifferent. Tested on pfSense Plus 21.05
- 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