Unable to create a hotspot

Technical Support
, , ,
1

Question about broadcasting a hotspot from the iMX8.

I’ve got the following command + error when I try to broadcast a network (connected to the device in an Apalis board over serial):

fio@maidbot-don-d8c0a6cf6807:~$ nmcli device wifi hotspot con-name host-device ssid Maidbot-4818 band bg password Nbjecpu5929
[   35.870001] mwifiex_pcie 0000:01:00.0: info: successfully disconnected from 18:e8:29:65:68:02: reason code 3
[   35.926006] +V3.3: disabling
[   35.928894] +V3.3_AUDIO: disabling
[   35.932346] +V1.8: disabling
[   35.935261] pcie_switch: disabling
[   36.066338] mwifiex_pcie 0000:01:00.0: CMD_RESP: cmd 0xf7 error, result=0x2
[   36.077394] mwifiex_pcie 0000:01:00.0: CMD_RESP: cmd 0x112 error, result=0x1
[   46.165971] mwifiex_pcie 0000:01:00.0: mwifiex_cmd_timeout_func: Timeout cmd id = 0xb0, act = 0x1
[   46.174926] mwifiex_pcie 0000:01:00.0: num_data_h2c_failure = 0
[   46.180873] mwifiex_pcie 0000:01:00.0: num_cmd_h2c_failure = 0
[   46.186720] mwifiex_pcie 0000:01:00.0: is_cmd_timedout = 1
[   46.192219] mwifiex_pcie 0000:01:00.0: num_tx_timeout = 0
[   46.197632] mwifiex_pcie 0000:01:00.0: last_cmd_index = 2
[   46.203046] mwifiex_pcie 0000:01:00.0: last_cmd_id: 5b 00 12 01 b0 00 28 00 28 00
[   46.210557] mwifiex_pcie 0000:01:00.0: last_cmd_act: 01 00 01 00 01 00 13 00 13 00
[   46.218142] mwifiex_pcie 0000:01:00.0: last_cmd_resp_index = 1
[   46.223998] mwifiex_pcie 0000:01:00.0: last_cmd_resp_id: 5b 80 12 81 28 80 28 80 28 80
[   46.231935] mwifiex_pcie 0000:01:00.0: last_event_index = 1
[   46.237513] mwifiex_pcie 0000:01:00.0: last_event: 33 00 58 00 2b 00 1c 00 33 00
[   46.244921] mwifiex_pcie 0000:01:00.0: data_sent=0 cmd_sent=1
[   46.250678] mwifiex_pcie 0000:01:00.0: ps_mode=0 ps_state=0
[   46.256311] mwifiex_pcie 0000:01:00.0: Failed to set AP configuration
[   46.257377] mwifiex_pcie 0000:01:00.0: ===mwifiex driverinfo dump start===
[   46.262799] mwifiex_pcie 0000:01:00.0: Failed to start AP
[   46.269727] mwifiex_pcie 0000:01:00.0: info: MWIFIEX VERSION: mwifiex 1.0 (16.68.1.p195) 
[   46.283334] mwifiex_pcie 0000:01:00.0: PCIE register dump start
[   46.289312] mwifiex_pcie 0000:01:00.0: pcie scratch register:
[   46.295108] mwifiex_pcie 0000:01:00.0: reg:0xcf0, value=0xfedcba00
[   46.295108] reg:0xcf8, value=0x18f0022
[   46.295108] reg:0xcfc, value=0x1e1e207
[   46.295108] 
[   46.310269] mwifiex_pcie 0000:01:00.0: PCIE register dump end
[   46.310697] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.316103] mwifiex_pcie 0000:01:00.0: ===mwifiex driverinfo dump end===
[   46.322338] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[   46.329046] mwifiex_pcie 0000:01:00.0: == mwifiex firmware dump start ==
[   46.341880] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.348172] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[   46.354281] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.360611] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[   46.366647] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.372947] mwifiex_pcie 0000:01:00.0: deleting the crypto keys
[   46.379247] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.385544] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.391846] mwifiex_pcie 0000:01:00.0: wifi0: changing to 2 not supported
[   46.398747] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.405125] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.411490] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.417786] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.429863] mwifiex_pcie 0000:01:00.0: wifi0: changing to 2 not supported
[   46.438379] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.444676] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.451413] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   46.457710] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state

I’ve also seen:

Error: Connection activation failed: (11) 802.1X supplicant took too long to authenticate.

But I’m not sure how to debug the issue from here. Wondering what else I could look at to figure out what the problem is? Is there an issue going through NetworkManager to broadcast an access point?

2

Hi @nckswt

I think this page will help you here. Please let me know if you are successful.

Drew

3

Followed the example on that page and this is what I got:

root@maidbot-don-d8c0a6cf660b:/# nmcli con add type wifi ifname uap0 mode ap con-name hotspot-test ssid test-hotspot-ssid
Connection 'hotspot-test' (640b09e1-ab94-4986-9429-925f792279fb) successfully added.
root@maidbot-don-d8c0a6cf660b:/# nmcli con modify hotspot-test 802-11-wireless-security.key-mgmt wpa-psk
root@maidbot-don-d8c0a6cf660b:/# nmcli con modify hotspot-test 802-11-wireless-security.proto rsn
root@maidbot-don-d8c0a6cf660b:/# nmcli con modify hotspot-test 802-11-wireless-security.group ccmp
root@maidbot-don-d8c0a6cf660b:/# nmcli con modify hotspot-test 802-11-wireless-security.pairwise ccmp
root@maidbot-don-d8c0a6cf660b:/# nmcli con modify hotspot-test 802-11-wireless-security.psk password1234
root@maidbot-don-d8c0a6cf660b:/# nmcli con modify hotspot-test ipv4.addresses 10.10.10.10
root@maidbot-don-d8c0a6cf660b:/# nmcli con modify hotspot-test ipv4.method manual
root@maidbot-don-d8c0a6cf660b:/# nmcli con up hotspot-test
Error: Connection activation failed: No suitable device found for this connection (device wifi0 not available because profile is not compatible with device (mismatching interface name)).

Tried doing the exact same thing with nmcli con add type wifi ifname wifi0 mode ap con-name hotspot-test ssid test-hotspot-ssid

For reference here’s my ifconfig:

# ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:cc:2e:4b:f6  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 286  bytes 27822 (27.8 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 286  bytes 27822 (27.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wifi0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.140.126  netmask 255.255.255.0  broadcast 192.168.140.255
        inet6 fe80::689:5921:aa94:e182  prefixlen 64  scopeid 0x20<link>
        ether d8:c0:a6:cf:66:0b  txqueuelen 1000  (Ethernet)
        RX packets 1459  bytes 185483 (185.4 KB)
        RX errors 0  dropped 10  overruns 0  frame 0
        TX packets 983  bytes 149591 (149.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
4

What SOM and carrier board are you using? What does ifconfig -a return?
Drew