pppoe reconnect problem with ADSL on linux
Steffen Peters
since 5 days I have got a problem to get reconnected router(linux-box)
with my ISP. It worked fine for the last year. But now I'm getting in
trouble after my ISP kicks me out after 24h. I'm actaully using a SuSE
9.0 with pppd version 2.4.1 and smpppd 1.06. The pppd options are set to
idletime=99999, persist , maxfail 0......
Here is the log:
snip.......
May 19 14:27:44 xxxxxx pppd[357]: LCP terminated by peer
May 19 14:27:44 xxxxxx pppd[357]: Setting MTU to 1492.
May 19 14:27:44 xxxxxx pppd[357]: Couldn't increase MRU to 1500
May 19 14:27:44 xxxxxx pppd[357]: Script /etc/ppp/ip-down finished (pid
3716), status = 0x0
May 19 14:27:46 xxxxxx pppd[357]: Connection terminated.
May 19 14:27:46 xxxxxx pppd[357]: Connect time 1440.0 minutes.
May 19 14:27:46 xxxxxx pppd[357]: Sent 2828510 bytes, received 18782385
bytes.
May 19 14:27:46 xxxxxx pppd[357]: Doing disconnect
May 19 14:28:16 xxxxxx pppd[357]: Sending PADI
May 19 14:28:16 xxxxxx pppd[357]: invalid packet Ether addr:
00:90:1a:40:df:3c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1
code=0xd3 sid=0xb515 length=0x001a (Unknown) PPPoE tag: type=0111
length=0016 (Unknown) unrecognized data
May 19 14:28:16 xxxxxx pppd[357]: Failed to negotiate PPPoE connection:
25 Inappropriate ioctl for device
May 19 14:28:16 xxxxxx pppd[357]: Exit.
snip.......
This one is from the time it owrked fine....
snip.......
May 11 10:10:55 xxxxxx pppd[357]: LCP terminated by peer
May 11 10:10:55 xxxxxx pppd[357]: Setting MTU to 1492.
May 11 10:10:55 xxxxxx pppd[357]: Couldn't increase MRU to 1500
May 11 10:10:55 xxxxxx pppd[357]: Script /etc/ppp/ip-down finished (pid
15654), status = 0x0
May 11 10:10:57 xxxxxx pppd[357]: Connection terminated.
May 11 10:10:57 xxxxxx pppd[357]: Connect time 1440.1 minutes.
May 11 10:10:57 xxxxxx pppd[357]: Sent 5466712 bytes, received 897352 bytes.
May 11 10:10:57 xxxxxx pppd[357]: Doing disconnect
May 11 10:11:27 xxxxxx pppd[357]: Sending PADI
May 11 10:11:27 xxxxxx pppd[357]: HOST_UNIQ successful match
May 11 10:11:28 xxxxxx pppd[357]: HOST_UNIQ successful match
May 11 10:11:28 xxxxxx pppd[357]: Got connection: 1375
May 11 10:11:28 xxxxxx pppd[357]: Connecting PPPoE socket:
00:90:1a:40:df:3c 7513 eth1 0x808a928
May 11 10:11:28 xxxxxx pppd[357]: Using interface ppp0
May 11 10:11:28 xxxxxx pppd[357]: Connect: ppp0 <--> eth1
snip.......
Is there anyone with an idea to solve my problem? For the next time I
will go over cron and stop/start smpppd for 5 minutes evers night to
work arround the 24h-limit....but that's not the way.....
thx an best reguards
Steffen Peters
--
... just remove the X from the first n last position of this
Email-Adress ;-)
James Carlson
> since 5 days I have got a problem to get reconnected router(linux-box)
> with my ISP. It worked fine for the last year. But now I'm getting in
> trouble after my ISP kicks me out after 24h.
Sounds like your ISP has changed its policies.
> I'm actaully using a SuSE
> 9.0 with pppd version 2.4.1 and smpppd 1.06. The pppd options are set
> to idletime=99999, persist , maxfail 0......
If you don't want an idle timer at all, don't set that parameter.
Setting it to 99999 isn't the right way to disable it.
> Here is the log:
>
> snip.......
>
> May 19 14:27:44 xxxxxx pppd[357]: LCP terminated by peer
> May 19 14:27:44 xxxxxx pppd[357]: Setting MTU to 1492.
> May 19 14:27:44 xxxxxx pppd[357]: Couldn't increase MRU to 1500
> May 19 14:27:44 xxxxxx pppd[357]: Script /etc/ppp/ip-down finished
> (pid 3716), status = 0x0
> May 19 14:27:46 xxxxxx pppd[357]: Connection terminated.
> May 19 14:27:46 xxxxxx pppd[357]: Connect time 1440.0 minutes.
I don't see any debug information there. Hope that's ok.
1440 minutes is exactly one day ... so it sounds like you're running
into ISP policy. They're hanging up on you.
> May 19 14:28:16 xxxxxx pppd[357]: Sending PADI
> May 19 14:28:16 xxxxxx pppd[357]: invalid packet Ether addr:
> 00:90:1a:40:df:3c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1
> code=0xd3 sid=0xb515 length=0x001a (Unknown) PPPoE tag: type=0111
> length=0016 (Unknown) unrecognized data
> May 19 14:28:16 xxxxxx pppd[357]: Failed to negotiate PPPoE
That doesn't look good. Unfortunately, I don't know much about that
part of the problem, and I hope someone else will post on that.
> Is there anyone with an idea to solve my problem? For the next time I
> will go over cron and stop/start smpppd for 5 minutes evers night to
> work arround the 24h-limit....but that's not the way.....
That might be the only way to deal with it ...
--
James Carlson, IP Systems Group <james.d...@sun.com>
Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677
Steffen Peters
Thx! ...was my first thought too! But the ISP told me that there was NO!
change at all.
The time before it was nomral that the signal was terminated after 24h
(1440 minutes) by the ISP. Therefor I set the persist option of the pppd
an it worked fine for 1 year. But no the new PADI (broadcast?) is
canceled with this error:
May 19 14:28:16 xxxxxx pppd[357]: invalid packet Ether addr:
00:90:1a:40:df:3c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1
code=0xd3 sid=0xb515 length=0x001a (Unknown) PPPoE tag: type=0111
length=0016 (Unknown) unrecognized data
May 19 14:28:16 xxxxxx pppd[357]: Failed to negotiate PPPoE
Is there any way to explain that?
James Carlson
> Thx! ...was my first thought too! But the ISP told me that there was
> NO! change at all.
In that case, it sounds like they're lying to you.
> May 19 14:28:16 xxxxxx pppd[357]: invalid packet Ether addr:
> 00:90:1a:40:df:3c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1
> code=0xd3 sid=0xb515 length=0x001a (Unknown) PPPoE tag: type=0111
> length=0016 (Unknown) unrecognized data
> May 19 14:28:16 xxxxxx pppd[357]: Failed to negotiate PPPoE
>
> Is there any way to explain that?
Code number 0xd3 is the never-quite-documented PADM (PPPoE Active
Discovery Message) feature, and a tag value of 0111 indicates HURL
(Host URL?). The text inside (24 bytes long) should be a URL.
This means the peer is likely a RedBack server, and is attempting to
force your browser to display some page. I'd suspect that the page
says something friendly like "sorry, we don't allow customer
connections to persist for more than 24 hours unless you pay us a
whole lot more money."
Pppd should just be ignoring (but logging) this bogus message, rather
than treating it as a failure reason. Log a bug via
ppp-...@dp.samba.org.
Steffen Peters
Thanks a lot for these nice and good explaination, easiely to understand....
Best reguards
Steffen