From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: smartwires@gmail.com
Subject: Re: Network stops passing traffic randomly
Date: Mon, 25 May 2020 10:43:07 +0200 [thread overview]
Message-ID: <32459667.Id32LJz2i1@bentobox> (raw)
In-Reply-To: <20200525083512.832.13419@diktynna.open-mesh.org>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On Monday, 25 May 2020 10:35:12 CEST smartwires@gmail.com wrote:
> I have been battling a weird problem recently, I have this problem occurring on two (2) separate networks, one with 2 nodes and the other with 3 nodes. What happens is the network is fine and all of a sudden the clients can not reach the Internet, This what I have observed. on both Openwrt 19.07, 18.07. A reboot of the gateway corrects the problem.
[...]
> root@Main-GW:~# batctl ping e8:5b:b7:00:10:6b
> PING e8:5b:b7:00:10:6b (e8:5b:b7:00:10:6b) 20(48) bytes of data
> Reply from host e8:5b:b7:00:10:6b timed out
> Reply from host e8:5b:b7:00:10:6b timed out
> Reply from host e8:5b:b7:00:10:6b timed out
> Reply from host e8:5b:b7:00:10:6b timed out
My first guess is that the underlying interfaces (mesh0) stopped to transport
unicast frames. Did you check this by setting an IP on mesh0 and ping between
these devices using the IPv4 ping?
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-25 8:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 8:35 Network stops passing traffic randomly smartwires
2020-05-25 8:43 ` Sven Eckelmann [this message]
[not found] ` <CAL3ir7+RWLrYOzjNQh1VwiKg1sxSgHZMwwqx=9xSfXFnFjE_KQ@mail.gmail.com>
2020-05-25 13:22 ` Sven Eckelmann
2020-05-25 13:45 ` Sven Eckelmann
2020-05-28 1:05 ` smartwires
2020-05-28 8:46 ` Sven Eckelmann
[not found] ` <cf75d66e-b0ac-632d-34e6-681ed9c6769d@coolheads.com>
2020-05-28 19:31 ` Sven Eckelmann
2020-05-28 21:17 ` Steve Newcomb
2020-05-28 19:03 ` Steve Newcomb
2020-05-28 19:19 ` Sven Eckelmann
2020-05-28 19:22 ` Ben Greear
2020-05-28 20:59 ` Steve Newcomb
2020-05-28 21:28 ` Ben Greear
2020-06-02 1:41 ` Steve Newcomb
2020-06-02 12:40 ` Steve Newcomb
2020-05-29 0:13 ` smartwires
2020-06-02 2:05 ` Steve Newcomb
2020-06-02 20:02 ` Ben Greear
2020-06-03 2:06 ` Steve Newcomb
2020-06-03 12:48 ` Ben Greear
2020-06-03 15:35 ` Steve Newcomb
2020-06-03 16:42 ` Ben Greear
2020-06-03 17:56 ` Steve Newcomb
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=32459667.Id32LJz2i1@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=smartwires@gmail.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