asus rt n16 openwrt

User Tools

Site Tools

Table of Contents

The Asus RT-N16 is a middle class router from 2010 with gigabit ethernet and 802.11n draft. It is based on the Broadcom BCM47xx SoC platform.

Supported Versions

Brand	Model	Version	Current Release	OEM Info	Forum Topic	Technical Data
Asus	RT-N16	18.06.5		View/Edit data

Status

The Barrier Breaker release have almost full support of Asus RT-N16. The following is a list of everything that needs polish in order to update this device’s status to ‘fully supported’.

Hardware Highlights

Model	Version	SoC	CPU MHz	Flash MB	RAM MB	WLAN Hardware	WLAN2.4	WLAN5.0	100M ports	Gbit ports	Modem	USB
RT-N16	Broadcom BCM4718	480	32	128	Broadcom BCM4718	b/g/n	—	—	5	—	2x 2.0

Installation

Model	Version	Current Release	Firmware OpenWrt Install	Firmware OpenWrt Upgrade	Firmware OEM Stock
RT-N16	18.06.5			http://dlcdnet.asus.com/pub/ASUS/wireless/RT-N16/FW_RT_N16_30043763754.zip

Install from Tomato

Install from ddwrt

Below instructions install bleeding edge.

this is how i installed it from ddwrt ssh session:

cat /proc/mtd

cd /tmp wget mtd -r write openwrt-15.05.1-brcm47xx-mips74k-asus-rt-n16-squashfs.trx linux

after router reboots, you should be able to telnet to 192.168.1.1 and go from there.

be sure to reset to default settings using :

firstboot

otherwise things will be missing and misconfigured.

Flash Layout

→flash.layout for a detailed explanations.

OEM easy installation

Note that (at least for some version of the Asus firmware) the generic OpenWrt builds are not accepted by the ASUS web interface. Hence, there is a need for a special build for initial flashing. A patch still needs to be made for this but it is not worked on as of yet. Until then, you can either use the methods below, or use the DD-WRT file for initial flashing and then flash OpenWrt through the DD-WRT web interface. The page at wl500gp has detailed backup, flash, & recovery information which should largely apply to the RT-N16 as well.

OEM installation using the TFTP method

From Windows

Flash from a Windows PC using the Firmware Restoration utility. (Download or install the Firmware Restoration Utility to your PC.)

The Asus RT-N16 has a failover mode, like the DIR-600 Bx (X=1,2).

To launch the recovery mode disconnect power from the router first.

Hold the WPS button while plugging in the power to the router to reset nvram, router will restart 2x. Hold the RESET button while plugging in the power to the router to get into recovery mode in which tftpd will be listening. The power LED should start to blink (low frequency,

1 time every 3 seconds). Retry if that doesn’t work for you.

Configure your PC (don’t use 192.168.1.1)

netsh interface ip set address name=“Local Area Connection” static 192.168.1.2 255.255.255.0

Ping 192.168.1.1 should give a response.

Launch the Firmware Restoration utility, select the firmware and press the Upload button.

Ignore the warning, we want to be on OpenWrt!

It may now take several minutes. Be patient and enjoy a cup of tea or coffee.

Reconfigure your PC back to DHCP

netsh interface ip set address name=“Local Area Connection” source=dhcp

Connect to and proceed with the basic configuration.

This may work with other tftp utilities, too.

From Linux

The Asus RT-N16 has a failover mode, like the DIR-600 Bx (X=1,2).

Get a tftp client, Since Ubuntu is a popular choice snag it :

sudo apt-get install tftp

Now to modify the router … To launch the recovery mode disconnect power from the router first.

Hold the WPS button while plugging in the power to the router to reset nvram, router will restart 2x. Hold the RESET button while plugging in the power to the router to get into recovery mode in which tftpd will be listening. The power LED should start to blink (low frequency,

1 time every 3 seconds). Retry if that doesn’t work for you.

Configure your box to use an ip 192.168.1.15; this specific IP is required in order to transfer via tftp.

sudo ifconfig eth0 192.168.1.15

Ping the interface to be sure it’s up :

ping 192.168.1.1

If you get ping responses then it’s up and ready to flash.

tftp 192.168.1.1

Set it to binary mode transfer :

mode binary

upload the firmware :

put openwrt-brcm47xx-squashfs.trx

When it’s complete the router will be writing the firmware and may not automatically reboot. Wait up to 5 minutes, then power off the router and plug it back in.

Upgrading OpenWrt

LuCI Web Upgrade Process

Terminal Upgrade Process

Failsafe mode

If you forgot your password, broken one of the startup scripts, firewalled yourself or corrupted the JFFS2 partition, you can get back in by using OpenWrt’s failsafe mode. If you are unsuccesful solving the problem with OpenWrt’s failsafe mode, i.e. you have bricked the device, you can use Asus’s failsafe mode to flash a new image.

OpenWrt Failsafe Mode

Follow these steps to boot into the OpenWrt failsafe mode:

What to do in failsafe mode?

NOTE: The root file system in failsafe mode is the SquashFS partition mounted in readonly mode. To switch to the normal writable root file system run mount_root and make any changes. Run mount_root now.

If you are done with failsafe mode power cycle the router to boot in normal mode.

Asus Recovery Mode

