On 10 January 2019 10:56:23 Roger James <roger@xxxxxxxxxxxxxxxxxxxxx> wrote:
Hello,
I am using wpa_supplicant to set up 802.11s mesh networks. I would like to
be able to set bandwidth and mcs in the same way I can with the iw command.
iw dev <devname> mesh join <mesh ID> [[freq <freq in MHz>
<NOHT|HT20|HT40+|HT40-|80MHz>] [basic-rates <rate in Mbps,rate2,...>]],
[mcast-rate <rate in Mbps>] [beacon-interval <time in TUs>] [dtim-period
<value>] [vendor_sync on|off] [<param>=<value>]*
Join a mesh with the given mesh ID with frequency, basic-rates,
mcast-rate and mesh parameters. Basic-rates are applied only if
frequency is provided.
The only relevant parameters I can find in wpa_supplicant.conf are:
# disable_ht: Whether HT (802.11n) should be disabled.
# 0 = HT enabled (if AP supports it)
# 1 = HT disabled # # disable_ht40: Whether HT-40 (802.11n) should be disabled.
# 0 = HT-40 enabled (if AP supports it)
# 1 = HT-40 disabled
#
# ht40_intolerant: Whether 40 MHz intolerant should be indicated.
# 0 = 40 MHz tolerant (default)
# 1 = 40 MHz intolerant
#
# ht_mcs: Configure allowed MCS rates.
# Parsed as an array of bytes, in base-16 (ascii-hex)
# ht_mcs="" // Use all available (default)
# ht_mcs="0xff 00 00 00 00 00 00 00 00 00 " // Use MCS 0-7 only
# ht_mcs="0xff ff 00 00 00 00 00 00 00 00 " // Use MCS 0-15 only
It is not clear to me whether these parameters can be used to configure
mesh nodes. The defaults would seem to suggest that I should be able to see
802.11n modes being used on the mesh. I dont see any HT modes being used.
Any one got any ideas?
Cheers
Roger
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
I have investigated this some more and it looks like that mesh frequency
and bandwidth are setup in wpa_supplicant/wpa_supplicant.c:2077
ibss_mesh_setup_frequency. I stuck in some extra debug and it appears that
an assumption has been made that the mesh will already exist and that
frequency, bandwidth, modulation, will be set up from the results of a
previous scan. The situation where the first join will creaate the mesh is
not handled.
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: New scan results
available (own=1 ext=0)
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: Radio work
'scan'@0x404bc8 done in 2.219395 seconds
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint:
radio_work_free('scan'@0x404bc8): num_active_works --> 0
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: Selecting BSS from
priority group 0
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: 0:
c2:56:27:d4:a7:53 ssid='peglegpete-low' wpa_ie_len=0 rsn_ie_len=20
caps=0x431 level=-66 freq=2462
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: skip - SSID mismatch
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: 1:
a6:08:f5:a6:aa:d8 ssid='BTWifi-X' wpa_ie_len=0 rsn_ie_len=20 caps=0x411
level=-85 freq=2462
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: skip - SSID mismatch
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: 2:
a4:08:f5:a6:a8:da ssid='BTHub6-3758' wpa_ie_len=0 rsn_ie_len=20 caps=0x411
level=-89 freq=2462 wps
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: skip - SSID mismatch
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: 3:
a6:08:f5:a6:aa:db ssid='BTWifi-with-FON' wpa_ie_len=0 rsn_ie_len=0
caps=0x401 level=-85 freq=2462
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: skip - SSID mismatch
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: No suitable
network found
Jan 12 20:35:44 heathers wpa_supplicant[329]: meshpoint: Setup a new network
Jan 12 20:35:44 heathers wpa_supplicant[329]: mesh: Calling
ibss_mesh_setup_freq
Jan 12 20:35:44 heathers wpa_supplicant[329]: last_scan_res_used = 4
Jan 12 20:35:44 heathers wpa_supplicant[329]: Checking result 0
Jan 12 20:35:44 heathers wpa_supplicant[329]: mode != WPAS_MODE_IBSS
Loop bails at this point. As a result none of the extra parameters to set
bandwidth etc. get set up.
Jan 12 20:35:44 heathers wpa_supplicant[329]: phy: phy0
Jan 12 20:35:44 heathers wpa_supplicant[329]: BSS count 1, BSSID mask
00:00:00:00:00:00 (0 bits)
Jan 12 20:35:44 heathers wpa_supplicant[329]: nl80211: Regulatory
information - country=GB (DFS-ETSI)
Jan 12 20:35:44 heathers wpa_supplicant[329]: nl80211: 2402-2482 @ 40 MHz
20 mBm
Jan 12 20:35:44 heathers wpa_supplicant[329]: nl80211: 5170-5250 @ 80 MHz
20 mBm
Jan 12 20:35:44 heathers wpa_supplicant[329]: nl80211: 5250-5330 @ 80 MHz
20 mBm (DFS)
Jan 12 20:35:44 heathers wpa_supplicant[329]: nl80211: 5490-5710 @ 160 MHz
27 mBm (DFS)
Jan 12 20:35:44 heathers wpa_supplicant[329]: nl80211: 57000-66000 @ 2160
MHz 40 mBm
Jan 12 20:35:44 heathers wpa_supplicant[329]: nl80211: Added 802.11b mode
based on 802.11g information
No sensible defaults have been set. I have not yet checked to see if the
hostapd.conf frequency settings that are being used here would be honoured
when found in a wpa_supplicant.conf network stanza.
For small mesh networks this is not sensible behaviour.
-
Any comments anyone, please?
What have I missed?
Roger
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
