This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
install_guide [2010/01/31 06:53] ispyisail |
install_guide [2019/12/16 10:53] (current) lantis [Install a Gargoyle Image] |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| < | < | ||
| WARNING: If you make a mistake installing this software, it is possible to permanently disable your router, effectively turning it into a brightly colored brick. Bricked routers aren't very useful -- you can use one to beat someone about the head or as modern art, but that's about it. | WARNING: If you make a mistake installing this software, it is possible to permanently disable your router, effectively turning it into a brightly colored brick. Bricked routers aren't very useful -- you can use one to beat someone about the head or as modern art, but that's about it. | ||
| - | |||
| You can pretty much eliminate this risk by following the directions given here so please read them first before attempting to install Gargoyle. | You can pretty much eliminate this risk by following the directions given here so please read them first before attempting to install Gargoyle. | ||
| - | Garoyle | + | Gargoyle |
| - | </ | + | </ |
| + | \\ \\ | ||
| + | :!: **Check** that your [[supported_routers_-_tested_routers|Router Hardware]] meets the minimum requirements. | ||
| - | - [[install_guide# | + | ===== Install a Gargoyle |
| - | - [[install_guide# | + | |
| - | - [[install_guide# | + | |
| - | - [[install_guide# | + | |
| - | - [[install_guide# | + | |
| - | - [[install_guide# | + | |
| - | - [[install_guide# | + | |
| - | - [[install_guide# | + | |
| - | =====Overview -- READ FIRST===== | + | The recommended way to install Gargoyle |
| - | Installing the firmware onto your router | + | |
| - | Instructions for installing images onto several models are provided below, but there many routers that will (likely) run Gargoyle that are not listed here and for which instructions are not provided. Gargoyle should run on any router | + | :!: Check the __exact version__ of your router |
| - | Be VERY careful of the 4MB flash memory requirement. Most newer WRT54G models have only 2MB, making installation of Gargoyle/ | + | :-? If you get the **error message " |
| - | If you install Gargoyle using one of our images the inital connection procedure is a little different than for OpenWrt. OpenWrt defaults | + | * Wait about 5 minutes then you should be able to connect |
| + | * If after 5 minutes | ||
| + | * If after 20 minutes | ||
| - | If you find the documentation here insufficient there are several | + | Installation instructions |
| - | - [[http:// | + | |
| - | - [[http:// | + | |
| - | - [[http:// | + | |
| - | - [[http:// | + | |
| + | * [[TP-Link-install|TP-Link Routers]] | ||
| + | * [[Linksys WRT54GL|Linksys WRT54GL, WRTSL54GS]] | ||
| + | * [[Linksys WRT54G-TM|Linksys WRT54G-TM]] | ||
| + | * [[Asus WL500G Premium|Asus WL500G Premium (V1 & V2)]] | ||
| + | * [[La Fonera|La Fonera]] | ||
| + | * [[D-Link DIR-3001|D-Link DIR-300]] | ||
| + | * [[Buffalo WZR-HP-G300NH|Buffalo WZR-HP-G300NH]] | ||
| + | * [[Ubiquiti RouterStation Pro|Ubiquiti RouterStation Pro]] | ||
| + | * [[x86|x86 Based Routers]] | ||
| + | * [[Other Routers|Other Routers]] | ||
| - | =====Linksys WRT54GL, WRTSL54GS===== | + | ===== Connecting to a Gargoyle Image ===== |
| - | The Linksys WRT54G* routers were the first routers to work with 3rd Party firmware. However, be aware that **newer WRT54G routers do NOT work with OpenWrt or Gargoyle** -- they have only 2.0MB of Flash, unlike their predecessors which had 4.0MB which is sufficient. If you want to use a Linksys WRT54G* router with Gargoyle, hunt down one of the old WRT54G units, v1-4 or obtain a Linksys WRT54GL or WRTSL54GS. | + | |
| - | These routers have a broadcom wireless chip, so you will want to use the brcm-2.4 images. There are several *.bin images for different models and a generic | + | To [[getting_started|get started]] |
| - | If you upgrade using the Gargoyle web interface | + | * browse |
| + | * ssh root@192.168.1.1 with the default " | ||
| - | It is also possible to upload the image to the router via tftp. As the router boots there will be a few seconds when it will accept tftp connections | + | OpenWrt defaults to having no root password and telnet |
| - | =====Linksys WRT54G-TM===== | + | ===== Migrating from OpenWRT |
| - | This router was only produced briefly by Linksys but is compatible with Gargoyle because it has 8 Megs of RAM and 32 Megs of flash giving you plenty of room to do cool stuff. | + | |
| - | To prepare for the procedure | + | FIXME Can you flash directly to Gargoyle from an OpenWRT install?? |
| - | - Download latest .trx image of the [[http://www.gargoyle-router.com/ | + | It **may** be possible to install |
| - | - Download this [[http:// | + | |
| - | - Download Tornado' | + | |
| - | < | + | ===== Migrating from DD-WRT ===== |
| - | 1. First assign two STATIC IP addresses | + | Attempts |
| - | On Windows XP, Control Panel/ | + | ===== More Information |
| - | + | If you find the documentation here insufficient there are several other resources | |
| - | On Windows Vista, Control Panel/ | + | - [[http:// |
| - | Go into the properties of the Local Area Connection/ | + | - [[http://oldwiki.openwrt.org/TableOfHardware.html|OpenWrt Table of Hardware]] |
| - | + | - [[http://wiki.x-wrt.org/index.php/Kamikaze_Installation|Kamikaze Installation Instructions | |
| - | IP Address: 192.168.0.2 | + | |
| - | Subnet Mask: 255.255.255.0 | + | |
| - | Default Gateway: 192.168.0.1 | + | |
| - | + | ||
| - | Click the Advanced button in the TCP/IP setup window and in the IP Address section click the ADD button to add the following 2nd IP Address to the adapter: | + | |
| - | + | ||
| - | IP Address: 192.168.1.2 | + | |
| - | Subnet Mask: 255.255.255.0 | + | |
| - | + | ||
| - | Then click OK on each screen. Your network interface card (NIC) now has 2 LAN IP Address statically set on it, 192.168.0.2 and 192.168.1.2. | + | |
| - | This will allow your PC to communicate with the router before and after the CFE_Updater is on it. | + | |
| - | It will also allow you to be able to tell when the router is ready for a TFTP upload. | + | |
| - | + | ||
| - | 2. Open a command prompt window and type ping -t 192.168.1.1 and hit enter. The ping with begin execution and there will be no response. | + | |
| - | + | ||
| - | 3. Log into the WRT54G-TM' | + | |
| - | + | ||
| - | !!!ATTENTION!!! You MUST wait 5 minutes after clicking the Upgrade button to allow the CFE_Updater to replace the stock CFE on the router and for it to erase the rest of the flash. | + | |
| - | + | ||
| - | A few seconds after clicking the Upgrade button the Linksys web interface will report that the upload has been successful and the power light will begin flashing on the router. | + | |
| - | + | ||
| - | Confirm that the process is complete by observing continuous ping responses in your still open ping window. | + | |
| - | + | ||
| - | 4. Start up the TFTP utility and set the following: | + | |
| - | + | ||
| - | Server: 192.168.1.1 | + | |
| - | Password: <leave blank> | + | |
| - | File: <path to your Gargoyle Image> | + | |
| - | + | ||
| - | Now click the Upgrade button. Once the firmware is sent to the router, it will reboot. The power light will change from flashing to solid when it is ready to be configured @ http:// | + | |
| - | + | ||
| - | If at some point you want to revert to the stock Linksys firmware you can find instructions at[[ http:// | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | =====Asus WL500G Premium (V1 & V2)===== | + | |
| - | The Asus WL500G Premium is another router that uses a broadcom wireless chip and is very much like the LinksysWRT54G* routers. You will want to use the generic .trx image for this router. The best way to upload it is using the upgrade utility for Windows that ships with the router. Unfortunately, | + | |
| - | + | ||
| - | Before | + | |
| - | - Unplug the router' | + | |
| - | - Confirm your PC is configured to request an address via DHCP. | + | |
| - | - Connect the router' | + | |
| - | - Push the black RESTORE button using a pen or such, and keep the button pushed down. | + | |
| - | - Plug the power on while keeping the RESTORE button pushed for few seconds. | + | |
| - | - When you see a slowly blinking power light, you are in diag mode. | + | |
| - | + | ||
| - | Once you are in diag mode you can use the windows utility to upgrade the firmware. | + | |
| - | + | ||
| - | Alternatively, | + | |
| - | + | ||
| - | Like the broadcom-based Linksys routers, if you already have other 3rd party firmware such as Tomato or DD-WRT installed, you can upgrade directly from there using the generic broadcom .trx file. | + | |
| - | + | ||
| - | =====La Fonera===== | + | |
| - | The La Fonera is somewhat different than the other devices listed here. First, it uses an atheros wireless device, and second you must access the RedBoot bootloader to install OpenWrt/ | + | |
| - | + | ||
| - | The easiest way to install on a La Fonera is to use the FonFlash utility available in the download section to automatically upload the firmware on to the router. | + | |
| - | + | ||
| - | Read the instructions below carefully before proceeding. For the purpose of these instructions it is assumed you are running linux (or another unix variant) on your local machine and that you have some knowledge of how to configure your network and network services. | + | |
| - | + | ||
| - | Before you can access the RedBoot bootloader, you have to " | + | |
| - | + | ||
| - | - [[http://bingobommel.blogspot.com/2006/11/ | + | |
| - | - [[http://www.notmart.org/index.php/ | + | |
| - | - [[http://stefans.datenbruch.de/lafonera/#kolofonium|Kolofonium Hack]] | + | |
| - [[http:// | - [[http:// | ||
| - | Before you telnet into RedBoot bootloader you may need to put the following lines in your telnet configuration file on your local machine (~/ | ||
| - | |||
| - | < | ||
| - | 192.168.1.254 9000 | ||
| - | mode line | ||
| - | </ | ||
| - | |||
| - | Next, configure your local machine to have a static ip in the 192.168.1.* subnet other than 192.168.1.254. For the purposes of these instructions I will assume you have configured your local machine to ip 192.168.1.3, | ||
| - | |||
| - | The next step is to configure a webserver on your local machine. There are multiple web servers available -- any will do. Place both the .lzma and the .squashfs atheros image files in the root directory of your web server so that they can be accessed at http:// | ||
| - | |||
| - | Now you are ready to telnet into Redboot. Reboot the Router and wait a few seconds, until the light in the middle starts flashing. Then open a new terminal and telnet into RedBoot by running " | ||
| - | |||
| - | < | ||
| - | mockingbird@linuxbox: | ||
| - | </ | ||
| - | |||
| - | Then, hit Ctrl-C to halt the boot process. | ||
| - | |||
| - | Once you are in, execute the commands listed below in the order listed below. Replace 192.168.1.3 on the first line with the ip of your local machine running the web server, if you configured it to have a different ip. Be aware that the "fis create" | ||
| - | |||
| - | < | ||
| - | ip_address -l 192.168.1.254/ | ||
| - | fis init | ||
| - | load -r -v -b 0x80040450 / | ||
| - | fis create -b 0x80040450 -f 0xA8030000 -l 0x006F0000 | ||
| - | -e 0x00000000 rootfs | ||
| - | load -r -v -b %{FREEMEMLO} / | ||
| - | fis create -r 0x80041000 -e 0x80041000 vmlinux.bin.l7 | ||
| - | fis load -l vmlinux.bin.l7 | ||
| - | exec | ||
| - | </ | ||
| - | |||
| - | The final " | ||
| - | |||
| - | |||
| - | ====== D-Link DIR-300 ====== | ||
| - | **Airlink101 AR430W** | ||
| - | |||
| - | The D-link/ | ||
| - | |||
| - | It appears that Dlink in there wisdom have changed the chipset of the DIR-300. **This procedure only works for revision A** | ||
| - | |||
| - | This procedure has been tested and works with | ||
| - | P/N: IIR300NTO....A1G | ||
| - | H/W: A1 F/W: v1.01-tomi-1.0 | ||
| - | S/N: P1RK 1850 XXXXX | ||
| - | |||
| - | //WARNING: Bricking you router is a high if you get this procedure wrong. A serial cable should bring it back to life but this is quite involved and requires soldering a header on your circuit board// | ||
| - | |||
| - | ===== Install Procedure ===== | ||
| - | We need to install a new redboot to do this we need to go to dd-wrt and lookup D-Link DIR-300 and install the supplied redboot | ||
| - | |||
| - | www.dd-wrt.com | ||
| - | |||
| - | It now appears that DD-WRT have changed the RedBoot in new releases and it now no longer works with gargoyle. Working previous release found here: | ||
| - | |||
| - | http:// | ||
| - | |||
| - | Windows flashing instruction for the D-Link DIR-300 to DD-WRT (by Brainslayer, | ||
| - | |||
| - | ==== Install Method ==== | ||
| - | Configure your local ip to 192.168.20.80 | ||
| - | connect your lan cable to the WAN port of the router. | ||
| - | unplug the power cord and replug it. | ||
| - | Now enter the redboot using telnet and ip 192.168.20.81 and port 9000. connect your lan cable to the dir300 wan port. | ||
| - | you might need several tries since its only available for 1 second after aprox. 5 sec. of booting | ||
| - | (in the appendix is a windows instruction for easy connecting to redboot) | ||
| - | |||
| - | DIR-300 Info: | ||
| - | IP: 192.168.20.81/ | ||
| - | Default server: 192.168.20.80 | ||
| - | |||
| - | Now start a local tftp server on your computer and place ap61.ram as well as ap61.rom in the root dir of this server | ||
| - | |||
| - | back to the redboot enter: | ||
| - | load ap61.ram | ||
| - | go | ||
| - | |||
| - | Now a new temporarily bootloader should start. (on serial console it will display some warnings. but you don't need to worry about this) | ||
| - | Plug you lan cable to the lan port of the dir-300. | ||
| - | reconfigure your ip to 192.168.1.2 and connect via telnet to 192.168.1.1 and port 9000. | ||
| - | |||
| - | Important: while doing the following steps. never unplug the lan cable or the power supply | ||
| - | |||
| - | fis init | ||
| - | About to initialize [format] FLASH image system - continue (y/n)? y | ||
| - | *** Initialize FLASH Image System | ||
| - | ... Erase from 0xbffe0000-0xbfff0000: | ||
| - | ... Program from 0x807f0000-0x80800000 at 0xbffe0000: | ||
| - | |||
| - | ip_address -h 192.168.1.2 | ||
| - | IP: 192.168.1.1/ | ||
| - | Default server: 192.168.1.2 | ||
| - | |||
| - | load -r -b %{FREEMEMLO} ap61.rom | ||
| - | Using default protocol (TFTP) | ||
| - | Raw file loaded 0x80080000-0x800a8717, | ||
| - | |||
| - | fis create -l 0x30000 -e 0xbfc00000 RedBoot | ||
| - | An image named ' | ||
| - | ... Erase from 0xbfc00000-0xbfc30000: | ||
| - | ... Program from 0x80080000-0x800a8718 at 0xbfc00000: | ||
| - | ... Erase from 0xbffe0000-0xbfff0000: | ||
| - | ... Program from 0x807f0000-0x80800000 at 0xbffe0000: . | ||
| - | |||
| - | reset | ||
| - | |||
| - | now the unit will reboot and the new bootloader will be executed and is waiting for your connection. | ||
| - | this wil take 30+ sec. | ||
| - | |||
| - | connect to the bootloader with telnet on port 9000 and ip 192.168.1.1 | ||
| - | ==== Install DD-WRT ==== | ||
| - | |||
| - | now do the following: (consider that fis create operations are taking sometimes several minutes to finish) | ||
| - | | ||
| - | ip_address -h 192.168.1.2 | ||
| - | IP: 192.168.1.1/ | ||
| - | Default server: 192.168.1.2 | ||
| - | |||
| - | load -r -b 0x80041000 linux.bin | ||
| - | fis create linux | ||
| - | |||
| - | fconfig boot_script true | ||
| - | fconfig boot_script_timeout 4 | ||
| - | |||
| - | now type fconfig again and configure the bootscript to | ||
| - | fis load -l linux | ||
| - | exec | ||
| - | now type reset again. the unit should now boot dd-wrt and work as known from other atheros based platforms | ||
| - | ==== Install Gargoyle ==== | ||
| - | If DD-WRT is all ready installed on your router start installing Gargoyle form **this** point. | ||
| - | * Download and run [[http:// | ||
| - | * Select correct ethernet port | ||
| - | * Load gargoyle files | ||
| - | * gargoyle_x.x.xx-atheros-root.squashfs | ||
| - | * gargoyle_x.x.xx-atheros-vmlinux.lzma | ||
| - | * Plug ethernet cable between router and PC | ||
| - | * Unplug power to router | ||
| - | * With fon flash click "Flash router now!" | ||
| - | * Plug in power to router | ||
| - | * Wait 20 - 30 minutes for router to finish flashing | ||
| - | Router should automatically reboot and install procedure is finished | ||
| - | {{: | ||
| - | ==== Windows easy connecting to redboot ==== | ||
| - | |||
| - | Appendix: | ||
| - | 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.20.81 -n 1 -w 1 > NULL | ||
| - | IF ERRORLEVEL 1 goto start | ||
| - | rem putty | ||
| - | rem ------------------------------------------------ | ||
| - | break | ||
| - | putty.exe telnet:// | ||
| - | 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 | ||
| - | =====Other Routers== | ||
| - | These are the only routers Gargoyle has been tested/ | ||
| - | Anyone interested in trying to get a specific model working should contact me and I will likely be happy to help. (NOTE: I do mean HELP -- you'll still have to do the heavy lifting). Gargoyle aims to be as flexible and hardware-independent as possible, and over time I anticipate hardware compatibility to expand significantly. | ||
| - | =====Installing Gargoyle As A Set Of Packages===== | ||
| - | Finally, if you have OpenWrt // | ||
| Line 345: | Line 82: | ||
| - | SSH into the router and take a look at the / | ||
| - | < | ||
| - | src/gz snapshots http:// | ||
| - | dest root / | ||
| - | dest ram /tmp | ||
| - | lists_dir ext / | ||
| - | option overlay_root /jffs | ||
| - | </ | ||
| - | You need to add a line to this file, and it will be slightly different depending on whether you have a broadcom or an atheros based router. You can tell by looking at the first line already in the file. In the file above the first line indicates that this is a broadcom router because it ends with / | ||
| - | < | ||
| - | src gargoyle http:// | ||
| - | </ | ||
| - | If it's an atheros router, add this line: | ||
| - | < | ||
| - | src gargoyle http:// | ||
| - | </ | ||
| - | Then run "opkg update" | ||
| - | < | ||
| - | root@OpenWrt: | ||
| - | Downloading http:// | ||
| - | Connecting to downloads.openwrt.org (195.56.146.238: | ||
| - | Packages.gz | ||
| - | Inflating http:// | ||
| - | Updated list of available packages in / | ||
| - | root@OpenWrt: | ||
| - | </ | ||
| - | Before you begin installation on a broadcom router you should verify that you have ~800kb of free space available, or ~2.0Mb on an atheros router. That's how much space gargoyle, along with all of it's dependencies requires. Atheros requires so much more space because it requires libopenssl (which is HUGE) to enable WPA wireless encryption. | ||
| - | The next (and final) step is to actually install the packages. If you're running a broadcom router, especially one with lots of memory, this is very simple. Merely run "ipkg install gargoyle" | ||
| - | < | ||
| - | root@OpenWrt: | ||
| - | </ | ||
| - | However, if you're on an atheros router there' | ||
| - | < | ||
| - | opkg install libopenssl | ||
| - | opkg install hostapd | ||
| - | opkg install wpa-supplicant | ||
| - | opkg install tc | ||
| - | opkg install kmod-sched | ||
| - | opkg install kmod-ipt-imq | ||
| - | opkg install kmod-ipt-filter | ||
| - | opkg install kmod-ipt-ipopt | ||
| - | opkg install kmod-ipt-conntrack | ||
| - | opkg install miniupnpd | ||
| - | opkg install ntpclient | ||
| - | opkg install uci | ||
| - | opkg install haserl-dev | ||
| - | opkg install qos-gargoyle | ||
| - | opkg install ddns-gargoyle | ||
| - | opkg install httpd-gargoyle | ||
| - | opkg install bwmon-gargoyle | ||
| - | opkg install gargoyle | ||
| - | </ | ||
| - | ... And that's it. You're done. Gargoyle should now be installed and accessible via the web interface at your router' | ||
| - | If you still are having trouble getting the gargoyle packages to install because of memory issues, first try rebooting the router. Sometimes this frees enough memory to make the installation work. If that doesn' | ||