I have same errors in log and same behavior on one of my firewall
cluster. Carp flapping is a result of master system lagging and not
sending carp packets on time. You can workaround it by setting advbase
to some larger value, e.g. 10, but it will obviously still keep
lagging and dropping packets
> On 05 Jan 2016, at 13:06, Stefan Sperling wrote:
>
> On Tue, Jan 05, 2016 at 12:29:43PM +0100, Håkon Lerring wrote:
>> Hello misc.
>>
>> I was investigating a problem with a firewall that goes AWOL every week.
It
>> happens only if i activate an ipv6 address on a carp interface.
Hello misc.
I was investigating a problem with a firewall that goes AWOL every week. It
happens only if i activate an ipv6 address on a carp interface. The carp log
has this message:
Jan 5 12:10:06 /bsd: carp: packet size 48 too small
I think i have narrowed down the leak to the handling of
On Tue, Jan 05, 2016 at 12:29:43PM +0100, Håkon Lerring wrote:
> Hello misc.
>
> I was investigating a problem with a firewall that goes AWOL every week. It
> happens only if i activate an ipv6 address on a carp interface. The carp log
> has this message:
>
> Jan 5 12:10:06 /bsd: carp: packet
On 05/01/16(Tue) 12:29, Håkon Lerring wrote:
> Hello misc.
>
> I was investigating a problem with a firewall that goes AWOL every week. It
> happens only if i activate an ipv6 address on a carp interface. The carp log
> has this message:
>
> Jan 5 12:10:06 /bsd: carp: packet size 48 too small
5 matches
Mail list logo