Navigation

    MakerGram Logo

    MakerGram
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags
    • Users
    • Groups

    NMCLI AP Mode config error | Connection activation failed: No suitable device found for this connection | Raspberry Pi 3 Model B Rev 1.2

    Raspberry Pi
    2
    2
    62
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • rafitc99
      rafitc99 last edited by

      I was trying to configure AP mode in Raspberrypi by using Network Manager. I'm using the below script. but it is throwing some errors.

      Bash Script to set AP Mode

      host="MyRPiAPMode"
sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host
sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared
sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk
sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword"
sudo nmcli radio wifi on
sudo nmcli con up $host

      Error ----

      Connection 'MyRPiAPMode' (60965f2a-f510-48ef-afaf-0864242d0c06) successfully added.
Error: Connection activation failed: No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name)).

      nmcli con (After script execution)

      NAME                UUID                                  TYPE      DEVICE 
Wired connection 1  9589ff1a-9923-3de3-a8a4-90b319661878  ethernet  eth0   
MyRPiAPMode         60965f2a-f510-48ef-afaf-0864242d0c06  wifi      --

      nmcli dev

      DEVICE  TYPE      STATE        CONNECTION         
eth0    ethernet  connected    Wired connection 1 
wlan0   wifi      unavailable  --                 
lo      loopback  unmanaged    --

      I tried to make it availble via sudo nmcli radio wifi on
      But not working.

      this is the log

      -- Journal begins at Sat 2021-08-07 09:28:21 IST. --
