>>> On Mon, Aug 11, 2008 at 11:42 PM, YanBo <[email protected]> wrote:
>>>> By reading the 8011s standard draft, it also define the MPP(Mesh
>>>> Portals) and MAP(Mesh Access Point), I don't know does currently
>>>> open80211s project implement them?
>>>> I also read a file named olpc-mesh.pdf which is write by you, in this file you refer to MPP and
>>>> said "L2 bridging not possible because of the 3-address problem"
>>>> want ask you guide what's your mean 3-address problem, do you mean all
>>>> currently b&g even n card doesn't support 6 mac address 80211s header?
>>>
>>> That presentation was for OLPC mesh, which had different requirements
>>> (e.g. work with legacy equipment, single radio) than o11s. But the
>>> three address problem applies to o11s as well. It happens when you
>>> try to connect the mesh to an outside network using an normal AP.
>>>
>>> A - AP -)) ((-B - C
>>>
>>> B, C: are mesh nodes. B is associated with AP.
>>> Using 3-address 802.11 frames between AP and B, there is no way for A
>>> to reach C.
>>
>> By using 6 addresses mesh header, is it possible to make A can reach C?
>> And how B and C know the route info to reach A?
>
> No need for 6 address, just 4. 6 address are needed when mesh points
> are proxying non-mesh capable stations.
> But legacy APs don't know anything about 4 (nor 6) address frames.
> The "three adddress problem" is caused by the use of *legacy* (e.g.
> any unmodified off-the shelf) AP to connect a mesh portal to an
> external network.
> There is no problem if you use a wired ethernet connection and a
> standard 802.3 bridge between the wired and the mesh interface, e.g
>
> A -- ethernet -- B --- mesh --- C
In currently o11s implementation, after bridge a wired and the mesh
interface, it seemed o11s can't correctly deal with the packet that
forward by 802.3 bridge. so A still can't reach C.
BR
yanbo
YanBo,
On Mon, Aug 18, 2008 at 1:46 AM, YanBo <[email protected]> wrote:
>> The "three adddress problem" is caused by the use of *legacy* (e.g.
>> any unmodified off-the shelf) AP to connect a mesh portal to an
>> external network.
>> There is no problem if you use a wired ethernet connection and a
>> standard 802.3 bridge between the wired and the mesh interface, e.g
>>
>> A -- ethernet -- B --- mesh --- C
>
> In currently o11s implementation, after bridge a wired and the mesh
> interface, it seemed o11s can't correctly deal with the packet that
> forward by 802.3 bridge. so A still can't reach C.
This is correct, yes. What I was trying to say is that it will never
be possible to connect a mesh to an external network using a legacy
AP. On the other hand, it will be possible to connect the mesh to an
external network via an 802.1D bridge and a wired ethernet interface.
But only when mesh portal functionality is implemented in o11s.
Cheers,
Javier