PPPOE Failure on Verizon DSL
JP Glutting
I have been running pppoe over a Verizon DSL service for about a year
and a half, and it suddenly has failed. I first noticed this a few days
ago, and assumed the the connection hd timed-out (which it used to to,
until I started to run Kmil, which makes periodic pop requests over the
ethenet connection). Kmail was not running, and since I had never
figured out to get pppoe running without rebooting, I decided to try to
figure it out once and for all. The normal boot gets pptpd and
ppp_on_boot (redirected to a dsl script) running. I restarted all these,
but no luck.
Since then, I have not pppoe onnection when using the linux box. It is
not a hardware issue, bucause we have a PowerBook running on this line,
and the Debian box is dual boot to Win2K, which connects without any
problems (so the NIC is working).
I have looked at all the configuration files, and none of them were
modified recently, so I didn't accidently mess something up while poking
around.
Does anyone know if Verizon (in Boston here) has made any modifications
to their connection protocols recently?
Has the recent upgrade of tcpdump affected pppoe in any way? I could not
find it installed on the Debian box at home, but I remember it being
upgraded recently (probably here at work).
Thanks for any help,
JP
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sam Williams
<j...@research.dfci.harvard.edu> wrote:
> Hi,
>
<snip>
>
> I have looked at all the configuration files, and none of them were
> modified recently, so I didn't accidently mess something up while poking
> around.
If you type the command "plog" you should see all the recent entries in
the system log made by pppd. These should indicate why the connection is
not working.
You haven't recompiled your kernel / made any changes with modutils
recently have you? Last time I had problems with dsl it was after a kernel
upgrade where I missed out one of the required modules.
Sam.
ntr...@bellatlantic.net
JP Glutting <j...@research.dfci.harvard.edu> wrote:
> ethenet connection). Kmail was not running, and since I had never
> figured out to get pppoe running without rebooting, I decided to try to
> figure it out once and for all. The normal boot gets pptpd and
> ppp_on_boot (redirected to a dsl script) running. I restarted all these,
> but no luck.
It isn't necessary to reboot to start pppoe. "pon provider" or "pon dsl-provider" brings up the default pppoe connection. "poff provider" or "poff dsl-provider" will disconnect.
The file /etc/ppp/ppp_on_boot simply makes this happen when you start your computer.
"provider" and "dsl-provider" are found in /etc/ppp/peers/.
Dunno what's happening in Boston.
Kevin
Scott McCallum
at some point yesterday (03/13/03), but works in windows. I keep getting
"No response to PAP authenticate-requests". I've tried everything I can
find from google for that error but to no avail. I ran a bunch of debug
messages and everything looks fine right up until I send a PAP req over
and over and never get a response. If I run pppoe -A I get the concentrator
to show up, but that's it.
Any help at all, any grasped straws, any remotely relevant suggestions,
anyone at all? please?
...scott
JP Glutting <j...@research.dfci.harvard.edu> wrote in message news:<20030312145010$1c...@gated-at.bofh.it>...
Devin Bayer
> I'm on the south shore and my verizon pppoe stopped working under linux
> at some point yesterday (03/13/03), but works in windows. I keep getting
> "No response to PAP authenticate-requests". I've tried everything I can
> find from google for that error but to no avail. I ran a bunch of debug
> messages and everything looks fine right up until I send a PAP req over
> and over and never get a response. If I run pppoe -A I get the concentrator
> to show up, but that's it.
>
> Any help at all, any grasped straws, any remotely relevant suggestions,
> anyone at all? please?
I've recently been having problems with my Verizon DSL connection too.
At first I thought my router (a netgear) had messed up, but now I'm
having the same problem as this thread is describing.
What changed must have been on verizon's side, because the changes
happened while I was away. It isn't a hardware (at least upsteam of
the modem) or software issue, since both the router and my linux box
fail.
I found a suggestion is another thread that said one should add
'default-asyncmap' as an option to the dsl-provider file. This cured
my problem. I don't understand why one would need to specify a
default-ANYTHING, so I'll report it as a bug on the pppoe package.
Hope that helps you too.
--
Devin Bayer
Scott McCallum
> > Does anyone know if Verizon (in Boston here) has made any modifications
> > to their connection protocols recently?
> >
> > Has the recent upgrade of tcpdump affected pppoe in any way? I could not
> > find it installed on the Debian box at home, but I remember it being
> > upgraded recently (probably here at work).
> >
> > Thanks for any help,
> >
> > JP
It's nothing you did, I suspect. I'm in Boston too and my Verizon DSL stopped
working on my linux box on 3/12 as well. Works fine in windows. pppoe -A
shows the AC just fine, pppd in debug shows some ConfReq and ConfAck/Nak
chatting whereupon they agree on pap authentication. Then I send pap AuthReqs
until the lcp echo times out... and that's it. I haven't been able to sniff
the windows connection yet... need to rewire a bit for that.
If anyone knows anything at all... please, m o s k r i n @ a n s i b l e . n e t