Hi, Bisha As long as the mesh id is different, then it should be no problem. Are you using the same mesh id for both mesh interfaces in one single node?
If using the same mesh id in one single node, the mesh path link (iw mesh0 mpath dump) will have dest addr of our another interface mesh1. But I think that internal forwarding is not working yet. Regards, Chun-Yeow On Mon, Dec 19, 2011 at 2:12 PM, B <[email protected]> wrote: > I will tomorrow. In the mean time could you please have both interfaces > talk.on the same channel. > Thanks. > > Sent from my Verizon Wireless 4G LTE Smartphone > > ----- Reply message ----- > From: "Yeoh Chun-Yeow" <[email protected]> > To: "Bishal Thapa" <[email protected]> > Cc: <[email protected]> > Subject: Question about joining meshes together > Date: Sun, Dec 18, 2011 9:27 pm > > > Hi, Bishal > > I had done two radio interfaces on a single mesh node (say A), bridge >> them together (802.1d). If I turn off the STP, enable forwarding, and try >> to ping any other mesh node (say B), I used to get ping DUPS. Just FYI. >> > > Do you mind to share your network setup. I have setup this, even with STP > off, the ping DUPS is not happened. > > Node A [Radio MN2] <------ Channel 36 -------> [Radio MN2] Node B [Radio > MN1] <------ Channel 149 --------> [Radio MN1] Node C > > Ping from Node A to Node C is alright with no DUPS. Node B consists of two > mesh interfaces bridging together using brctl. > > Regards, > Chun-Yeow >
_______________________________________________ Devel mailing list [email protected] http://open80211s.com/mailman/listinfo/devel
