Re: mbuf leak in carp with ipv6

2016-01-13 Thread Martin Hlavatý
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

Re: mbuf leak in carp with ipv6

2016-01-07 Thread Håkon Lerring
> 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.

mbuf leak in carp with ipv6

2016-01-05 Thread Håkon Lerring
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

Re: mbuf leak in carp with ipv6

2016-01-05 Thread Stefan Sperling
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

Re: mbuf leak in carp with ipv6

2016-01-05 Thread Martin Pieuchot
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