1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

routing issues with my tomato setup?

Discussion in 'Tomato Firmware' started by cyked, Jul 26, 2010.

  1. cyked

    cyked Networkin' Nut Member

    So I have a few issues and just now getting around to looking into it.

    My setup:

    running 2 linksys routers with tomato
    Router 1 (WRT54G): connected to att uverse gateway. The gateway passes my external IP address to this router. IP is .2.1

    Router 2 (WRT54GL): connected to Router 1 as a wireless client with 2 machines wired to it (windows XP and Ubuntu). IP is .2.2 with gateway set as .2.1.

    Computers: both machines are static IP as .2.101 and .2.102.

    Issue 1: For the longest time I can not access hometheaterlounge.com. It just times out and have not been able to figure out why.
    I can ping and tracert the site from windows and I can resolve the the IP in linux, but that's ALL I can do from either machine. Here is what happens though from the Windows tracert

    Code:
    Tracing route to hometheaterlounge.com [67.15.245.6]
    over a maximum of 30 hops:
    
      1     1 ms     1 ms     1 ms  [192.168.2.1]
      2     *        *        *     Request timed out.
      3    23 ms    22 ms    25 ms  99-185-0-2.lightspeed.frokca.sbcglobal.net [99.1
    85.0.2]
      4    24 ms    22 ms    22 ms  75.29.76.196
      5     *        *        *     Request timed out.
      6     *       23 ms    22 ms  75.29.64.76
      7    27 ms     *        *     75.29.64.14
      8    23 ms    22 ms    22 ms  151.164.38.36
      9    27 ms    26 ms    25 ms  ppp-151-164-52-207.rcsntx.swbell.net [151.164.52
    .207]
     10    27 ms    26 ms    26 ms  xe-0-2-0-5.r07.snjsca04.us.bb.gin.ntt.net [129.2
    50.9.121]
     11    26 ms    26 ms    26 ms  ae-8.r21.snjsca04.us.bb.gin.ntt.net [129.250.5.5
    6]
     12    83 ms    68 ms    69 ms  ae-5.r21.dllstx09.us.bb.gin.ntt.net [129.250.4.2
    4]
     13     *        *        *     Request timed out.
     14    68 ms    68 ms    68 ms  xe-7-3.r01.dllstx09.us.ce.gin.ntt.net [157.238.2
    24.182]
     15    72 ms    72 ms    72 ms  et1-1.ibr01.hstntx2.theplanet.com [70.87.253.50]
    
     16    72 ms    72 ms    72 ms  2-2.dsr02.hstntx2.theplanet.com [74.55.252.38]
     17    74 ms    73 ms    72 ms  po2.car12.hstntx2.theplanet.com [74.55.252.210]
    
     18     *        *        *     Request timed out.
     19     *        *        *     Request timed out.
     20     *        *        *     Request timed out.


    Issue 2: No idea how long this has really been going on. When I tracert/traceroute from the machines I get different things.

    Here is what I get from computer 1 (windows xp):
    Code:
    Tracing route to google.com [74.125.19.104]
    over a maximum of 30 hops:
    
      1     1 ms     1 ms     1 ms      [192.168.2.1]
      2     *        *        *     Request timed out.
      3   814 ms   597 ms   502 ms  99-185-0-2.lightspeed.frokca.sbcglobal.net [99.1
    85.0.2]
      4    24 ms    22 ms    24 ms  75.29.76.196
      5    27 ms    37 ms    23 ms  75.29.64.81
      6     *        *        *     Request timed out.
      7     *        *        *     Request timed out.
      8    23 ms    22 ms    22 ms  151.164.38.36
      9    26 ms    33 ms    27 ms  151.164.38.18
     10    81 ms    26 ms    29 ms  151.164.251.222
     11    71 ms    42 ms    28 ms  216.239.49.250
     12    28 ms    31 ms    39 ms  209.85.249.30
     13    34 ms    28 ms    27 ms  nuq04s01-in-f104.1e100.net [74.125.19.104]
    
    Trace complete.
    When I trace from computer 2 (ubuntu)... this happens for every site:
    Code:
     traceroute google.com
    traceroute to google.com (74.125.19.104), 30 hops max, 40 byte packets
     1  (192.168.2.1)  2.065 ms  2.968 ms  3.090 ms
     2  * * *
     3  * * *
     4  * * *
     5  * * *
     6  * * *
     7  * * *
    30 * * *
    
    nslookup from computer 2 ubuntu:
    Code:
    nslookup google.com
    Server:         192.168.2.1
    Address:        192.168.2.1#53
    
    Non-authoritative answer:
    Name:   google.com
    Address: 74.125.19.99
    Name:   google.com
    Address: 74.125.19.103
    Name:   google.com
    Address: 74.125.19.104
    Name:   google.com
    Address: 74.125.19.147
    


    I'm sure more details are needed, but will start with this. My networking knowledge is laughable, I'm sure, so any help is greatly appreciated.
     
  2. mstombs

    mstombs Network Guru Member

    What mode is Router2 in? If nat Gateway mode it will be confused with have local lan addresses to both lan and wan.
     
  3. cyked

    cyked Networkin' Nut Member

    Do you mean the wireless mode? Its a Wireless Ethernet Bridge.
     
  4. mstombs

    mstombs Network Guru Member

    Your first post says "connected to Router 1 as a wireless client", which should work even if Router 1 not tomato compatible, but yes as both tomato Router2 should be in "Wireless Ethernet Bridge" mode with all the routing/dns/dhcp done by Router1
     
  5. cyked

    cyked Networkin' Nut Member

    I should set them both as wireless ethernet bridges?
     
  6. mstombs

    mstombs Network Guru Member

  7. cyked

    cyked Networkin' Nut Member

  8. TexasFlood

    TexasFlood Network Guru Member

    Can't say why you can't get to hometheaterlounge.com. Seems like once the traceroute leaves your box, if it fails down the line that is a fault of your ISP not your router. Or perhaps the site was down? Generically speaking I should probably ask if you did a full nvram reset after first flashing tomato as not doing so can cause weird problems. As far as the ubuntu box is concerned seems like nslookup works ok, perhaps you have iptables enabled on ubuntu with some restrictive rules without realizing it?
     
  9. cyked

    cyked Networkin' Nut Member


    Yeah, nothing should be in iptables. I'm pretty much only blocking things based on brute type attacks for apache/sql stuff. Beyond that I have completely cleared every everything in IP tables and still have issues.

    Finding a lot on nvram get http_passwd. Do I need to do this before/after I do the Admin > Config > Restore Default Config > erase all data in NVRAM?

    Should I just go ahead and do this on both routers? Does this just do some kind of cache clearing, or does it also clear all settings to default?
     
  10. TexasFlood

    TexasFlood Network Guru Member

    Just to be clear are you referring to iptables on the router, ubuntu or both? I was asking about the ubuntu box but wasn't clear if that's what you meant.

    Yes, you want to do a thorough when first loading tomato or switching between major builds, as recommended in the official Tomato FAQ. You'll have to refer to the specific recommendations for other tomato based builds as to whether it's required on upgrades of the same build. I don't think it's required for upgrades the official tomato build from Jon Zarate, only the initial load. And yes, this clears all settings to default.
     
  11. cyked

    cyked Networkin' Nut Member

    I'm referring to iptables on the linux box. The only things I have really changed on the router other than the typical stuff are setting up the secondary as a bridge and some port forwarding stuff...


    The second router (54gl) went from vanilla to tomato, there was nothing else before it.
    The primary router MAY have had DDWRT on before I upgraded to tomato.
     
  12. TexasFlood

    TexasFlood Network Guru Member

    Weird, something blocking access on the ubuntu box was the only thing I could think of to explain that symptom, now I'm at a loss. I mean it's possible there could be some kind of access restriction etc on the router but seems unlikely a specific device would get blocked by accident.
    Right, so in either case a thorough erase is recommended after the initial load, per the official Tomato FAQ, not unlike other 3rd party builds such as dd-wrt. All sorts of weird things can happen if this isn't done by unexpected reactions to leftover nvram crap, I've seen it myself, on dd-wrt at least, odd inexplicable symptoms that just vanished after a good nvram clear.
     
  13. cyked

    cyked Networkin' Nut Member

    I'll report back after I've had time to do this. I'm short on free time lately.
     

Share This Page