On 1 October 2011 11:04, johan Hendriks wrote:
> Op 29-09-11 16:49, Damien Fleuriot schreef:
>>>
>>>
>>> Quick follow-up again.
>>>
>>> This is the code for sys/netinet/ip_carp.c on FreeBSD 8.2, OpenBSD
>>> 3.8, OpenBSD 3.9 in function carp_setrun(struct carp_softc *sc,
>>> sa_family_t af)
>>>
>>>
Op 29-09-11 16:49, Damien Fleuriot schreef:
Quick follow-up again.
This is the code for sys/netinet/ip_carp.c on FreeBSD 8.2, OpenBSD
3.8, OpenBSD 3.9 in function carp_setrun(struct carp_softc *sc,
sa_family_t af)
FREEBSD 8.2-PRERELEASE with init + preempt => auto MASTER bug
Function start
>
>
>
> Quick follow-up again.
>
> This is the code for sys/netinet/ip_carp.c on FreeBSD 8.2, OpenBSD
> 3.8, OpenBSD 3.9 in function carp_setrun(struct carp_softc *sc,
> sa_family_t af)
>
>
>
> FREEBSD 8.2-PRERELEASE with init + preempt => auto MASTER bug
> Function starts at line 1371.
> --
On 29 September 2011 14:20, Damien Fleuriot wrote:
>
>
> On 9/15/11 11:07 AM, Damien FLEURIOT wrote:
>> Hello list,
>>
>>
>>
>>
>> TLDR: carp interface becomes MASTER for a split second after being
>> created, even if another MASTER exists on the network with faster
>> advertisements. Breaks conne
On 9/15/11 11:07 AM, Damien FLEURIOT wrote:
> Hello list,
>
>
>
>
> TLDR: carp interface becomes MASTER for a split second after being
> created, even if another MASTER exists on the network with faster
> advertisements. Breaks connections. HOWTO prevent ?
>
>
>
>
> We've been experiencin
On 18 Sep 2011, at 12:44, Patrick Lamaiziere wrote:
> Le Sat, 17 Sep 2011 23:40:06 -0400 (EDT),
> "Brian Seklecki (Mobile)" a écrit :
>
>>>
What would help here, is for a carp interface to wait a given delay
(tunable through a sysctl ?) after creation or after being brought
up
Le Sat, 17 Sep 2011 23:40:06 -0400 (EDT),
"Brian Seklecki (Mobile)" a écrit :
> >
> >> What would help here, is for a carp interface to wait a given delay
> >> (tunable through a sysctl ?) after creation or after being brought
> >> up
>
> I see now.
>
> The tunable sounds like a good idea; we s
What would help here, is for a carp interface to wait a given delay
(tunable through a sysctl ?) after creation or after being brought up
I see now.
The tunable sounds like a good idea; we should check OpenBSD, they
probably already implemented something and we're behind.
If not, a "preemp
On Sep 15, 2011, at 23:14 , Damien Fleuriot wrote:
> What would help here, is for a carp interface to wait a given delay
> (tunable through a sysctl ?) after creation or after being brought up
> from down.
I have the same observation. Perhaps it can just avoid going up initially ---
it will bec
On 15 September 2011 18:12, Brian Seklecki (Mobile)
wrote:
>> Things went smoothly but when we brought the production VLANs up again
>> at layer 2 on the switches, when spanning-tree converged we had again a
>> double MASTER problem.
>>
>
>
> In older versions of FBSD, creating logical interfaces
Things went smoothly but when we brought the production VLANs up again
at layer 2 on the switches, when spanning-tree converged we had again a
double MASTER problem.
In older versions of FBSD, creating logical interfaces like vlan(4) and
carp(4) had an nasty inadvertent side effect of togglin
Posting to -stable since -pf didn't show much interest :/
Original Message
Subject: CARP interfaces and mastership issue
Date: Thu, 15 Sep 2011 11:07:37 +0200
Hello list,
TLDR: carp interface becomes MASTER for a split second after being
created, even if another M
12 matches
Mail list logo
