I was able to setup a mesh wifi network, but I did so with 802.11s, not 
BATMAN or OSLR. This does not require you to set the device in ad-hoc mode. 
It works out of the box on the BeagleBone Black Wireless with Debian 9.5 
(Linux 4.14.71-ti-r80). I did the setup with the command line tool "iw".  
Additional details here:  
https://e2e.ti.com/support/processors/f/791/t/780010

On Monday, January 28, 2019 at 3:37:48 PM UTC-6, don_wrt wrote:
>
> Hello,
>
> I wonder that what happens when I try to reach to a node where it is in 
> non-line of sight position for me. I have to make some number of 'hops' 
> over nodes in my line of sight to reach to non-line of sight node for me. I 
> wonder that, if ad-hoc is not supported, can I reach to node where it is in 
> the non-line of sight position for me in a mesh - networking by using BBBW?
>
> Best Regards
>
> On Mon, Jan 28, 2019 at 11:09 PM <[email protected] <javascript:>> wrote:
>
>> To add a little bit of background to this;
>>
>> There are several posts on TI's e2e forum stating that ad-hoc mode is no 
>> longer supported. In TI's use cases ad-hoc was replaced by Wi-Fi Direct.
>> http://e2e.ti.com/support/wireless-connectivity/wifi/f/968/t/367550
>>
>> TI supported 802.11s meshing (http://open80211s.org/) in the last driver 
>> release family (R8.7)
>> http://software-dl.ti.com/ecs/WiLink8/R8_7/exports/release_notes_R8_7.html
>> I have used that in builds from the TI SDK in the past. 
>>
>> However, in this post someone talks about getting the TI open80211s mesh 
>> working in a Debian based release 
>> http://e2e.ti.com/support/wireless-connectivity/wifi/f/968/t/635441
>>
>> I'd never actually heard of BATMAN before these questions. A quick scan 
>> of the documentation suggested that it could also work using AP+STA or 
>> AP+AP modes which are standard modes for the Wilnk8.
>> Iain
>>
>>
>>
>>
>> On Monday, January 28, 2019 at 6:57:06 AM UTC, don_wrt wrote:
>>>
>>> Hello All,
>>>
>>> I have read a post that is "Beaglebone Black Wireless's Wilink8 driver 
>>> does not support the *ad-hoc* mode mesh networking anymore". That is 
>>> true?  I think that Beaglebone black wireless cannot do below things, if it 
>>> does not support the ad-hoc mode;
>>>
>>> *BBBW cannot find the "best path" for routing packets in a mesh network 
>>> over multiple hops?
>>> *How can be determined the effective number of hop count, if ad-hoc is 
>>> not supported?
>>> *BBBW cannot do self-forming of topology when some nodes fall the 
>>> non-line of sight position? (it cannot change topology dynamically)
>>>
>>> If above functions are able to perform with BATMAN or OLSR only, without 
>>> support of ad-hoc mode?
>>>
>>> Best Regards,
>>>
>>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/d82614f9-8529-4b2c-8a34-387111b19397%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/beagleboard/d82614f9-8529-4b2c-8a34-387111b19397%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/6e6701a4-76e5-4a2f-a9c3-7e6e537e4be4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to