Project

General

Profile

Bug #4390

Cannot create an IP alias on a CARP interface where the actual Interface address is in a different network

Added by Xuridisa Support over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Virtual IPs
Target version:
Start date:
02/08/2015
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.2
Affected Architecture:

Description

I have configured the WAN IP addresses to be private addresses (i.e. in the 10.0.254.0/30 network) so that I can preserve all public addresses for use as CARP/IP Alias. I have CARP address being the first usable public IP address which is fine (although config has carried over from when WAN addressing were legitimate public addresses). When I try and create the IP aliases addresses, using the WAN CARP address as the Interface I get as error as below:

Sorry, we could not locate an interface with a matching subnet for <private network range>. Please add an IP alias in this subnet on this interface.

Associated revisions

Revision 810b36ac (diff)
Added by Ermal Luçi over 4 years ago

Fixes #4390 Properly return the vip subnet now that the CARP might not match its parent interface subnet.

Revision eaa89cc6 (diff)
Added by Ermal Luçi over 4 years ago

Ticket #4390 Return only the subnet bits not the full network in cidr format.

History

#1 Updated by Chris Buechler over 4 years ago

  • Project changed from pfSense Packages to pfSense
  • Category set to Virtual IPs

#2 Updated by Ermal Luçi over 4 years ago

  • Status changed from New to Feedback

It behaves correctly with the applied patch.

#3 Updated by Ermal Luçi over 4 years ago

  • % Done changed from 0 to 100

#4 Updated by Chris Buechler over 4 years ago

  • Status changed from Feedback to Resolved

fixed

Also available in: Atom PDF