[B.A.T.M.A.N.] link local mcast

[B.A.T.M.A.N.] link local mcast

[ecfu]

[-- Attachment #1: Type: text/plain, Size: 75 bytes --]

Does Batman Adv provide correct mcast routing for link-local mcast groups?

[-- Attachment #2: Type: text/html, Size: 224 bytes --]

Re: [B.A.T.M.A.N.] link local mcast

[Marek Lindner]

On Thursday 07 January 2010 22:35:50 ecfu wrote:
> Does Batman Adv provide correct mcast routing for link-local mcast groups?

Yes, all multicast packets are simply flooded through the whole network.

Regards,
Marek

Re: [B.A.T.M.A.N.] link local mcast

[ecfu]

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

I guess I am confused then...  I am trying to see my avahi services on the
other side of a hop.  the middle node sees the services of both ends, but
the ends do not see the services of each other.  After talking to the Avahi
users group, they seemed to think this had something to do with batman
advanced implementation of its mcast routing.  If you say they are flooded
through the network, is there another reason why I wouldn't see the mDNS
broadcasts over the hop?

Thanks

On Thu, Jan 7, 2010 at 12:52 PM, Marek Lindner <lindner_marek@yahoo.de>wrote:

> On Thursday 07 January 2010 22:35:50 ecfu wrote:
> > Does Batman Adv provide correct mcast routing for link-local mcast
> groups?
>
> Yes, all multicast packets are simply flooded through the whole network.
>
> Regards,
> Marek
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@lists.open-mesh.org
> https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n
>

[-- Attachment #2: Type: text/html, Size: 1420 bytes --]

Re: [B.A.T.M.A.N.] link local mcast

[Marek Lindner]

On Friday 08 January 2010 05:12:33 ecfu wrote:
> I guess I am confused then...  I am trying to see my avahi services on the
> other side of a hop.  the middle node sees the services of both ends, but
> the ends do not see the services of each other.  After talking to the Avahi
> users group, they seemed to think this had something to do with batman
> advanced implementation of its mcast routing.  If you say they are flooded
> through the network, is there another reason why I wouldn't see the mDNS
> broadcasts over the hop?

So, you have 3 nodes (let's call them A/B/C) in a row. A sends mDNS data, B 
receives it but C does not ?
The best starting point is "batctl td" or wireshark which allow you to inspect 
the packets. You could verify what happens with your broadcasts. Feel free to 
post your logs here.

Regards,
Marek

Re: [B.A.T.M.A.N.] link local mcast

[Linus Lüssing]

[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]

One quick thing that comes to my mind is, that you can specify
allowed or denied interfaces in avahi. Maybe it has chosen the
wrong ones? (should probably be bat0 and not the direct wlan0
interfaces for example)
Of course this is just an assumption in case batman-adv itself
works perfectly well. :)

Cheers, Linus

On Thu, Jan 07, 2010 at 04:12:33PM -0500, ecfu wrote:
> I guess I am confused then...  I am trying to see my avahi services on the
> other side of a hop.  the middle node sees the services of both ends, but
> the ends do not see the services of each other.  After talking to the Avahi
> users group, they seemed to think this had something to do with batman
> advanced implementation of its mcast routing.  If you say they are flooded
> through the network, is there another reason why I wouldn't see the mDNS
> broadcasts over the hop?
> 
> Thanks
> 
> On Thu, Jan 7, 2010 at 12:52 PM, Marek Lindner <lindner_marek@yahoo.de>wrote:
> 
> > On Thursday 07 January 2010 22:35:50 ecfu wrote:
> > > Does Batman Adv provide correct mcast routing for link-local mcast
> > groups?
> >
> > Yes, all multicast packets are simply flooded through the whole network.
> >
> > Regards,
> > Marek
> > _______________________________________________
> > B.A.T.M.A.N mailing list
> > B.A.T.M.A.N@lists.open-mesh.org
> > https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n
> >

> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@lists.open-mesh.org
> https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]