framemainer
Premium
join:2004-12-11
Atlanta, GA
| reply to framemainer
Re: [Tomato] WRT54-GL LCP appears to be disconnected - VOIP with
Not sure that it much matters, but in the unlikely event anybody else has such symptoms...
Our Motorola Netopia 2210 modem finally failed entirely about 10 days after I first posted (changed filters and telephone cords/outlets to no avail; tech brought replacement modem which worked immediately). My problem was due to its failing intermittently - causing Tomato to issue the message - LCP appears to be disconnected.
The tech said that he replaces one of this model/serial-number-range of the 2210 almost every day. |
|
framemainer
Premium
join:2004-12-11
Atlanta, GA | reply to framemainer
A new telephone adapter is on its way after VOIP calls failed quickly today.
Now wondering about the "LCP appears to be disconnected" - could that be related to a failing device that is attached to the WRT54-GL? |
|
framemainer
Premium
join:2004-12-11
Atlanta, GA
| reply to framemainer
I may have found why the TA failed on the Comcast connection:
three messsages in router log like
[DOS attack: STORM] attack packets in last 20 sec from ip [192.168.1.5], Thursday, Apr 16,2009 14:39:24
(Comcast connection uses Netgear router.) |
|
framemainer
Premium
join:2004-12-11
Atlanta, GA
| [Tomato] WRT54-GL LCP appears to be disconnected - VOIP with Int
I'll start with a question - is there a way to increase the 5-second-pending value after disconnect is first detected? I am thinking that the Tomato keep-alive just needs a little more time.
I've been running Tomato (now on v1.23) since November 2008 on WRT54-GL. I have Netopia 2210 modem with BellSouth DSL-extreme and AT&T CallVantage D-Link DVG 5102-S Telephone Adapter (TA) two-line plan behind router. Tomato eliminated the frequent power-cycles required to keep the TA working.
No wireless.
I hardly ran anything but the TA (I was using Comcast for Internet).
Last week, I moved our Ethernet cables to the WRT54-GL - thinking if it works, I would cancel the Comcast service. However, I started getting "Daemon.warn pppoe[nnnn]: LCP appears to be disconnected (pending:5)" (had a month of continuous service until then). Yesterday, I changed the Keep Alive check interval from 30 to 14400 - had even more disconnects (9). I should mention that I often run two VPN clients simultaneously - although my bandwidth requirements are usually fairly low, I can see that the VPNs and AT&T-CV could be a toxic mix.
A Line Tech came and found no problems two days ago.
Then again, two horribly weird things happened yesterday. First, I had audible hiss on the land line that runs the DSL - called in a problem, but did not get a return call. Second, I moved the TA behind the Comcast router, made a call, and was disconnected, just like I'd been with the TA on DSL. So, a total home office melt-down yesterday. I could see the TA maybe being bad, but it's a strange coincidence that I started having problems after moving Internet access.
Today, the check-interval is back to 30 seconds, and my Internet is back on Comcast. |
|
