Search
Results (397)
- Feature #8474 (New): Easier Conversion to HA Pair from Existing Non-HA Firewall
- Requesting perhaps a guided wizard built-in t ... r having up to 3 WAN IP's including the CARP VIP; it seems rather tedious to go HA if not on a fresh install even with 2.4.x
- Bug #8465 (Resolved): Lost default gateway after recover from failover with CARP VIP and HA
- Both boxes works with SuperMicro Boards which ... also set (This firewall, WAN Interface, CARP VIP). External IP Currently there are 4 static external IPs configured as CARP VIP. The "master" IP for outgoing traffic is ... for some machines, ports and the other CARP VIPs, i.e. outgoing mail is the IP of the MX rec ... restored with c) but not with a) or b)?
- Bug #8424 (Duplicate): IPv6 stops working com ... erfaces that use interface tracking and have VIPs configured on them
- If you have a downstream interface configured ... ned prefix (my isp gives a /56) and you have VIPs configured on the same interface (ie. fd00: ... ining both the pd-assigned addresses and the VIP networks since connectivity policy logic doe ... Reproductible: always Workaround: remove VIPs from interface and reboot, assign vips again after reboot. Notes: I have not trie ... _all_ interfaces or just the ones that have VIPs assigned to them. This setup is very common ... the root cause originates from the same stem.
- Bug #8408 (Resolved): invalid rule written due to ipv6 ipalias being present
- The following rule is generated due to a IPv6 ... present, this is supposed to fill a array of vips6 , but adds a mode item for the vips array. This causes the empty rule.. <pre> ... https://github.com/pfsense/pfsense/pull/3924
- Bug #8395 (Duplicate): #6677 broke IP Aliases on loopback interfaces
- The fix for #6677 broke IP Aliases on loopbac ... reboot. Re-applying the config after a no-op VIP edit fixes this until the subsequent reboot. ... loopback interface has no "enable" attribute.
- Bug #8393 (Resolved): IPAlias VIPs on localhost are not applied at boot.
- An VIP configured like: <pre> <vip> <mode>ipalias</mode> <interface>lo0</in ... bnet_bits> <subnet>192.168.0.1</subnet> </vip> </pre> Is not present after booting: < ... roups: lo </pre> But after resaving the VIP via the GUI is added: <pre> [2.4.3-RELEASE ... It does not affect other real interfaces.
- Bug #8386 (Not a Bug): Virtual IPs not considered as part of interface net
- Every network interface with ips configured h ... get forgotten to be added to this new alias.
- Bug #8359 (Not a Bug): Packets from phase1 bound to CARP VIP do not have the right source address
- Hello, I have a cluster with one member having a wan IP of 192.168.0.1. I have configured a CARP VIP of 192.168.0.10 on the wan interface. I hav ... configurations, all of them are bound to the VIP Interface and the ipsec logs show: <pre> c ... shows that the packets are not sent from the VIP but from the interface address: <pre> IP 1 ... n order for my packets to originate from the VIP and not the interface address. I have a s ... ual packet makes me think that this is a bug.
- Feature #8346 (New): Allow pfSense to act as an IPsec VPN client
- It would be useful to let pfSense act as a VP ... ss and other settings from the server (e.g. "vips" config in strongSwan, along with other set ... ly exist, which complicates things further.
- Bug #8341 (Rejected): NAT Port forwarding issues (port collision from internal host)
- I think this should be omitted by design: Fo ... s something that should be solved internally?