Project

General

Profile

Actions

Bug #3846

closed

Adding interface for new VLAN selects active WAN VIP address breaking connectivity

Added by Brian Taber about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Category:
Interfaces
Target version:
Start date:
09/04/2014
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

Description

I utilize CARP for failover on WAN and have multiple VLANS. When adding a new VLAN that works fine, but when adding the interface for the new VLAN the system does not ask you what network port you want assigned, and grabs the first/random network port, which happens to be the wan_vip1 interface, breaking all connectivity to the firewall and breaking all external connectivity to the firewall.

When adding a new interface, the user should be asked what network port will be assigned to it

Actions #1

Updated by Ermal Luçi about 10 years ago

Can you provide more information on this.
It seems rather strange that you see this since it is not related in general.

Actions #2

Updated by Brian Taber about 10 years ago

it is basically an issue when adding a new interface, I do not think it is specifically related to CARP or VLANs . From the interfaces->assign screen, when you click the add button, the system does not ask you what network port you want assigned to the new interface, it just grabs an available one, which in my case happens to the the wan_vip1 (I am unsure how it decides what network port it decides to assign to the newly created interface).

basically, when you click the add button, the system should ask you what network port you want assigned to the new interface before creating it, currently it does not ask the user anything when clicking the add button, it just creates an interface and assigns whatever network port if feels like

Actions #3

Updated by Renato Botelho about 10 years ago

  • Assignee set to Renato Botelho
  • Priority changed from Urgent to Normal
Actions #4

Updated by Renato Botelho about 10 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #5

Updated by Chris Buechler about 10 years ago

  • Status changed from Feedback to Resolved

fixed

Actions

Also available in: Atom PDF