From: Simon Wunderlich <sw@simonwunderlich.de>
To: Clemens John <clemens-john@gmx.de>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Bad link quality if routers are connected by 2 interfaces
Date: Tue, 12 Nov 2013 20:57:16 +0100 [thread overview]
Message-ID: <201311122057.16685.sw@simonwunderlich.de> (raw)
In-Reply-To: <2195225.ZahV9KD01s@flohlap>
> Am Freitag, 8. November 2013, 10:51:26 schrieben Sie:
> > However, a2:f3:c1:5b:54:a6 is used as Ethernet source address for sending
> > in both eth0.3 and wlan0-1 dumps. Is it possible that there is a mac
> > address conflict?
>
> Hi Simon,
>
> this seems to be the right hint. I checked this and we really had a mac
> address conflict on the interfaces wlan0-1 and eth0.3 we used for meshing.
> This was due to a fix for some mac adress problem in our firmware that
> seems to be outdated now.
>
> On my router the problem is fixed. We will check our other hardware also
> but I think we have a good chance that solving the mac adress conflicts
> will also solve this link quality problem. If not, I´ll ask again.
Would be nice to hear if the problem was resolved, also we can reference to
that later when somebody asks again for "my TQ dropped to half, why?" :)
Thanks,
Simon
next prev parent reply other threads:[~2013-11-12 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 11:12 [B.A.T.M.A.N.] Bad link quality if routers are connected by 2 interfaces Clemens John
2013-11-04 10:28 ` Simon Wunderlich
2013-11-07 23:25 ` Clemens John
2013-11-08 9:51 ` Simon Wunderlich
2013-11-08 22:57 ` Clemens John
2013-11-12 19:57 ` Simon Wunderlich [this message]
2013-11-13 12:14 ` Clemens John
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=201311122057.16685.sw@simonwunderlich.de \
--to=sw@simonwunderlich.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=clemens-john@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.