Silly me, there was an article in the wiki alreadyhttp://buffalo.nas-central.org/index.ph ... ess_Dongle
This is something I wanted to try for a long time, (someone had also asked about it in the past
). I have to credit the author of this article (I think it was kuroguy?) which I ended up porting to the wiki: ALL IN ONE NAS
. You probably should have serial console access to the box in case things go wrong
And the 184.108.40.206 Kernel/modules and Debian-lenny distribution cooked up by Davy-Gravy1. Kuropro running Debian LennyRe: (Towards) an armel root-fs image for Freelink : : Lenny-armel*-Debian rootfs image for testing available...2. A USB Wifi Stick
In this case a Nintendo WiFi USB connector, which used to be widely available at every store that sold a Wii (before the CSIRO lawsuit). http://en.wikipedia.org/wiki/Nintendo_w ... _connector
Udev should pick this up automatically when inserted and load the proper kernel module. You can do a quick dmesg to make sure that it was recognized.
# dmesg | tail -n43. Software
usb 1-1: new high speed USB device using orion-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice
phy0: Selected rate control algorithm 'pid'
usbcore: registered new interface driver rt2500usb
Get wpasupplicant and wireless
tools (throw in bridge-utils for later)
apt-get install wpasupplicant wireless-tools bridge-utils
I use WPA on my network, so I used wpa_passphrase to generate the basic contents of /etc/wpa_supplicant.conf
wpa_passphrase ESSID passphrase
Here is what mine looks like:/etc/wpa_supplicant.conf
Edit the interfaces file (I used a static configuration, you could always use DHCP instead):/etc/network/interfaces
#4. Test it out
# we always want the loopback interface
iface lo inet loopback
# default dynamic setup (no adjustment necessary)
# auto eth0
# iface eth0 inet dhcp
# sample wireless setup
iface wlan0 inet static
dns-nameservers 220.127.116.11, 18.104.22.168
Restart networking or reboot the box, you should be able to login on the address you gave the box
(192.168.1.145 in this example)
with the ethernet unplugged!
Edit: You may want to keep eth0 active as well, so that you can get back in if for some reason the wireless
does not work. Otherwise you would need serial console access to get back in.