From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: johnzeng <johnzeng2013@yahoo.com>
Subject: Re: [B.A.T.M.A.N.] High latency with batman-adv on ethernet
Date: Fri, 21 Oct 2016 17:11:08 +0200 [thread overview]
Message-ID: <2284104.QWR2gm6sJD@bentobox> (raw)
In-Reply-To: <1744565.jjMyA2xSBQ@bentobox>
[-- Attachment #1: Type: text/plain, Size: 2564 bytes --]
On Freitag, 21. Oktober 2016 16:43:41 CEST Sven Eckelmann wrote:
[...]
> > because i tested between ethernet network port ( i don't test in wifi
> > port ) , whether it will master reason ?
>
> Should not be the "reason". batman-adv doesn't care much about it. It just
> requires an ethernet compatible device. The re-broadcast is a little bit
> less aggressive on non-wifi devices but this has nothing to do with your
> problem.
Just created a small test setup via ethernet with batman-adv 2016.3 to show
you how the results are here. They were connected via a single cable:
without batman-adv
------------------
$ ping -c 10 192.168.2.196
PING 192.168.2.196 (192.168.2.196) 56(84) bytes of data.
64 bytes from 192.168.2.196: icmp_seq=1 ttl=64 time=0.478 ms
64 bytes from 192.168.2.196: icmp_seq=2 ttl=64 time=0.682 ms
64 bytes from 192.168.2.196: icmp_seq=3 ttl=64 time=0.392 ms
64 bytes from 192.168.2.196: icmp_seq=4 ttl=64 time=0.642 ms
64 bytes from 192.168.2.196: icmp_seq=5 ttl=64 time=0.574 ms
64 bytes from 192.168.2.196: icmp_seq=6 ttl=64 time=0.466 ms
64 bytes from 192.168.2.196: icmp_seq=7 ttl=64 time=0.602 ms
64 bytes from 192.168.2.196: icmp_seq=8 ttl=64 time=0.619 ms
64 bytes from 192.168.2.196: icmp_seq=9 ttl=64 time=0.658 ms
64 bytes from 192.168.2.196: icmp_seq=10 ttl=64 time=0.440 ms
--- 192.168.2.196 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 0.392/0.555/0.682/0.098 ms
with batman-adv
---------------
$ ping -c 10 10.10.130.66
PING 10.10.130.66 (10.10.130.66) 56(84) bytes of data.
64 bytes from 10.10.130.66: icmp_seq=1 ttl=64 time=0.489 ms
64 bytes from 10.10.130.66: icmp_seq=2 ttl=64 time=0.675 ms
64 bytes from 10.10.130.66: icmp_seq=3 ttl=64 time=0.552 ms
64 bytes from 10.10.130.66: icmp_seq=4 ttl=64 time=0.562 ms
64 bytes from 10.10.130.66: icmp_seq=5 ttl=64 time=0.612 ms
64 bytes from 10.10.130.66: icmp_seq=6 ttl=64 time=0.573 ms
64 bytes from 10.10.130.66: icmp_seq=7 ttl=64 time=0.534 ms
64 bytes from 10.10.130.66: icmp_seq=8 ttl=64 time=0.622 ms
64 bytes from 10.10.130.66: icmp_seq=9 ttl=64 time=0.454 ms
64 bytes from 10.10.130.66: icmp_seq=10 ttl=64 time=0.468 ms
--- 10.10.130.66 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8996ms
rtt min/avg/max/mdev = 0.454/0.554/0.675/0.067 ms
Kind regards,
Sven
PS: I've changed the subject because it was extremely unspecific and
too long.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-10-21 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 14:31 i found time delay is very high and there are more caution info , if possible , please give me some advisement johnzeng
2016-10-21 14:43 ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-10-21 15:11 ` Sven Eckelmann [this message]
2016-10-21 15:29 ` [B.A.T.M.A.N.] High latency with batman-adv on ethernet johnzeng
2016-10-21 15:53 ` Sven Eckelmann
2016-10-21 15:52 ` tiger
2016-10-24 5:11 ` i found time delay is very high and there are more caution info , if possible , please give me some advisement johnzeng
2016-10-24 6:29 ` [B.A.T.M.A.N.] High latency with batman-adv on ethernet Sven Eckelmann
2016-10-24 9:08 ` johnzeng
2016-10-24 9:14 ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-10-24 9:45 ` johnzeng
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=2284104.QWR2gm6sJD@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=johnzeng2013@yahoo.com \
/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