linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Mesh hwmp mpath service causes ping packet drop
@ 2014-12-08  8:30 deepak kumar Pradhan
  2014-12-09 16:14 ` Bob Copeland
  0 siblings, 1 reply; 2+ messages in thread
From: deepak kumar Pradhan @ 2014-12-08  8:30 UTC (permalink / raw)
  To: linux-wireless

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

Here the station peer C blocked station B, so drops all the packet
coming from station B.
Can someone please help me?
Anything required please feel free to mail me.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Mesh hwmp mpath service causes ping packet drop
  2014-12-08  8:30 Mesh hwmp mpath service causes ping packet drop deepak kumar Pradhan
@ 2014-12-09 16:14 ` Bob Copeland
  0 siblings, 0 replies; 2+ messages in thread
From: Bob Copeland @ 2014-12-09 16:14 UTC (permalink / raw)
  To: deepak kumar Pradhan; +Cc: linux-wireless

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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-12-09 16:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-12-08  8:30 Mesh hwmp mpath service causes ping packet drop deepak kumar Pradhan
2014-12-09 16:14 ` Bob Copeland

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).