Since this is an Asus product you can also use the failsafe mode (included in the boot loader). Press and hold the “Reset” button on the back of the device, then plug it in. When the ‘PWR’ light blinks slowly then it is listening in TFTP mode (

once every 3 seconds). The default address is 192.168.1.1. If this is not pingable, do the NVRAM reset first, described as follows.

To reset the NVRAM, hold the “WPS” button and plug in the router. When the ‘PWR’ light is blinking quickly, then when you let go of the WPS button, the router will perform a reboot, wipe and reboot again. Note that clearing NVRAM does not clear much of OpenWrt’s configuration, unlike other router software which keep configuration data in NVRAM. Since OpenWrt’s configuration is kept in the main JFFS file system, using UCI configuration files, if you cannot boot normally you can reset or change this with OpenWrt’s failsafe mode. See also flash.layout.

Basic configuration

Since this part is identical for all devices, see Basic configuration.

Tsan-Kuang Lee’s Blog 李璨光個人網誌

Thursday, November 27, 2014

Use 802.11n on Asus RT-N16 with OpenWrt

Overview

Background

Choosing Alternatives

Therefore, I started to look for an alternative. Besides dd-wrt, Tomato and it’s family, and OpenWrt are the other two high-profile router firmware development efforts. And both lineages provide very customizable environment.

However, there are two things I’m looking for.

1. I am looking for a project that’s still actively maintained, especially after Heart Bleed, Shell Shock, and Poodle. (Note that these vulnerabilities don’t necessarily compromise home routers, but in my environment, I’d rather not take the chance.) While a repository system allows individual package upgrade, I want the base developers to still be around.

2. I’m looking for a project that’s owned by a team rather than individuals. In the WRT history, there have been many brilliant individuals that made crucial advances for everyone. However, it has happened a few times when these individuals moved on, their projects died, too.

Therefore, I ended up choosing OpenWrt.

Installation

It was quite straightforward to switch to OpenWrt from dd-wrt, as instructed in the official guide.

Securing the admin access was obvious. However, it took me a while to realize that I also needed to reboot my Cable Modem for it to reset its DHCP. If you are also doing this, I suggest you open all installation guides in the browser first before you flash your new firmware. I had to use my phone to check the guides before my internet was up.

802.11n

This took me a while because the guide is not very obvious. Anyway, after some trials and errors, broadcom-wl was the only one that worked for me (thanks to Stratos about the dependency nas. I already had that so I didn’t realize that dependency).

1. # opkg update
2. # opkg install kmod-brcm-wl wl wlc
3. # rm /etc/config/wireless
4. # opkg install nas
5. # reboot

config wifi-device wl0
option type broadcom
option channel 1
option txantenna 3
option rxantenna 3
option txpower ’20’
option plcphdr ‘auto’
option frameburst 1
option disabled 0
config wifi-iface
option device wl0
option network lan
option mode ap
option ssid YOUR_SSID
option key YOUR_KEY
option wmm 1
option encryption ‘psk2’
option disabled ‘0’

Update: badineu in the comment mentioned that he also needed to manually select the wifi frequency. You may also have to do so if, for some reason, it’s not already properly set.

Есть желание настроить впн на роутере.
Прошивка openwrt barrier breaker 14.07
Настраивал по инструкции wiki.openwrt.org/doc/howto/vpn.openvpn#installation
Не заработало. Чуть подправил конфиг /etc/config/openvpn, согласно настройкам сервера (mullvad.net) — но не работает по прежнему. Кроме того, не смотря на то, что туннель не создается(?), интернет через роутер — есть, IP — мой, так что по видимому не работает и firewall

По ссылке — конфиги
cat /etc/config/network
cat /etc/config/firewall
cat /etc/config/openvpn

Если кто подскажет куда копать, буду благодарен. Ну или вдруг кто уже настраивал и имеет опыт.
sprunge.us/TiZQ

• Вопрос задан более трёх лет назад
• 11726 просмотров

Использование роутера RT-N16 (openwrt) в качестве openvpn клиента:
1. Использовал прошивку openwrt-brcm47xx-mips74k-asus-rt-n16-squashfs.trx
Предполагается подключение по ssh через putty.
2. Установить openvpn: opkg update && opkg install openvpn-openssl
3. Установить web interface luci кому нужен opkg update && opkg install luci (почему-то он либо не был установлен, либо не работал)
4. Скопировать ключи (cert.crt, cert.key, ca.crt в папку /etc/openvpn/keys ) и конфиг на роутер в папку /etc/openvpn
конфиг /etc/openvpn/client.conf (где хх.хх.хх.хх — ip сервера openvpn):

4. Запустить openvpn /etc/init.d/openvpn start
5. Смотреть лог и ошибки : cat /var/openvpn.log

6. После этих манипуляций должны идти пинги с роутера до удалённой сети.
7. Настраиваем интерфейсы (через web выглядит так):
Network -> Interfaces -> Add
Name of new interface: VPN
Protocol of new interface: Unmanaged
Cover of following interface: tun0
Submit.
8. Добавить в Firewall зону VPN c интерфейсом tun0 и разрешить с него доступ на LAN, разрешить доступ с LAN на VPN.

Ньюансы:
копировать серты файлы можно несколькими способами:
1.копируя через sftp, установив его opkg update && opkg install openssh-sftp-server (предварительно желательно поменять порт в dropbear на отличный от 22, например 222),
2. копируя через буфер и вставляя в vi,
3. Подняв web сервер на локальном компе, и забирать через wget.
4. .