Yes, get them now. If you don’t then they’ll go to someone else and you won’t
be able to expand in a contiguous block. Using CARP implies that you care
about reliability during edge cases and partial failures. If so, then you need
to do it right and use 3 IPs where you want 1 carp. 3 on uplink A, 3 on uplink
B, 3 on each internal network that you are providing services to.
If you are concerned more with cost, simplicity, or are just plain willing to
drive to the office when the network goes flaky then don’t use CARP. I don’t
see a scenario where the complexity of CARP is justified but not the cost of
the extra IP space. Cold spare with a recent config backup provides you with
much of the same reliability and minimal downtime but reduces cost, complexity,
and IP space.
ED.
> On 2015, Mar 2, at 11:47 AM, Steve Yates <[email protected]> wrote:
>
> Steve Yates wrote on Mon, Mar 2 2015 at 9:09 am:
>
>> I received an email directly...to perhaps shorten my example, if we
>> have two public subnets 1.1.1.0/28 and 2.2.2.0/28, I would like to use both
>> of
>> those subnets on different servers, use pfSense as the firewall, and use
>> CARP.
>> Is there a way to do that and minimize the number of IPs used?
>
> Having had more coffee...by "on different servers" let's assume 8 IPs
> in each subnet would be in use.
>
> I'm trying to plan for a couple years down the road when we need more
> IPs from the data center, to see if it's better to get a larger block now
> even though it won't all be used for a while.
>
> --
>
> Steve Yates
> ITS, Inc.
>
> _______________________________________________
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
