> On 4 Aug 2016, at 04:59, Jason Litzinger wrote:
>
Testing multicast is ... challenging. I barely have any idea how to set
up a test environment for IPv4, and no idea what to do for IPv6. If you
can speak to this in your tests (and hopefully docs as well) that would be
> When you say *no* interfaces, do you mean actually no interfaces? As in, no
> loopback as well?
I do not, sorry, that was poorly worded. The loopback interface was
up for all test runs, and all other interfaces on my machine (ethernet
and wifi) were down. Down in this context has two meanings
> On 4 Aug 2016, at 17:03, Jason Litzinger wrote:
>
>> When you say *no* interfaces, do you mean actually no interfaces? As in, no
>> loopback as well?
>
> I do not, sorry, that was poorly worded. The loopback interface was
> up for all test runs, and all other interfaces on my machine (ether
On Thu, 4 Aug 2016 at 18:04 Jason Litzinger wrote:
> I did try specifying the loopback index, however, I received a
> "Network Unreachable" error. I didn't have time to dig into whether
> it was possible to do what I wanted with the loopback interface last
> night.
>
By default, the "multicast"
> By default, the "multicast" flag is not enabled for the loopback interface
> on Linux. Does running "ip link set dev lo multicast on" help here?
> (Although requiring this would then be rather problematic for testing, as
> doing this in containerized environments and restricted environments like
