USB-to-WiFi adapter not working with Linux 6.15 (driver issue?)

Dear All,

I've installed a USB-to-WiFi adapter in a Neatgear ReadyNAS RN102. The box is now able to scan for WiFi networks, but is unable to connect. The error message is "No DHCPOFFERS received". Connecting fails the same way on a second network.

The adaper is a TP-Link AC600 Archer T600U Nano. It's the kind of adapter that barely extends out of the USB connector on the box. Some details after a fresh reboot:

root@rn102:~# uname -a
Linux rn102 6.15.2-mvebu-370xp-tld-1 #1 PREEMPT Sun Jun 22 21:40:09 PDT 2025 armv7l GNU/Linux

root@rn102:~# cat /etc/debian_version 
12.11

root@rn102:~# lsusb
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 2357:011e TP-Link AC600 wireless Realtek RTL8811AU [Archer T2U Nano]
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


root@rn102:~# lsmod
Module                  Size  Used by
rtw88_8821au           12288  0
rtw88_8821a            32768  1 rtw88_8821au
rtw88_88xxa            20480  1 rtw88_8821a
rtw88_usb              20480  1 rtw88_8821au
rtw88_core            139264  3 rtw88_88xxa,rtw88_usb,rtw88_8821a
mac80211              569344  2 rtw88_core,rtw88_usb
cfg80211              339968  2 rtw88_core,mac80211
snd_soc_spdif_tx       12288  0
snd_soc_kirkwood       20480  0
snd_soc_simple_card    20480  0
snd_soc_simple_card_utils    20480  1 snd_soc_simple_card
snd_soc_core          163840  4 snd_soc_spdif_tx,snd_soc_kirkwood,snd_soc_simple_card_utils,snd_soc_simple_card
rfkill                 24576  1 cfg80211
libarc4                12288  1 mac80211
snd_compress           20480  1 snd_soc_core
ac97_bus               12288  1 snd_soc_core
snd_pcm_dmaengine      12288  1 snd_soc_core
snd_pcm                90112  5 snd_soc_kirkwood,snd_compress,snd_pcm_dmaengine,snd_soc_simple_card_utils,snd_soc_core
snd_timer              32768  1 snd_pcm
sg                     36864  0
snd                    73728  4 snd_compress,snd_timer,snd_soc_core,snd_pcm
soundcore              12288  1 snd
g762                   16384  0
uio_pdrv_genirq        16384  0
uio                    16384  1 uio_pdrv_genirq
mvneta                 49152  0
mvneta_bm              12288  1 mvneta
phylink                40960  1 mvneta


