Search
Results (397)
- Bug #4852 (Resolved): Unbound outgoing-interface not working with CARP VIPs
- When binding outgoing-interface in Unbound to ... <pre> outgoing-interface: Array </pre>
- Bug #4845 (Confirmed): CARP preemption doesn' ... vity between systems is lost but not NIC link
- Take a basic WAN and LAN setup, one CARP IP o ... en upon loss of connectivity on one network.
- Bug #4802 (Duplicate): OpenVPN Client wont st ... oot, when set to a Gateway Group specifing a VIP
- An OpenVPN Client won't start after reboot of ... ode, when set to a Gateway Group specifing a VIP.
- Bug #4685 (Resolved): Crash/panic "Sleeping thread owns a non-sleepable lock"
- Several reported similar panics have been hap ... starting with their relevant ticket numbers.
- Bug #4661 (Resolved): OpenVPN client can't assign to GWGroup specifying VIPs
- # Failover pfSense with CARP —> OpenVPN clien ... has no IPv4 address.?? How fix this error?
- Bug #4642 (Resolved): OpenVPN process status stopped... but its running
- Hi again... This is something i suffer con ... could someday be workarounded! Best regards!
- Bug #4633 (Resolved): CARP not enabled upon creation of first CARP IP
- On a new system, after creating a new CARP VIP, the CARP Status gadget for the dashboard sh ... with standard practice of always using CARP VIPs, and nothing indicates that CARP needs to be "enabled", whatever that means.
- Feature #4632 (New): Support for Multipath TCP (MPTCP)
- Hi, i have read a lot of articles about MP ... IBLE TO BUILD SYSTEMS LIKE THESE: http://www.viprinet.com Even IOS supports it for Siri! Kind regards and i would love to see this feature!
- Bug #4624 (Closed): VPN PPTP via Virtual IPs
- Hi, I do not know if that is a bug or not. ... I have the 2.2.1-RELEASE (i386) of PFsense.
- Bug #4602 (Not a Bug): Captive Portal pfSense 2.2 not working as before when used with CARP
- I feel that there might be a bug in captive p ... 192.168.4.78 and 192.168.4.79 sharing a CARP VIP of 192.168.4.1. The DHCP server provided 192 ... ll in backup mode while the gateway IP (CARP VIP 192.168.4.1) leads to the secondary firewall ... I suspect that the changed behavior is a bug.