Date: Wed, 08 May 2019 06:57:53 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 234472] CARP using wrong multicast MAC destination (was: Missing outgoing CARP traffic on interface) Message-ID: <bug-234472-7501-ty5ppaIv1g@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234472-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-234472-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234472 --- Comment #12 from Andreas Pflug <pgadmin@pse-consulting.de> --- Well applying routing to a non-routable protocol (in the sense of normal IP routing) seems not too sensible in any case. Maybe omitting 224.0.0.0/4 from routing unless it's specified explicitely might be a solution. Should be probably discussed elsewhere. In my very first post, I mentioned an early pass out quick wouldn't help either: I tested again, and now it works, maybe not flushing the rules was = the problem back then. pass out quick carp from {(self)} to 224.0.0.18 is the fix for misformed CARP packets. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234472-7501-ty5ppaIv1g>