> 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.
I wouldnt expect them to be. The lo interface does no
> > 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
>
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
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.
I wouldnt expect them to be. The lo interface does not support
> 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 option
In developing multicast applications, I would like to be able to test
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.
This route statement is not necessary with
In developing multicast applications, I would like to be able to test
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.
This route statement is not necessary with
7 matches
Mail list logo
