All of lore.kernel.org
 help / color / mirror / Atom feed
From: jmh8@nhfn.net
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Cc: ligang.liu@mail.sim.ac.cn, liujp@mail.sim.ac.cn,
	qianhw@mail.sim.ac.cn, zhuj@mail.sim.ac.cn,
	kekegai@smart-com.org
Subject: Re: [B.A.T.M.A.N.] Paper "Performance Evaluation of BATMAN-adv Wireless Mesh Network Routing Algorithms "
Date: Sat, 4 Aug 2018 10:39:50 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1808041038340.8742@nhfn.net> (raw)
In-Reply-To: <2791173.mX5NbDZpiX@sven-edge>


Hi All,

    I HATE dealing with ieee.org. Please login. Pay LOTS of money. MAYBE we 
will get around to you eventually.

    I USED to be a member. Waste of $$.

    Bitchingly yours,
    John


On Sat, 4 Aug 2018, Sven Eckelmann wrote:

> Hi,
>
> Just saw your paper "Performance Evaluation of BATMAN-adv Wireless
> Mesh Network Routing Algorithms" [1]. Some small questions:
>
> * What is OpenWrt 1703? (you've referenced a batman-adv config tutorial here
>  and there is no such version as OpenWrt 1703)
> * When did you want to contact the authors of the B.A.T.M.A.N. V
>  implementation in batman-adv about your findings?
> * How did you solve the cfg80211 bug which returns uninitialized (random)
>  data when asked for the expected throughput of a station? Maybe you remember
>  that the expected throughput is *the value* which B.A.T.M.A.N. V needs to
>  calculate routes.
> * What batman-adv version was used?
> * Did you use the openwrt-routing feed (which exact version) for
>  batctl+batman-adv or how did you build it?
> * Did you generate graphs for the chosen best next hop and how it changes
>  over time in comparison to B.A.T.M.A.N. IV?
>
> Kind regards,
> 	Sven
>
> [1] https://ieeexplore.ieee.org/document/8421863/

  reply	other threads:[~2018-08-04 14:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-04 11:38 [B.A.T.M.A.N.] Paper "Performance Evaluation of BATMAN-adv Wireless Mesh Network Routing Algorithms " Sven Eckelmann
2018-08-04 14:39 ` jmh8 [this message]
2018-08-04 15:34   ` Sven Eckelmann
2018-08-11  6:47     ` jmh8
     [not found] ` <2018081310240755548768@mail.sim.ac.cn>
2018-08-13  7:40   ` Sven Eckelmann
2018-08-30  7:50     ` [B.A.T.M.A.N.] Recent test result. " Ligang LIU
2018-08-30  8:17       ` Sven Eckelmann
2018-08-30  8:55         ` Ligang LIU
2018-08-30  9:06           ` Sven Eckelmann
2018-08-31  9:52             ` Ligang LIU
2018-08-31 10:30               ` Sven Eckelmann
2018-08-31 10:41                 ` Sven Eckelmann
2018-08-31 12:16                 ` Marek Lindner
2018-09-01  9:33                   ` Antonio Quartulli
2018-09-01  9:08                 ` Sven Eckelmann
2018-09-03  4:03                 ` [B.A.T.M.A.N.] mcast_rate setting of wifi interface has significant effect to performance of V. " Ligang LIU
2018-09-03  6:25                   ` Sven Eckelmann
     [not found]                     ` <aa797db.cdf1.165a3d64b19.Coremail.heishuihe2008@163.com>
2018-09-04 10:34                       ` Sven Eckelmann
2018-09-05 17:40                         ` Sven Eckelmann

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=alpine.DEB.2.00.1808041038340.8742@nhfn.net \
    --to=jmh8@nhfn.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=kekegai@smart-com.org \
    --cc=ligang.liu@mail.sim.ac.cn \
    --cc=liujp@mail.sim.ac.cn \
    --cc=qianhw@mail.sim.ac.cn \
    --cc=zhuj@mail.sim.ac.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.