Search
Results (717)
- Revision 4b46e9b1: Fix OpenVPN server listening on associated IPv6 address
- As reported in forum https://forum.pfsense.or ... rface. If the interface has other associated VIPs (e.g. a CARP VIP) and the related IPv6 entry is selected as t ... r IPv6 as does the appropriate stuff with it.
- Revision 1d421723: When deleting a VIP check it is not used by OpenVPN
- I noticed this when cleaning up VIPs and OpenVPN server when testing for this fo ... pic=92174.0 The system let me delete my test VIP before I deleted the OpenVPN server using, p ... a clue about which OpenVPN instance uses the VIP.
- Revision 52856a80: When deleting a VIP check it is not used by OpenVPN
- I noticed this when cleaning up VIPs and OpenVPN server when testing for this fo ... pic=92174.0 The system let me delete my test VIP before I deleted the OpenVPN server using, p ... a clue about which OpenVPN instance uses the VIP.
- 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.
- Revision e27bc6cf: Fix OpenVPN server listening on associated IPv6 address
- As reported in forum https://forum.pfsense.or ... rface. If the interface has other associated VIPs (e.g. a CARP VIP) and the related IPv6 entry is selected as t ... r IPv6 as does the appropriate stuff with it.
- Feature #4597 (Duplicate): Allow gateway monitoring via VIP
- I've been playing with the new CARP implement ... .x The ability to float a single public CARP VIP on two nodes is useful in some situations, ... e the monitoring traffic via the public CARP VIP. Not sure if this is feasible with apinger, ... mind if a replacement for apinger is written.
- Bug #4596 (Duplicate): NAT 1:1 vs VIP, limiters works on LAN, but on WAN breaks NAT
- I use this configuration on PfSense 2.1.5 and ... limiters on WAN breaks NAT 1:1. - Several VIPs on WAN (PARP or IPAlias, is the same..) - 1:1 NAT from VIPs to LAN IPs - Limiters on LAN IPs (to limit ... If I disable limiters on WAN works fine.
- Revision 486d7278: Fix IPsec on CARP IPs, broken when fixing IPsec with gateway groups and VIPs.
- Revision 74c749be: Fix IPsec on CARP IPs, broken when fixing IPsec with gateway groups and VIPs.
- Revision c8a4eb40: Save vip interface and subnet to use to delete old vips from secondary nodes. Fixes #4446