linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: deepak kumar Pradhan <hydipu@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Mesh hwmp mpath service causes ping packet drop
Date: Tue, 9 Dec 2014 11:14:05 -0500	[thread overview]
Message-ID: <20141209161405.GJ28394@localhost> (raw)
In-Reply-To: <CAGKQeFifW2FGKUh_i0h4Nkw22biNLYz1T=bKZW2ZgrkFsp9aTQ@mail.gmail.com>

On Mon, Dec 08, 2014 at 02:00:52PM +0530, deepak kumar Pradhan wrote:
> Hi,
> 
> I am using mesh network. Kernel ver 3.12.2.
> Scenario: When 2 wired and 1 wireless boards are forming mesh network,
> packets are dropped
> because of 'iw mesh0 mpath dump" changed entry.
> This case no Issue:
> // Own mac X:X:X:14:17:AD  -------> A     wireless
>                   X:X:X:10:3f:ad    -------> B     wired
>                   X:X:X:14:18:01    -------> C    wired
> # iw mesh0 mpath dump
> DEST ADDR         NEXT HOP          IFACE
> X:X:X:10:3f:ad    X:X:X:10:3f:ad   mesh0         //All traffic travels
> through this mesh peer
> X:X:X:14:18:01   X:X:X:14:18:01  mesh0
>  # iw mesh0 mpath dump        //Changed packet is dropped because of mpath entry
> DEST ADDR         NEXT HOP        IFACE
> X:X:X:10:3f:ad    X:X:X:14:18:01     mesh0
> X:X:X:14:18:01   X:X:X:14:18:01     mesh0

Are both B and C wired _and_ wireless, and A is wireless only?  So B and C
are mesh portals, to the same wired network?

If that's the case you need to enable STP on the bridges.

-- 
Bob Copeland %% http://bobcopeland.com/

      reply	other threads:[~2014-12-09 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08  8:30 Mesh hwmp mpath service causes ping packet drop deepak kumar Pradhan
2014-12-09 16:14 ` Bob Copeland [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=20141209161405.GJ28394@localhost \
    --to=me@bobcopeland.com \
    --cc=hydipu@gmail.com \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).