From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Phill Raynsford <phill@blupoint.org>
Subject: Re: [B.A.T.M.A.N.] Issues with mesh routing
Date: Sat, 09 Mar 2019 14:35:51 +0100 [thread overview]
Message-ID: <10494594.TRTkPdsu0N@sven-edge> (raw)
In-Reply-To: <FE867393-B71B-4CEB-8C98-93E0991A6BA4@blupoint.org>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On Tuesday, 5 March 2019 11:03:31 CET Phill Raynsford wrote:
[...]
> Has anyone ever seen this kind of thing occur before, and perhaps to fix it? I haven't seen any suspicious messages in any of the system logs, and other batctl diagnostic outputs seem OK.
Seen this with broken or misconfigured wifi drivers. For example drivers which
were changing broadcast frames to unicast frames (which breaks OGMs because
they must be broadcasts) or some of them were changing the source address of
broadcast frames (which is also not acceptable).
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-03-09 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 10:03 [B.A.T.M.A.N.] Issues with mesh routing Phill Raynsford
2019-03-09 13:35 ` Sven Eckelmann [this message]
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=10494594.TRTkPdsu0N@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=phill@blupoint.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