https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234472
--- Comment #10 from Andreas Pflug <pgad...@pse-consulting.de> ---
AFAICS the rule actually does as advised, since naively speaking 224.0.0.18
isn't in the ix4 network and so anything should be routed to the stdgw.
But it's IP multicast, and so route-to shouldn't be applied in any case on
224.0.0.0/4, according to RFC1112.
I added "pass out quick from {ix4} to 224.0.0.0/4" before that route-to rule,
preventing the misshaped multicast packet.
So actually pf does as advised to straight forward, but this will break
multicast specifications. IMHO pf should implement the special behaviour on
multicast packets implicitely, i.e. excepting them from routing, because this
issue has been around for years without being diagnosed correctly (probably
blaming some innocent switch IGMP implementations), and users probably don't
expect a standard default gateway routing command breaking local multicast
traffic.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
