|
These instructions were developed by Stafford Taillon from Colishay Technologies for the Engenius EAP-3660. Thanks for all of your hard work Stafford!
They will work with all engenius nodes with these few exceptions:
The firmware must be specific to the model of access point that you are trying to reflash.
The image length and memory address will be different based upon your access point.
nonetheless...
Here are the most clear and concise instructions you will find for reflashing stock firmware onto an engenius node.
Trust me, these instructions will become very important with some of the new network management systems that Chuck will be deploying shortly...
Enjoy
fis list
ip_address -l 192.168.1.1 -h 192.168.1.50
fis init
fis create256 -b 0x80060000 -f 0xbfc30000 -l 0x2f0000 -e 0 rootfs
fis create256 -b 0x80060000 -l 0xa0000 -f 0xbff20000 -e 0x80170040 -r 0x80041000 vmlinux.bin.l7
fis create -b 0x80060000 -l 0x20000 -f 0xbffc0000 -e 0 cfg
fis list
load -r -v -b 0x80060000 EAP-3660-1.3.4.img -h 192.168.1.101
fis write -f 0xbfc30000 -b 0x8006000a -l 0x380000
reset
Above is the master list of the commands needed for re-flashing stock firmware
They are in the order that they are to be entered
Read everything before flashing, trust me
Software and files needed...
- MS-DOS Command Prompt
- PuTTY
- Tftdp32
- EAP-3660-1.3.4.img
Setup of computer...
- Static IP of 192.168.1.101
- Static Subnet of 255.255.255.0
Setup of PuTTY...
- IP address 192.168.1.1
- Port 9000
- Connection type TelNet
Setup of Tftdp32...
- Location of EAP-3660-1.3.4.img into directory of Tftdp32
- Keep open in background
Steps to flash...
1> Open Tftdp32 and PuTTY with settings above
2> Open fresh command prompt and type [ping -t 192.168.1.1]
3> Plug in ethernet then power cable to node
4> As soon as a response is seen, hit Open on PuTTY
5> In the new window, make sure there is a [Redboot> ] command prompt
6> fis list
To check for a response from the node
7> ip_address -l 192.168.1.1 -h 192.168.1.50
Should happen instantly
8> fis init
Type [y] as a response, should process quickly
9> fis create256 -b 0x80060000 -f 0xbfc30000 -l 0x2f0000 -e 0 rootfs
Should take less than 2 minutes
10> fis create256 -b 0x80060000 -l 0xa0000 -f 0xbff20000 -e 0x80170040 -r 0x80041000 vmlinux.bin.l7
Should take less than 1 minute
11> fis create -b 0x80060000 -l 0x20000 -f 0xbffc0000 -e 0 cfg
Should take less than 2 minutes
12> The command prompt opwn pinging should be getting a good response, if not, you fucked up somewhere
13> fis list
To check for the same response from earlier
14> load -r -v -b 0x80060000 EAP-3660-1.3.4.img -h 192.168.1.101
This will load the file, should see activity in Tftdp32, will take a bit
15> fis write -f 0xbfc30000 -b 0x8006000a -l 0x380000
Longest process, nothing will happen at first, should take less than 5 minutes
16> Once the [Redboot> ] command line comes up, type [reset] before unplugging node
17> Wait for a repeating response from the command prompt, it will connect once falsely during reset
18> Open a browser and check 192.168.1.1 for a login screen, User: admin, Pass: admin
19> If said login screen exists, celebrate
20> I like even numbers...
Notes for above steps...
- A number that may change is the 0xbfc30000, this is the flash address of rootfs when [fis list] is
typed into the command prompt to check for a connection to the node
- If there are any errors above the section when it states [* CAUTION * about to program FLASH] there
is probably a spelling error in a code
- Your computer MUST have a static IP of 192.168.1.101, don't know why, but you got to
- Be careful with the number of 0's in some of the command codes, its best to copy and paste.
It will not error if you mess one up, so if something goes haywire start there
- To copy and paste into PuTTY, copy normally with CTRL+C, then right click PuTTY and it will paste
Instructions translated and laid out by Stafford Taillon, Colishay Technologies
|
Login
FAQ
