Support for new devices by DD-WRT.
DD-WRT v24 supports all Ubiquiti devices (LS2, LS5, NS2, NS5, PS2, PS5).
The associated firmware versions are part of the line of DD-WRT firmwares for professional use.
Ubiquiti offers affordable yet powerful devices based on Atheros wireless technology and allows
high performance long range Wireless LAN connections, especially when driven by DD-WRT.
The upcoming DD-WRT v24 will also support channel mapping for Ubiquiti XR7, SR9, XR9, XR3 and XR4.
And of course all other Ubiquiti WLAN cards (SR2, XR2, SR5, XR5, SRC) are also supported with showing
the right txpower.
DD-WRT and WiliGear announce that DD-WRT recently added support for the WBD-111 and WBD-500
CPU Boards from WiliGear. Both platforms have 48V PoE support and allow the use of high power
mini PCI cards. They are equipped with 8MB flash and 32MB RAM and are well suited for
outdoor CPE solutions
Upgrade to DD-WRT process for WBD-111:
The ip of your local pc running the tftp server must be 192.168.1.254
Place the fwupdate.bin in your tftp server folder.
Now push the reset button and plugin the power.
Hold the button for some seconds until the transfer starts. after the transfer is complete,
wait for 3 - 4 minutes.
The unit will then respond on 192.168.1.1
Howto to flash WBD-500 with dd-wrt v24-sp :
1. Configure your local computer IP address to 192.168.2.100.
2. Connect to the RedBoot bootloader by telnet on 192.168.2.66
and port 9000.
Enter telnet command at the moment
Ethernet LED lights up after powering on the WBD-500 board
(about 10 sec. after power on).
Because timeslot for this is short, you might need several tries.
3. Enter the RedBoot console by pressing CTRL+C.
4. Copy linux.bin to your TFTP server directory.
5. Configure the RedBoot bootloader IP and TFTP server settings using
ip_address -l [local ip address] -h [remote server address]
6. Flash the unit by entering the following commands:
RedBoot> fis init
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> load -r -v -b 0x80041000 linux.bin
Using default protocol (TFTP)
-
Raw file loaded 0x80041000-0x80663fff, assumed entry at 0x80041000
RedBoot> fis create linux
... Erase from 0xa8030000-0xa8653000: ..........................
... Program from 0x80041000-0x80664000 at 0xa8030000: ..........
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> fconfig
Enter the bootscript:
fis load -l linux
exec
Save the config and do:
RedBoot> reset
Boot break in method
Windows easy connecting to redboot
Download putty.exe to c: create a file an c: called redboot.bat with the following content:
rem echo off
:start
rem ------------------------------------------------
ping 192.168.84.1 -n 1 -w 1 > NULL
IF ERRORLEVEL 1 goto start
rem putty
rem ------------------------------------------------
break putty.exe telnet://192.168.2.66:9000 -m redboot.txt exit
create a file on c: called redboot.txt with the following content:
^C
start the bat file and power on the router…..here comes redboot
Edit Redboot
Editing the redboot through a serial connection is straight forward but through ethernet cable it is a bit more tricky. When using a ethernet cable you will receive and need to ignore any "AHB ERROR" messages you may see. The other problem is the backspace and the delete key don't work. To delete existing figures you need to use ^H (Ctrl H) keys to backspace. This example is how you want to change the Bootscript timeout and Baud rate
Boot script timeout (1000ms resolution): 2^H10
Console baud rate: 195200^H^H^H^H^H^H9600
In order to restore original firmware of WBD-500 please follow the below instructions:
1. Configure your local computer IP address to 192.168.2.100.
2. Connect to the RedBoot bootloader by telnet on 192.168.2.66 and port 9000. Enter telnet command at the moment Ethernet LED lights up after powering on the WBD-500 board (about 10 sec. after power on). Because timeslot for this is short, you might need several tries.
3.Enter RedBoot command prompt. Press Ctrl+C to stop startup script (if enabled).
4. Configure the RedBoot bootloader IP and TFTP server settings using
ip_address -l [local ip address] -h [remote server address]
RedBoot> ip_address -l 192.168.2.66 -h 192.168.2.100
Here 192.168.2.66 is local IP address and 192.168.2.100 is TFTP server IP address.
5. Initialize FIS:
RedBoot> fis init
6. Load kernel from TFTP and store to FLASH
RedBoot> load -r -b 0x80041000 vmlinuz
RedBoot> fis create -b 0x80041000 -f 0xA8030000 -l 0x00100000 -r 0x80041000 -e 0x80041000 kernel
7. Load cramfs from TFTP and store to FLASH
RedBoot> load -r -b 0x80040000 initrd.img
RedBoot> fis create -f 0xA8130000 -b 0x80040000 -l 0x00500000 ramdisk
8. Create cfg (configuration) and etc (jffs2 filesystem)
RedBoot> fis create -b 0x80040000 -f 0xA8630000 -l 0x00080000 -n cfg
RedBoot> fis create -b 0x80040000 -f 0xA86B0000 -l 0x00120000 -n etc
9. Configure RedBoot - setup startup script and IP addresses
RedBoot> fconfig -i
Initialize non-volatile configuration - continue (y/n)? y
Run script at boot: true
Boot script:
Enter script, terminate with empty line
fis load -l kernel
exec
Boot script timeout (1000ms resolution): 1
Use BOOTP for network configuration: false
Gateway IP address: 192.168.2.254
Local IP address: 192.168.2.66
Local IP address mask: 255.255.255.0
Default server IP address: 192.168.2.254
Console baud rate: 115200
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration - continue (y/n)? y
10. Reboot
RedBoot> reset
|
Follow us on Twitter