On Fri, May 3, 2013 at 9:25 PM, Chaoxing Lin <[email protected]>wrote:
> I have some questions and comments.
>
> Question 1
>
> The typical use case of multiple interfaces on this same host is to do RF
> segregation in order to improve overall network performance. e.g. divide a
> original mesh of 16 radios into 2 meshes of 8 radios each. This multi-radio
> host bridges these two small meshes which are on different channels. I
> can't see why user would put multiple radios of the same host on the same
> channel. They would just interfere with each other very badly.
>
Yes. I think that the idea is to used the orthogonal channel or
non-overlapping channel in the same host. And also, the important part is
to create a single mesh network for mesh nodes that could join the mesh
network and still operating in different channels. Previously, create a
single mesh network is not possible if we simply bridge the two mesh
interfaces using bridge utility since the mesh nodes operating in different
channels cannot see each others.
> So, it does not matter whether they have matching mesh setup profile or
not. Two MBSS-es simply can't see each other in air.
>
It is actually one single MBSS but with two or many more set of mesh nodes
operating in different non-overlapping channel.
> Question 2
>
> In MPP where there are multiple mesh interfaces, AP interface and/or
> Ethernet interface, how does this "MBSS sharing" work?
> a. add both mesh interface in 802.1d bridge, or
b. add either interface in bridge, or
> c. sharing can't be used
As far as I know, sharing can't be used for mesh interfaces with AP or
Ethernet interfaces. Perhaps, Thomas and Bob can comment further.
----
Chun-Yeow
_______________________________________________
Devel mailing list
[email protected]
http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
