Project

General

Profile

Actions

Feature #3025

closed

Allow Proxy Arp to Bind to CARP Interface

Added by Imrane Dessai over 12 years ago. Updated over 12 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
CARP
Target version:
-
Start date:
06/06/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Hi,

We are using a cluster pfSense to NAT 1:1 two network.

I need to make Proxy ARP VIP to bind to CARP Interface.

Now, it is not allowed.

Is it possible to make it work ?

What is important (for me) is to "expand" a full network with a single line of configuration

I also try with "Other" VIP, but same message.

Actions #1

Updated by Chris Buechler over 12 years ago

  • Status changed from New to Rejected

no need. IP alias or more CARP.

Actions #2

Updated by Imrane Dessai over 12 years ago

Ip Alias can't expand a whole network withing a single line of conf

When configuring a Proxy ARP you can specify a CIDR directly (a range of address ie 192.168.0.0/24 will be equivalent to 255 ip addresses)

With IP Alias or CARP we can only specify one address at a time.

Am I wrong ?

Actions #3

Updated by Jim Pingle over 12 years ago

IP Alias VIPs don't work that way, but proxy ARP VIPs are not and cannot be compatible in the way you describe.

On 2.1, "Other" type VIPs can work with a subnet mask to expand to an entire segment, but the subnet must be routed to you, it can't be your WAN subnet.

If the IPs in question are in an interface subnet, there is no way to do that properly for failover with "a single line of config". If the subnet is routed to you, use 2.1 and "Other" type VIPs. Either way, the original request as stated isn't possible.

Actions #4

Updated by Imrane Dessai over 12 years ago

Thanks a lot for your time and sorry for the useless ticket opening.

Actions

Also available in: Atom PDF