Wow, thanks for the detailed rundown on multicast routing, Adrian.

So anyone correct me if I'm wrong, but it sounds like is the current status quo is:

- You can run an SSB peer and give it a fixed IP on the mesh which your friends can sync with, if they know that IP.

- If that device is running Babel, they will also be able to keep syncing with it as you move around and connect with different mesh peers.

What people want to accomplish with multicast is:

- You can run an SSB peer, on a client device. Your friends will receive multicast traffic informing them of which IP your peer is currently accessible at.

Is this correct?

On Thu, Apr 13, 2017 at 3:19 PM, Adrian Chadd <adrian@freebsd.org> wrote:

On 13 April 2017 at 15:11, Marc Juul <juul@labitat.dk> wrote:
>
>
> On Thu, Apr 13, 2017 at 3:01 PM, Adrian Chadd <adrian@freebsd.org> wrote:
>>
>> Hi,
>>
>> Hm, maybe make it use mDNS and run an mDNS relay to go between
>> multiple subnets (for a subset of mDNS, or hilarity ensues.)
>
>
> Yes we did discuss doign that but then why not mrouted + a filter?

You can try both! heh.

mrouted +kernel multicast should be fine on linux these days, it's
just more moving parts versus just broadcast sockets and UDP. :-)

A lot of old timer-y people are leery of multicast and mrouted
because, well, it's not exactly been a path well traveled. So give it
a go and see what happens.

-adrian