public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: ligang.liu@mail.sim.ac.cn, liujp@mail.sim.ac.cn,
	qianhw@mail.sim.ac.cn, zhuj@mail.sim.ac.cn
Cc: b.a.t.m.a.n@lists.open-mesh.org, kekegai@smart-com.org
Subject: [B.A.T.M.A.N.] Paper "Performance Evaluation of BATMAN-adv Wireless Mesh Network Routing Algorithms "
Date: Sat, 04 Aug 2018 13:38:30 +0200	[thread overview]
Message-ID: <2791173.mX5NbDZpiX@sven-edge> (raw)

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

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/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-08-04 11:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-04 11:38 Sven Eckelmann [this message]
2018-08-04 14:39 ` [B.A.T.M.A.N.] Paper "Performance Evaluation of BATMAN-adv Wireless Mesh Network Routing Algorithms " jmh8
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=2791173.mX5NbDZpiX@sven-edge \
    --to=sven@narfation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox