Search
Results (717)
- Revision 52d4dc91: Fixes a bug where an IP alias on loopback interface is not initialized at boot.
- A recent change changed the IP alias setup to ... duplicate code and apply the same rules for VIPs and IP aliases. Ticket: #8393 Github PR: #3920
- 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?
- Revision d1f69741: Allow Dual Stack IPsec P1 interface. Fixes #6886
- Allow "Both" to be selected for IPv4/IPv6 on ... ddress. Doesn't make sense when selecting a VIP that is a single type, but should still hand ... edge cases that this doesn't handle properly.
- Revision b0e29e62: Fixed #8322 to accommodate case where no VIPs are defined
- Bug #8322 (Resolved): PPP UI error
- Warning: array_merge(): Argument #2 is not an ... erfaces_ppps_edit.php on line 507 and defined