> it seems that 2.1.x requires an explicit route for sending packets to
> multicast addresses ?
Yes.
> 2.0 worked nicely enough without any such route, but
> if I don't do a
> route add -net 224.0.0.0 netmask 240.0.0.0 eth0
> in 2.1, multicast packets get forwarded to the default gateway (gateway's
> ether address in header rather than multicast ether addr).
> maybe I didn't look hard enough, but I couldn't find this documented
> anywhere.
It was bad idea, because it made gatewayed multicasts impossible
and bypassed routing tables.
Alan, should I restore it? Argument pro: NBMA multicasting is not
finished in any case and this thing really will confuse folks, who
did not create multicast routes. From the other hand, I think
this feature will die in any case and very soon. I'd prefer that kernel
did the things, which prescribed by routing tables, rather than making
some not overridable hacks hardwired to code.
Alexey Kuznetsov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html