> > locally over the loopback interface. This does not work without adding a
> > bogus route statement to get the kernel to hand up the packets from
> > loopback to my waiting application.
> The multicast ABI includes the ability to toggle loopback of multicast
> datagrams. Use the socket options instead
I read that multicast loopback is by default enabled, and I have witnessed
this, when having my application bind to my ethernet interface, but the
datagrams do not seem to be looped back when I bind to the 'lo' interface.
Could this possibly be a conflict with the inherently 'looped back'
behavior of the loopback net driver?
As far as toggling the flag, or even reading it, I cannot, as I am
developing in Java.
For developing, I can easily kludge it to work, by adding a fake route
statement, forcing the packets back up to the application, but I want to
make sure the differing behavior is not a bug in the kernel networking
-Erik G. Burrows
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Feb 15 2001 - 21:00:25 EST