Bruce M. Simpson wrote:
Max Laier wrote:
Alternatively you could change IPPROTO_CARP in netinet/in.h to another
unused protocol number. This is really the preferred way of dealing
with mixed CARP and VRRP environments as the CARP packets might in
turn irritate the VRRP routers, too.
This
Max Laier wrote:
Alternatively you could change IPPROTO_CARP in netinet/in.h to another
unused protocol number. This is really the preferred way of dealing with
mixed CARP and VRRP environments as the CARP packets might in turn
irritate the VRRP routers, too.
This sounds like a common use c
On Friday 14 December 2007, Bruce M. Simpson wrote:
> Tom Judge wrote:
> > I guess that there will be more than one VRRP implementation that
> > does not generate packets with a header the same size as the carp
> > header.
> >
> > I will look into generating a patch for this over the weekend,
> > h
Tom Judge wrote:
I guess that there will be more than one VRRP implementation that does
not generate packets with a header the same size as the carp header.
I will look into generating a patch for this over the weekend,
however any thoughts/suggestions would be appreciated before I start
wor
Hi,
I have just looked into the source of an error that we are seeing a lot
on our FreeBSD 6.2-p5 systems. The error is:
"carp_input: received len 20 < sizeof(struct carp_header)"
The messages are coming from a pair of systems that are configured to
have a pair of load balancing carp interfa
