Stable firmware for RT-N12/B1 for basic use and client (bridge) mode

Discussion in 'Tomato Firmware' started by Hogwild, Dec 11, 2012.

  1. Hogwild

    Hogwild LI Guru Member

    Hi all:

    Well, I've been so happy with my other routers running Tomato, I offered to set up an Asus RT-N12/B1 for a good friend.

    I'm leaning toward Shibby, as my friend won't need some of the features Toastman includes, and my friend being a novice, I want him to have a more "sparse" GUI Web interface.

    I read that if I use Shibby on the RT-N12/B1, that I'm supposed to use an RT-N series firmware.

    Can someone recommend a build that will yield really stable wireless? This will be used as either a client or client bridge. I'm hoping to get range of at least 200 and possibly as much as 1000 feet. This will be in a rural setting.

    Thanks in advance for any guidance.
  2. Monk E. Boy

    Monk E. Boy Network Guru Member

    Yes, the RT-N12/B1 requires an RT-N build. RT-N has new wireless drivers required by newer routers, basically.

    I've had one up and running with a Toastman non-USB build for a couple months now. When I first set it up I looked at Shibby, but stayed with Toastman for familiarity's sake, since I'm running it everywhere else and its been quite stable.
  3. Hogwild

    Hogwild LI Guru Member

    Monk E. Boy:

    Thanks for that info. I will consider it if I can't find a suitable Shibby build. Certainly it's obvious that Toastman's work speaks for itself, but in this case, I need a sparse interface for someone with next to no tech knowledge.

  4. gfunkdave

    gfunkdave LI Guru Member

    Shibby doesn't have a "sparse interface"...all Tomato builds I've seen have essentially the same interface.

    Might be better, if you want to go Tomato for your friend, for you to set up the router and have him plug it in. When you set it up, include a ssh key so you can remote in to it.
  5. Monk E. Boy

    Monk E. Boy Network Guru Member

    Just a thought, rather than bridge mode, you may want to consider using WDS and expanding the network that way. Bridge mode, unless you're talking about a single client attached to the 2nd router via ethernet (which is usually called client mode), is quite an odd hack.

    In terms of making the distance, with directional antennas, assuming there's a reasonable unobstructed line of sight between the two points, WiFi can bridge gaps measured in miles. Omnidirectional antennas have much shorter range, but allow clients to connect to the router (with directional antennas the only way clients can connect is if they were physically moved to a point between the two routers).

    Agreed that Shibby's interface is basically the same as Toastmans. Maybe you're thinking of that simplified Tomato build that's based off Toastman's build...
  6. gfunkdave

    gfunkdave LI Guru Member

    How so?

    Bridge mode lets you connect multiple ethernet devices to the router that pull their connection over wifi.
    Client mode does the same thing, but adds NAT on the router. The wifi behaves like the WAN interface, in other words.
  7. Monk E. Boy

    Monk E. Boy Network Guru Member

    The bridge mode I'm familiar with bridges a single device onto a WiFi network. When you bridge two networks, in this case ethernet and WiFi, there's really only one network and MACs are shared between the different media. The problem with WiFi is that only a single MAC address can be active on any one radio at any given time. Bridging multiple (ethernet) devices onto WiFi in this manner is a nightmare, as the radio has a MAC address for itself as well as all the other MAC addresses of attached systems. Client mode, as you describe it, would work since only one MAC address would be receiving & transmitting. But it sounds like what you guys are talking about when you say bridging is something completely different, and not bridging in the traditional sense.
  8. Hogwild

    Hogwild LI Guru Member

    Thanks for that info. With 2 "advertised" 5dbi antennas on the RT-N12/B1, I'm hoping I can make the connection to the router in the neighbouring house (~200 feet) . They've agreed to share with my buddy since he is both unemployed and in very poor health.

    Oh, I didn't know that. You're right, I'm using TomatoUSB and stock tomato on my two current routers. Thanks for the tip.

    Yes, I am in fact talking about a single client attached to the 2nd router via Ethernet. Thanks for that.

  9. Monk E. Boy

    Monk E. Boy Network Guru Member

    EasyTomato! That's the build I couldn't remember for the life of me yesterday.
  10. gfunkdave

    gfunkdave LI Guru Member

    You could be right; I've actually never tried it. I was just saying what I thought I understood the case to be from reading stuff I've Googled. Most articles seem to mention multiple clients attached to the LAN ports in bridge mode.
  11. Hogwild

    Hogwild LI Guru Member

    so, ANYONE, can anyone at all suggest a build for the RT-N12/B ? Are most of the builds stable enough that they will be okay? I'd really prefer to use a build someone has at least tried.

    Oh, and if I decide to go with a Toastman build, would someone please be kind enough to explain what this means for those of us without programming knowledge? Does this mean there is a problem with using a Toastman RT-N build or was that just the case back in Feb. of this year?

  12. Toastman

    Toastman Super Moderator Staff Member Member

    hogwild, support was reinstated for these models long ago on the RT-N branch
  13. mvsgeek

    mvsgeek LI Guru Member

    @hogwild - I'm testing tomato-K26-1.28.0500.5MIPSR2Toastman-RT-N-Std on a RT-N12/B1 in a WDS environment, not client bridge. It's been in place for about 4 days, and I've seen more frequent WDS disconnects than with the WRT310N slave running Toastman 1.28-7633 (same router location, TX power settings etc.). Just for grins I tried flashing it with 7483.2, which is acknowledged to be the most stable WDS build - it flashed OK, but I couldn't access the router afterwards, so I re-flashed 0500.5. Looks like an RT-N build is mandatory for this router.

    @toastman - which of the RT-N builds is the closest equivalent to RT 7483.2?
  14. Hogwild

    Hogwild LI Guru Member


    Good to know, thanks. So, can anyone suggest a fairly stable build for that model? I don't even know where to start, and couldn't find much that is relevant in the forums
    here using the search function.

  15. Hogwild

    Hogwild LI Guru Member

    Okay, for anyone following, I ended up just putting on the latest stable mini build for RT-N that was current as of this thread.

    I only tested it for about a day and a half, but so far, experienced no problems at all with testing as a Wireless Client. The connection sat stable, transferring files
    for 6 1/2 hours with not a hiccup. That doesn't guarantee anything, but it's a good start. The only problem I experienced so far, was that the WiFi Signal Quality
    number was different on the Status-->Overview page (Wireless section) than it was on the Tools-->Site Survey page. The difference was sometimes 2 or even
    3 units apart. I couldn't find anything in the changelog about this. Is this a known issue, or a fluke or ??

    Any input would be appreciated.
  16. neftv

    neftv Networkin' Nut Member

    I have this same router and it seems like there is very little help with tomato firmware on this router. For my purposes and I watch tv streaming from internet on 3 devices on my Lan. I was not happy with the performance of the present shibby version for this router. I decided to use the SVN version 20119 mini of DD-WRT firmware and its working so much better.
    Don't know why IPTV works better with DDWrt on the RTN12b1 but it does. Look forward to comments.

    Sent from my RM-820_nam_att_100 using Board Express
  17. Hogwild

    Hogwild LI Guru Member


    Thanks for that. Can you give me an idea what kind of performance issues we're talking about that you've experienced? What
    kind of differences did you see?

  18. Monk E. Boy

    Monk E. Boy Network Guru Member

    I would guess he was having performance issues because multicast support is disabled by default in most Tomato firmwares.
  19. neftv

    neftv Networkin' Nut Member

    Hogwild.. It seemed when I had all three feeds going but not always that my one device would tend to buffer alot. I don't think its the multicast issue because most ISPs don't transport multicast from outside their own network. I know my ISP Verizon Fios don't and I think that is lame but that is another story. I'm on day 3 with dd-wrt and working well. I not tried Toastman version yet and my thinking is that Toastman firmware focus on router things more that all the extras that the shibby version offers. Just that the variety of firmware is not as much as it is for other routers in the same RT-N branch.

    Sent from my RM-820_nam_att_100 using Board Express
  20. neftv

    neftv Networkin' Nut Member

    I decided to try Tomato Firmware v1.28.0501 MIPSR2Toastman-RT-N K26 VLAN-VPN on my RT-N12b1 and will report how it goes in three days. Giving the same amount of time as I did with ddwrt. Interestingly this Toastman version has CPU clock adjustment but I not brave enough to try that at this time.

    Sent from my RM-820_nam_att_100 using Board Express
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice