dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
5385
share rss forum feed

shalom68

join:2002-01-30
Passaic, NJ

1 edit

[modem/router] PPPoE keeps dropping, but DSL stays lit

OK, here's a long story.

I have DSL, have had it since the old Infospeed days (had ISDN before that). Been at this address for about 6 years now. Provisioned for 3360/832. I had all sorts of problems related to line noise when I first moved in, there being about 4 generations of rats nest old TELCO wires in the basement, but they ran a new line straight to the NID and that cured it. No noise on the voice line.

Fast forward 5 years. My (t)rusty old 327W finally died last month; it went into a constant reboot cycle. VZ said they'd send me a new 7500. Meantime I hauled out the ancient B90-36R515 with the old blue Bell Atlantic logo on it, hooked up to a DI604, and voila I was back on line, but no wireless obviously.

So I received the new 7500. Ever since I installed this, the damn thing kept disconnecting at random intervals. Relevant sample log entries attached at the end. What basically is happening is that the PPPoE session dies "No response to 6 echo-requests", and it refuses to reconnect until I physically yank the DSL line and plug it back in. Otherwise it sits there for hours contemplating its navel and trying to reconnect every so often but not succeeding. Even if I go to the DSL Connection page and press Connect, it goes to "connecting", then back to "connect" again. Note that the DSL connection is still there, just the PPPoE session ends and won't restart.

I hooked up the B90 to the E4/Data port on the 7500 and disabled the internal modem, and the problem went away. I'd leave it like that, but the problem is that both the 7500 and the B90 takes up 2 sockets each on the power strip (fat wallwarts blocking the plugs to both sides) and I need those sockets. Plus, I'd like the damn thing to work as advertised, just on principle.

They did line tests, find out nothing is wrong. Yeah right. Finally did a second test, tells me it's the modem, they're sending me another. Installed that one. Worked about a week, then it started doing the exact same thing. I doubt it's the line if the older modem still works fine.

Before I call them and tell them their new modem is as bad as the old one, can anyone here recommend a fix? Maybe there's some setting in the Advanced area (I don't know what 3/4 of that stuff does so I just left it the hell alone) that can be tweaked to prevent this problem.

Transceiver stats at the moment:

Transceiver Revision A2pB020b3.d20h
Vendor ID Code 4D54
Line Mode ADSL_G.dmt
Data Path INTERLEAVED

Transceiver Information Down Up
DSL Speed (Kbits/Sec) 3360 832
Margin (dB) 18.1 10.0
Line Attenuation (dB) 42.0 27.0
Transmit Power (dBm) 19.1 11.9


This doesn't seem so terrible to me; it was much worse before they changed the wiring.

(Edit to add: Beautiful weather this week, so it's not related to rain. I also noticed that in the past two months the following users seems to have had the same problem:
»Verizon tech couldn't pinpoint issue?
»[connectivity] DSL was bad, new modem has new problems
»Gateway goes down once every day or two.
»Westell 7500 drops connection
and possibly »[connectivity] keep losing my internet connection...please help
)

Log entry for when it crashes:

