public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@web.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Basic Multicast Optimizations
Date: Wed, 12 Jun 2013 22:33:26 +0200	[thread overview]
Message-ID: <20130612203325.GA28709@Linus-Debian> (raw)
In-Reply-To: <20130612124437.GA14493@pandem0nium>

On Wed, Jun 12, 2013 at 02:44:38PM +0200, Simon Wunderlich wrote:
> On Wed, Jun 12, 2013 at 02:27:14PM +0200, Linus Lüssing wrote:
> > On Wed, Jun 12, 2013 at 12:14:11PM +0200, Simon Wunderlich wrote:
> > > Hello Linus,
> > > 
> > > I gave it a try - but there seems something off. What I did is:
> > >  * apply your patches on 3b38a80 - multicast was enabled by default
> > >  * start 2 VMs directly connected
> > >  * ping6 -I bat0 ff02::1
> > > 
> > > I only got a reply locally, but not from the peer. When I disabled
> > > multicast, I got two replies from the local host and the peer.
> > > 
> > > As far as I have tracked the problem down, it appears that
> > > batadv_mcast_forw_mode() returns 1 correctly, but the packet is dropped
> > 
> > Ok, found a bug - the return 1 is actually incorrect. You've
> > chosen the one multicast address where no optimization is
> > conceptually possible. ff02::1 is the only link-local IPv6
> > multicast address which should return a BATADV_FORW_ALL (0)
> > instead.
> 
> Ah, wonderful, and I thought I found a testcase. :D

Well, it was a testcase I hadn't used and you found a bug by that
;).

> 
> Can you advise how the feature can be tested then, practically?
> I guess I'll need to add some routes and ping6 another address?

I was usually using 'ip maddr show' to check which address isn't
in use yet, then I use something like 'ping6 ff02::3%bat0' which should
by default result in no reply.

Then I'd start adding listeners with this tiny C code snippet:
http://pastebin.com/fg9z8z5b on various nodes
(because I didn't find any simple, tiny command line program to do
just that yet).

You'd then get ICMP replies from the according nodes and I checked
via tcpdump that the ICMP packets were forwarded correctly via
unicast or broadcast.


And since "batman-adv: Add dummy soft-interface rx mode handler"
I'm not using that C code snippet that much anymore, but just
adding listeners via "ip maddr add 33:33:00:00:00:03 dev bat0"
for instance. And just checking via tcpdump (since you won't get
any ICMP replies) and the 'batctl tg' output.

  reply	other threads:[~2013-06-12 20:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10  7:11 [B.A.T.M.A.N.] Basic Multicast Optimizations Linus Lüssing
2013-06-10  7:11 ` [B.A.T.M.A.N.] [PATCHv4 1/3] batman-adv: Multicast Listener Announcements via Translation Table Linus Lüssing
2013-06-10  7:11 ` [B.A.T.M.A.N.] [PATCHv4 2/3] batman-adv: Announce new capability via multicast TVLV Linus Lüssing
2013-06-10  7:11 ` [B.A.T.M.A.N.] [PATCHv4 3/3] batman-adv: Modified forwarding behaviour for multicast packets Linus Lüssing
2013-06-12 10:14 ` [B.A.T.M.A.N.] Basic Multicast Optimizations Simon Wunderlich
2013-06-12 12:27   ` Linus Lüssing
2013-06-12 12:44     ` Simon Wunderlich
2013-06-12 20:33       ` Linus Lüssing [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-27  9:48 Linus Lüssing
2013-11-14  6:26 Linus Lüssing
2013-10-26 19:16 Linus Lüssing
2013-08-15 19:21 Linus Lüssing
2013-08-19 20:12 ` Simon Wunderlich
2013-08-13  8:23 Linus Lüssing
2013-08-15 13:56 ` Simon Wunderlich
2013-08-15 18:25   ` Linus Lüssing
2013-07-03 22:03 Linus Lüssing
2013-07-04  5:06 ` Linus Lüssing
2013-06-14 17:50 Linus Lüssing
2013-06-16 14:08 ` Simon Wunderlich
2013-06-14  9:02 Linus Lüssing
2013-06-10  6:28 Linus Lüssing
2013-06-10  7:06 ` Linus Lüssing
2013-05-24  8:02 Linus Lüssing
2013-05-24  9:00 ` Linus Lüssing
2013-05-24  9:06   ` Antonio Quartulli
2013-05-24  9:33 ` Marek Lindner
2013-05-11 17:23 Linus Lüssing
2013-05-16 11:51 ` Simon Wunderlich
2013-05-16 17:42   ` Linus Lüssing
2013-05-16 18:31     ` Simon Wunderlich
2013-05-17  1:38       ` Linus Lüssing
2013-05-17 10:24         ` Simon Wunderlich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130612203325.GA28709@Linus-Debian \
    --to=linus.luessing@web.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox