Hi Daniel and Denis,
I got a final hardware prototype to run iwd + connman, the WiFi works
with wpa_supplicant, now I changed to use iwd version 1.26 and connman
I have 2 network interfaces, an 4G LTE and a WiFi so I want to use
connman to control interface connection PreferredTechnologies =
Following your advice, I set up EnableNetworkConfiguration=false in
/etc/iwd/main.conf, the WiFi was connected, but no IP address. Here is
On 12/3/21, Daniel Wagner <wagi(a)monom.org> wrote:
> On 30.11.21 23:42, Denis Kenzior wrote:
>> Note that for iwd + connman, connman would be the one performing DHCP
>> and iwd should use EnableNetworkConfiguration=false. Daniel can correct
>> me if I'm wrong.
> This is correct. Though I think it should be possible to change this.
> For example for VPN the VPN service tells ConnMan the IP configuration
> to use. The iwd plugin could do the amse and tell the ConnMan core which
> IP configuration to use.
$ cat /etc/iwd/main.conf
The WiFi interface is connected:
$ iwctl station mlan0 show
Settable Property Value
Connected network JupiterIoT
No IP addresses Is DHCP client configured?
RSSI -54 dBm
TxBitrate 19500 Kbit/s
RxBitrate 1000 Kbit/s
The DHCP works as well:
# udhcpc -i mlan0
udhcpc: started, v1.35.0
udhcpc: broadcasting discover
udhcpc: broadcasting select for 192.168.0.101, server 192.168.0.1
udhcpc: lease of 192.168.0.101 obtained from 192.168.0.1, lease time 86400
But there is no IP address:
mlan0 Link encap:Ethernet HWaddr D4:CA:6E:A4:E8:E0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:188 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:11256 (10.9 KiB) TX bytes:6990 (6.8 KiB)
What I could be missing in iwd configuration?
The iwd also kept showing the following message, the 34:XX:XX:XX:b1:a2
is not the wlan MAC address, what did that mean?
[ 8456.501736] wlan: Send EAPOL pkt to 34:XX:XX:XX:b1:a2
I set up my WiFi driver module to connect one WiFi modem in station
mode, no AP, no WIFIDIRECT, only one WiFi modem is available so no
roaming. After it connected to the WiFi modem, iwd kept scanning the
For what purpose should iwd be configured to keep scanning after
connection? Should iwd be set up isablePeriodicScan=true and
DisableRoamingScan=true in main.conf?
How to set up iwd to scan just for the station not for the AP? Or
there is no distinction between scanning AP or station?
A major concern is it is also connected to an AP MAC 34:XX:XX:XX:b1:a2
which is not my WiFi modem MAC, I have no idea where that AP from,
that could be a security issue.
[ 1333.979194] wlan: SCAN COMPLETED: scanned AP count=5
[ 1414.017667] wlan: mlan0 START SCAN
[ 1415.628124] wlan: SCAN COMPLETED: scanned AP count=6
[ 1575.675241] wlan: mlan0 START SCAN
[ 1577.286099] wlan: SCAN COMPLETED: scanned AP count=3
[ 1724.631357] wlan: SCAN COMPLETED: scanned AP count=1
[ 1724.657147] wlan: Connected to bssid 34:XX:XX:XX:b1:a2 successfully
[ 1724.723445] mlan0:
[ 1724.723719] wlan: Send EAPOL pkt to 34:XX:XX:XX:b1:a2
[ 1724.823275] mlan0:
[ 1724.823365] wlan: Send EAPOL pkt to 34:XX:XX:XX:b1:a2
Appreciate your insight comments.
I got the following error messages, but iwd was still running and the
network was connected. Was it serious or should I not worry about it?
# systemctl status iwd -l
* iwd.service - Wireless service
enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-07-06 09:59:35 UTC; 42min ago
Main PID: 6431 (iwd)
`- 6431 /usr/libexec/iwd
Jul 06 09:59:35 solar iwd: HT Capabilities:
Jul 06 09:59:35 solar iwd: HT20
Jul 06 09:59:35 solar iwd: Short GI for 20Mhz
Jul 06 09:59:35 solar iwd: HT RX MCS indexes:
Jul 06 09:59:35 solar iwd: 0-7
Jul 06 09:59:35 solar iwd: Ciphers: CCMP TKIP BIP
Jul 06 09:59:35 solar iwd: Supported iftypes: station ap
Jul 06 09:59:35 solar iwd: Wiphy mwiphy0 will only use the
Jul 06 10:17:22 solar iwd: WARNING:
Jul 06 10:17:22 solar iwd: WARNING:
Please correct me if I am wrong, but I thought that iwd is a Linux
WiFi daemon to manage Linux WiFi, it has no mechanism to support
cellular networks like 4G LTE, so why does it have a build argument
--enable-ofono and what is that for?
--enable-ofono Enable support for oFono SIM authentication
Are there any chances that iwd could support cellular networks as well?