Source IP,Generated,Received,Source Name,Facility,Severity,Tag,Origin,Message
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Info,pppd[3435],,"No response to 6 echo-requests"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Notice,pppd[3435],,"Serial link appears to be disconnected."
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Notice,pppd[3435],,"Westell phase_hook PHASE=PHASE_TERMINATE(9)"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 ifname:ppp0 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Notice,pppd[3435],,"Westell ip_down()"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 ifname:ppp0 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 connect_time:950 bytes_sent:279827 bytes_rcvd:2179659 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Notice,pppd[3435],,"Westell phase_hook PHASE=PHASE_NETWORK(7)"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 ifname:ppp0 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 connect_time:950 bytes_sent:279827 bytes_rcvd:2179659 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Notice,pppd[3435],,"Westell phase_hook PHASE=PHASE_ESTABLISH(4)"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 ifname:ppp0 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 connect_time:950 bytes_sent:279827 bytes_rcvd:2179659 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Notice,ip-down[5326],,"ppp0: disconnected; connected for 950 seconds"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Notice,ip-down[5326],,"ppp0: 279827 bytes sent, 2179659 bytes received"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Warning,pppd[3435],,"Couldn't increase MTU to 1500"
192.168.1.1,09/08/10 13:30:04,09/08/10 13:30:04,dslrouter,system,Warning,pppd[3435],,"Couldn't increase MRU to 1500"
192.168.1.1,09/08/10 13:30:09,09/08/10 13:30:09,dslrouter,system,Notice,net_mgr[360],,"QoS on ppp0 transitioning to Down state."
192.168.1.1,09/08/10 13:30:09,09/08/10 13:30:09,dslrouter,system,Notice,net_mgr[360],,"Routes transitioning to Down state on ppp0."
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Info,pppd[3435],,"Connect time 15.9 minutes."
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Info,pppd[3435],,"Sent 279827 bytes, received 2179659 bytes."
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Error,pppd[3435],,"Unlinking PPPoE session file: /WFIO/ppp-config0"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Error,cwmpd[371],,"ddnsWanIPCallback : WAN State Down"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Notice,pppd[3435],,"Westell phase_hook PHASE=PHASE_DEAD(0)"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Notice,pppd[3435],,"PPPD Exit Status changed EXIT_OK->EXIT_PEER_DEAD during phase PHASE_ESTABLISH->PHASE_DEAD"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 ifname:ppp0 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 connect_time:950 bytes_sent:279827 bytes_rcvd:2179659 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Notice,pppd[3435],,"Connection terminated."
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Notice,pppd[3435],,"Westell phase_hook PHASE=PHASE_DISCONNECT(10)"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 connect_time:950 bytes_sent:279827 bytes_rcvd:2179659 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Notice,pppd[3435],,"Westell Random Holdoff returning 43 seconds"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Notice,pppd[3435],,"Westell phase_hook PHASE=PHASE_HOLDOFF(11)"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 connect_time:950 bytes_sent:279827 bytes_rcvd:2179659 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Warning,pppd[3435],,"pppd[3435] EXIT_PEER_DEAD caused InternetFail light to be lit"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Warning,pppd[3435],,"Enter destroy_pppoesessionfile"
192.168.1.1,09/08/10 13:30:10,09/08/10 13:30:10,dslrouter,system,Warning,pppd[3435],,"Leaving destroy_pppoesessionfile"
192.168.1.1,09/08/10 13:30:53,09/08/10 13:30:53,dslrouter,system,Notice,pppd[3435],,"Westell phase_hook PHASE=PHASE_DORMANT(3)"
192.168.1.1,09/08/10 13:30:53,09/08/10 13:30:53,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 connect_time:950 bytes_sent:279827 bytes_rcvd:2179659 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:30:53,09/08/10 13:30:53,dslrouter,system,Notice,pppd[3435],,"Wan link is up and PPPoE Terminator on DSL:nas1 is done working"
192.168.1.1,09/08/10 13:30:53,09/08/10 13:30:53,dslrouter,system,Notice,pppd[3435],,"Westell phase_hook PHASE=PHASE_SERIALCONN(2)"
192.168.1.1,09/08/10 13:30:53,09/08/10 13:30:53,dslrouter,system,Notice,pppd[3435],,"PPPD Exit Status changed EXIT_PEER_DEAD->EXIT_OK during phase PHASE_DORMANT->PHASE_SERIALCONN"
192.168.1.1,09/08/10 13:30:53,09/08/10 13:30:53,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 connect_time:950 bytes_sent:279827 bytes_rcvd:2179659 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:30:58,09/08/10 13:30:58,dslrouter,system,Warning,pppd[3435],,"waitForPADO: timed out"
192.168.1.1,09/08/10 13:31:03,09/08/10 13:31:03,dslrouter,system,Warning,pppd[3435],,"waitForPADO: timed out"
192.168.1.1,09/08/10 13:31:13,09/08/10 13:31:13,dslrouter,system,Error,pppd[3435],,"Unable to complete PPPoE Discovery"
192.168.1.1,09/08/10 13:31:13,09/08/10 13:31:13,dslrouter,system,Error,pppd[3435],,"Unlinking PPPoE session file: /WFIO/ppp-config0"
192.168.1.1,09/08/10 13:31:13,09/08/10 13:31:13,dslrouter,system,Notice,pppd[3435],,"Westell Random Holdoff returning 76 seconds"
192.168.1.1,09/08/10 13:31:13,09/08/10 13:31:13,dslrouter,system,Notice,pppd[3435],,"Westell phase_hook PHASE=PHASE_HOLDOFF(11)"
192.168.1.1,09/08/10 13:31:13,09/08/10 13:31:13,dslrouter,system,Notice,pppd[3435],,"PPPD Exit Status changed EXIT_OK->EXIT_PPPOE_TIMEOUT_PADO during phase PHASE_SERIALCONN->PHASE_HOLDOFF"
192.168.1.1,09/08/10 13:31:13,09/08/10 13:31:13,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 connect_time:950 bytes_sent:279827 bytes_rcvd:2179659 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:31:13,09/08/10 13:31:13,dslrouter,system,Warning,pppd[3435],,"waitForPADO: timed out"
192.168.1.1,09/08/10 13:31:13,09/08/10 13:31:13,dslrouter,system,Warning,pppd[3435],,"Timeout waiting for PADO packets"
192.168.1.1,09/08/10 13:31:13,09/08/10 13:31:13,dslrouter,system,Warning,pppd[3435],,"Enter destroy_pppoesessionfile"
192.168.1.1,09/08/10 13:31:13,09/08/10 13:31:13,dslrouter,system,Warning,pppd[3435],,"Leaving destroy_pppoesessionfile"
192.168.1.1,09/08/10 13:31:13,09/08/10 13:31:13,dslrouter,system,Warning,pppd[3435],,"pppd[3435] EXIT_PPPOE_TIMEOUT_PADO caused InternetFail light to be lit"
192.168.1.1,09/08/10 13:32:29,09/08/10 13:32:29,dslrouter,system,Notice,pppd[3435],,"Westell phase_hook PHASE=PHASE_DORMANT(3)"
192.168.1.1,09/08/10 13:32:29,09/08/10 13:32:29,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 connect_time:950 bytes_sent:279827 bytes_rcvd:2179659 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:32:29,09/08/10 13:32:29,dslrouter,system,Notice,pppd[3435],,"Wan link is up and PPPoE Terminator on DSL:nas1 is done working"
192.168.1.1,09/08/10 13:32:29,09/08/10 13:32:29,dslrouter,system,Notice,pppd[3435],,"Westell phase_hook PHASE=PHASE_SERIALCONN(2)"
192.168.1.1,09/08/10 13:32:29,09/08/10 13:32:29,dslrouter,system,Notice,pppd[3435],,"PPPD Exit Status changed EXIT_PPPOE_TIMEOUT_PADO->EXIT_OK during phase PHASE_DORMANT->PHASE_SERIALCONN"
192.168.1.1,09/08/10 13:32:29,09/08/10 13:32:29,dslrouter,system,Notice,pppd[3435],,"Westell PPP Environment: device:nas1 linkname:config0 iplocal:108.5.33.231 ipremote:10.5.132.1 ppplogname:root orig_uid:0 connect_time:950 bytes_sent:279827 bytes_rcvd:2179659 usepeerdns:1 dns1:71.250.0.12 dns2:68.237.161.12"
192.168.1.1,09/08/10 13:32:34,09/08/10 13:32:34,dslrouter,system,Warning,pppd[3435],,"waitForPADO: timed out"
192.168.1.1,09/08/10 13:32:39,09/08/10 13:32:39,dslrouter,system,Warning,pppd[3435],,"waitForPADO: timed out"
192.168.1.1,09/08/10 13:32:49,09/08/10 13:32:49,dslrouter,system,Error,pppd[3435],,"Unable to complete PPPoE Discovery"


