Having Trouble Configuring TomatoUSB as a wireless access point.

Discussion in 'Tomato Firmware' started by fefrie, Jul 12, 2017.

  1. fefrie

    fefrie Networkin' Nut Member

    I'm a Toastman tomato guy.

    Simply the best. Pretty straightforward, configurable.

    Recently got a Netgear router, that didn't have an official build, just a beta build. It's TomatoUSB I think.


    I want to configure it as a wireless access point.

    I've done this many times with Toastman, but with T-USB, it seems to be a bit more complex than I'm used to. There are a couple of settings I don't recognize.

    I want to have a N-network 2.4ghz only and assign an IP address to the router of

    I can't seem to get it to work.

    I'm assuming that all the settings are made from the Basic-wireless page?

    Where do I plug in the router IP address I want to assign to it?
    I've done it where it says bridge. but should be be default gateway?

    I'm so confused.

    When I try to set it into 2.4ghz mode, I get locked out or it refuses to accept the changes.

    [OneEightSeven] Basic_ Network.jpg
    Last edited: Jul 12, 2017
  2. Sean B.

    Sean B. LI Guru Member

    It looks that by wireless access point you're referring to using the Wireless Client Mode according to your screen shot. What is the configuration for the router your connecting it to? IE: IP address of the LAN interface, subnet mask, DHCP range and any custom VLAN'ing, and radio channel+encryption settings. What specific model of Netgear router is it? Some routers are not hardware capable of client modes.
  3. fefrie

    fefrie Networkin' Nut Member

    That wireless client thing was a mistake. I changed it to access point, but the problems still remain. Here's the router that it's conecting to that has all the DHCP assigning functions.

    With all other router, stock firmware or tomato or otherwise, I've had absolutely no problems. Only with this TOMATO USB version.


    Here's another router as an access point configured completely fine to the main router aa.JPG
  4. Sean B.

    Sean B. LI Guru Member

    I'm confused. How exactly are you wanting to link this router to your "main" router? Because access point simply broadcasts an SSID for clients to connect to.. it does not link the router to another.
  5. fefrie

    fefrie Networkin' Nut Member

    Router(DHCP, <ethernet> Router(configured as a wireless access point,

    That's it. Pretty simple.

    I'm hating TomatoUSB right now. I'm about ready to flash back to the original firmware right about now.
  6. Sean B.

    Sean B. LI Guru Member

    Ah, the wireless client mode in the SS caused me to assume the link to main router was not via cable. To confirm, this screenshot is of the router your trying to configure as the access point, correct?

  7. fefrie

    fefrie Networkin' Nut Member

    All router to router connections are connected via ethernet cable into LAN ports.

    Beige SS is the main toastman router that does all the "tomato" functions, that is DHCP, QOS, all that stuff. It's connected to Blue SS via ethernet which is also another Toastman firmware, running strictly as a wireless access point, and a ethernet access point for some local devices. Works perfect, fine

    Connecting 'black' SS which is TomatoUSB firmware via ethernet. Nightmare. Nothing works
  8. Sean B.

    Sean B. LI Guru Member

    If so:

    Set default gateway to

    Static dns: ( if you use hostnames that are set in the DNS service of your main router )

    Access point router LAN port ( not WAN ) <--cable--> main router LAN port
  9. Sean B.

    Sean B. LI Guru Member

    It also appears the version of TomatoUSB you're using is running multiwan. Could you post a SS of the Advanced->VLAN page please?
  10. fefrie

    fefrie Networkin' Nut Member

    Well with your suggestions, it's at least 'on network' right now.

    Getting wireless working is another matter.

  11. Sean B.

    Sean B. LI Guru Member

    What is the issue with wireless?
  12. Sean B.

    Sean B. LI Guru Member

    Odd VLAN port config. Is anything currently connected to Port 4 of the access point router? Order may be reversed.. possibly Port 1 going by labeling on router.
  13. fefrie

    fefrie Networkin' Nut Member

    Well after 2 days of teching, I'm going to just get rid of the router.

    Bricked it, then TFTP'd into it to restore the tomato FW, wireless, just bad, then TFTP'd the original FW. Seemed to be working, then this morning, nothing.

    Not worth the effort. Time to let it go.
  14. Monk E. Boy

    Monk E. Boy Network Guru Member

    Only thing I noticed is you had WAN set to DHCP, for an access point you should disable the WAN. This then lets you do two things, make the WAN a LAN port (useful for linking the two together - in case the firmware resets to defaults you don't end up with two DHCP servers on your LAN), then it enables you to set a default gateway. I don't use Netgear routers though so I can't speak to specific issues with the WNDR3400...
  15. darksky

    darksky Addicted to LI Member

    Does this help?
  16. fefrie

    fefrie Networkin' Nut Member

    Not really.

    I know how to set up a network using routers as wireless access points.

    Apparently I'm just using crummy hardware. It could be brand new, or it could be used, but something I am doing is just killing routers when it comes to attaining N-spec performance.

    I have a 30mbps line, 2 access points, and a router. I have 7 people on my network. No one torrents, some people stream, I do do big transfers from one computer to another. That's about the heaviest of work that gets done from the router.

    I've killed 4 routers from brand new. 3 linksys. My most recent was an RT-N16. The N antenna died long ago, and it was running as a G antenna untill I returned it for warranty reasons.

    Since this latest debacle, I got a used N router. Worked for a day untill that one went spotty after a day.

    I just can't have that. I need access points that at the very least, have zero issues with connecting to clients.

    At this point, I've given up. I'm down to 2 devices. Both wrt54gl. Both give people the password, and there are no problems with connecting, both overclocked to 250mhz. Asides from the slow LAN transfers, they work fine. I'm thinking of getting a third wrt54gl and calling it a day.

    Maybe I'll flash this d link router to tomato. I just need a bit of a break for now.

    But I'll be on the lookout for a cheap enterprise WAP.
  17. Sean B.

    Sean B. LI Guru Member

    Are ambient temps where your located rather high? Are the routers kept in locations that are enclosed or have little ventilation? It's certainly odd to kill that many routers so easily. Would stand to reason there may be some common factor shortening their lifespan. How's the quality of mains power there? Maybe excessive fluctuation.. or possibly another electronic device backfeeding ripple onto the grid. Wouldn't have to be on your premises either, a crappy refrigerator on it's last leg that a neighbor has or a amateur ham radio enthusiast that built a horrible RF amplifier he saw on youtube can dump plenty of spikes onto the grid. Even tho the wall warts these routers use employ isolation transformers, they have barely enough filtering to handle the ripple from their own transistor switching.. let alone handle the dirty D/C that results from dirty A/C rectification. The RF circuitry of the routers, mainly the power amps, can be sensitive to unclean power. Just some ideas, sense you'd have to be a very unlucky person to have those all just die from a rather average use case.
  18. fefrie

    fefrie Networkin' Nut Member

    All open cool places.

    Maybe I have dirty power, who knows.

    I'm slowly probably just going to stick with wrt54gl routers and WAPs and ethernet the two computers that do Heavy duty transfers. I just hate the extra cables on my laptop.
  19. Monk E. Boy

    Monk E. Boy Network Guru Member

    I've seen RT-N12D1 access points run in cramped enclosed spaces for months w/o issues.

    Used hardware is really a crapshoot, you never know how the previous owner(s) abused them. Even refurbished hardware can be bad, depending on who did the refurbishing.

    Only issues I've seen with the N12s are limited CPU causing a fairly low WAN-to-LAN ceiling, and they're 2.4-only so you end up with interference issues, though w/o interference they will transfer 50MB/s in access point mode. Note that the original N12 should probably be avoided, mine never survived more than a month before freezing solid, but the B1 and D1 seem pretty robust.
  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