# Jetson TX2 Wifi Hotspot **URL:** \ **Category:** Product support\ **Tags:** wifi, network\ **Created:** [July 8, 2018, 1:46am UTC](https://forums.balena.io/t/jetson-tx2-wifi-hotspot/3474 "2018-07-08T01:46:52Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![jemoster](https://avatars.discourse-cdn.com/v4/letter/j/ce7236/32.png) [@jemoster](https://forums.balena.io/u/jemoster)\ **Post date:** [July 8, 2018, 1:46am UTC](https://forums.balena.io/t/jetson-tx2-wifi-hotspot/3474/1 "2018-07-08T01:46:52Z")
I’m attempting to setup a wifi hotspot on a Jetson TX2. Following the [instructions](https://docs.resin.io/reference/resinOS/network/2.x/) I was able to add a `resin-hotspot` file in `/system-connections/`. However, for the TX2 also needs the Broadcomm `op_mode` set to 2 for it to work as per their [wiki](https://elinux.org/Jetson/TX1_WiFi_Access_Point). The hotspot works if I run these commands after boot: ```auto nmcli radio wifi off echo 2 > /sys/module/bcmdhd/parameters/op_mode nmcli radio wifi on nmcli connection up resin-hotspot ``` I would rather like to set the `op_mode` in `/etc/modprobe.d/bcmdhd.conf` so that I don’t have to manually set this up every time. I tried preparing a fresh SD-card, adding that file to the `resin-rootA` partition and then provisioning the Jetson. The provisioning seems to go okay and the board shows up in the dashboard. However, upon inspecting the filesystem the `bcmdhd.conf` file has not shown up on the device. Any ideas on how to properly add a file to the read-only file-system or is there something else that I’m missing. Thanks! ---
**Author:** ![CameronDiver](https://avatars.discourse-cdn.com/v4/letter/c/2acd7d/32.png) [@CameronDiver](https://forums.balena.io/u/CameronDiver)\ **Post date:** [July 9, 2018, 5:11pm UTC](https://forums.balena.io/t/jetson-tx2-wifi-hotspot/3474/4 "2018-07-09T17:11:30Z")
Hey @jemoster I believe this should be added to the `resin-boot` partition. Note that this is not officially supported though, as any changes will be lost on a host OS update (and may cause other instabilities - although adding a network manager file shouldn’t cause this). ---
**Author:** ![jemoster](https://avatars.discourse-cdn.com/v4/letter/j/ce7236/32.png) [@jemoster](https://forums.balena.io/u/jemoster)\ **Post date:** [August 25, 2018, 3:08pm UTC](https://forums.balena.io/t/jetson-tx2-wifi-hotspot/3474/5 "2018-08-25T15:08:56Z")
Following your suggestion, where in `resin-boot` would I need to put the `bcmdhd.conf` for it to end up in the correct place? Or is the feature to support adding the `bcmdhd.conf` file something that would be needed to be added as a feature of `resin-boot`? ---
**Author:** ![floion](https://avatars.discourse-cdn.com/v4/letter/f/45deac/32.png) [@floion](https://forums.balena.io/u/floion)\ **Post date:** [August 25, 2018, 4:03pm UTC](https://forums.balena.io/t/jetson-tx2-wifi-hotspot/3474/6 "2018-08-25T16:03:04Z")
Hi, I think it would be better if you run this from your container. You can interact with NM from within the user container so you can turn the radio off, set `op-mode` to 2 and then restarwifi and bring your connection up. Some info on interacting over dbus can be found here: [https://docs.resin.io/reference/OS/network/2.x/#changing-the-network-at-runtime](https://docs.resin.io/reference/OS/network/2.x/#changing-the-network-at-runtime) ---
**Author:** ![floion](https://avatars.discourse-cdn.com/v4/letter/f/45deac/32.png) [@floion](https://forums.balena.io/u/floion)\ **Post date:** [August 26, 2018, 10:14am UTC](https://forums.balena.io/t/jetson-tx2-wifi-hotspot/3474/7 "2018-08-26T10:14:08Z")
One example to use nmcli from the container would be here: [https://github.com/resin-io-playground/nmcli-no-network-manager](https://github.com/resin-io-playground/nmcli-no-network-manager)