lather, rinse, repeat, until I disconnect the DSL line and reconnect it.

Help?


LairdDrambeg

join:2002-08-30
Denville, NJ

1 recommendation

I don't have a solution but I'm in NW NJ, Green Twp off a RT to Hackettstown CO, and have seen similar PPPOe failure behavior, though a power cycle of the modem has generally helped to establish a PPPoE session, sometimes after a couple of failed attempts with PADO timeout messages in the log.

I've had Verzon DSL for 4 months now and did not see this issue until about 2 months into service when I also saw my address block had changed from 73.n.n.n to 108.n.n.n and I also had download speed issues which are due to being routed through the Juniper ERX routers. I don't know if those are all associated - the only conclusion I have so far is that the Verizon network is just flaky and poorly maintained. About 10 days ago they had DNS servers which failed two or three times in one day. Uhh, it's the telephone company[shrug].



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24
Reviews:
·Verizon Online DSL
·Frontier Communi..

1 edit

1 recommendation

reply to shalom68

Interesting you post about this. Normally the issue is with Verizon's RADIUS servers, but the logs are showing what appears to be a brief moment of connectivity and then a spontaneous drop. I would not be surprised if this is a firmware bug you're hitting, as I've seen myself some small issues with a 7500 in my area with the DSL light turning off when clearing the logs but Internet connectivity remaining, or the modem needing to be forced to connect after a reboot. Are you aware of the modem being rebooted, particularly around the middle of the night the day you noticed this problem occurring? I know Verizon doesn't ship the modems out with the latest firmware already installed.

