Netmask surely
has a relation to broadcast packets, but not multicast.
Several user on this list use /32 (255.255.255.255) netmask on their
tunl0 interface.
It is not completely clear to me what the netmask on tunl0 really does.
I understand what it does on a local network, but not for tunl0.
For the routing, it does not appear to influence anything. And at least by
setting it this way, I avoid having that unclear route for 44.0.0.0/8 that is added
when tunl0 is created. Maybe it breaks multicast, but I don't know how.
My tunl0 has a netmask of 255.255.255.255, and multicast works fine.
I've always used a netmask of 255.255.255.255 for the tunnel
interface, since I don't want an interface route to be generated
automatically either.
The actual tunnel routes inserted by the RIP daemon or munge script
are the ones doing routing, anyway.
- Hessu