* issue using virtual interface with iwd
@ 2023-06-01 13:17 Michael John
2023-06-01 15:06 ` James Prestwood
2023-06-01 15:38 ` Denis Kenzior
0 siblings, 2 replies; 14+ messages in thread
From: Michael John @ 2023-06-01 13:17 UTC (permalink / raw)
To: iwd
Hello,
I'm having an issue getting iwd to recognize a virtual interface.
Using 'iw' I've created a virtual interface called wlan1:
iw dev wlan0 interface add wlan1 type __ap
This leaves me with the following two interfaces:
~> iw dev
phy#0
Interface wlan1
ifindex 8
wdev 0x5
addr c0:ee:40:64:4a:1d
type AP
txpower 23.00 dBm
Interface wlan0
ifindex 7
wdev 0x4
addr c0:ee:40:64:4a:1c
type managed
txpower 23.00 dBm
When running 'iwctl' to list devices and APs I'm not seeing wlan1.
~> iwctl ap list
Devices in Access Point Mode
--------------------------------------------------------------------------------
Name Started
--------------------------------------------------------------------------------
No devices in access point mode available.
~> iwctl device list
Devices
--------------------------------------------------------------------------------
Name Address Powered Adapter Mode
--------------------------------------------------------------------------------
wlan0 c0:ee:40:64:4a:1c on phy0 station
When previously using 'wpa_supplicant' and 'NetworkManager' this virtual interface (wlan1) was usable in AP mode. The radio does support AP+STA mode.
~> iw phy
...
valid interface combinations:
* #{ AP } <= 3, #{ managed, P2P-client, P2P-GO } <= 2,
total <= 3, #channels <= 1
* #{ IBSS } <= 1,
total <= 1, #channels <= 1
...
So I'm left wondering if 'iwd' supports virtual interfaces created with the 'iw' utility and if so, what am I missing?
Thanks,
Michael John
CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-01 13:17 issue using virtual interface with iwd Michael John
@ 2023-06-01 15:06 ` James Prestwood
2023-06-01 15:17 ` James Prestwood
2023-06-01 15:38 ` Denis Kenzior
1 sibling, 1 reply; 14+ messages in thread
From: James Prestwood @ 2023-06-01 15:06 UTC (permalink / raw)
To: Michael John, iwd
Hi Michael,
On 6/1/23 6:17 AM, Michael John wrote:
> Hello,
>
> I'm having an issue getting iwd to recognize a virtual interface.
> Using 'iw' I've created a virtual interface called wlan1:
>
> iw dev wlan0 interface add wlan1 type __ap
>
> This leaves me with the following two interfaces:
>
> ~> iw dev
> phy#0
> Interface wlan1
> ifindex 8
> wdev 0x5
> addr c0:ee:40:64:4a:1d
> type AP
> txpower 23.00 dBm
> Interface wlan0
> ifindex 7
> wdev 0x4
> addr c0:ee:40:64:4a:1c
> type managed
> txpower 23.00 dBm
>
> When running 'iwctl' to list devices and APs I'm not seeing wlan1.
>
> ~> iwctl ap list
> Devices in Access Point Mode
> --------------------------------------------------------------------------------
> Name Started
> --------------------------------------------------------------------------------
> No devices in access point mode available.
>
> ~> iwctl device list
> Devices
> --------------------------------------------------------------------------------
> Name Address Powered Adapter Mode
> --------------------------------------------------------------------------------
> wlan0 c0:ee:40:64:4a:1c on phy0 station
>
>
> When previously using 'wpa_supplicant' and 'NetworkManager' this virtual interface (wlan1) was usable in AP mode. The radio does support AP+STA mode.
>
> ~> iw phy
> ...
> valid interface combinations:
> * #{ AP } <= 3, #{ managed, P2P-client, P2P-GO } <= 2,
> total <= 3, #channels <= 1
> * #{ IBSS } <= 1,
> total <= 1, #channels <= 1
> ...
So this appears to me that you cannot do AP+STA with this adapater. You
would need to see "AP" and "managed" in the same block e.g.:
#{ AP, managed, ...} <= 2
For example this adapter I have:
valid interface combinations:
* #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 2,
total <= 2, #channels <= 1, STA/AP BI must match
If you could get the debug logs of IWD starting up I could take a look
at those to see why the wlan1 interface wasn't brought up, but to me it
looks like the adapter simply cannot support AP+STA modes at the same time.
Thanks,
James
>
> So I'm left wondering if 'iwd' supports virtual interfaces created with the 'iw' utility and if so, what am I missing?
>
>
> Thanks,
>
> Michael John
> CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-01 15:06 ` James Prestwood
@ 2023-06-01 15:17 ` James Prestwood
2023-06-01 15:42 ` Michael John
0 siblings, 1 reply; 14+ messages in thread
From: James Prestwood @ 2023-06-01 15:17 UTC (permalink / raw)
To: Michael John, iwd
Hi Michael,
On 6/1/23 8:06 AM, James Prestwood wrote:
> Hi Michael,
>
> On 6/1/23 6:17 AM, Michael John wrote:
>> Hello,
>>
>> I'm having an issue getting iwd to recognize a virtual interface.
>> Using 'iw' I've created a virtual interface called wlan1:
>>
>> iw dev wlan0 interface add wlan1 type __ap
>>
>> This leaves me with the following two interfaces:
>>
>> ~> iw dev
>> phy#0
>> Interface wlan1
>> ifindex 8
>> wdev 0x5
>> addr c0:ee:40:64:4a:1d
>> type AP
>> txpower 23.00 dBm
>> Interface wlan0
>> ifindex 7
>> wdev 0x4
>> addr c0:ee:40:64:4a:1c
>> type managed
>> txpower 23.00 dBm
>>
>> When running 'iwctl' to list devices and APs I'm not seeing wlan1.
>>
>> ~> iwctl ap list
>> Devices in Access Point Mode
>> --------------------------------------------------------------------------------
>> Name Started
>> --------------------------------------------------------------------------------
>> No devices in access point mode available.
>>
>> ~> iwctl device list
>> Devices
>> --------------------------------------------------------------------------------
>> Name Address Powered Adapter
>> Mode
>> --------------------------------------------------------------------------------
>> wlan0 c0:ee:40:64:4a:1c on phy0
>> station
>>
>>
>> When previously using 'wpa_supplicant' and 'NetworkManager' this
>> virtual interface (wlan1) was usable in AP mode. The radio does
>> support AP+STA mode.
>>
>> ~> iw phy
>> ...
>> valid interface combinations:
>> * #{ AP } <= 3, #{ managed, P2P-client, P2P-GO } <= 2,
>> total <= 3, #channels <= 1
>> * #{ IBSS } <= 1,
>> total <= 1, #channels <= 1
>> ...
>
> So this appears to me that you cannot do AP+STA with this adapater. You
> would need to see "AP" and "managed" in the same block e.g.:
Actually sorry, I take that back. The interface combos always confuses
me when I have to take a look again. The card in my laptop has a similar
combo to yours and I can do AP+STA:
* #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device }
<= 1, total <= 3, #channels <= 2
In my case I was having issues because the virtual interface was being
created in station mode (despite passing "__ap" when creating). Looks
like yours is already in AP mode from the "iw dev" command so I'd need
to see the debug logs of IWD starting up to see why the iface wasn't
recognized. You could also try bringing both interfaces up prior to
starting IWD.
>
> #{ AP, managed, ...} <= 2
>
> For example this adapter I have:
>
> valid interface combinations:
> * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 2,
> total <= 2, #channels <= 1, STA/AP BI must match
>
> If you could get the debug logs of IWD starting up I could take a look
> at those to see why the wlan1 interface wasn't brought up, but to me it
> looks like the adapter simply cannot support AP+STA modes at the same time.
>
> Thanks,
> James
>
>>
>> So I'm left wondering if 'iwd' supports virtual interfaces created
>> with the 'iw' utility and if so, what am I missing?
>>
>>
>> Thanks,
>>
>> Michael John
>> CONFIDENTIALITY NOTICE: This message, including any attachments,
>> contains confidential information intended for a specific individual
>> and purpose. If you are not the intended recipient, you should delete
>> this message and any disclosure, copying, or distribution of this
>> message, or the taking of any action based on it, by you is strictly
>> prohibited.
>>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-01 13:17 issue using virtual interface with iwd Michael John
2023-06-01 15:06 ` James Prestwood
@ 2023-06-01 15:38 ` Denis Kenzior
1 sibling, 0 replies; 14+ messages in thread
From: Denis Kenzior @ 2023-06-01 15:38 UTC (permalink / raw)
To: Michael John, iwd
Hi Michael,
On 6/1/23 08:17, Michael John wrote:
> Hello,
>
> I'm having an issue getting iwd to recognize a virtual interface.
> Using 'iw' I've created a virtual interface called wlan1:
>
> iw dev wlan0 interface add wlan1 type __ap
>
Are you doing this before or after starting iwd? Right now iwd ignores any
interfaces created after iwd has detected a phy. This allows one to create
interfaces on the fly and start hostapd on them.
If you want iwd to manage all interfaces, pre-create them prior to starting iwd
(and use the --interfaces command line argument)
iwd only supports STA+P2P combination at the moment. You could add
functionality to have iwd create STA+AP interfaces, similar to how we handle P2P
today (see src/manager.c manager_create_interfaces() or so.) Perhaps based on
some main.conf setting? Patches are always welcome.
Regards,
-Denis
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-01 15:17 ` James Prestwood
@ 2023-06-01 15:42 ` Michael John
2023-06-01 15:53 ` James Prestwood
0 siblings, 1 reply; 14+ messages in thread
From: Michael John @ 2023-06-01 15:42 UTC (permalink / raw)
To: James Prestwood, iwd
[-- Attachment #1: Type: text/plain, Size: 5348 bytes --]
Hi James,
On 6/1/23 8:06 AM, James Prestwood wrote:
>> Hi Michael,
>>
>> On 6/1/23 6:17 AM, Michael John wrote:
>>> Hello,
>>>
>>> I'm having an issue getting iwd to recognize a virtual interface.
>>> Using 'iw' I've created a virtual interface called wlan1:
>>>
>>> iw dev wlan0 interface add wlan1 type __ap
>>>
>>> This leaves me with the following two interfaces:
>>>
>>> ~> iw dev
>>> phy#0
>>> Interface wlan1
>>> ifindex 8
>>> wdev 0x5
>>> addr c0:ee:40:64:4a:1d
>>> type AP
>>> txpower 23.00 dBm
>>> Interface wlan0
>>> ifindex 7
>>> wdev 0x4
>>> addr c0:ee:40:64:4a:1c
>>> type managed
>>> txpower 23.00 dBm
>>>
>>> When running 'iwctl' to list devices and APs I'm not seeing wlan1.
>>>
>>> ~> iwctl ap list
>>> Devices in Access Point Mode
>>> --------------------------------------------------------------------------------
>>> Name Started
>>> --------------------------------------------------------------------------------
>>> No devices in access point mode available.
>>>
>>> ~> iwctl device list
>>> Devices
>>> --------------------------------------------------------------------------------
>>> Name Address Powered Adapter
>>> Mode
>>> --------------------------------------------------------------------------------
>>> wlan0 c0:ee:40:64:4a:1c on phy0
>>> station
>>>
>>>
>>> When previously using 'wpa_supplicant' and 'NetworkManager' this
>>> virtual interface (wlan1) was usable in AP mode. The radio does
>>> support AP+STA mode.
>>>
>>> ~> iw phy
>>> ...
>>> valid interface combinations:
>>> * #{ AP } <= 3, #{ managed, P2P-client, P2P-GO } <= 2,
>>> total <= 3, #channels <= 1
>>> * #{ IBSS } <= 1,
>>> total <= 1, #channels <= 1
>>> ...
>>
>> So this appears to me that you cannot do AP+STA with this adapater. You
>> would need to see "AP" and "managed" in the same block e.g.:
>
> Actually sorry, I take that back. The interface combos always confuses
> me when I have to take a look again. The card in my laptop has a similar
> combo to yours and I can do AP+STA:
>
> * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device }
> <= 1, total <= 3, #channels <= 2
>
> In my case I was having issues because the virtual interface was being
> created in station mode (despite passing "__ap" when creating). Looks
> like yours is already in AP mode from the "iw dev" command so I'd need
> to see the debug logs of IWD starting up to see why the iface wasn't
> recognized. You could also try bringing both interfaces up prior to
> starting IWD.
>
Attached is a capture of the log from iwd. I had a wlan0 and wlan1
created before starting iwd. I noticed after starting iwd my wlan1
in then gone.
~> systemctl stop iwd
~> iw phy phy0 interface add wlan0 type managed
~> iw dev
phy#0
Interface wlan0
ifindex 15
wdev 0xc
addr c0:ee:40:64:4a:1c
type managed
txpower 23.00 dBm
~> iw dev wlan0 interface add wlan1 type __ap
~> iw dev
phy#0
Interface wlan1
ifindex 16
wdev 0xd
addr c0:ee:40:64:4a:1d
type AP
txpower 23.00 dBm
Interface wlan0
ifindex 15
wdev 0xc
addr c0:ee:40:64:4a:1c
type managed
txpower 23.00 dBm
~> systemctl start iwd
~> iw dev
phy#0
Interface wlan0
ifindex 17
wdev 0xe
addr c0:ee:40:64:4a:1c
ssid MIDGUEST
type managed
channel 48 (5240 MHz), width: 40 MHz, center1: 5230 MHz
txpower 23.00 dBm
Looking at the ifindex ID it looks like iwd created a new interface for wlan0.
Thanks,
Michael
>>
>> #{ AP, managed, ...} <= 2
>>
>> For example this adapter I have:
>>
>> valid interface combinations:
>> * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 2,
>> total <= 2, #channels <= 1, STA/AP BI must match
>>
>> If you could get the debug logs of IWD starting up I could take a look
>> at those to see why the wlan1 interface wasn't brought up, but to me it
>> looks like the adapter simply cannot support AP+STA modes at the same time.
>>
>> Thanks,
>> James
>>
>>>
>>> So I'm left wondering if 'iwd' supports virtual interfaces created
>>> with the 'iw' utility and if so, what am I missing?
>>>
>>>
>>> Thanks,
>>>
>>> Michael John
>>>
CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: iwd-with-debug-enabled.log --]
[-- Type: text/x-log; name="iwd-with-debug-enabled.log", Size: 28731 bytes --]
Jun 01 15:36:00 cm1sd systemd[1]: Starting Wireless service...
Jun 01 15:36:01 cm1sd iwd[7396]: No Diffie-Hellman support found, WPS will not be available
Jun 01 15:36:01 cm1sd iwd[7396]: No asymmetric key support found.
Jun 01 15:36:01 cm1sd iwd[7396]: TLS based WPA-Enterprise authentication methods will not function.
Jun 01 15:36:01 cm1sd iwd[7396]: Kernel 4.20+ is required for this feature.
Jun 01 15:36:01 cm1sd iwd[7396]: The following options are missing in the kernel:
Jun 01 15:36:01 cm1sd iwd[7396]: CONFIG_ASYMMETRIC_KEY_TYPE
Jun 01 15:36:01 cm1sd iwd[7396]: CONFIG_KEY_DH_OPERATIONS
Jun 01 15:36:01 cm1sd iwd[7396]: CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE
Jun 01 15:36:01 cm1sd iwd[7396]: CONFIG_PKCS7_MESSAGE_PARSER
Jun 01 15:36:01 cm1sd iwd[7396]: CONFIG_X509_CERTIFICATE_PARSER
Jun 01 15:36:01 cm1sd iwd[7396]: CONFIG_PKCS8_PRIVATE_KEY_PARSER
Jun 01 15:36:01 cm1sd iwd[7396]: Wireless daemon version 2.3
Jun 01 15:36:01 cm1sd iwd[7396]: src/main.c:main() Using configuration directory /etc/iwd
Jun 01 15:36:01 cm1sd iwd[7396]: Loaded configuration from /etc/iwd/main.conf
Jun 01 15:36:01 cm1sd iwd[7396]: src/storage.c:storage_create_dirs() Using state directory /var/lib/iwd
Jun 01 15:36:01 cm1sd iwd[7396]: src/main.c:nl80211_appeared() Found nl80211 interface
Jun 01 15:36:01 cm1sd iwd[7396]: src/module.c:iwd_modules_init()
Jun 01 15:36:01 cm1sd systemd[1]: Started Wireless service.
Jun 01 15:36:01 cm1sd iwd[7396]: src/wsc.c:wsc_init()
Jun 01 15:36:01 cm1sd iwd[7396]: src/resolve.c:resolve_resolvconf_init() Trying to find resolvconf in $PATH
Jun 01 15:36:01 cm1sd iwd[7396]: src/resolve.c:resolve_resolvconf_init() resolvconf found as: /usr/sbin/resolvconf
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap.c:__eap_method_enable()
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap-wsc.c:eap_wsc_init()
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap-md5.c:eap_md5_init()
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap-tls.c:eap_tls_init()
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap-ttls.c:eap_ttls_init()
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap-mschapv2.c:eap_mschapv2_init()
Jun 01 15:36:01 cm1sd iwd[7396]: EAP_MSCHAPv2 init: MD4 support not found, skipping
Jun 01 15:36:01 cm1sd iwd[7396]: Ensure that CONFIG_CRYPTO_MD4 is enabled
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap-sim.c:eap_sim_init()
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap-aka.c:eap_aka_prime_init()
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap-aka.c:eap_aka_init()
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap-peap.c:eap_peap_init()
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap-gtc.c:eap_gtc_init()
Jun 01 15:36:01 cm1sd iwd[7396]: src/eap-pwd.c:eap_pwd_init()
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_wiphy_dump_callback() New wiphy phy0 added (0)
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_wiphy_dump_done()
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_filtered_wiphy_dump_done()
Jun 01 15:36:01 cm1sd iwd[7396]: Wiphy: 0, Name: phy0
Jun 01 15:36:01 cm1sd iwd[7396]: Permanent Address: c0:ee:40:64:4a:1c
Jun 01 15:36:01 cm1sd iwd[7396]: 2.4Ghz Band:
Jun 01 15:36:01 cm1sd iwd[7396]: Bitrates (non-HT):
Jun 01 15:36:01 cm1sd iwd[7396]: 1.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 2.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 5.5 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 11.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 6.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 9.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 12.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 18.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 24.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 36.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 48.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 54.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: HT Capabilities:
Jun 01 15:36:01 cm1sd iwd[7396]: HT20
Jun 01 15:36:01 cm1sd iwd[7396]: Short GI for 20Mhz
Jun 01 15:36:01 cm1sd iwd[7396]: HT RX MCS indexes:
Jun 01 15:36:01 cm1sd iwd[7396]: 0-15
Jun 01 15:36:01 cm1sd iwd[7396]: 32
Jun 01 15:36:01 cm1sd iwd[7396]: VHT Capabilities:
Jun 01 15:36:01 cm1sd iwd[7396]: Short GI for 80Mhz
Jun 01 15:36:01 cm1sd iwd[7396]: Max RX MCS: 0-9 for NSS: 2
Jun 01 15:36:01 cm1sd iwd[7396]: Max TX MCS: 0-9 for NSS: 2
Jun 01 15:36:01 cm1sd iwd[7396]: 5Ghz Band:
Jun 01 15:36:01 cm1sd iwd[7396]: Bitrates (non-HT):
Jun 01 15:36:01 cm1sd iwd[7396]: 6.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 9.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 12.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 18.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 24.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 36.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 48.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: 54.0 Mbps
Jun 01 15:36:01 cm1sd iwd[7396]: HT Capabilities:
Jun 01 15:36:01 cm1sd iwd[7396]: HT40
Jun 01 15:36:01 cm1sd iwd[7396]: Short GI for 20Mhz
Jun 01 15:36:01 cm1sd iwd[7396]: Short GI for 40Mhz
Jun 01 15:36:01 cm1sd iwd[7396]: HT RX MCS indexes:
Jun 01 15:36:01 cm1sd iwd[7396]: 0-15
Jun 01 15:36:01 cm1sd iwd[7396]: 32
Jun 01 15:36:01 cm1sd iwd[7396]: VHT Capabilities:
Jun 01 15:36:01 cm1sd iwd[7396]: Short GI for 80Mhz
Jun 01 15:36:01 cm1sd iwd[7396]: Max RX MCS: 0-9 for NSS: 2
Jun 01 15:36:01 cm1sd iwd[7396]: Max TX MCS: 0-9 for NSS: 2
Jun 01 15:36:01 cm1sd iwd[7396]: Ciphers: BIP-CMAC-256 BIP-GMAC-256 BIP-GMAC-128 CCMP-256
Jun 01 15:36:01 cm1sd iwd[7396]: GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128
Jun 01 15:36:01 cm1sd iwd[7396]: TKIP
Jun 01 15:36:01 cm1sd iwd[7396]: Supported iftypes: ad-hoc station ap p2p-client p2p-go
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_interface_dump_callback()
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_get_interface_cb()
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_get_interface_cb()
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_interface_dump_callback()
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_get_interface_cb()
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_get_interface_cb()
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_interface_dump_done()
Jun 01 15:36:01 cm1sd iwd[7396]: src/wiphy.c:wiphy_update_reg_domain() New reg domain country code for phy0 is US
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_config_notify() Notification of command Del Interface(8)
Jun 01 15:36:01 cm1sd iwd[7396]: src/netdev.c:netdev_link_notify() event 17 on ifindex 16
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_del_interface_cb()
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_config_notify() Notification of command Del Interface(8)
Jun 01 15:36:01 cm1sd iwd[7396]: src/netdev.c:netdev_link_notify() event 17 on ifindex 15
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_del_interface_cb()
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_create_interfaces() creating wlan0
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_config_notify() Notification of command New Interface(7)
Jun 01 15:36:01 cm1sd iwd[7396]: src/netdev.c:netdev_link_notify() event 16 on ifindex 17
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_new_station_interface_cb()
Jun 01 15:36:01 cm1sd iwd[7396]: src/netdev.c:netdev_create_from_genl() Created interface wlan0[17 e]
Jun 01 15:36:01 cm1sd iwd[7396]: src/netdev.c:netdev_link_notify() event 16 on ifindex 17
Jun 01 15:36:01 cm1sd iwd[7396]: src/netdev.c:netdev_set_4addr() netdev: 17 use_4addr: 0
Jun 01 15:36:01 cm1sd iwd[7396]: src/netdev.c:netdev_initial_up_cb() Interface 17 initialized
Jun 01 15:36:01 cm1sd iwd[7396]: src/netconfig.c:netconfig_new() Creating netconfig for interface: 17
Jun 01 15:36:01 cm1sd iwd[7396]: src/station.c:station_enter_state() Old State: disconnected, new state: autoconnect_quick
Jun 01 15:36:01 cm1sd iwd[7396]: src/wiphy.c:wiphy_radio_work_insert() Inserting work item 1
Jun 01 15:36:01 cm1sd iwd[7396]: src/wiphy.c:wiphy_radio_work_next() Starting work item 1
Jun 01 15:36:01 cm1sd iwd[7396]: src/rrm.c:rrm_add_frame_watches()
Jun 01 15:36:01 cm1sd iwd[7396]: src/netdev.c:netdev_link_notify() event 16 on ifindex 17
Jun 01 15:36:01 cm1sd iwd[7396]: src/netdev.c:netdev_link_notify() event 16 on ifindex 17
Jun 01 15:36:01 cm1sd iwd[7396]: src/manager.c:manager_config_notify() Notification of command Set Interface(6)
Jun 01 15:36:01 cm1sd iwd[7396]: src/scan.c:scan_notify() Scan notification Trigger Scan(33)
Jun 01 15:36:01 cm1sd iwd[7396]: src/scan.c:scan_request_triggered() Passive scan triggered for wdev e
Jun 01 15:36:01 cm1sd iwd[7396]: src/station.c:station_quick_scan_triggered() Quick scan triggered for wlan0
Jun 01 15:36:01 cm1sd iwd[7396]: src/wiphy.c:wiphy_reg_notify() Notification of command Reg Beacon Hint(42)
Jun 01 15:36:01 cm1sd iwd[7396]: src/wiphy.c:wiphy_reg_notify() Notification of command Reg Beacon Hint(42)
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_notify() Scan notification New Scan Results(34)
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 10/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 2/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 10/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 10/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 76/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 76/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 20/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 76/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 20/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 20/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 20/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 20/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 71/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 71/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 2/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 35/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 51/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 10/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 2/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 2/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 35/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 9/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_callback() get_scan_callback
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_parse_bss_information_elements() Load: 71/255
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:get_scan_done() get_scan_done
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'ac:3a:67:ed:6a:ef' with SSID: MIDLAB-AuthTest, freq: 5320, rank: 2455, strength: -5800, data_rate: 300.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Added new Network "MIDLAB-AuthTest" security 8021x
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:30:72:ab' with SSID: SCADA, freq: 5240, rank: 2210, strength: -6200, data_rate: 270.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Added new Network "SCADA" security psk
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:30:72:af' with SSID: MIDLAB-AuthTest, freq: 5240, rank: 2210, strength: -6200, data_rate: 270.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'ac:3a:67:ed:6a:eb' with SSID: SCADA, freq: 5320, rank: 1964, strength: -6300, data_rate: 240.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:30:72:ae' with SSID: MIDGUEST, freq: 5240, rank: 1964, strength: -6300, data_rate: 240.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Added new Network "MIDGUEST" security psk
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'ac:3a:67:ed:6a:ec' with SSID: MIDCORP, freq: 5320, rank: 1964, strength: -6300, data_rate: 240.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Added new Network "MIDCORP" security 8021x
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:30:72:ad' with SSID: MIDTEST, freq: 5240, rank: 1473, strength: -6400, data_rate: 180.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Added new Network "MIDTEST" security 8021x
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'ac:3a:67:ed:6a:ed' with SSID: MIDTEST, freq: 5320, rank: 1473, strength: -6400, data_rate: 180.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'ac:3a:67:ed:6a:ee' with SSID: MIDGUEST, freq: 5320, rank: 1473, strength: -6400, data_rate: 180.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:30:72:ac' with SSID: MIDCORP, freq: 5240, rank: 1473, strength: -6500, data_rate: 180.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'c0:ee:40:64:6a:e5' with SSID: midmark-234567, freq: 2412, rank: 985, strength: -4600, data_rate: 144.4
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Added new Network "midmark-234567" security psk
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'ac:3a:67:ed:6a:e4' with SSID: SCADA, freq: 2437, rank: 492, strength: -5100, data_rate: 72.2
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'ac:3a:67:ed:6a:e3' with SSID: MIDCORP, freq: 2437, rank: 492, strength: -5100, data_rate: 72.2
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'ac:3a:67:ed:6a:e0' with SSID: MIDLAB-AuthTest, freq: 2437, rank: 492, strength: -5300, data_rate: 72.2
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'ac:3a:67:ed:6a:e2' with SSID: MIDTEST, freq: 2437, rank: 492, strength: -5400, data_rate: 72.2
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'ac:3a:67:ed:6a:e1' with SSID: MIDGUEST, freq: 2437, rank: 492, strength: -5400, data_rate: 72.2
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:30:72:aa' with SSID: MIDVERDNC, freq: 5240, rank: 368, strength: -6200, data_rate: 54.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Added new Network "MIDVERDNC" security psk
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS 'ac:3a:67:ed:6a:ea' with SSID: MIDVERDNC, freq: 5320, rank: 368, strength: -6300, data_rate: 54.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:30:ef:e2' with SSID: , freq: 2437, rank: 177, strength: -7600, data_rate: 21.7
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() BSS has hidden SSID
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:52:2c:6f' with SSID: MIDLAB-AuthTest, freq: 5660, rank: 118, strength: -8200, data_rate: 14.4
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:52:2c:62' with SSID: MIDTEST, freq: 2412, rank: 59, strength: -8000, data_rate: 7.2
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:52:2c:64' with SSID: SCADA, freq: 2412, rank: 59, strength: -8000, data_rate: 7.2
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:52:2c:6b' with SSID: SCADA, freq: 5660, rank: 16, strength: -8300, data_rate: 2.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:52:2c:6c' with SSID: MIDCORP, freq: 5660, rank: 16, strength: -8300, data_rate: 2.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '00:18:0a:22:11:ed' with SSID: SERVICEDESKTEST, freq: 2412, rank: 16, strength: -9100, data_rate: 2.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Added new Network "SERVICEDESKTEST" security psk
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:52:2c:6a' with SSID: MIDVERDNC, freq: 5660, rank: 13, strength: -8200, data_rate: 2.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_add_seen_bss() Processing BSS '70:b3:17:43:b9:c2' with SSID: MIDTEST, freq: 2437, rank: 13, strength: -8400, data_rate: 2.0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_autoconnect_start()
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_autoconnect_next() autoconnect: Trying SSID: MIDGUEST
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_autoconnect_next() autoconnect: '70:b3:17:30:72:ae' freq: 5240, rank: 1964, strength: -6300
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_cqm_rssi_update()
Jun 01 15:36:02 cm1sd iwd[7396]: src/wiphy.c:wiphy_radio_work_insert() Inserting work item 2
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:__station_connect_network() connecting to BSS 70:b3:17:30:72:ae
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_enter_state() Old State: autoconnect_quick, new state: connecting (auto)
Jun 01 15:36:02 cm1sd iwd[7396]: src/scan.c:scan_cancel() Trying to cancel scan id 1 for wdev e
Jun 01 15:36:02 cm1sd iwd[7396]: src/wiphy.c:wiphy_radio_work_done() Work item 1 done
Jun 01 15:36:02 cm1sd iwd[7396]: src/wiphy.c:wiphy_radio_work_next() Starting work item 2
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_mlme_notify() MLME notification New Station(19)
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_netdev_event() Associating
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_mlme_notify() MLME notification Authenticate(37)
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_authenticate_event()
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_unicast_notify() Unicast notification Control Port Frame(129)
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_control_port_frame_event()
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_mlme_notify() MLME notification Associate(38)
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_associate_event()
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_link_notify() event 16 on ifindex 17
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_mlme_notify() MLME notification Connect(46)
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_connect_event()
Jun 01 15:36:02 cm1sd iwd[7396]: src/wiphy.c:wiphy_reg_notify() Notification of command Reg Change(36)
Jun 01 15:36:02 cm1sd iwd[7396]: src/wiphy.c:wiphy_update_reg_domain() New reg domain country code for (global) is US
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_get_oci_cb() Obtained OCI: freq: 5240, width: 2, center1: 5230, center2: 0
Jun 01 15:36:02 cm1sd iwd[7396]: src/eapol.c:eapol_handle_ptk_1_of_4() ifindex=17
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_mlme_notify() MLME notification Control Port TX Status(139)
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_unicast_notify() Unicast notification Control Port Frame(129)
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_control_port_frame_event()
Jun 01 15:36:02 cm1sd iwd[7396]: src/eapol.c:eapol_handle_ptk_3_of_4() ifindex=17
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_set_gtk() ifindex=17 key_idx=1
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_handshake_event() Setting keys
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_set_tk() ifindex=17 key_idx=0
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_set_rekey_offload() 17
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_mlme_notify() MLME notification Control Port TX Status(139)
Jun 01 15:36:02 cm1sd iwd[7396]: hardware_rekey not supported
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_connect_cb() 17, result: 0
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_connect_ok()
Jun 01 15:36:02 cm1sd iwd[7396]: [DHCPv4] l_dhcp_client_start:1219 Entering state: DHCP_STATE_SELECTING
Jun 01 15:36:02 cm1sd iwd[7396]: src/wiphy.c:wiphy_radio_work_done() Work item 2 done
Jun 01 15:36:02 cm1sd iwd[7396]: [DHCPv4] dhcp_client_handle_offer:811 Entering state: DHCP_STATE_REQUESTING
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_mlme_notify() MLME notification Frame TX Status(60)
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_link_notify() event 16 on ifindex 17
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_early_neighbor_report_cb() ifindex: 17, error: 0()
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:parse_neighbor_report() Neighbor report received for ac:3a:67:ed:6a:ee: ch 64 (oper class 118), MD not set
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:parse_neighbor_report() Neighbor report received for 70:b3:17:50:5e:ae: ch 100 (oper class 121), MD not set
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:parse_neighbor_report() Neighbor report received for ac:4a:67:72:be:ce: ch 161 (oper class 125), MD not set
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:parse_neighbor_report() Neighbor report received for 70:b3:17:7c:69:ce: ch 149 (oper class 125), MD not set
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:parse_neighbor_report() Neighbor report received for 70:b3:17:43:b9:ce: ch 52 (oper class 118), MD not set
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:parse_neighbor_report() Neighbor report received for 70:b3:17:44:13:e1: ch 112 (oper class 121), MD not set
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_unicast_notify() Unicast notification Frame(59)
Jun 01 15:36:02 cm1sd iwd[7396]: [DHCPv4] dhcp_client_rx_message:915 Entering state: DHCP_STATE_BOUND
Jun 01 15:36:02 cm1sd iwd[7396]: src/netconfig.c:netconfig_event_handler() l_netconfig event 0
Jun 01 15:36:02 cm1sd iwd[7396]: src/netconfig-commit.c:netconfig_commit_print_addrs() installing address: 172.16.152.240
Jun 01 15:36:02 cm1sd iwd[7410]: /usr/sbin/resolvconf: line 713: getopts: not found
Jun 01 15:36:02 cm1sd iwd[7411]: Usage: resolvconf [options] command [argument]
Jun 01 15:36:02 cm1sd iwd[7411]: Inform the system about any DNS updates.
Jun 01 15:36:02 cm1sd iwd[7411]: Commands:
Jun 01 15:36:02 cm1sd iwd[7411]: -a $INTERFACE Add DNS information to the specified interface
Jun 01 15:36:02 cm1sd iwd[7411]: (DNS supplied via stdin in resolv.conf format)
Jun 01 15:36:02 cm1sd iwd[7411]: -C $PATTERN Deprecate DNS information for matched interfaces
Jun 01 15:36:02 cm1sd iwd[7411]: -c $PATTERN Configure DNS information for matched interfaces
Jun 01 15:36:02 cm1sd iwd[7411]: -d $INTERFACE Delete DNS information from the specified interface
Jun 01 15:36:02 cm1sd iwd[7411]: -h Show this help cruft
Jun 01 15:36:02 cm1sd iwd[7411]: -i [$PATTERN] Show interfaces that have supplied DNS information
Jun 01 15:36:02 cm1sd iwd[7411]: optionally from interfaces that match the specified
Jun 01 15:36:02 cm1sd iwd[7411]: pattern
Jun 01 15:36:02 cm1sd iwd[7411]: -l [$PATTERN] Show DNS information, optionally from interfaces
Jun 01 15:36:02 cm1sd iwd[7411]: that match the specified pattern
Jun 01 15:36:02 cm1sd iwd[7411]: -u Run updates from our current DNS information
Jun 01 15:36:02 cm1sd iwd[7411]: --version Echo the resolvconf version
Jun 01 15:36:02 cm1sd iwd[7411]: Options:
Jun 01 15:36:02 cm1sd iwd[7411]: -f Ignore non existent interfaces
Jun 01 15:36:02 cm1sd iwd[7411]: -m metric Give the added DNS information a metric
Jun 01 15:36:02 cm1sd iwd[7411]: -p Mark the interface as private
Jun 01 15:36:02 cm1sd iwd[7411]: -x Mark the interface as exclusive
Jun 01 15:36:02 cm1sd iwd[7411]: Subscriber and System Init Commands:
Jun 01 15:36:02 cm1sd iwd[7411]: -I Init the state dir
Jun 01 15:36:02 cm1sd iwd[7411]: -r $SERVICE Restart the system service
Jun 01 15:36:02 cm1sd iwd[7411]: (restarting a non-existent or non-running service
Jun 01 15:36:02 cm1sd iwd[7411]: should have no output and return 0)
Jun 01 15:36:02 cm1sd iwd[7411]: -R Show the system service restart command
Jun 01 15:36:02 cm1sd iwd[7411]: -v [$PATTERN] echo NEWDOMAIN, NEWSEARCH and NEWNS variables to
Jun 01 15:36:02 cm1sd iwd[7411]: the console
Jun 01 15:36:02 cm1sd iwd[7411]: -V [$PATTERN] Same as -v, but only uses configuration in
Jun 01 15:36:02 cm1sd iwd[7411]: /etc/resolvconf.conf
Jun 01 15:36:02 cm1sd iwd[7396]: src/station.c:station_enter_state() Old State: connecting (auto), new state: connected
Jun 01 15:36:02 cm1sd iwd[7396]: [DHCPv4] dhcp_client_rx_message:948 T1 expiring in 1799618 ms
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_mlme_notify() MLME notification Notify CQM(64)
Jun 01 15:36:02 cm1sd iwd[7396]: src/netdev.c:netdev_cqm_event() Signal change event (above=1 signal=-62)
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-01 15:42 ` Michael John
@ 2023-06-01 15:53 ` James Prestwood
2023-06-01 18:28 ` Michael John
0 siblings, 1 reply; 14+ messages in thread
From: James Prestwood @ 2023-06-01 15:53 UTC (permalink / raw)
To: Michael John, iwd
Hi Michael,
On 6/1/23 8:42 AM, Michael John wrote:
> Hi James,
>
> On 6/1/23 8:06 AM, James Prestwood wrote:
>>> Hi Michael,
>>>
>>> On 6/1/23 6:17 AM, Michael John wrote:
>>>> Hello,
>>>>
>>>> I'm having an issue getting iwd to recognize a virtual interface.
>>>> Using 'iw' I've created a virtual interface called wlan1:
>>>>
>>>> iw dev wlan0 interface add wlan1 type __ap
>>>>
>>>> This leaves me with the following two interfaces:
>>>>
>>>> ~> iw dev
>>>> phy#0
>>>> Interface wlan1
>>>> ifindex 8
>>>> wdev 0x5
>>>> addr c0:ee:40:64:4a:1d
>>>> type AP
>>>> txpower 23.00 dBm
>>>> Interface wlan0
>>>> ifindex 7
>>>> wdev 0x4
>>>> addr c0:ee:40:64:4a:1c
>>>> type managed
>>>> txpower 23.00 dBm
>>>>
>>>> When running 'iwctl' to list devices and APs I'm not seeing wlan1.
>>>>
>>>> ~> iwctl ap list
>>>> Devices in Access Point Mode
>>>> --------------------------------------------------------------------------------
>>>> Name Started
>>>> --------------------------------------------------------------------------------
>>>> No devices in access point mode available.
>>>>
>>>> ~> iwctl device list
>>>> Devices
>>>> --------------------------------------------------------------------------------
>>>> Name Address Powered Adapter
>>>> Mode
>>>> --------------------------------------------------------------------------------
>>>> wlan0 c0:ee:40:64:4a:1c on phy0
>>>> station
>>>>
>>>>
>>>> When previously using 'wpa_supplicant' and 'NetworkManager' this
>>>> virtual interface (wlan1) was usable in AP mode. The radio does
>>>> support AP+STA mode.
>>>>
>>>> ~> iw phy
>>>> ...
>>>> valid interface combinations:
>>>> * #{ AP } <= 3, #{ managed, P2P-client, P2P-GO } <= 2,
>>>> total <= 3, #channels <= 1
>>>> * #{ IBSS } <= 1,
>>>> total <= 1, #channels <= 1
>>>> ...
>>>
>>> So this appears to me that you cannot do AP+STA with this adapater. You
>>> would need to see "AP" and "managed" in the same block e.g.:
>>
>> Actually sorry, I take that back. The interface combos always confuses
>> me when I have to take a look again. The card in my laptop has a similar
>> combo to yours and I can do AP+STA:
>>
>> * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device }
>> <= 1, total <= 3, #channels <= 2
>>
>> In my case I was having issues because the virtual interface was being
>> created in station mode (despite passing "__ap" when creating). Looks
>> like yours is already in AP mode from the "iw dev" command so I'd need
>> to see the debug logs of IWD starting up to see why the iface wasn't
>> recognized. You could also try bringing both interfaces up prior to
>> starting IWD.
>>
>
> Attached is a capture of the log from iwd. I had a wlan0 and wlan1
> created before starting iwd. I noticed after starting iwd my wlan1
> in then gone.
>
> ~> systemctl stop iwd
>
> ~> iw phy phy0 interface add wlan0 type managed
>
> ~> iw dev
> phy#0
> Interface wlan0
> ifindex 15
> wdev 0xc
> addr c0:ee:40:64:4a:1c
> type managed
> txpower 23.00 dBm
>
> ~> iw dev wlan0 interface add wlan1 type __ap
>
> ~> iw dev
> phy#0
> Interface wlan1
> ifindex 16
> wdev 0xd
> addr c0:ee:40:64:4a:1d
> type AP
> txpower 23.00 dBm
> Interface wlan0
> ifindex 15
> wdev 0xc
> addr c0:ee:40:64:4a:1c
> type managed
> txpower 23.00 dBm
>
> ~> systemctl start iwd
>
> ~> iw dev
> phy#0
> Interface wlan0
> ifindex 17
> wdev 0xe
> addr c0:ee:40:64:4a:1c
> ssid MIDGUEST
> type managed
> channel 48 (5240 MHz), width: 40 MHz, center1: 5230 MHz
> txpower 23.00 dBm
>
> Looking at the ifindex ID it looks like iwd created a new interface for wlan0.
Ah ok, this is the problem. This is what IWD does by default. Since your
managing the interfaces you need to specify them with "-i wlanA,wlanB,etc"
This will make IWD retain the interfaces it sees and not delete them.
So in your case:
iwd -i wlan0,wlan1
>
> Thanks,
> Michael
>
>>>
>>> #{ AP, managed, ...} <= 2
>>>
>>> For example this adapter I have:
>>>
>>> valid interface combinations:
>>> * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 2,
>>> total <= 2, #channels <= 1, STA/AP BI must match
>>>
>>> If you could get the debug logs of IWD starting up I could take a look
>>> at those to see why the wlan1 interface wasn't brought up, but to me it
>>> looks like the adapter simply cannot support AP+STA modes at the same time.
>>>
>>> Thanks,
>>> James
>>>
>>>>
>>>> So I'm left wondering if 'iwd' supports virtual interfaces created
>>>> with the 'iw' utility and if so, what am I missing?
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Michael John
>>>>
> CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-01 15:53 ` James Prestwood
@ 2023-06-01 18:28 ` Michael John
2023-06-01 18:34 ` James Prestwood
0 siblings, 1 reply; 14+ messages in thread
From: Michael John @ 2023-06-01 18:28 UTC (permalink / raw)
To: James Prestwood, iwd
Hi James,
on 6/1/23 11:53 AM, James Prestwood wrote:
> Hi Michael,
>
> On 6/1/23 8:42 AM, Michael John wrote:
>> Hi James,
>>
>> On 6/1/23 8:06 AM, James Prestwood wrote:
>>>> Hi Michael,
>>>>
>>>> On 6/1/23 6:17 AM, Michael John wrote:
>>>>> Hello,
>>>>>
>>>>> I'm having an issue getting iwd to recognize a virtual interface.
>>>>> Using 'iw' I've created a virtual interface called wlan1:
>>>>>
>>>>> iw dev wlan0 interface add wlan1 type __ap
>>>>>
>>>>> This leaves me with the following two interfaces:
>>>>>
>>>>> ~> iw dev
>>>>> phy#0
>>>>> Interface wlan1
>>>>> ifindex 8
>>>>> wdev 0x5
>>>>> addr c0:ee:40:64:4a:1d
>>>>> type AP
>>>>> txpower 23.00 dBm
>>>>> Interface wlan0
>>>>> ifindex 7
>>>>> wdev 0x4
>>>>> addr c0:ee:40:64:4a:1c
>>>>> type managed
>>>>> txpower 23.00 dBm
>>>>>
>>>>> When running 'iwctl' to list devices and APs I'm not seeing wlan1.
>>>>>
>>>>> ~> iwctl ap list
>>>>> Devices in Access Point Mode
>>>>> --------------------------------------------------------------------------------
>>>>> Name Started
>>>>> --------------------------------------------------------------------------------
>>>>> No devices in access point mode available.
>>>>>
>>>>> ~> iwctl device list
>>>>> Devices
>>>>> --------------------------------------------------------------------------------
>>>>> Name Address Powered Adapter
>>>>> Mode
>>>>> --------------------------------------------------------------------------------
>>>>> wlan0 c0:ee:40:64:4a:1c on phy0
>>>>> station
>>>>>
>>>>>
>>>>> When previously using 'wpa_supplicant' and 'NetworkManager' this
>>>>> virtual interface (wlan1) was usable in AP mode. The radio does
>>>>> support AP+STA mode.
>>>>>
>>>>> ~> iw phy
>>>>> ...
>>>>> valid interface combinations:
>>>>> * #{ AP } <= 3, #{ managed, P2P-client, P2P-GO } <= 2,
>>>>> total <= 3, #channels <= 1
>>>>> * #{ IBSS } <= 1,
>>>>> total <= 1, #channels <= 1
>>>>> ...
>>>>
>>>> So this appears to me that you cannot do AP+STA with this adapater. You
>>>> would need to see "AP" and "managed" in the same block e.g.:
>>>
>>> Actually sorry, I take that back. The interface combos always confuses
>>> me when I have to take a look again. The card in my laptop has a similar
>>> combo to yours and I can do AP+STA:
>>>
>>> * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device }
>>> <= 1, total <= 3, #channels <= 2
>>>
>>> In my case I was having issues because the virtual interface was being
>>> created in station mode (despite passing "__ap" when creating). Looks
>>> like yours is already in AP mode from the "iw dev" command so I'd need
>>> to see the debug logs of IWD starting up to see why the iface wasn't
>>> recognized. You could also try bringing both interfaces up prior to
>>> starting IWD.
>>>
>>
>> Attached is a capture of the log from iwd. I had a wlan0 and wlan1
>> created before starting iwd. I noticed after starting iwd my wlan1
>> in then gone.
>>
>> ~> systemctl stop iwd
>>
>> ~> iw phy phy0 interface add wlan0 type managed
>>
>> ~> iw dev
>> phy#0
>> Interface wlan0
>> ifindex 15
>> wdev 0xc
>> addr c0:ee:40:64:4a:1c
>> type managed
>> txpower 23.00 dBm
>>
>> ~> iw dev wlan0 interface add wlan1 type __ap
>>
>> ~> iw dev
>> phy#0
>> Interface wlan1
>> ifindex 16
>> wdev 0xd
>> addr c0:ee:40:64:4a:1d
>> type AP
>> txpower 23.00 dBm
>> Interface wlan0
>> ifindex 15
>> wdev 0xc
>> addr c0:ee:40:64:4a:1c
>> type managed
>> txpower 23.00 dBm
>>
>> ~> systemctl start iwd
>>
>> ~> iw dev
>> phy#0
>> Interface wlan0
>> ifindex 17
>> wdev 0xe
>> addr c0:ee:40:64:4a:1c
>> ssid MIDGUEST
>> type managed
>> channel 48 (5240 MHz), width: 40 MHz, center1: 5230 MHz
>> txpower 23.00 dBm
>>
>> Looking at the ifindex ID it looks like iwd created a new interface for wlan0.
>
> Ah ok, this is the problem. This is what IWD does by default. Since your
> managing the interfaces you need to specify them with "-i wlanA,wlanB,etc"
>
> This will make IWD retain the interfaces it sees and not delete them.
>
> So in your case:
>
> iwd -i wlan0,wlan1
>
>>
>> Thanks,
>> Michael
>>
>>>>
>>>> #{ AP, managed, ...} <= 2
>>>>
>>>> For example this adapter I have:
>>>>
>>>> valid interface combinations:
>>>> * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 2,
>>>> total <= 2, #channels <= 1, STA/AP BI must match
>>>>
>>>> If you could get the debug logs of IWD starting up I could take a look
>>>> at those to see why the wlan1 interface wasn't brought up, but to me it
>>>> looks like the adapter simply cannot support AP+STA modes at the same time.
>>>>
>>>> Thanks,
>>>> James
>>>>
>>>>>
>>>>> So I'm left wondering if 'iwd' supports virtual interfaces created
>>>>> with the 'iw' utility and if so, what am I missing?
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Michael John
>>>>>
>
>
Thanks James, that allowed iwd to preserve and see wlan1 and recognize it as
an AP.
~> iwctl device list
Devices
--------------------------------------------------------------------------------
Name Address Powered Adapter Mode
--------------------------------------------------------------------------------
wlan1 c0:ee:40:64:4a:1d on phy0 ap
wlan0 c0:ee:40:64:4a:1c on phy0 station
~> iwctl ap list
Devices in Access Point Mode
--------------------------------------------------------------------------------
Name Started
--------------------------------------------------------------------------------
wlan1 no
My last hurdle appears to be just bringing up an AP.
~> iwctl ap wlan1 start "testnet" test123456
Argument type is wrong
- Michael
CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-01 18:28 ` Michael John
@ 2023-06-01 18:34 ` James Prestwood
2023-06-01 20:00 ` Michael John
0 siblings, 1 reply; 14+ messages in thread
From: James Prestwood @ 2023-06-01 18:34 UTC (permalink / raw)
To: Michael John, iwd
Hi Michael,
<snip>
>>
>>
>
> Thanks James, that allowed iwd to preserve and see wlan1 and recognize it as
> an AP.
>
> ~> iwctl device list
> Devices
> --------------------------------------------------------------------------------
> Name Address Powered Adapter Mode
> --------------------------------------------------------------------------------
> wlan1 c0:ee:40:64:4a:1d on phy0 ap
> wlan0 c0:ee:40:64:4a:1c on phy0 station
>
> ~> iwctl ap list
> Devices in Access Point Mode
> --------------------------------------------------------------------------------
> Name Started
> --------------------------------------------------------------------------------
> wlan1 no
>
>
> My last hurdle appears to be just bringing up an AP.
>
> ~> iwctl ap wlan1 start "testnet" test123456
> Argument type is wrong
I'd need to see the debug logs, but this could be what others have
noticed where certain drivers don't like some of the recent AP mode
changes adding HT capabilities.
Again, don't know for certain without logs, but you could try and work
around this potentially by using an AP profile:
#file: /var/lib/iwd/ap/testnet.ap
[Security]
Passphrase=test123456
[General]
DisableHT=true
Then, you can start the AP:
$ iwctl ap wlan1 start-profile testnet
>
> - Michael
> CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-01 18:34 ` James Prestwood
@ 2023-06-01 20:00 ` Michael John
2023-06-01 20:18 ` James Prestwood
0 siblings, 1 reply; 14+ messages in thread
From: Michael John @ 2023-06-01 20:00 UTC (permalink / raw)
To: James Prestwood, iwd
Hi James,
> Hi Michael,
>
> <snip>
>
>>>
>>>
>>
>> Thanks James, that allowed iwd to preserve and see wlan1 and recognize it as
>> an AP.
>>
>> ~> iwctl device list
>> Devices
>> --------------------------------------------------------------------------------
>> Name Address Powered Adapter Mode
>> --------------------------------------------------------------------------------
>> wlan1 c0:ee:40:64:4a:1d on phy0 ap
>> wlan0 c0:ee:40:64:4a:1c on phy0 station
>>
>> ~> iwctl ap list
>> Devices in Access Point Mode
>> --------------------------------------------------------------------------------
>> Name Started
>> --------------------------------------------------------------------------------
>> wlan1 no
>>
>>
>> My last hurdle appears to be just bringing up an AP.
>>
>> ~> iwctl ap wlan1 start "testnet" test123456
>> Argument type is wrong
>
> I'd need to see the debug logs, but this could be what others have
> noticed where certain drivers don't like some of the recent AP mode
> changes adding HT capabilities.
>
> Again, don't know for certain without logs, but you could try and work
> around this potentially by using an AP profile:
>
> #file: /var/lib/iwd/ap/testnet.ap
> [Security]
> Passphrase=test123456
>
> [General]
> DisableHT=true
>
> Then, you can start the AP:
>
> $ iwctl ap wlan1 start-profile testnet
>
>>
>> - Michael
Here is some log information while using an AP profile.
~> iwctl ap wlan1 start-profile testnet
Argument type is wrong
~> journalctl --no-pager -u iwd --since -5m
-- Logs begin at Thu 2023-06-01 18:53:45 UTC, end at Thu 2023-06-01 18:54:19 UTC. --
Jun 01 18:53:51 cm1sd iwd[8884]: src/agent.c:agent_register() agent register called
Jun 01 18:53:51 cm1sd iwd[8884]: src/agent.c:agent_register() agent :1.84 path /agent/14661
Jun 01 18:53:52 cm1sd iwd[8884]: src/ap.c:ap_validate_band_channel() AP using frequency 2437 and channel width 40MHz
Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0000: -114
Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0020: -114
Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0040: -114
Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00a0: -114
Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00b0: -114
Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00c0: -114
Jun 01 18:53:52 cm1sd iwd[8884]: START_AP failed: -22
Jun 01 18:53:52 cm1sd iwd[8884]: src/agent.c:agent_disconnect() agent :1.84 disconnected
Jun 01 18:53:52 cm1sd iwd[8884]: src/agent.c:agent_free() agent free 0x35ff98
Thanks,
Michael
CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-01 20:00 ` Michael John
@ 2023-06-01 20:18 ` James Prestwood
2023-06-02 11:39 ` Michael John
0 siblings, 1 reply; 14+ messages in thread
From: James Prestwood @ 2023-06-01 20:18 UTC (permalink / raw)
To: Michael John, iwd
Hi Michael,
On 6/1/23 1:00 PM, Michael John wrote:
> Hi James,
>
>> Hi Michael,
>>
>> <snip>
>>
>>>>
>>>>
>>>
>>> Thanks James, that allowed iwd to preserve and see wlan1 and recognize it as
>>> an AP.
>>>
>>> ~> iwctl device list
>>> Devices
>>> --------------------------------------------------------------------------------
>>> Name Address Powered Adapter Mode
>>> --------------------------------------------------------------------------------
>>> wlan1 c0:ee:40:64:4a:1d on phy0 ap
>>> wlan0 c0:ee:40:64:4a:1c on phy0 station
>>>
>>> ~> iwctl ap list
>>> Devices in Access Point Mode
>>> --------------------------------------------------------------------------------
>>> Name Started
>>> --------------------------------------------------------------------------------
>>> wlan1 no
>>>
>>>
>>> My last hurdle appears to be just bringing up an AP.
>>>
>>> ~> iwctl ap wlan1 start "testnet" test123456
>>> Argument type is wrong
>>
>> I'd need to see the debug logs, but this could be what others have
>> noticed where certain drivers don't like some of the recent AP mode
>> changes adding HT capabilities.
>>
>> Again, don't know for certain without logs, but you could try and work
>> around this potentially by using an AP profile:
>>
>> #file: /var/lib/iwd/ap/testnet.ap
>> [Security]
>> Passphrase=test123456
>>
>> [General]
>> DisableHT=true
>>
>> Then, you can start the AP:
>>
>> $ iwctl ap wlan1 start-profile testnet
>>
>>>
>>> - Michael
>
> Here is some log information while using an AP profile.
>
> ~> iwctl ap wlan1 start-profile testnet
> Argument type is wrong
>
> ~> journalctl --no-pager -u iwd --since -5m
> -- Logs begin at Thu 2023-06-01 18:53:45 UTC, end at Thu 2023-06-01 18:54:19 UTC. --
> Jun 01 18:53:51 cm1sd iwd[8884]: src/agent.c:agent_register() agent register called
> Jun 01 18:53:51 cm1sd iwd[8884]: src/agent.c:agent_register() agent :1.84 path /agent/14661
> Jun 01 18:53:52 cm1sd iwd[8884]: src/ap.c:ap_validate_band_channel() AP using frequency 2437 and channel width 40MHz
> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0000: -114
> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0020: -114
> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0040: -114
> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00a0: -114
> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00b0: -114
> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00c0: -114
> Jun 01 18:53:52 cm1sd iwd[8884]: START_AP failed: -22
> Jun 01 18:53:52 cm1sd iwd[8884]: src/agent.c:agent_disconnect() agent :1.84 disconnected
> Jun 01 18:53:52 cm1sd iwd[8884]: src/agent.c:agent_free() agent free 0x35ff98
Seems like DisableHT was not set correctly? With DisableHT=true the AP
should not be using 40MHz channel width, it should use 20Mhz (no-HT).
>
> Thanks,
> Michael
> CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-01 20:18 ` James Prestwood
@ 2023-06-02 11:39 ` Michael John
2023-06-02 12:09 ` Michael John
0 siblings, 1 reply; 14+ messages in thread
From: Michael John @ 2023-06-02 11:39 UTC (permalink / raw)
To: James Prestwood, iwd
Hi James,
>Hi Michael,
>On 6/1/23 1:00 PM, Michael John wrote:
>> Hi James,
>>
>>> Hi Michael,
>>>
>>> <snip>
>>>
>>>>>
>>>>>
>>>>
>>>> Thanks James, that allowed iwd to preserve and see wlan1 and recognize it as
>>>> an AP.
>>>>
>>>> ~> iwctl device list
>>>> Devices
>>>> --------------------------------------------------------------------------------
>>>> Name Address Powered Adapter Mode
>>>> --------------------------------------------------------------------------------
>>>> wlan1 c0:ee:40:64:4a:1d on phy0 ap
>>>> wlan0 c0:ee:40:64:4a:1c on phy0 station
>>>>
>>>> ~> iwctl ap list
>>>> Devices in Access Point Mode
>>>> --------------------------------------------------------------------------------
>>>> Name Started
>>>> --------------------------------------------------------------------------------
>>>> wlan1 no
>>>>
>>>>
>>>> My last hurdle appears to be just bringing up an AP.
>>>>
>>>> ~> iwctl ap wlan1 start "testnet" test123456
>>>> Argument type is wrong
>>>
>>> I'd need to see the debug logs, but this could be what others have
>>> noticed where certain drivers don't like some of the recent AP mode
>>> changes adding HT capabilities.
>>>
>>> Again, don't know for certain without logs, but you could try and work
>>> around this potentially by using an AP profile:
>>>
>>> #file: /var/lib/iwd/ap/testnet.ap
>>> [Security]
>>> Passphrase=test123456
>>>
>>> [General]
>>> DisableHT=true
>>>
>>> Then, you can start the AP:
>>>
>>> $ iwctl ap wlan1 start-profile testnet
>>>
>>>>
>>>> - Michael
>>
>> Here is some log information while using an AP profile.
>>
>> ~> iwctl ap wlan1 start-profile testnet
>> Argument type is wrong
>>
>> ~> journalctl --no-pager -u iwd --since -5m
>> -- Logs begin at Thu 2023-06-01 18:53:45 UTC, end at Thu 2023-06-01 18:54:19 UTC. --
>> Jun 01 18:53:51 cm1sd iwd[8884]: src/agent.c:agent_register() agent register called
>> Jun 01 18:53:51 cm1sd iwd[8884]: src/agent.c:agent_register() agent :1.84 path /agent/14661
>> Jun 01 18:53:52 cm1sd iwd[8884]: src/ap.c:ap_validate_band_channel() AP using frequency 2437 and channel width 40MHz
>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0000: -114
>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0020: -114
>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0040: -114
>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00a0: -114
>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00b0: -114
>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00c0: -114
>> Jun 01 18:53:52 cm1sd iwd[8884]: START_AP failed: -22
>> Jun 01 18:53:52 cm1sd iwd[8884]: src/agent.c:agent_disconnect() agent :1.84 disconnected
>> Jun 01 18:53:52 cm1sd iwd[8884]: src/agent.c:agent_free() agent free 0x35ff98
>
> Seems like DisableHT was not set correctly? With DisableHT=true the AP
> should not be using 40MHz channel width, it should use 20Mhz (no-HT).
>
This is what I have for the profile:
~> cat /var/lib/iwd/ap/testnet.ap
[Security]
Passphrase=test1234
[General]
DisableHT=true
~> iwctl ap list
Devices in Access Point Mode
--------------------------------------------------------------------------------
Name Started
--------------------------------------------------------------------------------
wlan1 no
~> iwctl ap wlan1 show
Access Point Interface
--------------------------------------------------------------------------------
Settable Property Value
--------------------------------------------------------------------------------
Started no
Name
Scanning no
Frequency 0
PairwiseCiphers
GroupCipher
~> iwctl ap wlan1 start-profile testnet
Argument type is wrong
I'll add this is with iwd version 2.3 and with Linux Kernel 4.19.231.
Thanks,
-Michael
CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-02 11:39 ` Michael John
@ 2023-06-02 12:09 ` Michael John
2023-06-06 16:14 ` James Prestwood
0 siblings, 1 reply; 14+ messages in thread
From: Michael John @ 2023-06-02 12:09 UTC (permalink / raw)
To: James Prestwood, iwd
James,
> Hi James,
>
>> Hi Michael,
>> On 6/1/23 1:00 PM, Michael John wrote:
>>> Hi James,
>>>
>>>> Hi Michael,
>>>>
>>>> <snip>
>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> Thanks James, that allowed iwd to preserve and see wlan1 and recognize it as
>>>>> an AP.
>>>>>
>>>>> ~> iwctl device list
>>>>> Devices
>>>>> --------------------------------------------------------------------------------
>>>>> Name Address Powered Adapter Mode
>>>>> --------------------------------------------------------------------------------
>>>>> wlan1 c0:ee:40:64:4a:1d on phy0 ap
>>>>> wlan0 c0:ee:40:64:4a:1c on phy0 station
>>>>>
>>>>> ~> iwctl ap list
>>>>> Devices in Access Point Mode
>>>>> --------------------------------------------------------------------------------
>>>>> Name Started
>>>>> --------------------------------------------------------------------------------
>>>>> wlan1 no
>>>>>
>>>>>
>>>>> My last hurdle appears to be just bringing up an AP.
>>>>>
>>>>> ~> iwctl ap wlan1 start "testnet" test123456
>>>>> Argument type is wrong
>>>>
>>>> I'd need to see the debug logs, but this could be what others have
>>>> noticed where certain drivers don't like some of the recent AP mode
>>>> changes adding HT capabilities.
>>>>
>>>> Again, don't know for certain without logs, but you could try and work
>>>> around this potentially by using an AP profile:
>>>>
>>>> #file: /var/lib/iwd/ap/testnet.ap
>>>> [Security]
>>>> Passphrase=test123456
>>>>
>>>> [General]
>>>> DisableHT=true
>>>>
>>>> Then, you can start the AP:
>>>>
>>>> $ iwctl ap wlan1 start-profile testnet
>>>>
>>>>>
>>>>> - Michael
>>>
>>> Here is some log information while using an AP profile.
>>>
>>> ~> iwctl ap wlan1 start-profile testnet
>>> Argument type is wrong
>>>
>>> ~> journalctl --no-pager -u iwd --since -5m
>>> -- Logs begin at Thu 2023-06-01 18:53:45 UTC, end at Thu 2023-06-01 18:54:19 UTC. --
>>> Jun 01 18:53:51 cm1sd iwd[8884]: src/agent.c:agent_register() agent register called
>>> Jun 01 18:53:51 cm1sd iwd[8884]: src/agent.c:agent_register() agent :1.84 path /agent/14661
>>> Jun 01 18:53:52 cm1sd iwd[8884]: src/ap.c:ap_validate_band_channel() AP using frequency 2437 and channel width 40MHz
>>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0000: -114
>>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0020: -114
>>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 0040: -114
>>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00a0: -114
>>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00b0: -114
>>> Jun 01 18:53:52 cm1sd iwd[8884]: Could not register frame watch type 00c0: -114
>>> Jun 01 18:53:52 cm1sd iwd[8884]: START_AP failed: -22
>>> Jun 01 18:53:52 cm1sd iwd[8884]: src/agent.c:agent_disconnect() agent :1.84 disconnected
>>> Jun 01 18:53:52 cm1sd iwd[8884]: src/agent.c:agent_free() agent free 0x35ff98
>>
>> Seems like DisableHT was not set correctly? With DisableHT=true the AP
>> should not be using 40MHz channel width, it should use 20Mhz (no-HT).
>>
>
> This is what I have for the profile:
>
> ~> cat /var/lib/iwd/ap/testnet.ap
> [Security]
> Passphrase=test1234
>
> [General]
> DisableHT=true
>
> ~> iwctl ap list
> Devices in Access Point Mode
> --------------------------------------------------------------------------------
> Name Started
> --------------------------------------------------------------------------------
> wlan1 no
>
> ~> iwctl ap wlan1 show
> Access Point Interface
> --------------------------------------------------------------------------------
> Settable Property Value
> --------------------------------------------------------------------------------
> Started no
> Name
> Scanning no
> Frequency 0
> PairwiseCiphers
> GroupCipher
>
> ~> iwctl ap wlan1 start-profile testnet
> Argument type is wrong
>
> I'll add this is with iwd version 2.3 and with Linux Kernel 4.19.231.
>
> Thanks,
>-Michael
After looking through the commit history I see the DisableHT support was
added right after the 2.3 release. I've updated to 2.5 and retried and
was successful at getting the AP up.
Thanks for your help James!
-Michael
CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-02 12:09 ` Michael John
@ 2023-06-06 16:14 ` James Prestwood
2023-06-07 12:04 ` Michael John
0 siblings, 1 reply; 14+ messages in thread
From: James Prestwood @ 2023-06-06 16:14 UTC (permalink / raw)
To: Michael John, iwd
Hi Michael,
>
>
> After looking through the commit history I see the DisableHT support was
> added right after the 2.3 release. I've updated to 2.5 and retried and
> was successful at getting the AP up.
>
> Thanks for your help James!
Great! To try and get this addressed better could you provide the
wireless hardware you are using?
>
> -Michael
> CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: issue using virtual interface with iwd
2023-06-06 16:14 ` James Prestwood
@ 2023-06-07 12:04 ` Michael John
0 siblings, 0 replies; 14+ messages in thread
From: Michael John @ 2023-06-07 12:04 UTC (permalink / raw)
To: James Prestwood, iwd
Hi James,
> Hi Michael,
>
>>
>>
>> After looking through the commit history I see the DisableHT support was
>> added right after the 2.3 release. I've updated to 2.5 and retried and
>> was successful at getting the AP up.
>>
>> Thanks for your help James!
>
> Great! To try and get this addressed better could you provide the
> wireless hardware you are using?
>
>>
>> -Michael
The wireless chipset is a NXP 88W8997/88PG823. It's part of a 60SOM from Laird,
believe its one of Laird's Sterling radio.
~> cat /sys/class/net/wlan0/device/lrd/info
Driver name : lrdmwl
Chip type : 88W8997-SDIO
HW version : 7
FW version : 5.5.43.5
DRV version : 9.32.0.13
OTP version : 2
OTP num mac : 3
Radio Type : SU
MAC address : c0:ee:40:64:4a:1c
Region code : 0x10 (0x10)
Country code: 'US' ('US')
TX antenna : 2
RX antenna : 2
lrdmwl is the Laird wireless driver being used.
For reference: this is the SOM:
https://www.lairdconnect.com/system-on-module/microchip/60-series-som-wifi-80211ac-and-bluetooth-51
-Michael
CONFIDENTIALITY NOTICE: This message, including any attachments, contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2023-06-07 12:04 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-01 13:17 issue using virtual interface with iwd Michael John
2023-06-01 15:06 ` James Prestwood
2023-06-01 15:17 ` James Prestwood
2023-06-01 15:42 ` Michael John
2023-06-01 15:53 ` James Prestwood
2023-06-01 18:28 ` Michael John
2023-06-01 18:34 ` James Prestwood
2023-06-01 20:00 ` Michael John
2023-06-01 20:18 ` James Prestwood
2023-06-02 11:39 ` Michael John
2023-06-02 12:09 ` Michael John
2023-06-06 16:14 ` James Prestwood
2023-06-07 12:04 ` Michael John
2023-06-01 15:38 ` Denis Kenzior
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.