Search
Results (711)
- Revision f003f8db: Some small improvements to OpenVPN server handling when using CARP VIPs in Gateway Groups. Might help with issue #6607
- Revision 51d2e735: Some small improvements to OpenVPN server handling when using CARP VIPs in Gateway Groups. Might help with issue #6607
- Bug #6657 (Not a Bug): Unable to add network in the source section of a LAN firewall rule
- Since 2.3.2-RELEASE, the following causes an ... le Host 8.8.8.8, any ports 3. Click Save
- Bug #6607 (Not a Bug): OpenVPN server won't s ... , when set to a Gateway Group specifing CARP VIPs
- No problem for OpenVPN clients. When OpenVPN server is set to a simple CARP VIP, it will start after reboot. When CARP fa ... (when set to a Gateway Group specifing CARP VIPs).
- Bug #6605 (Confirmed): rc.linkup logic issues with actions taken
- The actions taken by rc.linkup differ dependi ... e interface_bring_down function removes CARP VIPs from the interface. If you have a static v4 ... ch makes the secondary take over for the WAN VIPs. What actually happens is it increments demotion by 240, fails over to the secondary, then the VIP is deleted from the LAN on primary so demotion gets a +240 on the primary because the VIP is gone, and the primary takes back over mas ... ld never be run on an interface where a CARP VIP resides to avoid this situation. It's questi ... eview, testing and time to run in snapshots.
- Bug #6579 (Resolved): IPv6 CARP VIPs lost upon config sync where they include non-significant zeros
- If you have IPv6 CARP VIPs specified with non-significant zeros, such ... 12::1, the secondary will see that as an old VIP and delete it upon config sync. The mwex ... L311 Because it ends up being part of $oldvips array. The OS doesn't show the non-signific ... ferences into account and omits from the $oldvips array.
- Revision ac3e3baa: Only call interfaces_vips_configure once if it's needed, rather than doing the same thing over and over for every VIP on an interface. Ticket #6515
- Revision 6fd9645e: Only call interfaces_vips_configure once if it's needed, rather than doing the same thing over and over for every VIP on an interface. Ticket #6515
- Revision d75c55fb: Only call interfaces_vips_configure once if it's needed, rather than doing the same thing over and over for every VIP on an interface. Ticket #6515
- Bug #6515 (Resolved): link_interface_to_vips slow with large numbers of VIPs
- link_interface_to_vips when called with the update parameter calls interfaces_vips_configure once per VIP on the interface, so it repeats the same act ... entirety over and over. With a few thousand VIPs, that adds minutes of unnecessary delays to anything that calls link_interface_to_vips with update.