Solved: /bsd: carpN: ip_output failed: 65

2012-01-16 Thread Markus Wernig
Hi all Disbling ipv6 on the ifs didn't help. It turned out pf was blocking the outgoing carp advertisements on 2 out of 4 interfaces without logging. Adding keep state (no-sync) to the carp rules, activating them, and then flushing states on both firewalls finally brought the cluster back to

Re: /bsd: carpN: ip_output failed: 65

2012-01-16 Thread Henning Brauer
* Markus Wernig liste...@wernig.net [2012-01-15 16:19]: After upgrading to 5.0 (and also on -current) I keep getting those errors for 2 out of 4 carp'd interfaces in a fw cluster pair: /bsd: carp2: ip_output failed: 65 /bsd: carp3: ip_output failed: 65 i bet pf is blocking your carp

/bsd: carpN: ip_output failed: 65

2012-01-15 Thread Markus Wernig
Hi all After upgrading to 5.0 (and also on -current) I keep getting those errors for 2 out of 4 carp'd interfaces in a fw cluster pair: /bsd: carp2: ip_output failed: 65 /bsd: carp3: ip_output failed: 65 And effectively, no CARP traffic is seen on those two interfaces, neither in nor out. Both