Operation not supported - when joining mesh. #67
Comments
|
What's the wireless driver that you used? Check whether it supports mesh
…On Oct 20, 2017 11:05 PM, "darkdrgn2k" ***@***.***> wrote:
Recently upgraded Raspbery Pi to Debian Stretch causes some issues with
meshing. I have no idea where the issue is (driver,kernel, etc)
example of issue below
PS: hardware worked Fine on Debain 8 (jessie)
sudo iw reg set CA
sudo iw phy phy1 interface add mesh0 type mp
sudo iw --debug dev mesh0 mesh join tomesh freq 2412
***@***.***:/usr/bin# iw --debug dev mesh0 mesh join tomesh freq 2412
-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 48
.type = 22 <0x16>
.flags = 5 <REQUEST,ACK>
.seq = 1508506231
.port = 1497367426
[GENERIC NETLINK HEADER] 4 octets
.cmd = 68
.version = 0
.unused = 0
[PAYLOAD] 28 octets
08 00 03 00 05 00 00 00 0a 00 18 00 74 6f 6d 65 ............tome
73 68 00 00 08 00 26 00 6c 09 00 00 sh....&.l...
--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets
.nlmsg_len = 68
.type = 2 <ERROR>
.flags = 0 <>
.seq = 1508506231
.port = 1497367426
[ERRORMSG] 20 octets
.error = -95 "Operation not supported"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.type = 22 <0x16>
.flags = 5 <REQUEST,ACK>
.seq = 1508506231
.port = 1497367426
--------------------------- END NETLINK MESSAGE ---------------------------
command failed: Operation not supported (-95)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#67>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABBewp6QCJqvEB4737fK0ApqwuYqCwV3ks5suLacgaJpZM4QAzQ7>
.
|
|
As i mentioned in my above post the hardware we are using has not changed between DEBIAN 8 and 9 everything works in 8, but not in 9 Also i can create the mesh INTERFACE (which if the drivers did not support would not be possible) I just cannot JOIN the mesh network
Also confirmed with a secondary device that we have used to mesh before too (supprts dual band) |
|
Should be no problem for ath9k_htc. While you up your interface, is that
any other VAP running on the same interface? If yes, try to remove it first.
Also make sure that there is no network-manager managing the interface on
the background.
…---
Chun-Yeow
On Sat, Oct 21, 2017 at 3:09 AM, darkdrgn2k ***@***.***> wrote:
As i mentioned in my above post the hardware we are using has not changed
between DEBIAN 8 and 9
everything works in 8, but not in 9
also i can create the mesh INTERFACE just not JOIN the mesh network
ath9k_htc,mac80211,ath,ath9k_common
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports T-DLS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CCMP-256 (00-0f-ac:10)
* GCMP-128 (00-0f-ac:8)
* GCMP-256 (00-0f-ac:9)
* CMAC (00-0f-ac:6)
* CMAC-256 (00-0f-ac:13)
* GMAC-128 (00-0f-ac:11)
* GMAC-256 (00-0f-ac:12)
Available Antennas: TX 0x1 RX 0x1
Configured Antennas: TX 0x1 RX 0x1
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
* P2P-client
* P2P-GO
* outside context of a BSS
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
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
Frequencies:
* 2412 MHz [1] (30.0 dBm)
* 2417 MHz [2] (30.0 dBm)
* 2422 MHz [3] (30.0 dBm)
* 2427 MHz [4] (30.0 dBm)
* 2432 MHz [5] (30.0 dBm)
* 2437 MHz [6] (30.0 dBm)
* 2442 MHz [7] (30.0 dBm)
* 2447 MHz [8] (30.0 dBm)
* 2452 MHz [9] (30.0 dBm)
* 2457 MHz [10] (30.0 dBm)
* 2462 MHz [11] (30.0 dBm)
* 2467 MHz [12] (disabled)
* 2472 MHz [13] (disabled)
* 2484 MHz [14] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* tdls_mgmt
* tdls_oper
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* channel_switch
* set_qos_map
* 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
* P2P-device: 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
* P2P-device: 0x40 0xd0
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed, P2P-client } <= 2, #{ AP, mesh point, P2P-GO } <= 2,
total <= 2, #channels <= 1
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.
Device supports SAE with AUTHENTICATE command
Device supports low priority scan.
Device supports scan flush.
Device supports AP scan.
Device supports per-vif TX power setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Device supports configuring vdev MAC-addr on create.
***@***.***:/usr/bin#
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#67 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABBewiXzzdtbdpt7xedvYYRzPeSJAI2Iks5suO_dgaJpZM4QAzQ7>
.
|
|
The only AP is the default one it seems the mesh came up when i re-purposed wlan0 instead of creating secondary one. intereting.. |
|
ok seems there is still a problem this does NOT work (and confirmed that wlan0 IS deleted and no longer exists in ifconfig -a) but this does |
|
Seemed to be an os issue of some sort. |
|
Found that I had the exact same issue as you, running Raspbian stretch and a RT5370. Did you ever figure out what was causing it? |
|
at the time we found creating a. virtual. interface was breaking things.l instead we reused the existing one and things started working. however I have found that network manager and wpa_supplicant both create problems. network manager seems to now be gone |
|
Thanks @darkdrgn2k, I also found that killing wpa_supplicant was necessary. There's supposedly 802.11s support coming in a version of wpa_supplicant but it doesn't appear to be in stretch. Reusing the existing interface looks like it works for me as well, will just stick to that moving forward. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently upgraded Raspbery Pi to Debian Stretch causes some issues with meshing. I have no idea where the issue is (driver,kernel, etc)
example of issue below
PS: hardware worked Fine on Debain 8 (jessie)
sudo iw reg set CA
sudo iw phy phy1 interface add mesh0 type mp
sudo iw --debug dev mesh0 mesh join tomesh freq 2412
The text was updated successfully, but these errors were encountered: