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

No response to 5 echo-requests

Discussion in 'Tomato Firmware' started by Xplorer4x4, Jun 24, 2012.

  1. Xplorer4x4

    Xplorer4x4 Addicted to LI Member

    Here is a complete system log of the disconnect and the reconnect. I started at this point in the log as the line previous to the first one in my pastebin was from 20 minuets earlier so I figured it was not relevant. This seems to happen a few times a day. How can I fix this?
    http://pastebin.com/ZMw20VBk
     
  2. Vitaliy69

    Vitaliy69 Serious Server Member

    Set LCP_FAILURE=0 in your pptp-config file. By the way, where is config file located? Can't find it at /etc/ppp/pptp.conf in TomatoUSB firmware. :(
     
  3. Xplorer4x4

    Xplorer4x4 Addicted to LI Member

    Can you elaborate on what exactly it is I am setting and why I am setting it to 0?
     
  4. koitsu

    koitsu Network Guru Member

    This type of issue really looks like it's something wrong with your DSL line (or equivalent) that may happen intermittently; the effect is that pppd notices the remote end isn't accessible any more (due to possibly a layer 1 issue).

    Can you describe your ISP connection set up (devices used + models of devices, etc.)? Chances are if you're using DSL, you can access the DSL bridge and get signal stats. I'm willing to bet you have a line issue that needs to be resolved by either the phone company or similar. I've dealt with this kind of crap before (back when I had ADSL + ISP that required PPPoE).
     
  5. Xplorer4x4

    Xplorer4x4 Addicted to LI Member

    koitsu, thanks for the reply. I am using an Actiontec GTR724R DSL Modem in bridged mode and a Linksys E2000 with Toastman TomatoUSB v1.28.7500 USB Ext. If you are familiar with AT&T I did have one of the silver Motorola modems that Qwest used also. The units had a super high failure rate due to over heating when they got just over a year old so I refuse to buy that or it's replacement model that sems better but still has high failure rates. My ISP is AT&T DSL. I am not entirely sure where the mainframe is but considering I pretty much squeeze every last bit of data out of my 6 Mbit line, I suspect it is close by. AT&T has a building about a mile down the road where the installers are dispatched out of, and a huge call centre is also just over a mile down the road and an AT&T store right across the street. I realize none of that confirms that I am close to the mainframe,but I have my suspicions. Anyway, this usually happens two or three times a day on average. I am pretty sure it is not a problem on the AT&T side but on my end. If it comes down to it I will call AT&T and ask for more info next time it happens to be sure, assuming there is no way to test it on my end.
     
  6. koitsu

    koitsu Network Guru Member

    Did you mean the Actiontec GT724R (not GTR724R)? If so: I've downloaded the User Manual and determined that the bridge has an administrative interface at http://192.168.0.1/. You may have to have a computer on the same subnet (probably 192.168.0.0/24, rather than 192.168.1.0/24 (default for TomatoUSB)) to access it -- it depends on the bridge/modem.

    Signal statistics are available by clicking on some menu item that's labelled "DSL Status". See page 12 (PDF page 15) of the manual for a screenshot of what it looks like. What matters the most here is SNR and attenuation. Those will be the deciding factors of line quality.

    I also strongly urge you to check out page 51 (PDF page 54), specifically "System Log". Chances are there will be something in there that indicates something bad happening as well.

    In either case, these are layer 1 (physical layer) problems, e.g. something wrong with the copper or telco network between you and wherever your connection terminates with AT&T. AT&T will first insist that your issue may be related to IW (inside wiring); the best way to determine this is to take the DSL bridge outside of your abode and over to the demarc point and hook it up there. An AT&T tech can probably help you with this. You'll need a laptop and so on too, since you'll need to view the DSL bridge's status page to determine what the levels are. Alternately, an AT&T tech can come out and pull signal levels from the demarc, as well as from your abode. Do not let the tech only test your abode; make sure he goes out and takes readings from the demarc. If the readings are horrible in your home but good at the demarc, then you have a wiring problem between the demarc and your home, or within your home. If the readings at the demarc are horrible then the problem is AT&T's (and good luck getting them to fix it). It's also very possible that you're simply too far from the CO (central office) or an RT (remote terminal) to get the speed you're set at. With DSL, higher speed = you need to be closer to the CO/RT.

    Also something I found over the years when using DSL and PPPoE -- it is always best to do the PPP encapsulation/decompression on the modem itself and not within a third-party router. I cannot tell you how many times I tried to get PPPoE to work on consumer routers (rather than let my DSL bridge do it); it would work reliably then randomly crap out, or sometimes never re-negotiate. In my case I ended up using my DSL bridge to do PPPoE + authentication, and set it up for 100% transparent pass-through, so that my router only had to do DHCP. This worked 100% of the time, barring layer 1 problems. Some bridges don't offer that; their "pass-through" mode forces you to do PPPoE on a router rather than on the bridge, which sucks. But before blaming the router, make sure your actual DSL connection is reliable/etc. (see previous paragraph).

    You might try visiting the AT&T DSLR/BBR forums (pick the proper region you're in) and post there. You can post anonymously if you want. Folks there should be able to help you with your situation too, if it turns out to be a layer 1 thing. Heck, a lot of AT&T techs hang out there, they might be able to tell you how far you are electrically from a CO/RT. :) If you're able to access your DSL bridge like I described above and get SNR and attenuation levels, if you post those on the forum people will be able to tell you if they're bad or good. It's been a while since I've done DSL so I forget what the acceptable levels are. You should also state what speed/plan you've signed up for. Heck, in general just copy-paste the contents of the "DSL Status" page. :)

    BTW: physical location / distance has absolutely zero bearing on actual electrical distance. My old flat was 6000 feet from the CO (physically), but electrically AT&T/SBC/PacBell had run copper for our side of town down a road for about a mile, then down a major street for another mile, then back down the opposite direction for about half a mile (think a big "U" shape, where my flat is at one tip of the U and the CO is at the other): electrically I was over 14,000 feet from the CO. There was also apparently an RT approximately 1200 feet from my flat (!!!), but quoting AT&T senior techs on the DSLR/BBR forums, "the RT was either full or non-operational". All that was in 2004, and is still that way today. My point is that physical distance from a CO/RT plays zero role with regards to how your signal is routed to a CO/RT; what matter is electrical loop length. This is the main reason I go with cable rather than DSL (cable generally speaking is not susceptible to this nonsense; I can get 50mbit/10mbit speeds no matter if I'm 10000 feet or 20000 feet from a CMTS head).
     

Share This Page