https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234472
--- Comment #11 from Kristof Provost <k...@freebsd.org> --- I'm not sure that's a good idea for a change. As you say, you can solve your problem by telling pf to not route-to for the multicast subnet, but if we'd add the (also somewhat unexpected) implicit behaviour of not doing that for multicast ranges there'd be no way to configure what you just ran into. You might not want to have route-to rewrite the MAC address, but there's certainly cases where you'd want it to route out of a different interface (which is possible if you don't specify an IP address with the route-to). I also don't think we should make that impossible. -- 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"
