Project

General

Profile

Search

Results (403)

Bug #3872 (Resolved): Enabling a disabled VLAN subinterface with multiple CARP VIPs configured causes system crash
When tagged VLAN interfaces have multiple CARP VIPs configured, disabling the interface via the ... WAN interface - untagged on em0 with 2 CARP VIPs configured. Disable/enable does not cause c ... - tagged with VLAN id 2 on em0 with two CARP VIPs configured. Disable/enable causes crash. EM2_Untagged interface - untagged on em2 with 2 CARP VIPs configured. Disable/enable does not cause c ... e - tagged with VLAN id 4 on em2 with 1 CARP VIP configured. Disable/enable does not cause cr ... e - tagged with VLAN id 5 on em2 with 2 CARP VIPs configured. Disable/enable causes crash. ... a couple of examples of the crash reports. 09/19/2014 07:25 AM
Bug #3855 (Resolved): Deleting an IP Alias using a CARP VIP as its interface does not fully get remove the IP from the secondary node
When you delete an IP Alias made using a CARP VIP as its interface, it does not get removed fr ... o reproduce: * On the primary, add IP Alias VIP using a CARP VIP as its interface * On the secondary, observe that the new VIP has synchronized as expected (shows in GUI and ifconfig) * On the primary, remove the IP alias VIP that was added above * On the secondary, note that the VIP is gone from the GUI, but is still present o ... se using 2.1.x in production in the meantime. 09/09/2014 12:15 PM
Bug #3846 (Resolved): Adding interface for new VLAN selects active WAN VIP address breaking connectivity
I utilize CARP for failover on WAN and have m ... om network port, which happens to be the wan_vip1 interface, breaking all connectivity to the ... sked what network port will be assigned to it 09/04/2014 07:54 AM
Bug #3811 (Closed): IP aliases on CARP w/IPsec getting mixed up on addition of a new VLAN.
Hi there, I've got a pair of boxes running ... vate networks and the public network. wan_vip11: flags=49<UP,LOOPBACK,RUNNING> metric 0 mt ... all of the "down" tunnels (because only some VIPs got swapped with others -- some were still ... .1 as the local endpoint being used, another VIP that is assigned as an IP alias to the same ... f those were using a different external CARP VIP which for some reason was NOT changed intern ... 3.1 and got remapped to 1.2.3.6 internally. 08/18/2014 04:38 AM
Bug #3807 (Resolved): Unable to edit existing Virtual IPs
Using "2.2-ALPHA (amd64) built on Fri Aug 15 ... ddress is being used by another interface or VIP. </pre> From the error message, could it ... ARP IP, instead of changing the existing one? 08/16/2014 04:16 AM
Feature #3806 (Resolved): Strongswan and CARP, initiator options
Putting this in a ticket so it isn't forgotte ... e automatically account for this when a CARP VIP is detected for binding. 08/15/2014 01:17 PM
Bug #3787 (Rejected): Outbound NAT to VIP AMD64 not working from OPT1 interface
No matter what I do and how I try to get it w ... or updates etc. AS soon as I change it to VIP, then it cannot connect to the internet. ... setting the OPT1 interface with ANY all over. 07/31/2014 11:40 AM
Bug #3773 (Resolved): Can't add an IP alias on lo0 through the web GUI in 2.2
In 2.2, if you go to Firewall->Virtual IPs an ... ut errors were detected: For this type of vip localhost is not allowed. This works in 2 ... to add one through the web interface. 07/24/2014 04:05 PM
Bug #3744 (Rejected): CARP IPs stuck in INIT on 2.2
On at least 32 bit. <pre> lan_vip10: flags=49<UP,LOOPBACK,RUNNING> metric 0 mt ... carp: INIT vhid 0 advbase 0 advskew 0 opt1_vip11: flags=49<UP,LOOPBACK,RUNNING> metric 0 mt ... carp: INIT vhid 0 advbase 0 advskew 0 opt2_vip12: flags=49<UP,LOOPBACK,RUNNING> metric 0 mt ... carp: INIT vhid 0 advbase 0 advskew 0 wan_vip13: flags=49<UP,LOOPBACK,RUNNING> metric 0 mt ... carp: INIT vhid 0 advbase 0 advskew 0 wan_vip14: flags=49<UP,LOOPBACK,RUNNING> metric 0 mt ... P MAC and more or less works minus failover. 07/06/2014 05:24 PM
Bug #3743 (Rejected): CARP status page broken on 2.2
Where CARP IPs are in INIT (at a minimum), St ... he "Status" column. ifconfig: <pre> lan_vip10: flags=49<UP,LOOPBACK,RUNNING> metric 0 mt ... carp: INIT vhid 0 advbase 0 advskew 0 opt1_vip11: flags=49<UP,LOOPBACK,RUNNING> metric 0 mt ... carp: INIT vhid 0 advbase 0 advskew 0 opt2_vip12: flags=49<UP,LOOPBACK,RUNNING> metric 0 mt ... carp: INIT vhid 0 advbase 0 advskew 0 wan_vip13: flags=49<UP,LOOPBACK,RUNNING> metric 0 mt ... carp: INIT vhid 0 advbase 0 advskew 0 </pre> 07/06/2014 04:21 PM
(281-290/403)