TomatoUSB

Here are the steps I have taken to install Shibby's 108 AIO build on a brand new ASUS RT-N16 from a Mac:

Combined Tutorial Installing On Asus Routers (RT-N16 etc) in Linux and forum post Installing On Asus Routers for Mac OS X

1. Downloaded the 108 AIO build of Shibby to the /Users/Drew/Downloads directory on my Mac

2. Use a cable to connect your computer to LAN port 1 on the router. FYI, this is a brand new router, straight from the box. Never operated before.
3. Turn off the router, disable your ethernet connection:

sudo ifconfig en0 down

sudo ifconfig en0 up 192.168.1.2

ping 192.168.1.1

NOTE: Confirmed.
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=100 time=2.606 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=100 time=0.665 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=100 time=0.697 ms

7. Upload the firmware:

cd /Users/Drew/Downloads
ls *.trx
tomato-K26USB-1.28.RT-MIPSR1-108-AIO.trx
tftp 192.168.1.1
tftp> binary
tftp> put tomato-K26USB-1.28.RT-MIPSR1-108-AIO.trx

8. Then wait for the prompt to be returned, and wait for a further minute.

tftp> quit

9. Finally turn off the router, set your ethernet back to auto, wait a minute, turn on the router and you should have a tomato install!

Source: Concentric Livers.

OK, at this point, I don't really know what "set your ethernet back to auto" means. man ifconfig does not list an "auto" switch. So I guess this means to go to DHCP on the Mac…? but I don't get an IP that makes any sense and I can't connect to 192.168.1.1. Just continue with manual network setting of 192.168.1.2, subnet mask 255.255.255.0, router 192.168.1.1.

So I continue reading…

Additional clarifications from Sergey Gleizer:

After TFTP session completes, wait about five minutes for the firmware to actually be flashed. There is no visual indicator that flashing is complete… If you fail to wait long enough before power cycling the router, it will have an incomplete firmare flash and will go to recovery mode (slow flashing power LED, same as when powering up with 'restore' button pressed)
After a successfull flash, it is a good idea to clear NVRAM by powering up while holding down WPS button and continuing to hold it for 30 sec after power-up.

I basically redo steps 2-7, then at step 8, change that to 5 minutes. Try to reconnect, and nothing.

Any thoughts?

Thanks.
Drew

Check page two for at least 5 ways.
http://tomatousb.org/forum/t-603465

Perhaps Shibby could add an Asus signed image to his collection, then could install directly from original Asus firmware. EasyTomato has done this in their latest beta for the RT-N16, so the addition to the Makefile will be in their git, their previous method using a small dd-wrt method already avoids the fiddly steps above.

A. For whatever reason, I cannot login as a Wikidot user, even though I'm registered
B. From GeeTek's post, here are the results of my efforts:

