Wireless network configuration was started on 2012-06-30 by fil, gaudenz, gismo and rmayorga, please check with them if you want to help.
 Using the debconf wireless
The SSID is debconf and password supercowpower .
 Hardware list
 Device List
|11||TP-Link||Lopez (BoF / Hacklab)||90:F6:52:20:1A:8C||tplink-lopez-11||172.30.4.111||no label, probably not in the inventory, former dc12-admin|
|dkg-005||1 / 36||WZR-HP-AG300H||Aula Magna||10:6F:3F:0C:19:D0||dkg-aula-1||172.30.1.101||802.11a radio (phy1) turned of because it was unstable|
 Documentation for the OpenWRT setup at DebConf12
This page describes the access point configuration for DebConf12.
 Building an image
 Buffalo (brcm-2.4)
 TP-Link and Buffalo WZR-HP-AG300H (ar71xx)
On this device the latest release (10.03.1) has some bugs. So we use a trunk snapshot. But the Image Generator for trunk needs libc 2.14 which is not yet in Debian (OMG). So we use the prebuilt sysupgrade image for TP-Link or the tftp flashing image for the Buffalo WZR-HP-AG300H or the sysupgrade image for the Buffalo WZR-HP-AG300H. If flashing over the manufacturer firmware you need the factory image and flash it via the web interface.
 Flashing an image
1. Connect your computer to one of the ports 1-4 (not WAN!) of the Buffalo via a Switch (without the switch your interface will go down if you restart the Buffalo for flashing)
2. Assign an address in the 192.168.11.0/24 range to your computer
3. Prepare your computer to tftp upload the image:
# sudo arping -f 192.168.11.1 && echo -e "binary\ntrace\nput openwrt-brcm-2.4-squashfs.trx" | tftp 192.168.11.1
4. Disconnect the Buffalo from power, press the "init" button on the small side, reconnect power, after a few seconds the tftp upload should start
5. After the upload finished and the image is written to the internal storage of the Buffalo it will restart itself.
6. With the Debconf configuration the Buffalo listens on 192.168.1.1/24 on the WAN port, the LAN ports are bridged and do DHCP.
1. Boot into rescue mode by pressing the QSS button after startup while the SYS LED is flashing.
2. Connect by telnet to the device on 192.168.1.1 and activate the writeble root and ssh (and change the root password if needed):
# telnet 192.168.1.1 # mount_root # /etc/init.d/dropbear start # passwd (only if you don't know the current root password)
3. Copy the new image to the device (to /tmp!)
# scp openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin email@example.com:/tmp
4. Flash the new image:
# ssh firstname.lastname@example.org # sysupgrade -n -d 10 -v /tmp/openwrt-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin
 Setting the channel and the transmission power
# setting the channel ssh email@example.com uci set wireless.wl0.channel=xx # setting transmission power uci set wireless.wl0.txpower=xx uci commit # restart wifi wifi
 Your .ssh config
You may want to add this stanza to your own ~/.ssh/config to disable host key checking on 192.168.1.* so that you can ssh into multiple APs as you're flashing them without getting annoying warnings about the host key (of course) being changed...
Host 192.168.1.* StrictHostKeyChecking no GlobalKnownHostsFile /dev/null UserKnownHostsFile /dev/null
 Issues Log
Add your issue here, including the MAC address of the AP you saw the issue with, the date & time, and any other useful information you can think of. Then tell rmayorga on IRC your own wireless MAC address.