root@rn102:~# dmesg | grep -A 1 rtw
[   27.777522] rtw_8821au 2-1:1.0: Firmware version 42.4.0, H2C version 0
[   28.157401] random: crng init done
[   29.525924] usbcore: registered new interface driver rtw_8821au
[   29.886528] rtw_8821au 2-1:1.0 wlx0123456789ab: renamed from wlan0
[   30.014116] rtw_8821au 2-1:1.0 wlan1: renamed from wlx0123456789ab
[   30.105256] warning: `iwconfig' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211

root@rn102:~# head /etc/network/interfaces
auto lo eth0
iface lo inet loopback

# Wireless network
rename /wlx*=wlan1
allow-hotplug wlan1
iface wlan1 inet dhcp
    wpa-ssid essid
    wpa-psk password

root@rn102:~# ip a | tail -2
5: wlan1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 01:23:45:67:89:ab brd ff:ff:ff:ff:ff:ff

root@rn102:~# ip link set wlan1 up

root@rn102:~# ip a | tail -2
5: wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 01:23:45:67:89:ab brd ff:ff:ff:ff:ff:ff

root@rn102:~# iwlist wlan1 scan | head -13
wlan1     Scan completed :
          Cell 01 - Address: AA:BB:CC:DD:EE:FF
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=62/70  Signal level=-48 dBm  
                    Encryption key:on
                    ESSID:"essid"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=00000001ecb6177e
                    Extra: Last beacon: 80ms ago

root@rn102:~# ifup wlan1
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan1/01:23:45:67:89:ab
Sending on   LPF/wlan1/01:23:45:67:89:ab
Sending on   Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

root@rn102:~# iwconfig wlan1
wlan1     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on

The firmware (not the driver) for the adapter is missing in Debian 12 (bookworm), so I just copied it from my laptop running Debian 13 (trixie):

root@rn102:~# md5sum /usr/lib/firmware/rtw88/rtw8821a_fw.bin
b5fdc50011a441dba8fc140fbbedc342  /usr/lib/firmware/rtw88/rtw8821a_fw.bin

This post says that the driver '8821au' was replaced by 'mac80211' in kernel version 6.13. Both are installed (see 'lsmod' output above). I tried blacklisting the 'rtw88_*' modules, but then the fimware is not loaded and no 'wlx*' device is registered. Is this the issue and, if so, what's the fix?

Regards,
Trond Melen

Hi Trond,

I've not tried USB Wifi on our MVEBU kernel here before. I did have success with the Kirkwood kernel using some generic Realtek USB Wifi adapters.

To see if I will have the same problem as yours, I removed a working USB Wifi adapter from one of my Pogo V4 and installed it on the Thecus N2350 which is running the MVEBU kernel. To my surprise, it did not work on the 1st try either! So there is some chance that the kernel or rootfs is lacking something.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,

To investigate further, I rolled back to Linux 6.13.8 and 6.12.6. I found no relevant differences between version 6.15.2 and 6.13.8. With 6.12.6 the USB-to-Wireless adapter is not supported. The device is detected, but the kernel does not try to load the firmware, and 'ip' does not report any wireless devices. Some details:

root@rn102:~# uname -a
Linux rn102 6.12.6-mvebu-370xp-tld-1 #1 PREEMPT Sun Dec 22 16:34:11 PST 2024 armv7l GNU/Linux

root@rn102:~# lsusb
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 2357:011e TP-Link AC600 wireless Realtek RTL8811AU [Archer T2U Nano]
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@rn102:~# lsmod
Module                  Size  Used by
sg                     32768  0
mvneta                 49152  0
mvneta_bm              12288  1 mvneta
phylink                40960  1 mvneta
g762                   16384  0
uio_pdrv_genirq        16384  0
uio                    16384  1 uio_pdrv_genirq

root@rn102:~# dmesg | grep -i -A 2 usb
[    1.165215] usbcore: registered new interface driver usbfs
[    1.170965] usbcore: registered new interface driver hub
[    1.176508] usbcore: registered new device driver usb
[    1.182233] pps_core: LinuxPPS API ver. 1 registered
[    1.187409] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
--
[    3.286313] usbcore: registered new interface driver smsc75xx
[    3.293472] orion-ehci d0050000.usb: EHCI Host Controller
[    3.299375] orion-ehci d0050000.usb: new USB bus registered, assigned bus number 1
[    3.307393] orion-ehci d0050000.usb: irq 35, io mem 0xd0050000
[    3.327232] orion-ehci d0050000.usb: USB 2.0 started, EHCI 1.00
[    3.333796] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12
[    3.342130] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.349505] usb usb1: Product: EHCI Host Controller
[    3.354691] usb usb1: Manufacturer: Linux 6.12.6-mvebu-370xp-tld-1 ehci_hcd
[    3.361827] usb usb1: SerialNumber: d0050000.usb
[    3.368333] hub 1-0:1.0: USB hub found
[    3.372622] hub 1-0:1.0: 1 port detected
[    3.378983] xhci_hcd 0000:02:00.0: vgaarb: pci_notify
--
[    3.384908] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[    3.393286] xhci_hcd 0000:02:00.0: hcc params 0x200073a1 hci version 0x100 quirks 0x0000000000080010
[    3.402695] xhci_hcd 0000:02:00.0: enabling Mem-Wr-Inval
--
[    3.409556] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3
[    3.417087] xhci_hcd 0000:02:00.0: Host supports USB 3.0 SuperSpeed
[    3.423859] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12
[    3.432229] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.439625] usb usb2: Product: xHCI Host Controller
[    3.444805] usb usb2: Manufacturer: Linux 6.12.6-mvebu-370xp-tld-1 xhci-hcd
[    3.451910] usb usb2: SerialNumber: 0000:02:00.0
[    3.458262] hub 2-0:1.0: USB hub found
[    3.462542] hub 2-0:1.0: 2 ports detected
[    3.468241] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.476536] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.12
[    3.484884] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.492280] usb usb3: Product: xHCI Host Controller
[    3.497740] usb usb3: Manufacturer: Linux 6.12.6-mvebu-370xp-tld-1 xhci-hcd
[    3.504810] usb usb3: SerialNumber: 0000:02:00.0
[    3.511155] hub 3-0:1.0: USB hub found
[    3.515339] hub 3-0:1.0: 2 ports detected
[    3.520999] xhci_hcd 0000:02:00.0: vgaarb: pci_notify
[    3.522548] usbcore: registered new interface driver usblp
[    3.528714] usbcore: registered new interface driver usb-storage
[    3.536137] mousedev: PS/2 mouse device common for all mice
[    3.544824] i2c_dev: i2c /dev entries driver
--
[    3.758438] usb 2-1: new high-speed USB device number 2 using xhci_hcd
[    3.765456] sdhci-pltfm: SDHCI platform and OF driver helper
[    3.772690] marvell-cesa d0090000.crypto: CESA device successfully registered
--
[    3.796520] usbcore: registered new interface driver usbhid
[    3.802482] usbhid: USB HID core driver
[    3.808207] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 (8000003f) counters available
[    3.819894] NET: Registered PF_INET6 protocol family
--
[    3.920132] usb 2-1: New USB device found, idVendor=2357, idProduct=011e, bcdDevice= 2.00
[    3.951940] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.974242] registered taskstats version 1
[    3.979358] usb 2-1: Product: 802.11ac WLAN Adapter 
[    3.984600] usb 2-1: Manufacturer: Realtek 
[    3.989804] Loading compiled-in X.509 certificates
[    4.007295] usb 2-1: SerialNumber: 00e04c000001
[    4.029404] Key type .fscrypt registered
[    4.033698] Key type fscrypt-provisioning registered

root@rn102:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
3: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1000
    link/tunnel6 :: brd :: permaddr 66e5:dde:52da::
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1024
    link/ether 00:11:22:33:44:55 brd ff:ff:ff:ff:ff:ff
    altname end1
    inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic eth0
       valid_lft 81003sec preferred_lft 81003sec

The 'mac80211' driver for wireless network devices has been around for almost 20 years. Support for the Realtek rtl8821/11au chip-sets was recently merged into Linux version 6.13/6.14. To find out what is missing in your Linux 6.15 release, these references may give a hint:
https://wireless.docs.kernel.org/en/latest/_downloads/601d0cfe4b4e1c3607851f726aceb378/mac80211.pdf
https://wireless.docs.kernel.org/en/latest/en/developers/documentation/mac80211.html
The first reference includes further links.

Thank's for your persistent efforts! I'll be happy to test any related development work of yours.

Regards,
Trond Melen



Edited 2 time(s). Last edit at 09/03/2025 02:19AM by tme.

Hi Trond,

It turned out my Wifi adapter problem was efuse related.

In Thecus N2350 with kernel Linux version 6.16.5-mvebu-tld-1

[   20.353686] rtw88_8821cu 4-1:1.0: Firmware version 24.11.0, H2C version 12
[   20.394250] mvneta f1070000.ethernet end0: renamed from eth0
[   20.555427] rtw88_8821cu 4-1:1.0: rfe 7 isn't supported
[   20.564553] rtw88_8821cu 4-1:1.0: failed to setup chip efuse info
[   20.571408] rtw88_8821cu 4-1:1.0: failed to setup chip information
[   20.578688] usbcore: registered new interface driver rtw88_8821cu

The same adapter in the Pogo V4 with kernel Linux version 6.16.5-kirkwood-tld-5.

[   49.238767] rtw88_8821cu 2-2:1.0: Firmware version 24.11.0, H2C version 12
[   49.872711] rtw88_8821cu 2-2:1.0: rfe 2
[   49.950854] usbcore: registered new interface driver rtw88_8821cu
[   50.059870] rtw88_8821cu 2-2:1.0 wlxa047d77010ff: renamed from wlan0
[   51.463251] EXT4-fs (sdb1): re-mounted 4d1a061b-0bcc-4702-986b-8ac8d3c2b2c1 r/w.
[   54.770445] Adding 524284k swap on /swapfile1.  Priority:-2 extents:13 across:4841772k 
[   55.985128] rtw88_8821cu 2-2:1.0 wlan0: renamed from wlxa047d77010ff
[   56.738234] warning: `iwconfig' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[   62.920843] NET: Registered PF_KEY protocol family
[   65.606665] wlan0: authenticate with 00:26:5a:xx:xx:xx (local address=a0:47:d7:xx:xx:xx)
[   65.780983] wlan0: send auth to 00:26:5a:xx:xx:xx (try 1/3)
[   65.794341] wlan0: authenticated
[   65.800281] wlan0: associate with 00:26:5a:xx:xx:xx (try 1/3)
[   65.820279] wlan0: RX AssocResp from 00:26:5a:xx:xx:xx (capab=0x431 status=0 aid=2)
[   65.849707] wlan0: associated
[   66.001145] wlan0: Limiting TX power to 27 (27 - 0) dBm as advertised by 00:26:5a:xx:xx:xx

