# Getting below error for wifi-connect on jetson nano

**URL:** <https://forums.balena.io/t/getting-below-error-for-wifi-connect-on-jetson-nano/31915>\
**Category:** balenaOS\
**Created:** [September 11, 2019, 1:03pm UTC](https://forums.balena.io/t/getting-below-error-for-wifi-connect-on-jetson-nano/31915 "2019-09-11T13:03:22Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![yyogeshwar](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/yyogeshwar/32/2369_2.png) [@yyogeshwar](https://forums.balena.io/u/yyogeshwar)\
**Post date:** [September 11, 2019, 1:03pm UTC](https://forums.balena.io/t/getting-below-error-for-wifi-connect-on-jetson-nano/31915/1 "2019-09-11T13:03:22Z")

</div>

Trying to run wifi-connect on jetson nano , getting below error

device uuid - 685fcb8a6920acadfc64fedca8c62c66 , in case someone from balena support wants to look.

 ![29%20PM](https://global.discourse-cdn.com/balena/original/2X/7/75fdfa613ea1a9a5cf1d5043e286f9d4ac0d163f.png)

nmcli d wifi list output ----

 ![34%20PM](https://global.discourse-cdn.com/balena/original/2X/5/53eb36487247bfc95bcfe7f90db6884c9e7f1fd1.png)

docker-compose.yml

![38%20PM](https://global.discourse-cdn.com/balena/original/2X/4/46ae1ea1f71ee55cdfb9d56873b0189f0c24ed99.png)

---

<div class="post-metadata">

**Author:** ![majorz](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/majorz/32/639_2.png) [@majorz](https://forums.balena.io/u/majorz)\
**Post date:** [September 11, 2019, 1:15pm UTC](https://forums.balena.io/t/getting-below-error-for-wifi-connect-on-jetson-nano/31915/2 "2019-09-11T13:15:53Z")

</div>

Thanks for providing the UUID. I will check the NetworkManager and kernel logs now.

---

<div class="post-metadata">

**Author:** ![majorz](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/majorz/32/639_2.png) [@majorz](https://forums.balena.io/u/majorz)\
**Post date:** [September 11, 2019, 1:31pm UTC](https://forums.balena.io/t/getting-below-error-for-wifi-connect-on-jetson-nano/31915/3 "2019-09-11T13:31:36Z")

</div>

The WiFi dongle attached to the device does not support access point mode (or the driver it is using does not support it). It is hard to find a WiFi dongle that runs flawlessly on Linux. I would advise for trying out a few different ones and see what works best for you.

---

<div class="post-metadata">

**Author:** ![ksmith9109](https://avatars.discourse-cdn.com/v4/letter/k/ce73a5/32.png) [@ksmith9109](https://forums.balena.io/u/ksmith9109)\
**Post date:** [October 29, 2019, 3:52am UTC](https://forums.balena.io/t/getting-below-error-for-wifi-connect-on-jetson-nano/31915/5 "2019-10-29T03:52:55Z")

</div>

I am a bit of a newbie but I have had good luck with the

[Intel wifi6 ax200](https://www.intel.com/content/www/us/en/products/wireless/wi-fi-6-series/wi-fi-6-ax200.html)

I have 2 copies of ax200.  
One works on a Windows 64 Pro laptop (old toshiba qosmio)  
The second works on the Nvidia Jetson Nano Developer board…

The intel drivers for wifi seem to work well and are extremely fast.

Good luck…

Ksmith9109

---

<div class="post-metadata">

**Author:** ![gabolema](https://avatars.discourse-cdn.com/v4/letter/g/f6c823/32.png) [@gabolema](https://forums.balena.io/u/gabolema)\
**Post date:** [December 1, 2021, 4:05am UTC](https://forums.balena.io/t/getting-below-error-for-wifi-connect-on-jetson-nano/31915/7 "2021-12-01T04:05:34Z")

</div>

I’m having a similar issue on my Jetson Nano with a TP-link TL-WN722N, same docker-compose file.

```auto
Starting wifi-connect_wifi-connect_1 ... done
Attaching to wifi-connect_wifi-connect_1
wifi-connect_1 | Checking internet connectivity ...
wifi-connect_1 | Your device is already connected to the internet.
wifi-connect_1 | Starting up Wifi-Connect.\n Connect to the Access Point and configure the SSID and Passphrase for the network to connect to.
wifi-connect_1 | Cannot get the NetworkManager service state
wifi-connect_1 | thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: D-Bus error: Failed to connect to socket /host/run/dbus/system_bus_socket: No such file or directory (org.freedesktop.DBus.Error.FileNotFound)', /checkout/src/libcore/result.rs:906:4
wifi-connect_1 | note: Run with `RUST_BACKTRACE=1` for a backtrace.
wifi-connect_1 | Checking internet connectivity ...
wifi-connect_1 | Your device is already connected to the internet.
wifi-connect_1 | Skipping setting up Wifi-Connect Access Point. Will check again in 120 seconds

```

---

<div class="post-metadata">

**Author:** ![builder555](https://avatars.discourse-cdn.com/v4/letter/b/cc9497/32.png) [@builder555](https://forums.balena.io/u/builder555)\
**Post date:** [December 23, 2021, 9:59pm UTC](https://forums.balena.io/t/getting-below-error-for-wifi-connect-on-jetson-nano/31915/8 "2021-12-23T21:59:25Z")

</div>

Hello,

Welcome to the forums.  
Looking at the log, it appears to be a different issue than the previous user. I believe this thread would be closer to the issue you’re experiencing: [D-Bus setup failed: Failed to connect to socket /var/run/dbus/system\_bus\_socket: No such file or directory - #2 by CameronDiver](https://forums.balena.io/t/d-bus-setup-failed-failed-to-connect-to-socket-var-run-dbus-system-bus-socket-no-such-file-or-directory/15541/2)

You can also take a look at the documentation here: [Communicate outside the container - Balena Documentation](https://www.balena.io/docs/learn/develop/runtime/#d-bus-communication-with-host-os) . You may be missing this line in your Dockerfile:

`DBUS_SYSTEM_BUS_ADDRESS=unix:path=/host/run/dbus/system_bus_socket`

---

<div class="post-metadata">

**Author:** ![gabolema](https://avatars.discourse-cdn.com/v4/letter/g/f6c823/32.png) [@gabolema](https://forums.balena.io/u/gabolema)\
**Post date:** [April 1, 2022, 8:20pm UTC](https://forums.balena.io/t/getting-below-error-for-wifi-connect-on-jetson-nano/31915/10 "2022-04-01T20:20:51Z")

</div>

I am trying it on a khadas VIM 3 which has the same architecture as jetson nano (aarch64), and I ran into the same issue. So I’m not sure why it works for others, but in my case what I did was to add the

```auto
volumes:
  - /run/dbus/system_bus_socket:/host/run/dbus/system_bus_socket

```

which is where DBUS\_SYSTEM\_BUS\_ADDRESS was pointing to, but didn’t have access. Now it works on my khadas. Haven’t tested it yet in my Jetson, but most likely it will 🙂
