public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.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.] [PATCH] batman-adv: add compat support for the new netlink ops
Date: Tue, 19 Feb 2013 09:08:44 +0800	[thread overview]
Message-ID: <201302190908.44891.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20130218234904.GA24241@pandem0nium>


Hi Simon,

> I've tested this (just test, no code review) in my 2.6.32 qemu (Debian
> squeeze, iproute from wheezy). It generally loads and batctl if add/del
> seems to work, but there is something weird going on with bridge
> interaction. After calling the following 3 commands:
> 
> brctl addbr br0
> batctl if add eth0
> ip link set dev eth0 master br0
> 
> I would expect that eth0 moved from bat0 to br0 (or some error is
> reported). 

I feel some confusion here. It could very well be that 2.6.32 did not yet 
support this kind of "interface transfer". You could repeat your test without 
any of the later patches (just go back to the last stable release) to see what 
happens. It is very likely that our patches have nothing to do with that.

These are the tests we should do in order to confirm the compat patch in 
question:

* batctl if add $iface && some OGMS here && batctl if del $iface
* ip link add dev bat0 type batadv && ip link set dev $iface master bat0 && 
some OGMS here && ip link set dev $iface nomaster && ip link del dev bat0

Even more interesting are combinations of those:
* batctl if add $iface && some OGMS here && ip link set dev $iface nomaster && 
ip link del dev bat0
* ip link add dev bat0 type batadv && ip link set dev $iface master bat0 && 
some OGMS here && batctl if del $iface

Thanks for testing!

Cheers,
Marek

  reply	other threads:[~2013-02-19  1:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-17 14:43 [B.A.T.M.A.N.] [PATCH] batman-adv: add compat support for the new netlink ops Antonio Quartulli
2013-02-18 23:49 ` Simon Wunderlich
2013-02-19  1:08   ` Marek Lindner [this message]
2013-02-19 21:43     ` Simon Wunderlich
2013-02-20 13:26       ` Antonio Quartulli
2013-02-20 14:14         ` Simon Wunderlich
2013-02-20 14:27           ` Antonio Quartulli
2013-02-20 14:40             ` Antonio Quartulli
2013-02-20 14:57               ` [B.A.T.M.A.N.] [PATCHv2] " Antonio Quartulli
2013-02-26 21:28                 ` Simon Wunderlich
2013-02-26 21:31                   ` Antonio Quartulli
2013-02-27  3:20                   ` Marek Lindner

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=201302190908.44891.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.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