ap51-flash¶
Supported devices¶
In general you can flash all devices which use the redboot bootloader that has the reflashing function enabled. ap51-flash will automatically detect redboot when you turn on the device. If your device is not in the “known to work” list which follows you still can try it and inform us about the result.
ap51-flash also supports plain tftp flashing without redboot. This method is quite common amongst a variety of devices.
Tested¶
- Alfa Network
- AP121F
- Dlink
- DIR-300 (after installing a reflash-enabled redboot)
- Engenius
- EOC-1650
- EOC-2610
- EOC-2610p
- 3660
- FON
- La Fonera (2100)
- Open Mesh
- A40
- A42
- A60
- A62
- D200
- G200
- MR500
- MR600 (v1, v2)
- MR900 (v1, v2)
- MR1750 (v1, v2)
- OM1P
- OM2P (v1, v2, v4)
- OM2P-HS (v1, v2, v3, v4)
- OM2P-LC
- OM5P
- OM5P-AN
- OM5P-AC (v1, v2)
- Plasma Cloud
- PA300
- PA1200
- PA2200
- Ubiquiti
- Bullet2 & HP
- NanoStation2
- NanoStation5
- Pico2 & HP
- RouterStation
- UniAppliance
- Colibrì (!UniData)
- Zyxel
- NBG6817
Other Devices¶
There are many different devices out there which differ slighty in their way of doing things. Even if your device does not work out of the box it might require only small changes to support it.
ap51-flash station for OpenWRT¶
OpenWRT-package¶
Makefile
- files/
ap51-flash.conf
- files/
ap51-flash.init
Example configuration of a Dlink DIR-300 as a ap51-flash station¶
- minimal
.config
-file (kicking out a lot of the standard applications and modules to save as much RAM as possible and adding nfs-support for remote images) - /etc/config/
network
(configuring ports 1-4 as seperate VLANS for flashing other devices and the WAN-port as the adminstration port) - /etc/
fstab
(for mounting nfs-shares at boot time)
Example image (using the same config as stated above):
2-port-vlan without host learning (hub-mode, for debugging ap51-flash)
- /etc/config/
network2
- /etc/init.d/
switch-2-hub