The ALL0305 is a dual-band access-point/bridge system with aluminium outdoor IP68 enclosure. Support for the board used in the device was added to OpenWrt trunk and the device comes with a patched version backfire 10.03 pre-installed.
- Atheros AR7161 680 MHz MIPS 24Kc CPU
- 8 MB flash memory
- 64 MB RAM
- 2x Atheros AR5413 wireless module, one for 802.11b/g and one for 802.11a
- Gigabit Ethernet (with proprierary 48V PoE)
The ALL0305 got two wireless radio as well as an Gigabit Ethernet nic. By default, all network interfaces are bridged into one common interface.
The device listens to http and https request on IP 192.168.1.1 to make the configuration easy. Set your LAN Network TCP/IP settings to Manual and set your local IP to 192.168.1.100 (or any other address between 192.168.1.2 and 192.168.1.254), Netmask 255.255.255.0. No DNS, WINS or Gateway settings are required.
Login to the device using the username 'root' (without the quotes), leave the password empty.
The password as well as a ssh public key to access the device should be set in the Administration section of the web interface.
To activate the wireless radios, open the configuration page of the corresponding radio:
- WIFI0: 802.11b/g (2.4 GHz)
- WIFI1: 802.11a (5 GHz)
In order to respect your local regulation rules, it is necessary to set the country code for each wireless radio. Note that as there is no globally valid regulation of frequencies in the 5 GHz range, the 802.11a (5 GHz) radio remains disabled unless a country code is set. Check the list of ISO3166 country codes to find your country code, e.g. 276 if you live in Germany.
The built-in AR5413 modules can work with both, madwifi or the fully GPLed ath5k driver; the ALL0305 comes with madwifi preinstalled. While madwifi fully supports all features of the WiFi modules, ath5k doesn't offer some features available only in the Atheros-domain (such as AR or XR). Therefore, in homogenous Atheros-environments, madwifi performs way better than ath5k. In some situations, however, using ath5k instead of madwifi helps, as it is closely integrated into the 802.11 stack shipped with the Linux kernel and therefore supports some new features like 802.11s mesh networking. If you are using a stock-binary from OpenWrt.org, you will need to install either kmod-madwifi OR kmod-ath5k (but NOT both!) before being able to use the wireless interfaces (the Allnet factory version comes with madwifi pre-installed)
For safety reasons, access to RedBoot is disabled by default. If you want to try OpenWrt trunk snapshots or your own home-baked Linux kernel, it makes sense to change the RedBoot configuration so you can access the bootloader in case something goes wrong. The bootloader configuration is stored in a seperate partition of the on-board flash memory. The best way is to install the fconfig tool and follow the instruction on http://oldwiki.openwrt.org/OpenWrtDocs%282f%29Bootloaders%282f%29RedBoot.html. i.e. set boot_script_timeout to something like 3 or 5 instead of 0. After having done this, you can then install a bleeding edge stock OpenWrt version by downloading openwrt-ar71xx-generic-eap7660d-squashfs-sysupgrade.bin and flashing it via sysupgrade.
Since this part is identical for all devices, see Basic configuration.
toh/allnet/all0305.txt · Last modified: 2013/05/12 10:04 by dangole