2017-09-27 22:33 GMT+02:00 Chris L :
>
>> On Sep 27, 2017, at 12:43 PM, dayer wrote:
>>
>> 2017-09-27 20:29 GMT+02:00 Steve Yates :
>>>I'm not sure if I am following you correctly, but the WAN CARP IP
>>> has to be the same on both
> On Sep 27, 2017, at 12:43 PM, dayer wrote:
>
> 2017-09-27 20:29 GMT+02:00 Steve Yates :
>>I'm not sure if I am following you correctly, but the WAN CARP IP has
>> to be the same on both routers. So router1 has a WAN of a.a.a.a and CARP of
>>
So you have both dual WAN and CARP?
--
Steve Yates
ITS, Inc.
-Original Message-
From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of dayer
Sent: Wednesday, September 27, 2017 2:43 PM
To: pfSense Support and Discussion Mailing List
Subject: Re:
Hi guys, It is too long to write how you can setup CARP. Well, I wrote an
article about CARP but not in English language, in my native language which
is Turkish. If you want to see you can go to my website, here :
https://lifeoverlinux.com/pfsense-2-2-carp-common-address-redundancy-konfigurasyonu/
2017-09-27 20:29 GMT+02:00 Steve Yates :
> I'm not sure if I am following you correctly, but the WAN CARP IP has
> to be the same on both routers. So router1 has a WAN of a.a.a.a and CARP of
> a.a.a.b, and router2 has a WAN of a.a.a.c and CARP of a.a.a.b. Same thing
I'm not sure if I am following you correctly, but the WAN CARP IP has
to be the same on both routers. So router1 has a WAN of a.a.a.a and CARP of
a.a.a.b, and router2 has a WAN of a.a.a.c and CARP of a.a.a.b. Same thing with
the LAN IPs.
--
Steve Yates
ITS, Inc.
-Original
2017-09-27 12:55 GMT+02:00 Jon Gerdes :
>
> On Wed, 2017-09-27 at 00:12 +0200, dayer wrote:
> > Hi everyone,
> >
> >
> > I'm getting this behavior and I can't find the reason. I've test the
> > same
> > scenario with pfSense 2.3.4 and 2.4.0-RC and I've posted in the
> >
On Wed, 2017-09-27 at 00:12 +0200, dayer wrote:
> Hi everyone,
>
>
> I'm getting this behavior and I can't find the reason. I've test the
> same
> scenario with pfSense 2.3.4 and 2.4.0-RC and I've posted in the
> forums
> without reply[1].
> I'm not sure if it's a configuration error or a bug,
Hi everyone,
I'm getting this behavior and I can't find the reason. I've test the same
scenario with pfSense 2.3.4 and 2.4.0-RC and I've posted in the forums
without reply[1].
I'm not sure if it's a configuration error or a bug, and I would prefer
confirm with someone expert.
Briefly, when