Otherwise, in regards to your actual line, the upstream isn't synced correctly. Proper upstream sync is 864kbps. See if you can correct that.


shalom68

join:2002-01-30
Passaic, NJ

said by Smith6612:

Interesting you post about this. Normally the issue is with Verizon's RADIUS servers, but the logs are showing what appears to be a brief moment of connectivity and then a spontaneous drop. I would not be surprised if this is a firmware bug you're hitting, as I've seen myself some small issues with a 7500 in my area with the DSL light turning off when clearing the logs but Internet connectivity remaining, or the modem needing to be forced to connect after a reboot.
The DSL light isn't turning off; the Internet light is turning off, and the DSL light is staying on. Note that the log message says it "caused Internet Fail light to be lit"; I guess this means the opposite, that the Internet Non-Fail light went out...

Are you aware of the modem being rebooted, particularly around the middle of the night the day you noticed this problem occurring?
Modem does not reboot spontaneously. It would have been logged, anyway, and I didn't see it in there. (I'm running Syslog Watcher, so as long as the computer itself is up, the logs get saved to disk even if the modem reboots, which normally erases the logs.) It doesn't always happen at the same times; in fact, sometimes it dies right in the middle of when I'm trying to do something, and the first thing I notice is the proxomitron complaining about not being able to access a page. At these times it hasn't rebooted.

I know Verizon doesn't ship the modems out with the latest firmware already installed.
Version reported is VER:5.01.00.02. Pretty sure that's the latest one. Should I be using a different version?

Otherwise, in regards to your actual line, the upstream isn't synced correctly. Proper upstream sync is 864kbps. See if you can correct that.
Right now sync is 3360/800. How do I go about fixing that? Can it be done from my end, or do I have to call VZ?

LairdDrambeg

join:2002-08-30
Denville, NJ

1 edit

1 recommendation

Just to be clear here, there is no brief connection and then a drop. Your modem is just not finding a PPPoE Server to complete its connection to the Verizon network. The evidence is the PADO (PPPoE Active Discovery Offer) timeouts and the initial echo-requests failure.

By default the modem is set to do up to 6 echo requests to the PPPoE Server periodically and if they fail, it has to kill its current PPPoE connection and retry a search for a PPPoE Server. It sends out up to 3 PADI (Initiate) broadcasts and expects a PADO reply from at least one PPPoE Server; it then would send a PADR (Request) and expect a PADS (Session) reply which establishes the connection.

I'm seeing PADO timeouts here when there is a loss of connection, for whatever reason and, in fact, I'm seeing "Hold-Offs" of 8 minutes or so, vs. the 43 and 76secs you're getting, before it is allowed to do its retry and usually succeed. There is something wrong with the Verizon PPPoE Servers and has been for a couple of weeks now - possibly they are just over-subscribed but I wish they'd fix it.

I'd suggest you post over in the Verizon Direct Forum to see if you can get an answer there but if they're just over-subscribed there may be nothing they can do. I'd do so myself but I'm not currently experiencing total failure.


shalom68

join:2002-01-30
Passaic, NJ

As an experiment, I went into the PPPoE config page at »192.168.1.1/htmlV/net_edit_vc.as···howVcs=1 and cleared the checkbox for LCP Echo. The thinking behind this was that if the only problem was that whatever machine on VZN's end whose job it was to respond to these echo requests just had its head up its butt and wasn't responding for some reason, then disabling this check would prevent the connection from being forced down. No such luck, though; now all that happens is that the connection dies silently. The PPPoE session stays up, because it's not being killed, but there's nothing there. Can't resolve anything because can't get to DNS server, and if you traceroute by IP it times out on step 2 (normally is 10.5.*.*).

Still don't understand why the 10-year-old Wirespeed modem doesn't do this, though, if the problem is at the other end.

I'm gonna post this in the DSL direct group and see what they say.


shalom68

join:2002-01-30
Passaic, NJ

1 recommendation

Case anyone was wondering, the cabling guys took out some bridge taps and it's working now.