Still trying to get to a solution for this. My guess is the Debian driver is too old.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 09/17/2025 06:12PM by bodhi.

Thanks for trying, bodhi!

Since the firmware file '/usr/lib/firmware/rtw88/rtw8821a_fw.bin' is missing in Debian 12, I assume support starts with Debian 13. My impression is that the new driver 'mac80211' (merged in kernel 6.13/6.14) is supposed to replace 'rtw88_88*', 'rtw88_core and 'cfg80211''. I think the problem might be that both 'cfg80211' and its replacement 'mac80211' are compiled as loadable modules in your kernel 6.16.5, and that both automatically get loaded:

tme@rn102:/boot$ grep -i cfg80211 config-6.16.5-mvebu-370xp-tld-1
CONFIG_CFG80211=m
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_CERTIFICATION_ONUS is not set
CONFIG_CFG80211_REQUIRE_SIGNED_REGDB=y
CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=y
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not set
CONFIG_CFG80211_CRDA_SUPPORT=y
CONFIG_CFG80211_WEXT=y

tme@rn102:/boot$ grep -i mac80211 config-6.16.5-mvebu-370xp-tld-1
CONFIG_MAC80211=m
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
CONFIG_MAC80211_MESH=y
CONFIG_MAC80211_LEDS=y
# CONFIG_MAC80211_DEBUG_MENU is not set
CONFIG_MAC80211_STA_HASH_MAX_SIZE=0
CONFIG_MAC80211_HWSIM=m

