Ok, I understand now what you mean. Thank you for the tip.

On 01/10/14 11:34, Yeoh Chun-Yeow wrote:
> I mean that you can create the direct static mesh path for your mesh
> STA to all other peer mesh STAs to avoid any PREQ/PREP exchange. But
> still let your L2.5 or L3 layer to handle the routing.
> 
> Regards,
> Chun-Yeow
> 
> On Wed, Oct 1, 2014 at 4:38 PM, Pau <[email protected]> wrote:
>> If I understand correctly your proposal I would say Batman-adv and/or
>> Bmx6 is taking care of the routing, so we don't need to specify the
>> next-hop-mac for a certain destination-mac.
>>
>> On 01/10/14 09:18, Yeoh Chun-Yeow wrote:
>>>> Until now we were using Ad-Hoc as link layer, however recently we have
>>>> started to consider the idea of using 11s instead. We are not interested
>>>> in the routing layer (HWMP) because we need some features provided by
>>>> batman-adv, so we disable it by setting the option mesh_forwarding to
>>>> false.
>>>
>>> Maybe you can set the mpath if you would like turn off the HWMP.
>>>
>>> iw dev <devname> mpath set <destination MAC address> next_hop <next
>>> hop MAC address>
>>> iw dev <devname> mpath new <destination MAC address> next_hop <next
>>> hop MAC address>
>>>
>>> ----
>>> Chun-Yeow
>>>
>>
>> --
>> ./p4u
>>

-- 
./p4u

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Devel mailing list
[email protected]
http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel

Reply via email to