Aug 10 15:06:19 NWPI-b5b072 NetworkManager[16140]: <info>  [1660124179.9816] audit: op="connection-update" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" args="802-11-wireless-security.psk" pid=25120 uid=0 result="success"
Aug 10 15:06:20 NWPI-b5b072 NetworkManager[16140]: <info>  [1660124180.0902] audit: op="radio-control" arg="wireless-enabled" pid=25125 uid=0 result="success"
Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info>  [1660124181.4241] agent-manager: agent[641f99ab55d9691c,:1.692/nmcli-connect/0]: agent registered
Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info>  [1660124181.4281] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))."
Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info>  [1660124212.0573] agent-manager: agent[70ee130ba0f26cd7,:1.696/nmcli-connect/1000]: agent registered
Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info>  [1660124212.0614] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))."
Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info>  [1660124243.0370] agent-manager: agent[cc77ef461499c164,:1.700/nmcli-connect/0]: agent registered
Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info>  [1660124243.0414] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))."
Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info>  [1660124261.8406] agent-manager: agent[79b01af218789b42,:1.702/nmcli-connect/0]: agent registered
Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info>  [1660124261.8446] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))."
      salmanfaris 1 Reply Last reply Reply Quote 0
      • salmanfaris
        salmanfaris @rafitc99 last edited by

        @rafitc99 said in NMCLI AP Mode config error | Connection activation failed: No suitable device found for this connection | Raspberry Pi 3 Model B Rev 1.2:

        host="MyRPiAPMode"
        sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host
        sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared
        sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk
        sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword"
        sudo nmcli radio wifi on
        sudo nmcli con up $host

        Hi @rafitc99, Are you able to set up the AP when trying the commands individually?

        1 Reply Last reply Reply Quote 0
        • First post
          Last post

        Recent Posts

        • @rafitc99 said in NMCLI AP Mode config error | Connection activation failed: No suitable device found for this connection | Raspberry Pi 3 Model B Rev 1.2:

          host="MyRPiAPMode"
          sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host
          sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared
          sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk
          sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword"
          sudo nmcli radio wifi on
          sudo nmcli con up $host

          Hi @rafitc99, Are you able to set up the AP when trying the commands individually?

          • read more

        • I was trying to configure AP mode in Raspberrypi by using Network Manager. I'm using the below script. but it is throwing some errors.

          Bash Script to set AP Mode

          host="MyRPiAPMode" sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword" sudo nmcli radio wifi on sudo nmcli con up $host

          Error ----

          Connection 'MyRPiAPMode' (60965f2a-f510-48ef-afaf-0864242d0c06) successfully added. Error: Connection activation failed: No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name)).

          nmcli con (After script execution)

          NAME UUID TYPE DEVICE Wired connection 1 9589ff1a-9923-3de3-a8a4-90b319661878 ethernet eth0 MyRPiAPMode 60965f2a-f510-48ef-afaf-0864242d0c06 wifi --

          nmcli dev

          DEVICE TYPE STATE CONNECTION eth0 ethernet connected Wired connection 1 wlan0 wifi unavailable -- lo loopback unmanaged --

          I tried to make it availble via sudo nmcli radio wifi on
          But not working.

          this is the log

          -- Journal begins at Sat 2021-08-07 09:28:21 IST. -- Aug 10 15:06:19 NWPI-b5b072 NetworkManager[16140]: <info> [1660124179.9816] audit: op="connection-update" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" args="802-11-wireless-security.psk" pid=25120 uid=0 result="success" Aug 10 15:06:20 NWPI-b5b072 NetworkManager[16140]: <info> [1660124180.0902] audit: op="radio-control" arg="wireless-enabled" pid=25125 uid=0 result="success" Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info> [1660124181.4241] agent-manager: agent[641f99ab55d9691c,:1.692/nmcli-connect/0]: agent registered Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info> [1660124181.4281] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info> [1660124212.0573] agent-manager: agent[70ee130ba0f26cd7,:1.696/nmcli-connect/1000]: agent registered Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info> [1660124212.0614] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info> [1660124243.0370] agent-manager: agent[cc77ef461499c164,:1.700/nmcli-connect/0]: agent registered Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info> [1660124243.0414] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info> [1660124261.8406] agent-manager: agent[79b01af218789b42,:1.702/nmcli-connect/0]: agent registered Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info> [1660124261.8446] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))."

          • read more

        • alt text

          Raspberry Pi Zero 2 W uses the same Broadcom BCM2710A1 SoC die as the launch version of Raspberry Pi 3, with Arm cores slightly down-clocked to 1GHz, bundled into a single space-saving package alongside 512MB of LPDDR2 SDRAM.

          Here are the highlights:

          Broadcom BCM2710A1, quad-core 64-bit SoC (Arm Cortex-A53 @ 1GHz) 512MB LPDDR2 SDRAM 2.4GHz IEEE 802.11b/g/n wireless LAN, * Bluetooth 4.2, BLE 1 × USB 2.0 interface with OTG HAT-compatible 40 pin I/O header footprint MicroSD card slot Mini HDMI port Composite video and reset pin solder points CSI-2 camera connector H.264, MPEG-4 decode (1080p30); H.264 encode (1080p30) OpenGL ES 1.1, 2.0 graphics

          src: https://www.raspberrypi.com/news/new-raspberry-pi-zero-2-w-2/

          • read more

        • @vishnumaiea :grin: :hand_with_index_and_middle_fingers_crossed:

          • read more

        • @salmanfaris Yeah, just like features and price, long term support is also crucial in determining the efficacy of a microcontroller. What RPi has done with the new introduction of the MCU is close to perfection. Like you said, they had everything ready before the release and that how it should be. No other manufacturer has ever done this before. RPi understands their users and what they seek, as always. With that, they have been able to pull something off that no other manufacturer could.

          RP2040 is not just going to be used in hobby spectrum, but also high volume commercial applications. And that's why I said before it is setting off a REVOLUTION. It's just a matter of time RP2040 supersedes ATmega328 in popularity. Microchip has to worry again! 🤭

          • read more
        By MakerGram | A XiStart Initiative | Built with ♥ NodeBB
        Copyright © 2021 MakerGram, All rights reserved.
        Privacy Policy | Terms & Conditions | Disclaimer | Code of Conduct