How can I prevent 'cfg80211' from being loaded?

Regards,
Trond Melen



Edited 1 time(s). Last edit at 09/23/2025 07:20AM by tme.

Hi Trond,

You can blacklist the driver. For example, I blacklist the Kirwood thermal for some 88F6282 boxes because the board does not support it.

~# cat /etc/modprobe.d/kirkwood-thermal-blacklist.conf

# This file blacklists the kirkwood_thermal module on ZyXEL boxes with 6282 SoC

blacklist kirkwood_thermal

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks bodhi,

So the root file system is mounted before WiFi interfaces on USB ports are probed? I didn't know.

I had no success when blacklisting any modules. When 'rtw88_8821au' is blacklisted, no other relevant modules are loaded, and 'ip a' reports no wireless interfaces. I no longer believe 'cfg80211' is a replacement for 'mac80211', rather that the modules are supposed to cooperate.

Anything else I could try?

Regards,
Trond Melen

Hi Trond,

> So the root file system is mounted before WiFi
> interfaces on USB ports are probed? I didn't
> know.

Not really. The Wifi interface is probed when the module was loaded by the kernel (and the initramfs should have the module included), which it does in my kernel build. That should happen before the rootfs is mounted.

> I had no success when blacklisting any modules.
> When 'rtw88_8821au' is blacklisted, no other
> relevant modules are loaded, and 'ip a' reports no
> wireless interfaces. I no longer believe
> 'cfg80211' is a replacement for 'mac80211', rather
> that the modules are supposed to cooperate.
>
> Anything else I could try?

