Hi Yeoh, I am using the same mesh (mesh_id, channel) combination for both interfaces. Here is my setup:
Node A [Radio MN2] <-------- Channel 6 ------> [Radio MN2] Node B Node A [Radio MN1] <-------- Channel 6 ------> [Radio MN1] Node B Node A [Radio MN1] <-------- Channel 6 ------> [Radio MN2] Node B Node A [Radio MN2] <-------- Channel 6 ------> [Radio MN1] Node B Two nodes with two interfaces each, all on the same Mesh_ID and Channel. Then I create a bridge on each of the nodes bridging MN2 with MN1. I have STP off. I get ping dups. I even tried the case with Node A having just one interface, and Node B with two interfaces. Same result. What do you mean by internal forwarding? Bridging? -Thanks. ----- Original Message ----- From: "Yeoh Chun-Yeow" <[email protected]> To: [email protected] Cc: [email protected] Sent: Monday, December 19, 2011 5:49:21 AM GMT -05:00 US/Canada Eastern Subject: Re: Question about joining meshes together Hi, Bishal 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. ----->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
