Re: [pfSense] 2.3-REL, HA, WAN CARP IPv6 MAC seen as active on both NICs

2016-05-13 Thread Olivier Mascia
> Le 3 mai 2016 à 11:17, Olivier Mascia a écrit : > >> Le 3 mai 2016 à 09:49, Chris Buechler a écrit : >> >>> Or would it be that my BACKUP (according to /status_carp.php) do also >>> advertise (which it shouldn't as BACKUP)? >> >> That's the problem. I'm seeing that in some cases and not oth

Re: [pfSense] 2.3-REL, HA, WAN CARP IPv6 MAC seen as active on both NICs

2016-05-04 Thread Olivier Mascia
We're on 2.2.6. > > "CARP is not permitted on their equipment" > > Is that even possible? How would they prevent that other than tying the IP > address to a MAC address? > > -- > > Steve Yates > ITS, Inc. > > -Original Message----- >

Re: [pfSense] 2.3-REL, HA, WAN CARP IPv6 MAC seen as active on both NICs

2016-05-04 Thread Steve Yates
4, 2016 5:12 AM To: pfSense Support and Discussion Mailing List Subject: Re: [pfSense] 2.3-REL, HA, WAN CARP IPv6 MAC seen as active on both NICs > Le 3 mai 2016 à 11:17, Olivier Mascia a écrit : > >> Le 3 mai 2016 à 09:49, Chris Buechler a écrit : >> >>> Or woul

Re: [pfSense] 2.3-REL, HA, WAN CARP IPv6 MAC seen as active on both NICs

2016-05-04 Thread Olivier Mascia
> Le 3 mai 2016 à 11:17, Olivier Mascia a écrit : > >> Le 3 mai 2016 à 09:49, Chris Buechler a écrit : >> >>> Or would it be that my BACKUP (according to /status_carp.php) do also >>> advertise (which it shouldn't as BACKUP)? >> >> That's the problem. I'm seeing that in some cases and not ot

Re: [pfSense] 2.3-REL, HA, WAN CARP IPv6 MAC seen as active on both NICs

2016-05-03 Thread Olivier Mascia
> Le 3 mai 2016 à 09:49, Chris Buechler a écrit : > >> Or would it be that my BACKUP (according to /status_carp.php) do also >> advertise (which it shouldn't as BACKUP)? > > That's the problem. I'm seeing that in some cases and not others with > IPv6 CARP in 2.3, with no apparent reason as to w

Re: [pfSense] 2.3-REL, HA, WAN CARP IPv6 MAC seen as active on both NICs

2016-05-03 Thread Chris Buechler
On Mon, May 2, 2016 at 5:43 PM, Olivier Mascia wrote: > Sorry, top-posting this time. > > Capturing on WAN(x:y:z:d8ff::2/64), link-local = fe80::250:56ff:febf:7014 (is > MASTER), I can see: > > 00:15:27.653423 IP6 (hlim 255, next-header VRRP (112) payload length: 36) > fe80::250:56ff:febf:7014 >

Re: [pfSense] 2.3-REL, HA, WAN CARP IPv6 MAC seen as active on both NICs

2016-05-02 Thread Olivier Mascia
> Le 2 mai 2016 à 20:24, Olivier Mascia a écrit : > > I have a problem with IPv6 on a HA setup. > > With IPv4, it is OK. > >> IPv4 : >> VLAN MAC Address TypeAge Port >> Mod >> -+-+---+-+-

Re: [pfSense] 2.3-REL, HA, WAN CARP IPv6 MAC seen as active on both NICs

2016-05-02 Thread Olivier Mascia
Sorry, top-posting this time. Capturing on WAN(x:y:z:d8ff::2/64), link-local = fe80::250:56ff:febf:7014 (is MASTER), I can see: 00:15:27.653423 IP6 (hlim 255, next-header VRRP (112) payload length: 36) fe80::250:56ff:febf:7014 > ff02::12: ip-proto-112 36 00:15:28.663409 IP6 (hlim 255, next-head

[pfSense] 2.3-REL, HA, WAN CARP IPv6 MAC seen as active on both NICs

2016-05-02 Thread Olivier Mascia
I have a problem with IPv6 on a HA setup. With IPv4, it is OK. > IPv4 : > VLAN MAC Address TypeAge Port > Mod > -+-+---+-+--+--- > 2776 .5e00.0168dynamic 0 Veth5