Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Wifi Tethering (KeithG)
----------------------------------------------------------------------
Date: Tue, 5 May 2020 17:53:40 -0500
From: KeithG <[email protected]>
Subject: Re: Wifi Tethering
To: Daniel Wagner <[email protected]>
Cc: [email protected], [email protected]
Message-ID:
<cag17s_mb31d12d4nmou6pjd759aosujvcpnjibhpamh5v7h...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="0000000000007aaa5f05a4ee859d"
--0000000000007aaa5f05a4ee859d
Content-Type: text/plain; charset="UTF-8"
Daniel,
I am on Arch Linux on my Pi and the latest version of iwd just came out and
I tried this again. I get the same response. I cannot make a connection.
Something tells me that I am doing something very simple wrong.
Current iwd is 1.7 and connman is 1.38. I have built the kernel with the
iwmon module and more of the functions of iwd now show up correctly, now. I
do not know if it is because Arch finally went to 5.4 kernel from 4.19, but
anyway it does look different:
# journalctl | grep iwd
May 05 11:02:20 runeaudio iwd[253]: No Diffie-Hellman support found, WPS
will not be available
May 05 11:02:20 runeaudio iwd[253]: The following options are missing in
the kernel:
May 05 11:02:20 runeaudio iwd[253]: CONFIG_KEY_DH_OPERATIONS
May 05 11:02:20 runeaudio iwd[253]: Wireless daemon version 1.7
May 05 11:02:20 runeaudio iwd[253]: netconfig: Network configuration is
disabled.
May 05 11:02:20 runeaudio iwd[253]: Wiphy: 0, Name: phy0
May 05 11:02:20 runeaudio iwd[253]: Permanent Address:
b8:27:eb:28:18:48
May 05 11:02:20 runeaudio iwd[253]: Bands: 2.4 GHz
May 05 11:02:20 runeaudio iwd[253]: Ciphers: CCMP TKIP
May 05 11:02:20 runeaudio iwd[253]: Supported iftypes: ad-hoc
station ap p2p-client p2p-go p2p-device
May 05 11:02:20 runeaudio iwd[253]: Wiphy phy0 will only use the default
interface
May 05 11:02:21 runeaudio iwd[253]: hardware_rekey not supported
When I type in the commands (either via connman or iwd) to enable AP mode,
all looks correct to me. I get the SSID to advertise. I can type in the
password, but Win10, linux and Android all refuse to connect to it.
Regards,
Keith
On Tue, Apr 28, 2020 at 7:33 AM KeithG <[email protected]> wrote:
> Daniel,
>
> The pcap is here:
> https://drive.google.com/open?id=18G8cM5Ob88YENZ6WCWJjhBDREol7vW-9
>
> Regards,
>
> Keith
>
> On Tue, Apr 28, 2020 at 7:16 AM Daniel Wagner <[email protected]> wrote:
>
>> [Cc: iwd mailing list]
>>
>> On Tue, Apr 28, 2020 at 06:45:25AM -0500, KeithG wrote:
>> > Daniel,
>> >
>> > I built the kernel/modules (I am on Arch on an RPi and the kernel I am
>> > using is 4.19.114) and tried to diagnose the ap mode problem with nlmon
>> and
>> > get this, though I am sure I am doing it wrong:
>> > # modprobe nlmon
>> > # ip link add name nlmon type nlmon
>> > # ip link set dev nlmon allmulticast on
>> > # ip link set dev nlmon up
>> > # tcpdump -i nlmon -w trace-file.pcap
>> > tcpdump: listening on nlmon, link-type NETLINK (Linux netlink), capture
>> > size 262144 bytes
>> > ^C158 packets captured
>> > 163 packets received by filter
>> > 0 packets dropped by kernel
>> > # iwmon -r trace-file.pcap
>> > Wireless monitor ver 1.6
>> > Invalid packet format
>>
>> Could you upload the pcap file somewhere? I suppose the iwd developers
>> might
>> be interested to inspect it.
>>
>> > In another window, I did this to see what was going on:
>> > ~# connmanctl tether wifi on myssid password
>> > Wifi SSID set
>> > Wifi passphrase set
>> > Enabled tethering for wifi
>> > # ip addr
>> > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>> group
>> > default qlen 1000
>> > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> > inet 127.0.0.1/8 scope host lo
>> > valid_lft forever preferred_lft forever
>> > inet6 ::1/128 scope host
>> > valid_lft forever preferred_lft forever
>> > 2: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc
>> fq_codel
>> > state UP group default qlen 1000
>> > link/ether a0:ce:c8:12:ed:05 brd ff:ff:ff:ff:ff:ff
>> > inet 192.168.2.25/24 brd 192.168.2.255 scope global eth0
>> > valid_lft forever preferred_lft forever
>> > inet6 fe80::a2ce:c8ff:fe12:ed05/64 scope link
>> > valid_lft forever preferred_lft forever
>> > 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
>> > fq_codel master tether state DORMANT group default qlen 1000
>> > link/ether b8:27:eb:28:18:48 brd ff:ff:ff:ff:ff:ff
>> > 4: nlmon: <NOARP,ALLMULTI,UP,LOWER_UP> mtu 3904 qdisc noqueue state
>> UNKNOWN
>> > group default qlen 1000
>> > link/netlink
>> > 5: tether: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1500 qdisc
>> > noqueue state DOWN group default qlen 1000
>> > link/ether 9a:69:3a:48:c1:32 brd ff:ff:ff:ff:ff:ff
>> > inet 192.168.0.1/24 brd 192.168.0.255 scope global tether
>> > valid_lft forever preferred_lft forever
>> > inet6 fe80::c20:faff:fec4:92b9/64 scope link
>> > valid_lft forever preferred_lft forever
>> >
>> > I tried to connect to this AP with my Win10 laptop and get the response:
>> > "Can't connect to this network". My Arch Laptop likewise will not
>> connect.
>> >
>> > Now, when I run iwd -d, I get this:
>> > # /usr/lib/iwd/iwd -d
>> > No Diffie-Hellman support found, WPS will not be available
>> > No asymmetric key support found.
>> > TLS based WPA-Enterprise authentication methods will not function.
>> > Kernel 4.20+ is required for this feature.
>> > The following options are missing in the kernel:
>> > CONFIG_ASYMMETRIC_KEY_TYPE
>> > CONFIG_KEY_DH_OPERATIONS
>> > CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE
>> > CONFIG_PKCS7_MESSAGE_PARSER
>> > CONFIG_X509_CERTIFICATE_PARSER
>> > CONFIG_PKCS8_PRIVATE_KEY_PARSER
>> > Wireless daemon version 1.6
>> > src/main.c:main() Using configuration directory /etc/iwd
>> > src/storage.c:storage_create_dirs() Using state directory /var/lib/iwd
>> > src/main.c:nl80211_appeared() Found nl80211 interface
>> > src/module.c:iwd_modules_init()
>> > src/netdev.c:netdev_init() Opening route netlink socket
>> > netconfig: Network configuration is disabled.
>> > src/wsc.c:wsc_init()
>> > src/eap.c:__eap_method_enable()
>> > src/eap-wsc.c:eap_wsc_init()
>> > src/eap-md5.c:eap_md5_init()
>> > src/eap-tls.c:eap_tls_init()
>> > src/eap-ttls.c:eap_ttls_init()
>> > src/eap-mschapv2.c:eap_mschapv2_init()
>> > src/eap-sim.c:eap_sim_init()
>> > src/eap-aka.c:eap_aka_prime_init()
>> > src/eap-aka.c:eap_aka_init()
>> > src/eap-peap.c:eap_peap_init()
>> > src/eap-gtc.c:eap_gtc_init()
>> > src/eap-pwd.c:eap_pwd_init()
>> > plugins/sim_hardcoded.c:sim_hardcoded_init() IWD_SIM_KEYS not set in env
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/wiphy.c:parse_supported_frequencies()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/wiphy.c:parse_supported_bands()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/manager.c:manager_wiphy_dump_callback()
>> > src/wiphy.c:wiphy_update_from_genl()
>> > src/agent.c:agent_register() agent register called
>> > src/agent.c:agent_register() agent :1.7 path /net/connman/iwd_agent
>> > Wiphy: 0, Name: phy0
>> > Permanent Address: b8:27:eb:28:18:48
>> > Bands: 2.4 GHz
>> > Ciphers: CCMP TKIP
>> > Supported iftypes: ad-hoc station ap p2p-client p2p-go
>> p2p-device
>> > Wiphy phy0 will only use the default interface
>> > src/manager.c:manager_interface_dump_callback()
>> > src/manager.c:manager_get_interface_cb()
>> > src/manager.c:manager_use_default()
>> > src/netdev.c:netdev_create_from_genl() Created interface wlan0[3 1]
>> > src/netdev.c:netdev_link_notify() event 16 on ifindex 3
>> > src/netdev.c:netdev_set_4addr() netdev: 3 use_4addr: 0
>> > src/netdev.c:netdev_initial_up_cb() Interface 3 initialized
>> >
>> > strange thing is that most of those features are built in the kernel. My
>> > kernel is 4.19.114 and the config specifies:
>> > # CONFIG_CRYPTO_HW is not set
>> > CONFIG_ASYMMETRIC_KEY_TYPE=y
>> > CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=y
>> > CONFIG_X509_CERTIFICATE_PARSER=y
>> > CONFIG_PKCS7_MESSAGE_PARSER=y
>> > I am currently re-building the kernel with:
>> > CONFIG_KEY_DH_OPERATIONS=y
>> > as it was previously not set.
>> > There does not seem to be any reference to PKCS8 for this kernel.
>> >
>> > Thanks!
>> >
>> > Keith
>> >
>> > On Mon, Apr 27, 2020 at 2:36 AM Daniel Wagner <[email protected]> wrote:
>> >
>> > > On Sat, Apr 25, 2020 at 11:20:45AM -0500, KeithG wrote:
>> > > > I looked at the IWD readme and cannot enable this on the RPi:
>> > > >
>> > > > # ip link set dev nlmon allmulticast on
>> > > > > Cannot find device "nlmon"
>> > >
>> > > The RPi kernel has no support for nlmon enabled. If you want to debug
>> this
>> > > you
>> > > propably need to compile your own RPi kernel with nlmon enabled.
>> > >
>> > > > I did verify a couple things. I do have iwd set explicitly when I
>> start
>> > > > connman
>> > > > /usr/bin/connmand --wifi=iwd_agent -n --nodnsproxy
>> > >
>> > > --wifi=iwd_agent is wrong. If you want iwd support you need to define
>> this
>> > > at compile time only:
>> > >
>> > > ./configure --enable-iwd --disable-wifi
>> > >
>> > > which adds the iwd plugin and disables the wpa_supplicant plugin. But
>> I
>> > > don't
>> > > think it matter. --iwfi-iwd_agent will be ignored and ConnMan will
>> > > dynamically
>> > > discover iwd. Just make sure wpa_supplicant is not running. With the
>> above
>> > > command line you would make sure wpa_supplicant is not accidentally
>> used.
>> > >
>> > > > When I issue the command from connman, the mode changes in iwd:
>> > > >
>> > > > > # connmanctl tether wifi on myssid password
>> > > > > Wifi SSID set
>> > > > > Wifi passphrase set
>> > > > > Enabled tethering for wifi
>> > > > > # ip addr
>> > > > > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state
>> UNKNOWN
>> > > group
>> > > > > default qlen 1000
>> > > > > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> > > > > inet 127.0.0.1/8 scope host lo
>> > > > > valid_lft forever preferred_lft forever
>> > > > > inet6 ::1/128 scope host
>> > > > > valid_lft forever preferred_lft forever
>> > > > > 2: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc
>> > > fq_codel
>> > > > > state UP group default qlen 1000
>> > > > > link/ether a0:ce:c8:12:ed:05 brd ff:ff:ff:ff:ff:ff
>> > > > > inet 192.168.2.25/24 brd 192.168.2.255 scope global eth0
>> > > > > valid_lft forever preferred_lft forever
>> > > > > inet6 fe80::a2ce:c8ff:fe12:ed05/64 scope link
>> > > > > valid_lft forever preferred_lft forever
>> > > > > 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
>> qdisc
>> > > > > fq_codel master tether state DORMANT group default qlen 1000
>> > > > > link/ether b8:27:eb:28:18:48 brd ff:ff:ff:ff:ff:ff
>> > > > > 4: tether: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1500
>> qdisc
>> > > > > noqueue state DOWN group default qlen 1000
>> > > > > link/ether 9a:69:3a:48:c1:32 brd ff:ff:ff:ff:ff:ff
>> > > > > inet 192.168.0.1/24 brd 192.168.0.255 scope global tether
>> > > > > valid_lft forever preferred_lft forever
>> > > > > inet6 fe80::d024:5eff:fe80:1a57/64 scope link
>> > > > > valid_lft forever preferred_lft forever
>> > > > > # iwctl device wlan0 show
>> > > > > Device: wlan0
>> > > > >
>> > > > >
>> > >
>> --------------------------------------------------------------------------------
>> > > > > Settable Property Value
>> > > > >
>> > > > >
>> > >
>> --------------------------------------------------------------------------------
>> > > > > Name wlan0
>> > > > > * Mode ap
>> > > > > * Powered on
>> > > > > Address b8:27:eb:28:18:48
>> > > > > Adapter phy0
>> > > > >
>> > > >
>> > > > I get these responses in the journal when I try to connect but it
>> never
>> > > > connects:
>> > > >
>> > > > > src/netdev.c:netdev_mlme_notify() MLME notification New
>> Station(19)
>> > > > > src/netdev.c:netdev_mlme_notify() MLME notification Del
>> Station(20)
>> > > > > src/netdev.c:netdev_mlme_notify() MLME notification Del
>> Station(20)
>> > > > >
>> > >
>> > > Did you try to run iwd with debug enabled 'iwd -d'? Maybe there is
>> more
>> > > info. And if there isn't any clue, the best way forward is to get
>> > > nlmon running and provide the information the iwd developers. From
>> what I
>> > > see ConnMan is talking to iwd and setups the AP mode.
>> > >
>> > > > I currently use hostapd and dnsmasq to have this headless RPi audio
>> > > > appliance work as an AP for initial setup, but want to remove
>> hostapd and
>> > > > dnsmasq if I can get connman/iwd to do the same thing. I tried to
>> get iwd
>> > > > to go into ap mode and connect, but cannot do it there, either. I
>> do get
>> > > > some messages at startup of iwd. I do not think these are the
>> problem,
>> > > but
>> > > > they are missing kernel modules:
>> > > >
>> > > > No Diffie-Hellman support found, WPS will not be available
>> > > > > No asymmetric key support found.
>> > > > > TLS based WPA-Enterprise authentication methods will not function.
>> > > > > Kernel 4.20+ is required for this feature.
>> > > > > The following options are missing in the kernel:
>> > > > > CONFIG_ASYMMETRIC_KEY_TYPE
>> > > > > CONFIG_KEY_DH_OPERATIONS
>> > > > > CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE
>> > > > > CONFIG_PKCS7_MESSAGE_PARSER
>> > > > > CONFIG_X509_CERTIFICATE_PARSER
>> > > > > CONFIG_PKCS8_PRIVATE_KEY_PARSER
>> > > > > Wireless daemon version 1.6
>> > >
>> > > I don't know but I would suggest to address this in the same go when
>> you
>> > > build
>> > > a new kernel with nlmon support.
>> > >
>> > > Thanks,
>> > > Daniel
>> > >
>>
>
--0000000000007aaa5f05a4ee859d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Daniel,</div><div><br></div><div>I am on Arch Linux o=
n my Pi and the latest version of iwd just came out and I tried this again.=
I get the same response. I cannot make a connection. Something tells me th=
at I am doing something very simple wrong. <br></div><div>Current iwd is 1.=
7 and connman is 1.38. I have built the kernel with the iwmon module and mo=
re of the functions of iwd now show up correctly, now. I do not know if it =
is because Arch finally went to 5.4 kernel from 4.19, but anyway it does lo=
ok different:</div><div><br></div><div># journalctl | grep iwd<br>May 05 11=
:02:20 runeaudio iwd[253]: No Diffie-Hellman support found, WPS will not be=
available<br>May 05 11:02:20 runeaudio iwd[253]: The following options are=
missing in the kernel:<br>May 05 11:02:20 runeaudio iwd[253]: =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 CONFIG_KEY_DH_OPERATIONS<br>May 05 11:02:20 runeaudio iwd=
[253]: Wireless daemon version 1.7<br>May 05 11:02:20 runeaudio iwd[253]: n=
etconfig: Network configuration is disabled.<br>May 05 11:02:20 runeaudio i=
wd[253]: Wiphy: 0, Name: phy0<br>May 05 11:02:20 runeaudio iwd[253]: =C2=A0=
=C2=A0 =C2=A0 =C2=A0 Permanent Address: b8:27:eb:28:18:48<br>May 05 11:02:=
20 runeaudio iwd[253]: =C2=A0 =C2=A0 =C2=A0 =C2=A0 Bands: 2.4 GHz<br>May 05=
11:02:20 runeaudio iwd[253]: =C2=A0 =C2=A0 =C2=A0 =C2=A0 Ciphers: CCMP TKI=
P<br>May 05 11:02:20 runeaudio iwd[253]: =C2=A0 =C2=A0 =C2=A0 =C2=A0 Suppor=
ted iftypes: ad-hoc station ap p2p-client p2p-go p2p-device<br>May 05 11:02=
:20 runeaudio iwd[253]: Wiphy phy0 will only use the default interface<br>M=
ay 05 11:02:21 runeaudio iwd[253]: hardware_rekey not supported</div><div><=
br></div><div>When I type in the commands (either via connman or iwd) to en=
able AP mode, all looks correct to me. I get the SSID to advertise. I can t=
ype in the password, but Win10, linux and Android all refuse to connect to =
it.</div><div><br></div><div>Regards,</div><div><br></div><div>Keith<br></d=
iv><div><br></div><div><br></div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Tue, Apr 28, 2020 at 7:33 AM KeithG <=
;<a href=3D"mailto:[email protected]";>[email protected]</a>> wrote:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><=
div>Daniel,</div><div><br></div><div>The pcap is here:</div><div><a href=3D=
"https://drive.google.com/open?id=3D18G8cM5Ob88YENZ6WCWJjhBDREol7vW-9"; targ=
et=3D"_blank">https://drive.google.com/open?id=3D18G8cM5Ob88YENZ6WCWJjhBDRE=
ol7vW-9</a></div><div><br></div><div>Regards,</div><div><br></div><div>Keit=
h<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Tue, Apr 28, 2020 at 7:16 AM Daniel Wagner <<a href=3D"mai=
lto:[email protected]" target=3D"_blank">[email protected]</a>> wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">[Cc: iwd mailing list]<=
br>
<br>
On Tue, Apr 28, 2020 at 06:45:25AM -0500, KeithG wrote:<br>
> Daniel,<br>
> <br>
> I built the kernel/modules (I am on Arch on an RPi and the kernel I am=
<br>
> using is 4.19.114) and tried to diagnose the ap mode problem with nlmo=
n and<br>
> get this, though I am sure I am doing it wrong:<br>
> # modprobe nlmon<br>
> # ip link add name nlmon type nlmon<br>
> # ip link set dev nlmon allmulticast on<br>
> # ip link set dev nlmon up<br>
> # tcpdump -i nlmon -w trace-file.pcap<br>
> tcpdump: listening on nlmon, link-type NETLINK (Linux netlink), captur=
e<br>
> size 262144 bytes<br>
> ^C158 packets captured<br>
> 163 packets received by filter<br>
> 0 packets dropped by kernel<br>
> # iwmon -r trace-file.pcap<br>
> Wireless monitor ver 1.6<br>
> Invalid packet format<br>
<br>
Could you upload the pcap file somewhere? I suppose the iwd developers migh=
t<br>
be interested to inspect it.<br>
<br>
> In another window, I did this to see what was going on:<br>
> ~# connmanctl tether wifi on myssid password<br>
> Wifi SSID set<br>
> Wifi passphrase set<br>
> Enabled tethering for wifi<br>
> # ip addr<br>
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKN=
OWN group<br>
> default qlen 1000<br>
>=C2=A0 =C2=A0 =C2=A0link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:=
00<br>
>=C2=A0 =C2=A0 =C2=A0inet <a href=3D"http://127.0.0.1/8"; rel=3D"noreferr=
er" target=3D"_blank">127.0.0.1/8</a> scope host lo<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_lft forever<br>
>=C2=A0 =C2=A0 =C2=A0inet6 ::1/128 scope host<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_lft forever<br>
> 2: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdis=
c fq_codel<br>
> state UP group default qlen 1000<br>
>=C2=A0 =C2=A0 =C2=A0link/ether a0:ce:c8:12:ed:05 brd ff:ff:ff:ff:ff:ff<=
br>
>=C2=A0 =C2=A0 =C2=A0inet <a href=3D"http://192.168.2.25/24"; rel=3D"nore=
ferrer" target=3D"_blank">192.168.2.25/24</a> brd 192.168.2.255 scope globa=
l eth0<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_lft forever<br>
>=C2=A0 =C2=A0 =C2=A0inet6 fe80::a2ce:c8ff:fe12:ed05/64 scope link<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_lft forever<br>
> 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 =
qdisc<br>
> fq_codel master tether state DORMANT group default qlen 1000<br>
>=C2=A0 =C2=A0 =C2=A0link/ether b8:27:eb:28:18:48 brd ff:ff:ff:ff:ff:ff<=
br>
> 4: nlmon: <NOARP,ALLMULTI,UP,LOWER_UP> mtu 3904 qdisc noqueue st=
ate UNKNOWN<br>
> group default qlen 1000<br>
>=C2=A0 =C2=A0 =C2=A0link/netlink<br>
> 5: tether: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1500 =
qdisc<br>
> noqueue state DOWN group default qlen 1000<br>
>=C2=A0 =C2=A0 =C2=A0link/ether 9a:69:3a:48:c1:32 brd ff:ff:ff:ff:ff:ff<=
br>
>=C2=A0 =C2=A0 =C2=A0inet <a href=3D"http://192.168.0.1/24"; rel=3D"noref=
errer" target=3D"_blank">192.168.0.1/24</a> brd 192.168.0.255 scope global =
tether<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_lft forever<br>
>=C2=A0 =C2=A0 =C2=A0inet6 fe80::c20:faff:fec4:92b9/64 scope link<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_lft forever<br>
> <br>
> I tried to connect to this AP with my Win10 laptop and get the respons=
e:<br>
> "Can't connect to this network". My Arch Laptop likewise=
will not connect.<br>
> <br>
> Now, when I run iwd -d, I get this:<br>
> # /usr/lib/iwd/iwd -d<br>
> No Diffie-Hellman support found, WPS will not be available<br>
> No asymmetric key support found.<br>
> TLS based WPA-Enterprise authentication methods will not function.<br>
> Kernel 4.20+ is required for this feature.<br>
> The following options are missing in the kernel:<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_ASYMMETRIC_KEY_TYPE<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_KEY_DH_OPERATIONS<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE<=
br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_PKCS7_MESSAGE_PARSER<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_X509_CERTIFICATE_PARSER<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_PKCS8_PRIVATE_KEY_PARSER<br>
> Wireless daemon version 1.6<br>
> src/main.c:main() Using configuration directory /etc/iwd<br>
> src/storage.c:storage_create_dirs() Using state directory /var/lib/iwd=
<br>
> src/main.c:nl80211_appeared() Found nl80211 interface<br>
> src/module.c:iwd_modules_init()<br>
> src/netdev.c:netdev_init() Opening route netlink socket<br>
> netconfig: Network configuration is disabled.<br>
> src/wsc.c:wsc_init()<br>
> src/eap.c:__eap_method_enable()<br>
> src/eap-wsc.c:eap_wsc_init()<br>
> src/eap-md5.c:eap_md5_init()<br>
> src/eap-tls.c:eap_tls_init()<br>
> src/eap-ttls.c:eap_ttls_init()<br>
> src/eap-mschapv2.c:eap_mschapv2_init()<br>
> src/eap-sim.c:eap_sim_init()<br>
> src/eap-aka.c:eap_aka_prime_init()<br>
> src/eap-aka.c:eap_aka_init()<br>
> src/eap-peap.c:eap_peap_init()<br>
> src/eap-gtc.c:eap_gtc_init()<br>
> src/eap-pwd.c:eap_pwd_init()<br>
> plugins/sim_hardcoded.c:sim_hardcoded_init() IWD_SIM_KEYS not set in e=
nv<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/wiphy.c:parse_supported_frequencies()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/wiphy.c:parse_supported_bands()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/manager.c:manager_wiphy_dump_callback()<br>
> src/wiphy.c:wiphy_update_from_genl()<br>
> src/agent.c:agent_register() agent register called<br>
> src/agent.c:agent_register() agent :1.7 path /net/connman/iwd_agent<br=
>
> Wiphy: 0, Name: phy0<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Permanent Address: b8:27:eb:28:18:48<=
br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Bands: 2.4 GHz<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Ciphers: CCMP TKIP<br>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Supported iftypes: ad-hoc station ap =
p2p-client p2p-go p2p-device<br>
> Wiphy phy0 will only use the default interface<br>
> src/manager.c:manager_interface_dump_callback()<br>
> src/manager.c:manager_get_interface_cb()<br>
> src/manager.c:manager_use_default()<br>
> src/netdev.c:netdev_create_from_genl() Created interface wlan0[3 1]<br=
>
> src/netdev.c:netdev_link_notify() event 16 on ifindex 3<br>
> src/netdev.c:netdev_set_4addr() netdev: 3 use_4addr: 0<br>
> src/netdev.c:netdev_initial_up_cb() Interface 3 initialized<br>
> <br>
> strange thing is that most of those features are built in the kernel. =
My<br>
> kernel is 4.19.114 and the config specifies:<br>
> # CONFIG_CRYPTO_HW is not set<br>
> CONFIG_ASYMMETRIC_KEY_TYPE=3Dy<br>
> CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=3Dy<br>
> CONFIG_X509_CERTIFICATE_PARSER=3Dy<br>
> CONFIG_PKCS7_MESSAGE_PARSER=3Dy<br>
> I am currently re-building the kernel with:<br>
> CONFIG_KEY_DH_OPERATIONS=3Dy<br>
> as it was previously not set.<br>
> There does not seem to be any reference to PKCS8 for this kernel.<br>
> <br>
> Thanks!<br>
> <br>
> Keith<br>
> <br>
> On Mon, Apr 27, 2020 at 2:36 AM Daniel Wagner <<a href=3D"mailto:wa=
[email protected]" target=3D"_blank">[email protected]</a>> wrote:<br>
> <br>
> > On Sat, Apr 25, 2020 at 11:20:45AM -0500, KeithG wrote:<br>
> > > I looked at the IWD readme and cannot enable this on the RPi=
:<br>
> > ><br>
> > > # ip link set dev nlmon allmulticast on<br>
> > > > Cannot find device "nlmon"<br>
> ><br>
> > The RPi kernel has no support for nlmon enabled. If you want to d=
ebug this<br>
> > you<br>
> > propably need to compile your own RPi kernel with nlmon enabled.<=
br>
> ><br>
> > > I did verify a couple things. I do have iwd set explicitly w=
hen I start<br>
> > > connman<br>
> > >=C2=A0 /usr/bin/connmand --wifi=3Diwd_agent -n --nodnsproxy<b=
r>
> ><br>
> > --wifi=3Diwd_agent is wrong. If you want iwd support you need to =
define this<br>
> > at compile time only:<br>
> ><br>
> >=C2=A0 =C2=A0 ./configure --enable-iwd --disable-wifi<br>
> ><br>
> > which adds the iwd plugin and disables the wpa_supplicant plugin.=
But I<br>
> > don't<br>
> > think it matter. --iwfi-iwd_agent will be ignored and ConnMan wil=
l<br>
> > dynamically<br>
> > discover iwd. Just make sure wpa_supplicant is not running. With =
the above<br>
> > command line you would make sure wpa_supplicant is not accidental=
ly used.<br>
> ><br>
> > > When I issue the command from connman, the mode changes in i=
wd:<br>
> > ><br>
> > > > # connmanctl tether wifi on myssid password<br>
> > > > Wifi SSID set<br>
> > > > Wifi passphrase set<br>
> > > > Enabled tethering for wifi<br>
> > > > # ip addr<br>
> > > > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noq=
ueue state UNKNOWN<br>
> > group<br>
> > > > default qlen 1000<br>
> > > >=C2=A0 =C2=A0 =C2=A0link/loopback 00:00:00:00:00:00 brd =
00:00:00:00:00:00<br>
> > > >=C2=A0 =C2=A0 =C2=A0inet <a href=3D"http://127.0.0.1/8"; =
rel=3D"noreferrer" target=3D"_blank">127.0.0.1/8</a> scope host lo<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_=
lft forever<br>
> > > >=C2=A0 =C2=A0 =C2=A0inet6 ::1/128 scope host<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_=
lft forever<br>
> > > > 2: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP>=
; mtu 1500 qdisc<br>
> > fq_codel<br>
> > > > state UP group default qlen 1000<br>
> > > >=C2=A0 =C2=A0 =C2=A0link/ether a0:ce:c8:12:ed:05 brd ff:=
ff:ff:ff:ff:ff<br>
> > > >=C2=A0 =C2=A0 =C2=A0inet <a href=3D"http://192.168.2.25/=
24" rel=3D"noreferrer" target=3D"_blank">192.168.2.25/24</a> brd 192.168.2.=
255 scope global eth0<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_=
lft forever<br>
> > > >=C2=A0 =C2=A0 =C2=A0inet6 fe80::a2ce:c8ff:fe12:ed05/64 s=
cope link<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_=
lft forever<br>
> > > > 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_U=
P> mtu 1500 qdisc<br>
> > > > fq_codel master tether state DORMANT group default qlen=
1000<br>
> > > >=C2=A0 =C2=A0 =C2=A0link/ether b8:27:eb:28:18:48 brd ff:=
ff:ff:ff:ff:ff<br>
> > > > 4: tether: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,U=
P> mtu 1500 qdisc<br>
> > > > noqueue state DOWN group default qlen 1000<br>
> > > >=C2=A0 =C2=A0 =C2=A0link/ether 9a:69:3a:48:c1:32 brd ff:=
ff:ff:ff:ff:ff<br>
> > > >=C2=A0 =C2=A0 =C2=A0inet <a href=3D"http://192.168.0.1/2=
4" rel=3D"noreferrer" target=3D"_blank">192.168.0.1/24</a> brd 192.168.0.25=
5 scope global tether<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_=
lft forever<br>
> > > >=C2=A0 =C2=A0 =C2=A0inet6 fe80::d024:5eff:fe80:1a57/64 s=
cope link<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_=
lft forever<br>
> > > > # iwctl device wlan0 show<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Device: wlan=
0<br>
> > > ><br>
> > > ><br>
> > -----------------------------------------------------------------=
---------------<br>
> > > >=C2=A0 =C2=A0Settable=C2=A0 Property=C2=A0 =C2=A0 =C2=A0=
=C2=A0 =C2=A0 =C2=A0 Value<br>
> > > ><br>
> > > ><br>
> > -----------------------------------------------------------------=
---------------<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Name=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 wlan0<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 *=C2=A0 Mode=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ap<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 *=C2=A0 Powered=C2=A0=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0on<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Address=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0b8:27:eb:28:18:48<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Adapter=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0phy0<br>
> > > ><br>
> > ><br>
> > > I get these responses in the journal when I try to connect b=
ut it never<br>
> > > connects:<br>
> > ><br>
> > > > src/netdev.c:netdev_mlme_notify() MLME notification New=
Station(19)<br>
> > > > src/netdev.c:netdev_mlme_notify() MLME notification Del=
Station(20)<br>
> > > > src/netdev.c:netdev_mlme_notify() MLME notification Del=
Station(20)<br>
> > > ><br>
> ><br>
> > Did you try to run iwd with debug enabled 'iwd -d'? Maybe=
there is more<br>
> > info. And if there isn't any clue, the best way forward is to=
get<br>
> > nlmon running and provide the information the iwd developers. Fro=
m what I<br>
> > see ConnMan is talking to iwd and setups the AP mode.<br>
> ><br>
> > > I currently use hostapd and dnsmasq to have this headless RP=
i audio<br>
> > > appliance work as an AP for initial setup, but want to remov=
e hostapd and<br>
> > > dnsmasq if I can get connman/iwd to do the same thing. I tri=
ed to get iwd<br>
> > > to go into ap mode and connect, but cannot do it there, eith=
er. I do get<br>
> > > some messages at startup of iwd. I do not think these are th=
e problem,<br>
> > but<br>
> > > they are missing kernel modules:<br>
> > ><br>
> > > No Diffie-Hellman support found, WPS will not be available<b=
r>
> > > > No asymmetric key support found.<br>
> > > > TLS based WPA-Enterprise authentication methods will no=
t function.<br>
> > > > Kernel 4.20+ is required for this feature.<br>
> > > > The following options are missing in the kernel:<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_ASYMMETRIC_KEY_=
TYPE<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_KEY_DH_OPERATIO=
NS<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_ASYMMETRIC_PUBL=
IC_KEY_SUBTYPE<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_PKCS7_MESSAGE_P=
ARSER<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_X509_CERTIFICAT=
E_PARSER<br>
> > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CONFIG_PKCS8_PRIVATE_K=
EY_PARSER<br>
> > > > Wireless daemon version 1.6<br>
> ><br>
> > I don't know but I would suggest to address this in the same =
go when you<br>
> > build<br>
> > a new kernel with nlmon support.<br>
> ><br>
> > Thanks,<br>
> > Daniel<br>
> ><br>
</blockquote></div>
</blockquote></div>
--0000000000007aaa5f05a4ee859d--
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 55, Issue 1
**************************************
