background preloader

OpenWRT

Facebook Twitter

OpenWRT vs. DD-WRT vs. Tomato (was: Decent home router that doesn't suck @$$) - Ars Technica OpenForum. I've personally owned and maintained a WRT54GL router w/DDWRT for over a year.

OpenWRT vs. DD-WRT vs. Tomato (was: Decent home router that doesn't suck @$$) - Ars Technica OpenForum

It runs: DD-WRT v23 SP2 (09/15/06) vpn - build 3932. It does everything:-Open VPN server-QoS rules x15 (port and machine based)-DDNS server I reset it once due to poor performance but I had been throwing a lot at it for a long time. Considering my ISP is Comcast, I can't even really be sure it was the WRT's fault my service was sluggish. I've also set up DD-WRT on a WRT54Gv2, v4 and v7 for friends/family. The v2 has been going strong at least a year.

I used to run EMB-Cop on a Nokia IP120, m0n0wall on a small tower, stock Dlink, Netgear and Linksys routers. Table of Hardware. This page contains compatibility tables for various router and non router models.

Table of Hardware

Note: As of autumn 2009, this page is still in the process of being ported over from OpenWrt's old wiki. So if you do not see your router on this page, additionally consult the old table of hardware. A very reliable way to check for existing support is to take a look at The devices are sorted by target rather than manufacturer and if there is an image for the device, it should work (Bleeding Edge does contain bugs). Note that with the release of 'Attitude Adjustment (12.09 final)' on 25th April 2013, "Lower end devices with only 16 MiB RAM will easily run out of Memory…".

Recommended image for bcm47xx based devices is Backfire with brcm-2.4. If you want to add a device to the ToH, please distinguish between supported, WiP and so on. Legend Supported Hardware - Router type Devices listed in this table have full or reasonably complete support and can be considered ready for use. 3Com 4G Systems 8devices Actiontec. Netgear WNDR3700. Hardware specific sections according to the Hardware Template wanted — Netgear has sold a number of these units in boxes marked WNDR37AV. This was done for marketing purposes solely, the hardware is exactly identical (even to the point of many users finding a router physically labeled "WNDR3700 or WNDR3700v2" inside of a box labeled "WNDR37AV").

Version Ram Flash Network Serial JTag Atheros AR7161 rev 2 680 MHz 64MiB 8MiB 4 x 1 Yes here 16MiB Broadcom BCM4718A1 Version/Model Launchdate OpenWrt Version Supported Model Specific Notes v1 Backfire aka WNDR37AV-100PES, WNDR3700-100PES v2 Backfire 10.03.1 Box side panel lists WNDR3700 , aka WNDRMAC-100PES, WNDR3700-100prs the WNDR3800 is the actual successor board v3. First Login. Command-line Interface(CLI) using Telnet (if you haven't already set up a password) HTTP (using your web browser) if there is no WebUI (Web user interface) in the image, you can swiftly install one following this HowTo: LuCI Please note: (HTTPS access is only available after First Login)

First Login

Index of /snapshots/trunk/ar71xx/ Building OpenWrt for Netgear WNDR3700. This page contains, thus far, one user's complete notes on how to build a working OpenWrt WNDR3700 image from scratch, including working wireless on 2.4 GHz and 5 GHz bands.

Building OpenWrt for Netgear WNDR3700

This page assumes that you are comfortable with building software and using kernel-style makefile systems, but otherwise, the page describes how to build the system from the ground up (including getting your base OS ready to build OpenWrt in the first place). This page also describes the method used to unbrick a WNDR3700 (which does NOT require a serial cable), as well as optional instructions for manufacturing a serial cable (should you wish to use it for running ramdisk images). These instructions are working fine as of the relatively-recent trunk revision 19064. Until WNDR3700 support is integrated into a release, you'll need to execute the following commands to pull down the latest bleeding-edge code:

The UCI System. The abbreviation UCI stands for Unified Configuration Interface and is intended to centralize the configuration of OpenWrt.

The UCI System

Configuration should be easy and straightforward, making life easier! UCI is all about that. It is the successor to the NVRAM-based configuration found in the White Russian series of OpenWrt. UCI can be seen as OpenWrt's main configuration user interface for the most important system settings. Typically, these are settings that are crucial for the functioning of the device, such as are typically found in the web interface of routers and embedded devices. In addition, selected third party programs have been made compatible with the UCI system, so these can be managed more easily as well.

Most applications (save some that are made in-house) are made UCI compatible by the package maintainer by simply writing the original configuration file (which is read by the program) according to the chosen settings in the corresponding UCI file. Common Principles File Syntax Usage.