#1 - TFTP from Linux ( might work with MAC computer )
(link to Linux tutorial which I can't post — see issue A)

Tried this method from Lubuntu VM. The problem is always the same… when I get to the point where I have rebooted the router after waiting 5 mins for the firmware to flash, and holding down the WPS button for 30 seconds during boot up (do I need to boot up first, then hold down the WPS button…?), I can no longer ping the router on 192.168.1.1 and of course, no web GUI.

#2 - ASUS recovery tool.
(link to tutorial which I can't post — see issue A)

Tried this method from a Windows XP VM. The problem here is the ASUS Recovery Tool does not see the router at all. It's not clear if the router is suppose to be in recovery mode or not when trying to connect.

#3 ( I recommend try first ) - Built in flash utility. Do step #4 from previous link. Connect computer to LAN port and open 192.168.1.1 in your browser. The built in flash utility GUI will open and let you browse the computer for the flash file. You flash it from there.

Can't use the built in flash utility as I have no access to the original GUI

#4 - TFTP from MAC command line using built in TFTP line command.

Original method I tried, which failed. Same problem as the Linux method — can't reach 192.168.1.1 after a flash.

#5 - TFTP from MAC or Windows computer using TFTP utility program.

Haven't tried this one, yet. Since the Linux and Mac TFTP methods did not work, I'm skeptical about the odds of either of these working. But will have a go at it if no other options come up.

Thanks for the responses. It's greatly appreciated.
Drew

Can't use the built in flash utility as I have no access to the original GUI

Why is it that you have no access to the GUI ? Did you assign a static IP to your computer and put the radio in recovery mode ?

A. I narrowed down my login issue with Wikidot — probably a Firefox add-on. Using Safari for the moment…
B.

Why is it that you have no access to the GUI ? Did you assign a static IP to your computer and put the radio in recovery mode ?

Because there was no firmware after the first flash failed. Yes, I assigned a static IP and put the radio in recovery mode.

I called Asus and they got me to the point where I had a factory firmware that I could flash with the Asus Firmware Restoration utility from a Windows XP VM — they basically said flat out it can't be done on Mac OS X or Linux.

After getting in original firmware up and running, I was able to flash Shibby's AIO build, but it has never started — even after waiting over 10 minutes for it to complete. I see in the bug log that AIO has issues, so I'm gonna try the Mega-VPN version (tomorrow).

I have the same router that I flashed 1.5 years ago with a Teddy Bear variant. Not sure why the Shibby build is so badly misbehaved…?

Drew

Because there was no firmware after the first flash failed

The recovery mode does not require firmware. Recovery mode is a special boot loader that is independent of the state of the firmware. The firmware can be fucked to high heaven and the boot loader will still run. That is why these radios are nearly impossible to brick. Recovery mode is always available no matter what. The fact that you couldn't get to it indicates other isssues. Shibby 108 has been reported to boot slowly on some rt-N16 radios, but it eventually boots after about 5 minutes.

I think you still have other computational issues. First thing I would do is hose down the Apple computer with the garden hose and then go buy yerself a computer that 99% of the rest of the world is using. It would be for your own good, and your routers and everything else connected to your network would magically start working.

First thing I would do is hose down the Apple computer with the garden hose and then go buy yerself a computer that 99% of the rest of the world is using.

Steve Balmer must have sucked your dick real good.

Recovery mode is always available no matter what. The fact that you couldn't get to it indicates other isssues. Shibby 108 has been reported to boot slowly on some rt-N16 radios, but it eventually boots after about 5 minutes.

So I'm suppose to be able to get to the router via web GUI when in Recovery mode? I can get to the router in Recovery mode via TFTP or Firmware Restoration, it just doesn't seem to take. FWIW, I'm pretty sure I flashed the wrong variant (R1 as seen in first post, vs R2). I went back and tried the correct one — it just becomes unavailable after a flash and waiting for more than 5 minutes.

Just to be clear, is the process to flash the tomato firmware, then go to Recovery mode to somehow do something else? I didn't get that from any instructions I've seen…

Thanks for the feedback.
Drew

GeeTek, you were correct in that there was something amiss in my system (networking, specifically)… Not sure if it is Mac or Hack specific, but I have a workaround. Thanks for pushing me in the right direction. Forget most of what I've written previously. Here's how I made it work from the Mac OS X environment only:

Reboot ASUS RT-N16 into Recovery Mode:

1. unplug power
2. hold down RESET (RESTORE) black button (need a ball point pen or philips screwdriver to hold down recessed button)
3. plug power back in — keep holding RESET button for 30 seconds
4. Release RESET button. Power light on router should be blinking slowly (approximately 1 sec ON, 1 sec OFF)

Open Terminal
Check IP to see if on the correct route (need to be 192.168.1.x subnet 255.255.255.0)

$ ifconfig

In the response, look for (en0 is the ethernet port, though could be en1):

en0:
    inet 192.168.1.66 netmask 0xffffff00 broadcast 192.168.1.255

All good. If not, open System Preferences… Network Preferences…

Click on Ethernet (or Ethernet 2 depending on which is plugged in to router)
Configure IPv4: Manually
IP Address: 192.168.1.66
Subnet Mask: 255.255.255.0
Router: 192.168.1.1
Click [ Apply ]

Back in Terminal, try pinging the router while it's in Recovery Mode (slow flashing Power light)

$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
^C

Result: No connection. Here's how to fix that flakey network issue:

$ sudo ifconfig en0 down
Password: <your_admin_rights_password>
$ sudo ifconfig en0 inet 192.168.1.66 netmask 255.255.255.0
$ sudo ifconfig en0 down
$ sudo ifconfig en0 up
$ ifconfig

Should get the en0: inet 192.168.1.66 response (along with a lot of other info)

Try pinging the router, again:

$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=100 time=2.474 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=100 time=0.957 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=100 time=0.965 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=100 time=1.009 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=100 time=0.962 ms
^C

OK, now we've established that the static IP on the computer is actually on the same route / subnet mask as the router and they can see each other. That's good.

In Terminal, navigate to where new firmware is located. (NOTE: Be sure to get the R2 variant for the ASUS RT-N16)

$ cd ~/Downloads
$ ls #.trx
tomato-K26USB-1.28.RT-MIPSR2-108-AIO.trx

Start up Tiny File Transfer Protocol client (TFTP) connection to router

$ TFTP 192.168.1.1
tftp> binary
tftp> put tomato-K26USB-1.28.RT-MIPSR2-108-AIO.trx

Wait for response…

Sent 9420800 bytes in 28.0 seconds
tftp>

Keep waiting, and keep an eye on the router. At about ?:?? after the response, wireless light should come on (NOTE: for Mega-VPN, this only took about 1:12 for the wireless light to come on). Failed to come on after 10:00+ mins on the AIO variant.

tftp> quit

Sometimes cycling the router hoses the networking on my Hack. Check to see that it's working:

$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
Request timeout for icmp_seq 0
ping: sendto: Host is down
Request timeout for icmp_seq 1
^C
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss

The networking is hosed.

$ sudo ifconfig en0 down
Password: <your_admin_rights_password>
$ sudo ifconfig en0 inet 192.168.1.66 netmask 255.255.255.0
$ sudo ifconfig en0 down
$ sudo ifconfig en0 up
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.816 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.318 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.340 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.337 ms
^C
--- 192.168.1.1 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.318/0.453/0.816/0.210 ms

This is good. Now let's fire up a browser and take a look see…

URL: 192.168.1.1

Put in User and Password (if brand new, put in admin admin)
Under Administration - Configuration - Restore Default Configuration - Erase all data in NVRAM memory (thorough)
Had to reboot at one point, too.

Happy routing,
Drew