Andrew,
> I did not
> think the source IP was relevant to the matching code in linux, since
> there are no source squelching socket options.
>
> There are no firewall rules active on this machine, and the packets are
> definitely visible at the interface (see tcpdump output in my email).
The source address is not relevant (other than potentially
for firewall rules), and I understand from your original mail that
they are arriving at the machine. The IP TTL is what I wanted to
know there; but "netstat -s" will normally tell you why a packet
was dropped, if it's arriving but not making it through the UDP/IP
stack (as is your case).
> I am going to try upgrading the kernel, and turning off the multicast
> router kernel options as a next step. But if you have any other ideas
> at all, I'm all ears.
"netstat -s" would be a good start. :-) tcpdump receiving a copy
of the packet does not mean UDP or IP won't drop it, but those drops
are counted.
+-DLS
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
