Asus RT-N13U

From DD-WRT Wiki

Revision as of 20:07, 1 September 2011 by U2n (Talk | contribs)
Jump to: navigation, search

There are two hardware versions of this device, the original 'v1', and the later 'B1'. Both have stable DD-WRT releases available.

By connecting an SD card, both can be fully self-contained; no more need for Internet access at bootup to load file system (FS) drivers. While this method requires some configuration (see #not done yet#), third-party developers have now produced firmware (FW) images with the FS drivers, including swap. (These are currently in beta, but getting good feedback.) Similar official releases are thought to be forthcoming, but the timeframe is unknown.

For wireless-N with USB, this router remains one of the best values. Besides the standard network printer and storage tasks, it can run Asterisk (PBX), host separate wireless LANs (WLANs), run many of the hundreds of optware programs including torrent clients such as Trasmission, serve small websites, serve sound (Ex. to stereo) with inexpensive sound card attached, and it even scratches your back. (:^) These are covered in detail below. (Web cam on the horizon.)


Overview Items

A Major Step Forward

Since the earliest FW releases, FS drivers have been absent. While no extra storage is required to run DD-WRT (there's a robust feature set as-installed), it's a must for Optware and many device-hosted programs or hardware.

To help us all, Gouryella brought the needed FS modules together, wrote the scripts, hosted everything on his website, and even made a guide (see here or in the thread). (He's done similar for Optware, and his work is now also used in other routers.) Many thanks, Gouryella.

By this method, the router downloads and installs the FS modules after each reboot; clearly some inherent shortcomings, but functional.

Now with the posting of Kirill's wiki (thanks to viking13 for bringing it to the forum), there is another option, one that allows FS drivers to be loaded directly from an attached drive. (See #not done yet# below.) Faster and more consistent reboots are reported, and dependency on web connection is eliminated. Many thanks, Kirill.

Differences in Hardware

The two versions differ primarily in the amount of flash memory and RAM onboard, the v1 at 4/32 and the B1 at 8/64 (MB flash/RAM). Because current official builds use the same memory envelope for both, there is little operational difference. This could change in the future if B1 releases expand to use the other 4 MB of native flash memory.

There is also a small but significant difference in bootloaders which causes the two FW versions to be incompatible. Flashing the wrong one reportedly bricks the device. Take care when downloading!

Support Threads

Each hardware version has it's own support thread, the v1 here, and B1 here. Much of the v1 discussion was driven by FS drivers and getting Optware operational, the B1 by many of the same topics as the early v1. Hot now on both threads is getting the third-party FW debugged.

Firmware Repository

Official releases are found here. After selecting folder year and release number, carefully choose either 'Asus-RTN13' for v1, or 'Asus-RTN13UB1' for B1.

Each directory contains two files, a .trx for first flash (from stock), and a .bin for later updates.

Third-party Developer FW Images

Thanks to grymster and to amitg0123.

For v1: grymster has posted here.

For B1: amitg0123 has created this thread and posted here.

Which FW Image for Me?

The good news is, there are now options! Those wanting to stay strictly with official releases should pick from the DD-WRT repository. Notes:

  • Some report r16994 of 05/08/11 is most stable, so preferred.
  • There is no indication that swap will ever be included in future official releases so if wanting to run memory-hungry programs like Transmission -- and not averse to the (small) risk -- consider grymster's or amitg0123's FW.

The grymster/amitg0123 FW has the advantage of auto-loading the FS drivers internally; no dependence on attached SD card, and little configuration needed.

Device Specifications

  • Power Supply = 12VDC 1,0A
  • Ethernet Ports = 1x WAN RJ-45 10/100 Base T, 4x LAN RJ-45 10/100 Base T
  • Antennas = 3x internal antennas
  • USB ports = 1x USB2.0
  • Wireless standards supported: 802.11b (max. 11 Mbit/s), 802.11g (max. 54 Mbit/s), 802.11n (max. 300 Mbit/s, 2.4 GHz only)
  • RAM = 32 MB (64 MB in rev B1)
  • Flash = 4 MB (8 MB in rev B1)
  • CPU = Ralink RT3052F clocked at 384 MHz

Flashing DD-WRT to a Stock Asus RT-N13U

This procedure places the router in recovery mode, then uses Asus' Firmware Restoration utility to upload the DD-WRT image. Subsequent updates, if any, are much easier - you can then make direct webflash through the Administration->FirmwareUpgrade menu, using only the 3.52Mb file named Asus-RTN13U-webflash.bin .

1. Preparation for Initial DD-WRT Install

1. Download latest DD-WRT Firmware Image
  • Browse to firmware repository and select/open most current directory, Ex. 12-24-10-r15962/
  • Open 'Asus-RTN13U' directory and download 'asus-to-ddwrt.trx'
2. Download latest version of the Asus Utility
  • Browse to
  • In the three dropdown menus, select 'Wireless', 'AP/Router', 'RT-N13U', and click 'Search'
  • Select OS in popup menu
  • Click '+' next to 'Utilities' and skip down to the most current non-B1 version, now dated 2010/01/06. In that box, click 'Global' and save the file. (Also see next step, download firmware.)
  • Within that zip file, navigate to the UT4063/Utility folder and run 'setup' to install.
  • Be sure there is access to the Firmware Restoration utility
3. Download safety copy of Asus firmware
  • Do same as previous step, except click '+' next to 'Firmware' and download latest non-B1 version, now dated 2010/01/06.
  • Note that this file should not be needed; use only to restore Asus FW to router if later desired.
4. Last few checks
  • If not already directly wired, connect Ethernet cable from one of the router's LAN ports to client PC.
  • Be sure router's other three LAN ports and WAN port are open (nothing connected)
  • On PC, disable all other network adapters: wireless, modem, etc.
  • On PC, disable any firewall (Ex. Windows Firewall)
  • Optional: Set PC to use a static IP, Ex., netmask, gateway
  • If possible, use uninterruptable power supply (UPS) for both PC and router. A power failure while flashing, though not likely, will probably brick the router.
  • Note: Early on, some had problems using Firefox. Consider using Internet Explorer or Chrome.
  • Final warning: Installing this firmware on a B1 version will brick the device. (See note at top of page.)

2. Flash to DD-WRT

1. Place router in Recovery mode
  • Disconnect power adapter plug from the RT-N13U
  • Push and hold the Restore button located on bottom panel. While continuing to hold down the Restore button, plug the power adapter back into router.
  • After five seconds, LED on front panel starts to blink, release the button.
2. Upload firmware image
  • On PC, open Asus' Firmware Restoration utility (installed earlier)
  • In Firmware Restoration window, click 'Browse' and select the DD-WRT image file, asus-to-ddwrt.trx (downloaded earlier)
  • Click 'Upload' to begin flash process that can take up to four minutes. Brick warning: Do not interrupt!
  • When message that router is rebooting appears, close Firmware Restoration utility.

3. Reboot, launch DD-WRT web interface, and cleanup

  • After a minute or two, disconnect power adapter plug from the RT-N13U
  • Wait at least ten seconds, then reconnect to power
  • If optional step of setting static IP was followed earlier, can reset to automatic
  • Browse to should bring up the DD-WRT web interface; set name/password for first access
  • Configure router as desired. Default connection is DHCP; for DSL check DSL with DD-WRT.
  • When satisfied that factory firmware will not be used again, uninstall Asus Utility from PC and delete Asus files.

NB: This operation is made only once, to convert the Asus firmware loader into a DD-WRT firmware loader; if you get nuts and want to get back to the Asus firmware, first you need to undo this operation before flashing the Asus firmware back [link needed here].

Automounting ext3/FAT/FAT32/NTFS

The following tutorial is provided primarily by gouryella (taken from, also by calvin18 and others of the community. The RT-N13U has only 4 MB flash, which is almost full with DD-WRT installed. Ext3 needs an extra 200 KB of storage, and the driver is not present in the DD-WRT firmware yet [BrS]. Gouryella wrote a smart script that downloads the ext3 driver and mounts the 1st partition to /opt during boot (after WAN is up)

1. Just paste the following into the text box in Administration -> Commands and click Save Startup

[NOTE: configuration of filesystem support and partitions can be easy set at first line, NTFS needs aditional driver, that can be installed after you pass Optware guide by ipkg install ntfs-3g]

EXT3="YES"; EXT3P="part1"; NTFS="NO"; NTFSP="part2"; FAT="NO"; FATP="part3"; mkdir /tmp/etc/config
echo "wget -P /tmp/root" >> /tmp/etc/config/fs.wanup
echo "tar -xvzf /tmp/root/fs.gz -C /tmp/root" >> /tmp/etc/config/fs.wanup
if [ "$EXT3" == "YES" ]; then echo "sh /tmp/root/ext3" >> /tmp/etc/config/fs.wanup; fi
if [ "$NTFS" == "YES" ]; then echo "insmod /tmp/root/fuse.ko" >> /tmp/etc/config/fs.wanup; fi
if [ "$FAT" == "YES" ]; then echo "sh /tmp/root/fat" >> /tmp/etc/config/fs.wanup; fi
echo "mount /dev/discs/disc0/$EXT3P -o noatime,nodiratime /opt" >> /tmp/etc/config/fs.wanup
echo "/opt/bin/ntfs-3g /dev/discs/disc0/$NTFSP /mnt" >> /tmp/etc/config/fs.wanup
echo "mount /dev/discs/disc0/$FATP /jffs" >> /tmp/etc/config/fs.wanup
echo "rm /tmp/root/*.ko /tmp/root/fs.gz /tmp/root/ext3 /tmp/root/fat" >> /tmp/etc/config/fs.wanup
chmod +x /tmp/etc/config/fs.wanup
echo "nobody:*:65000:65000:nobody:/mnt:/bin/false" >> /etc/passwd

1.1 Enable the following under Services -> USB

Core USB Support
USB 2.0 Support
USB Storage Support
Automatic Drive Mount

1.2. Reboot router with an ext3 formatted USB drive plugged in

If the drive was successfully mounted (which may take some time), try another filesystems by editing 1st line of script.

[NOTE: check mounts thru putty by DF -h because in dd-wrt gui is is shown only after repluging drive]

1.3 Debugging:

#delete or sharp 10th line, reboot again and check:
ls /tmp/root
cat /tmp/etc/config/fs.wanup
ls /tmp/etc/config/

Installing Optware Light

The following tutorial is provided by gouryella (taken from

1. Installing Optware (only to an ext3 partition; /opt MUST be empty)

wget -O - | tr -d '\r' > /tmp/
sh /tmp/; ipkg update; ipkg upgrade
wget -P /opt/bin; chmod +x /opt/bin/sort

[NOTE: gateway is hard set to, if u have problem with this replace in by vi or sed]

Now you can install another Optware packabe from or if u like:

1.1. Install xinetd, vsftpd, samba, webserver, pxe boot server, wget, nano, htop, dlq rapget

ipkg install xinetd htop nano samba2 vsftpd tftp-hpa wget; killall xinetd smbd nmbd
rm /opt/etc/samba/smb.conf /opt/etc/vsftpd.conf /opt/etc/init.d/S80samba  /opt/etc/xinetd.d/tftp
wget -P /opt; tar -xvzf /opt/opt.gz -C /opt
sh /opt/etc/init.d/S10httpd; sh /opt/etc/init.d/S10xinetd; rm /opt/opt.gz

1.2 Well done, RT-N13u is ready for basic usage, u can acces by

samba: \\
rem to add as hardrive in W7/XP run in command line 
net use a: \\\www
net use b: \\\dlq  
pxe: add: dhcp-boot=pxelinux.0,dd-wrt, to Services -> Services -> Additional DNSMasq Options

1.3 Open to the world (paste to Administrations -> Commands and Save Firewall)

iptables -t nat -I PREROUTING -p tcp -d $(nvram get wan_ipaddr) --dport 80 -j DNAT --to
iptables -t nat -I PREROUTING -p tcp -d $(nvram get wan_ipaddr) --dport 22 -j DNAT --to
iptables -t nat -I PREROUTING -p tcp -d $(nvram get wan_ipaddr) --dport 21 -j DNAT --to
iptables -I INPUT -p tcp -d --dport 8080 -j logaccept
iptables -I INPUT -p tcp -d --dport 22 -j logaccept
iptables -I INPUT -p tcp -d --dport 21 -j logaccept

Installing a Transmission-daemon onto Asus RT-N13U

I have just successfully installed and running this Transmission Torrent thingy

and thanks to "Gouryella" for showing us the light

adopted with slight Modification from Transmission daemon kudos to anonymous code-angels--Capper 22:07, 25 August 2010 (CEST)

1. Make the following folders

cd /opt
mkdir -p /opt/data/torrents/.config              # -p to make directories at the same time

The plan is to have everything torrent go to the folder /opt/data/torrents

2. Install Optware Transmission

/opt/bin/ipkg-opt -verbose_wget install transmission
Note: I like to see the progress of the downloading process, so I know the right thing is happening. This is done with the -verbose_wget parameter.

3. Started and stopped Transmission to get the basic work folders

/opt/bin/transmission-daemon -g /opt/data/torrents/.config/transmission-daemon
killall transmission-daemon

With the command above you get the basic folder structure of:

/opt/data/torrents/.config/transmission-daemon/settings.json  #file

4. Edit settings.json

nano /opt/data/torrents/.config/transmission-daemon/settings.json

5. Delete contents of settings.json and copy-paste following code into it.

     "blocklist-enabled": 1,
     "download-dir": "\/opt\/data\/torrents",
     "download-limit": 100,
     "download-limit-enabled": 1,
     "encryption": 2,
     "max-peers-global": 35,
     "peer-port": 25000,
     "pex-enabled": 1,
     "port-forwarding-enabled": 1,
     "rpc-authentication-required": 0,
     "rpc-password": "",
     "rpc-port": 9091,
     "rpc-username": "",
     "rpc-whitelist": "192.168.1.*",
     "upload-limit": 200,
     "upload-limit-enabled": 1

The file settings.json can also be downloaded from here (the wget command is one line):

 wget -O /opt/data/torrents/.config/transmission-daemon/settings.json 

but change to "download-dir": "\/opt\/data\/torrents", from "download-dir": "\/mnt\/data\/torrents",

6. Open listening port for WAN access

Go to your DD-WRT control panel and add the following to Administration - Commands - Firewall

iptables -t nat -I PREROUTING -p tcp -d $(nvram get wan_ipaddr) --dport 25000 -j DNAT --to 
iptables -I INPUT -p tcp -d --dport 25000 -j logaccept

You may change the value 25000 to whatever port you specified in the settings.json file for the value "peer-port"

7. Restart transmission

/opt/bin/transmission-daemon -g /opt/data/torrents/.config/transmission-daemon

8. Accessing Transmission web interface

Now you get web access to the Transmission page by going to That is, if your routers IP is

9. Autorun Transmission-daemon every time router reboot

I would not like to go to command shell and type to start the Daemon. so here is the autostart for couch potatoes like me.

cd /opt/etc/init.d
rm S99trans

This will remove old S99trans initializing file you might have in the directory . We will now create an autorun script for our Transmission-Daemon

nano S99trans

now type-in following lines in it

sleep 120
/opt/bin/transmission-daemon -g /opt/data/torrents/.config/transmission-daemon

Save it by presseing CTRL+O followed by CTRL+X , now we will Make it executable by...

chmod +x /opt/etc/init.d/S99trans

You are done. Enjoy downloadig sans PC.

10. How to get transmission to download torrent files?

     - In a web browser go to your favourite torrent site/tracker and download a "<myfile>.torrent" file
     - In a web browser go to to enter the Transmission web page.
     - click "open"
     - click the text field (or "select" button)
     - point out the "<myfile>.torrent"
     - click "upload"

     and the torrent'ed file should start downloading shortly.

The downloaded file will turn up in the /opt/data/torrents folder.

The full space of the file will be reserved from the start, so in a FTP, WinSCP or Explorer via Samba it may seem like the file is all there immediately, but it is not! It is fully downloaded when the line turns green in the Transmission web interface at

You can see details about any of the torrent files by clicking the Inspector button on the right in the Transmission web interface.

11. Another interface option

You might also want to check out a front-end (remote-GUI) for the rpc version of transmission.

transmission-remote-gui is an application written in Free Pascal to remotely manage Transmission See:

transmission-remote-dotnet is a .NET application written in C# to remotely manage Transmission. See:

"Try the latest one (beta is welcomed over here)"

Installing a Network Printer onto Asus RT-N13U

As of v24-PreSp2 (first versions to work on Asus RT-N13U) jffs was removed due to the lack of space available. However, Brainslayer put the support of network printing onto the firmware, enabling use of a network printer. Special Thanks for TimeKiller for figuring out most of the solution.

1. First enable USB support

Enable the following under Services -> USB:

Core USB Support
USB 1.1 Support (UHCI)
USB 1.1 Support (OHCI)
USB 2.0 Support
USB Printer Support

2. Startup Settings

Go to Administrations -> Commands, and add this:

sleep 4
mkdir -m 755 -p /dev/usb
mknod -m 660 /dev/usb/lp0 c 180 0
/usr/sbin/p910nd -f /dev/usb/lp0 1 

Save on the Startup.

3. Reboot and Install Drivers

Reboot the router, then install drivers through tcp/ip (9101)

For Windows 7:

Go to Devices and Printers
Then, press Add a Printer
Got to Network Printers
Skip the detection, as Windows will not find anything
Go to "Add a printer using a tcp/ip address or hostname"
Device type: Autodetect
Hostname and ip address: your router's ip (default
Port Name: Anything (puts your router's ip by default)
After it says it could not detect a printer, select custom, then Advanced
Make sure the protocol is RAW and change the Port Number is 9101
Install your drivers and finish.

You should print a test page to see if it works.

4. Troubleshooting If the test page does not come, try these settings instead:

Go to Administrations -> Commands, and add this:

sleep 4
chmod +rwx /usr/sbin/p910nd 
mkdir -m 755 -p /dev/usb
mknod -m 660 /dev/usb/lp0 c 180 0
chmod +rwx /dev/usb/lp0
/usr/sbin/p910nd -b -f /dev/usb/lp0 0 

Save again on the Startup. Reboot then follow the steps above but instead of port 9101, put in 9100. You should print a test page again to see if it works. If it doesn't work, you somehow did not follow the instructions correctly.

Fire up a Second Wireless Network w/ Optional Bandwidth Throttling

A second (or even third) wireless network is useful for sharing the router's Internet connection. The new wireless network(s) is easily configurable:

  • Secure or open (hotspot)
  • Complete or partial isolation from the main network
  • Amount of bandwidth alloted

All setup is done in the DD-WRT web interface. (The following instructions should work for other Ralink-based routers as well.)

Browse to the router's home page and login, then:

1. Create Virtual Interface for New Wireless Network

On Wireless | Basic Settings page, under 'Virtual Interfaces' click Add

  • Key second SSID, the 'Wireless Network Name' preferred, Ex. BobNet, YoHotspot.
  • Check that 'Wireless SSID Broadcast' is Enable
  • Set 'AP Isolation' as preferred: Enable (default) for client-to-client communication on the new wireless network, Disable to isolate each.
  • Set 'Network Configuration' to Bridged
  • Be sure 'Wireless Mode' at top of page is set to AP (Access Point)
  • Click Apply Settings.

2. Set Security for New Wireless Interface

On the Wireless | Wireless Security page, under 'Virtual Interfaces ra1 SSID...' ("ra1" is the new wireless interface just created in step 1.), set parameters as desired for security. These setting work exactly the same as for the router's physical interface (shown at top of page), but apply only to the new wireless network.

  • For public access/hotspot, 'Security Mode' would be Disable.
  • A shared secure network would normally use WPA2 and AES.
  • When done, click Save.

3. Create Bridge for New Wireless Interface

On the Setup | Networking page, under 'Bridging' click Add.

  • In leftmost (unlabled) field that pops up, key "br1" (without quotes),
  • Set 'STP' to Off, and
  • Leave 'Prio' (Priority) and MTU as they are. Click Save.
  • New fields will appear for 'IP Address' and 'Subnet Mask'. Populate these (Typical values might be and, used in following examples.) and click Save.
  • Reboot.

4. Assign New Wireless Interface to New Bridge

Still on Setup | Networking page, under 'Assign to Bridge' click Add. On Assignment line that appears:

  • Select 'br1' in dropdown menu,
  • Pick 'ra1' in second dropdown menu (labled 'Interface'),
  • Set priority, 'Prio', as desired. Higher number = lower priority. The corresponding priority numbers (under 'Create Bridge' and 'Assign to Bridge') should be similar. Ex. 32768 and 32760.
  • Click Save and reboot.
  • Check in 'Current Bridging Table' that ra1 interface is assigned to br1 (they appear on same line). If not, edit any bad entries, possibly Delete and re-key, Save, reboot, and repeat this step.

5. Enable DNSMasq as Sole DHCP Server

This has the added benefit of running the router more efficiently*. On Setup | Basic Setup page, see that:

  • 'DHCP Type' is DHCP Server
  • 'DHCP Server' is Enable
  • 'Use DNSMasq for DHCP' is checked
  • 'Use DNSMasq for DNS' is checked

On Services | Services page, set:

  • 'Used Domain' to 'LAN & WLAN"
  • 'LAN Domain' to some name (Ex. mylan, yourlan, lan1, alan etc.)
  • 'DNSMasq' to Enable
  • 'Local DNS' to Enable
  • In 'Additional DNSMasq Options' window, paste the following:
  • Edit the above pasted text to customize as needed:
    • Replace "mylan" with the name chosen for 'LAN Domain' if different; these must match.
    • Edit the "120" -- which allows 20 clients to connect simultaneously -- as desired.
    • Edit both occurences of "192.168.16." to match the address keyed in 'Create Bridge for New Wireless Interface', above.
  • Click Save and reboot.
*(For details, see DNSMasq page.)

6. Set Level of Isolation for New Wireless Network

Unless the new network is secure and all connected clients trusted, some isolation is needed.

  • The easiest setup completely isolates the new network -- its clients have full access to the Internet, but not to the router or its wired or wireless clients. On the Administration | Commands page, under 'Command Shell', paste the following into the 'Commands' window:
iptables -I FORWARD -i br1 -o br0 -j DROP
iptables -I INPUT -s -d -j DROP
  • As above, edit the subnet addresses, 192.168.16 and 192.168.1, if customized. Click Run Commands and test/verify that everything works as expected. All pings or other attempts to connect between the two subnets should fail. Reboot if any problems.
  • When satisfied, with final iptables rules in 'Commands' window, click Save Firewall. Note: A click of this button with bad rules showing can lock everyone out of the router, necessitating a hard reset (and loss of all custom settings). Do not skip the previous test step.
  • If instead of total isolation it is desired to grant partial access to new networks' clients, determine which rules to modify and use (Ex. below), test and save as above.
iptables -I INPUT -i br1 -p tcp --dport www -j REJECT
iptables -I INPUT -i br1 -p tcp --dport telnet -j REJECT
iptables -I INPUT -i br1 -p tcp --dport ssh -j REJECT
iptables -I INPUT -i br1 -p tcp --dport https -j REJECT

7. Set Bandwidth Limits on New WLAN (Optional)

The maximum bandwidth taken by the new wireless network can be limited by following these steps. New WLAN clients will otherwise compete for bandwidth on equal footing with those on the main network.

  • Navigate to one or more speed test sites (Ex. Speakeasy) and note maximum Up- and Down-link speeds.
  • On NAT/QoS | QoS page, enable QoS ('Start QoS' Enable) and check that 'Port' is WAN and 'Packet Scheduler' is HTB.
  • In 'Uplink' and 'Donwlink' fields, key desired maximum throttled values in light of speed test results above. To convert, Ex. 5.8 Mbps from test=5800 kbps, and 0.57 Mbps=570 kbps.
  • Note: Settings below will make the throttled speeds just entered ('Uplink'/'Downlink') apply only to the new wireless network. While the help screen sets a guideline of "80%-100%" of maximum, these throttled values can be set to whatever the admin desires, perhaps as low as 10%. A setting of 50% could prove perfectly functional. Performance testing and tweaking is recommended.
  • Under 'Netmask Priority', key new wireless subnet address. Using same as above, Click Add.
    • On the line that appears, set 'Priority', Ex. Bulk. Click Save.
  • Repeat for main interface (Ex., click Add, set priority as desired, typically 'Exempt', click Save.
  • Reboot.

Note that throttling can also be applied based on application Service or MAC address.

If all steps were followed, the second SSID should appear to wireless clients in the area, their login and connection subject to the security and bandwidth settings made here. It is good to share with thy neighbor!

Sound Card

Sound works great. (#full post on the way, not done yet#)