Date: Tue, 07 May 2019 08:29:02 +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-WQUosFXHYn@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 #8 from Andreas Pflug <pgadmin@pse-consulting.de> --- I can't post the original ruleset, but I shrinked it to a minimum and found= the line causing the problem on the WAN interface ix4: pass out log route-to ( ix4 ##.##.##.## ) from {ix4} to {!(ix4:network)} ke= ep state allow-opts ##.##.##.## is the WAN upstream default gateway. Without this line present = in the ruleset, the destination MAC will be 01:00:5e:00:00:12 as expected by t= he IP multicast address 224.0.0.18, but with this rule present the destination= mac is derived from the default gw ip address instead. NB: I'm observing wrong dst addresses on another interface as well, with more complicated symptoms. There's no stdgw present there, but two VIFs. One VIF will announce CARP using the partial IP of the other VIF, and the other VIF uses IP of a gateway on the same network. Didn't try to examine this furthe= r. --=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-WQUosFXHYn>