Not sure. I need to see something Wifi adapter works in my box running MVEBU kernel. Right now I don't have a "good' adapter.

Can you post the model of your Wifi adapter? If I can find it on eBay (US), I can get the same one and test it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Trond,

> I had no success when blacklisting any modules.

When you blacklist a module, did you remember to regenerate the initramfs and uInitrd? for example,

update-initramfs -u
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-6.16.5-mvebu-370xp-tld-1 -d initrd.img-6.16.5-mvebu-370xp-tld-1 uInitrd

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,

Problem solved. It was not a driver issue.

Modifying '/etc/network/interfaces' is sufficient to connect to an open WiFi network, but to connect to a WPA or WPA2 protected network, the 'wpasupplicant' package is needed. This makes sense since '/etc/network/interfaces' is normally readable for everyone and should not include any passwords.

sudo apt install -y wpasupplicant

Then create '/etc/wpa_supplicant/wpa_supplicant-wlan0.conf':

tme@rn102:~$ sudo cat /etc/wpa_supplicant/wpa_supplicant-wlan0.conf 
network={
    ssid="essid"
    psk="password"
}

and hide it's content:

tme@rn102:~$ sudo chmod 600 /etc/wpa_supplicant/wpa_supplicant-wlan0.conf

tme@rn102:~$ ls -alF /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
-rw------- 1 root root 55 Sep 26 10:50 /etc/wpa_supplicant/wpa_supplicant-wlan0.conf

Finally update the wireless section in '/etc/network/interfaces':

tme@drn102:~$ cat /etc/network/interfaces
[...]
# Wireless network
rename /wlx*=wlan1
allow-hotplug wlan1
iface wlan1 inet dhcp
    wpa-conf /etc/wpa_supplicant/wpa_supplicant-wlan0.conf

Thanks for the tip on regenerate the initramfs and uInitrd! I understand this is how a blacklist finds its way to the /boot partition.

Regards,
Trond Melen

Trond,

> Problem solved. It was not a driver issue.
>
> Modifying '/etc/network/interfaces' is sufficient
> to connect to an open WiFi network, but to connect
> to a WPA or WPA2 protected network, the
> 'wpasupplicant' package is needed. This makes
> sense since '/etc/network/interfaces' is normally
> readable for everyone and should not include any
> passwords.

Right, sorry I did not ask that question about wpasupplicant!

Note that the main pupose of the wpasupplicant package is to provide WPA or WPA2. /etc/wpa_supplicant/wpa_supplicant-wlan0.conf is just a convenient and a proper way to store the essid and password.

It also works if we put the essid and password in /etc/network/interfaces and then protect this file with chmod 600.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi,

Quote

It also works if we put the essid and password in /etc/network/interfaces and then protect this file with chmod 600.

I've come to realized that the range of these very small USB-to-WiFi adapters is very short, maybe just 2 meters (6') or so. When I've been unable to reproduce issues, it may just have been thet the distance between the box and the wirless router had changed. Sorry!

Regards,
Trond Melen

Hi Trond,

> I've come to realized that the range of these very
> small USB-to-WiFi adapters is very short, maybe
> just 2 meters (6') or so. When I've been unable to
> reproduce issues, it may just have been thet the
> distance between the box and the wirless router
> had changed. Sorry!

Not at all! I was just pointing out that this could also be placed in /etc/network/interfaces. And chmod 600 /etc/network/interfaces.

tme@rn102:~$ sudo cat /etc/wpa_supplicant/wpa_supplicant-wlan0.conf 
network={
    ssid="essid"
    psk="password"
}

But yes, /etc/wpa_supplicant/wpa_supplicant-wlan0.conf is where they should be.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)