802.11s is not supported by all wireless NICs. You should check your hardware
and http://linuxwireless.org/en/users/Drivers/. You may try batman-adv for HW
independent mesh.
> On Jan 23, 2016，07:29，William Hermans <yyrk...@gmail.com> Wrote：
>
> It also may be worth checking iw versions between the working on and non
> working systems.
>
> On Fri, Jan 22, 2016 at 4:14 PM, William Hermans <yyrk...@gmail.com> wrote:
>>> After seeing that mesh point mode isn't available, I tried different
>>> methods to solve the problem. First, I tried the adapter in another linux
>>> system and saw that at that system, mesh point is supported, so I thought
>>> the problem is on the kernel or image I am using. I did some updates and
>>> changes but I still couldn't solve the problem. What am I missing here? How
>>> can I make my beaglebone system to support mesh point?
>>
>> Thanks for your help.
>> Define "another linux system". Kernel, distro, and distro version.
>>
>>
>>
>>> On Fri, Jan 22, 2016 at 1:01 PM, <utku6...@gmail.com> wrote:
>>> Hello all,
>>>
>>> I am trying to setup a 802.11s mesh network using Beaglebone Black devices
>>> and TP-Link TL-WN722N wireless adapter. Debian image I am using is Debian
>>> 7.8 Wheezy and linux version is 3.8.13-bone79. I installed the required
>>> files (firmware and driver) for wireless adapter's chipset and when I
>>> started typing commands for mesh, I got the following error:
>>>
>>> $sudo iw dev wlan0 interface add mesh type mp
>>>
>>> command failed: Operation not supported (-95)
>>>
>>> Then, I checked the kernel configuration to see if mesh is enabled or not
>>> and I saw that all MAC80211 configurations related with mesh networking is
>>> enabled. Then I ran the iw list command to see if mesh point mode is
>>> supported or not, output can be found below:
>>>
>>> $iw list
>>>
>>> Wiphy phy0
>>> Band 1:
>>> Capabilities: 0x116e
>>> HT20/HT40
>>> SM Power Save disabled
>>> RX HT20 SGI
>>> RX HT40 SGI
>>> RX STBC 1-stream
>>> Max AMSDU length: 3839 bytes
>>> DSSS/CCK HT40
>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>> HT TX/RX MCS rate indexes supported: 0-7
>>> Frequencies:
>>> * 2412 MHz [1] (20.0 dBm)
>>> * 2417 MHz [2] (20.0 dBm)
>>> * 2422 MHz [3] (20.0 dBm)
>>> * 2427 MHz [4] (20.0 dBm)
>>> * 2432 MHz [5] (20.0 dBm)
>>> * 2437 MHz [6] (20.0 dBm)
>>> * 2442 MHz [7] (20.0 dBm)
>>> * 2447 MHz [8] (20.0 dBm)
>>> * 2452 MHz [9] (20.0 dBm)
>>> * 2457 MHz [10] (20.0 dBm)
>>> * 2462 MHz [11] (20.0 dBm)
>>> * 2467 MHz [12] (20.0 dBm)
>>> * 2472 MHz [13] (20.0 dBm)
>>> * 2484 MHz [14] (disabled)
>>> Bitrates (non-HT):
>>> * 1.0 Mbps
>>> * 2.0 Mbps (short preamble supported)
>>> * 5.5 Mbps (short preamble supported)
>>> * 11.0 Mbps (short preamble supported)
>>> * 6.0 Mbps
>>> * 9.0 Mbps
>>> * 12.0 Mbps
>>> * 18.0 Mbps
>>> * 24.0 Mbps
>>> * 36.0 Mbps
>>> * 48.0 Mbps
>>> * 54.0 Mbps
>>> max # scan SSIDs: 4
>>> max scan IEs length: 2257 bytes
>>> Coverage class: 0 (up to 0m)
>>> Supported Ciphers:
>>> * WEP40 (00-0f-ac:1)
>>> * WEP104 (00-0f-ac:5)
>>> * TKIP (00-0f-ac:2)
>>> * CCMP (00-0f-ac:4)
>>> Available Antennas: TX 0 RX 0
>>> Supported interface modes:
>>> * IBSS
>>> * managed
>>> * AP
>>> * AP/VLAN
>>> * monitor
>>> * P2P-client
>>> * P2P-GO
>>> software interface modes (can always be added):
>>> * AP/VLAN
>>> * monitor
>>> valid interface combinations:
>>> * #{ managed, P2P-client } <= 2, #{ AP, P2P-GO } <= 2,
>>> total <= 2, #channels <= 1
>>> Supported commands:
>>> * new_interface
>>> * set_interface
>>> * new_key
>>> * new_beacon
>>> * new_station
>>> * new_mpath
>>> * set_mesh_params
>>> * set_bss
>>> * authenticate
>>> * associate
>>> * deauthenticate
>>> * disassociate
>>> * join_ibss
>>> * join_mesh
>>> * remain_on_channel
>>> * set_tx_bitrate_mask
>>> * action
>>> * frame_wait_cancel
>>> * set_wiphy_netns
>>> * set_channel
>>> * set_wds_peer
>>> * Unknown command (84)
>>> * Unknown command (87)
>>> * Unknown command (85)
>>> * Unknown command (89)
>>> * Unknown command (92)
>>> * connect
>>> * disconnect
>>> Supported TX frame types:
>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * Unknown mode (10): 0x00 0x10 0x20 0x30 0x40 0x50 0x60
>>> 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> Supported RX frame types:
>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>> * managed: 0x40 0xd0
>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>> * mesh point: 0xb0 0xc0 0xd0
>>> * P2P-client: 0x40 0xd0
>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>> * Unknown mode (10): 0x40 0xd0
>>> Device supports RSN-IBSS.
>>> HT Capability overrides:
>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>> * maximum A-MSDU length
>>> * supported channel width
>>> * short GI for 40 MHz
>>> * max A-MPDU length exponent
>>> * min MPDU start spacing
>>> Device supports TX status socket option.
>>> Device supports HT-IBSS.
>>>
>>> After seeing that mesh point mode isn't available, I tried different
>>> methods to solve the problem. First, I tried the adapter in another linux
>>> system and saw that at that system, mesh point is supported, so I thought
>>> the problem is on the kernel or image I am using. I did some updates and
>>> changes but I still couldn't solve the problem. What am I missing here? How
>>> can I make my beaglebone system to support mesh point?
>>>
>>> Thanks for your help.
>>>
>>> Utku Ozgur
>>> --
>>> 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 beagleboard+unsubscr...@googlegroups.com.
>>> 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 beagleboard+unsubscr...@googlegroups.com.
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
