From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Super high package loss and weak connection
Date: Fri, 18 Dec 2015 14:43:48 +0100 [thread overview]
Message-ID: <1571704.ljWJ4IIlsa@sven-desktop> (raw)
In-Reply-To: <CAKrZ8yd4vy36ZXuEa4iN80mvuE92Pa1inG6BQwXsL+2gUBsgqQ@mail.gmail.com>
On Friday 18 December 2015 14:23:24 no name wrote:
> Hello Ruben thanks for your help!
>
> root@BASE2:~# batctl o
> [B.A.T.M.A.N. adv 2015.2, MainIF/MAC: wlan0/40:a5:ef:06:8d:74 (bat0
> BATMAN_IV)] Originator last-seen (#/255) Nexthop
> [outgoingIF]: Potential nexthops ...
> 7c:dd:90:79:e6:19 7.700s (107) 7c:dd:90:79:e6:19 [ wlan0]:
> 7c:dd:90:79:b5:f2 ( 33) 00:23:54:b4:c4:6f ( 27) 7c:dd:90:79:e6:19
> (107)
> 7c:dd:90:79:b5:f2 6.840s (104) 7c:dd:90:79:b5:f2 [ wlan0]:
> 00:23:54:b4:c4:6f ( 15) 7c:dd:90:79:e6:19 ( 46) 7c:dd:90:79:b5:f2
> (104)
> 00:23:54:b4:c4:6f 4.580s ( 66) 7c:dd:90:79:e6:19 [ wlan0]:
> 7c:dd:90:79:b5:f2 ( 31) 7c:dd:90:79:e6:19 ( 66) 00:23:54:b4:c4:6f (
> 45)
>
> This is the output from batctl o
These number look really bad. Looks like the wifi links between the nodes are
basically not working. You can check the signal of the links via `iw dev wlan0
station dump` but there is (most likely) nothing which can be done from the
batman-adv side. First you have to fix your wifi links.
I have no idea what these LOGILINK WL0084B are using or how good they are
(they look rather crappy regarding the antennas but please correct me). If
you want to try a different mode (in case Adhoc is broken in this driver) then
you can try to use meshpoint (802.11s) without the routing enabled. I think
this was done like this:
iw phy phy0 interface add $MESH_IFACE type mp
iw dev $MESH_IFACE set mesh_param mesh_ttl 1
iw dev $MESH_IFACE set mesh_param mesh_fwding 0
iw dev $MESH_IFACE mesh join $MESH_ID
Kind regards,
Sven
next prev parent reply other threads:[~2015-12-18 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 20:52 [B.A.T.M.A.N.] Super high package loss and weak connection no name
2015-12-17 23:02 ` Ruben Kelevra
2015-12-18 13:23 ` no name
2015-12-18 13:43 ` Sven Eckelmann [this message]
2015-12-18 14:20 ` no name
2015-12-18 14:42 ` Sven Eckelmann
2015-12-18 16:12 ` no name
2015-12-18 16:40 ` Sven Eckelmann
[not found] ` <CAKrZ8yffDYcr6UCw2Yv7hqUFEBNZQ+nTU09dovL=PO3+Zqy7ig@mail.gmail.com>
2015-12-18 17:30 ` Sven Eckelmann
2015-12-21 15:35 ` no name
-- strict thread matches above, loose matches on Subject: below --
2015-12-29 12:42 no name
[not found] ` <CAO9R-ZajkZRq-4==N3Y9aXkRCc3AhmPQiB_P4gSfKtu0X9W5tg@mail.gmail.com>
[not found] ` <CAO9R-ZZ=NT2Mh-OYtUpsZOYV=FHVjZjta+W1KeJU-v+HRgKaKg@mail.gmail.com>
2015-12-30 19:14 ` no name
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=1571704.ljWJ4IIlsa@sven-desktop \
--to=sven@narfation.org \
--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