Re: ppp redial unsuccessful

2006-10-06 Thread Ulrich Spoerlein 
Nick Gustas wrote:
 Oct  4 19:03:09 xxx ppp[55]: tun0: Phase: bundle: Authenticate
 Oct  4 19:03:09 xxx ppp[55]: tun0: Phase: deflink: his = PAP, mine = none
 Oct  4 19:03:09 xxx ppp[55]: tun0: Phase: Pap Output: [EMAIL PROTECTED] 
 
 Oct  4 19:03:09 xxx ppp[55]: tun0: LCP: deflink: RecvCodeRej(127) state = 
 Opened
 Oct  4 19:03:11 xxx ppp[55]: tun0: Phase: Pap Input: SUCCESS ()

 The real question is, is there's a way to work around your provider's 
 brokenness without 
 killing the ppp process?

Hi Nick,

I cranked up the debug logging, and compared my ppp login attempts with
your logfile. I get multiple

Oct  6 18:29:43 coyote ppp[67945]: tun0: IPCP: deflink: RecvConfigReq(12) state 
= Initial
Oct  6 18:29:43 coyote ppp[67945]: tun0: IPCP:  IPADDR[6] 213.191.89.20 
Oct  6 18:29:43 coyote ppp[67945]: tun0: IPCP: deflink: Oops, RCR in Initial.
Oct  6 18:29:46 coyote ppp[67945]: tun0: IPCP: deflink: RecvConfigReq(13) state 
= Initial
Oct  6 18:29:46 coyote ppp[67945]: tun0: IPCP:  IPADDR[6] 213.191.89.20
Oct  6 18:29:46 coyote ppp[67945]: tun0: IPCP: deflink: Oops, RCR in Initial.

Using Google Search then led me to the follow posts [1], that describe the
problem in more detail. 'disable ipv6cp' should do the trick, I'll check
this ASAP.

Thanks for your pointer!

[1] 
http://www.freebsd.de/archive/de-bsd-questions/de-bsd-questions.200506/0029.html
http://tech.barwick.de/openbsd/deflink-oops-rcr-in-initial.html

Ulrich Spoerlein
-- 
A: Yes.
Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting frowned upon?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ppp redial unsuccessful

2006-10-06 Thread cpghost 
On Fri, Oct 06, 2006 at 08:02:02PM +0200, Ulrich Spoerlein wrote:
 I cranked up the debug logging, and compared my ppp login attempts with
 your logfile. I get multiple
 
 Oct  6 18:29:43 coyote ppp[67945]: tun0: IPCP: deflink: RecvConfigReq(12) 
 state = Initial
 Oct  6 18:29:43 coyote ppp[67945]: tun0: IPCP:  IPADDR[6] 213.191.89.20 
 Oct  6 18:29:43 coyote ppp[67945]: tun0: IPCP: deflink: Oops, RCR in Initial.
 Oct  6 18:29:46 coyote ppp[67945]: tun0: IPCP: deflink: RecvConfigReq(13) 
 state = Initial
 Oct  6 18:29:46 coyote ppp[67945]: tun0: IPCP:  IPADDR[6] 213.191.89.20
 Oct  6 18:29:46 coyote ppp[67945]: tun0: IPCP: deflink: Oops, RCR in Initial.
 
 Using Google Search then led me to the follow posts [1], that describe the
 problem in more detail. 'disable ipv6cp' should do the trick, I'll check
 this ASAP.

Yesterday, I've had a brand new 6.2-PRERELEASE Oct 4th box installed
on T-Com ADSL, using the same ppp.conf from my previous post. I've just
logged into this box and seen a successful disconnect/reconnect, as
always after 24hrs. Everything seems all right with ppp and T-Com ADSL.

 Ulrich Spoerlein

Regards,
-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ppp redial unsuccessful

2006-10-06 Thread Ulrich Spoerlein 
cpghost wrote:
 On Fri, Oct 06, 2006 at 08:02:02PM +0200, Ulrich Spoerlein wrote:
  I cranked up the debug logging, and compared my ppp login attempts with
  your logfile. I get multiple
  
  Oct  6 18:29:43 coyote ppp[67945]: tun0: IPCP: deflink: RecvConfigReq(12) 
  state = Initial
  Oct  6 18:29:43 coyote ppp[67945]: tun0: IPCP:  IPADDR[6] 213.191.89.20 
  Oct  6 18:29:43 coyote ppp[67945]: tun0: IPCP: deflink: Oops, RCR in 
  Initial.
  Oct  6 18:29:46 coyote ppp[67945]: tun0: IPCP: deflink: RecvConfigReq(13) 
  state = Initial
  Oct  6 18:29:46 coyote ppp[67945]: tun0: IPCP:  IPADDR[6] 213.191.89.20
  Oct  6 18:29:46 coyote ppp[67945]: tun0: IPCP: deflink: Oops, RCR in 
  Initial.
  
  Using Google Search then led me to the follow posts [1], that describe the
  problem in more detail. 'disable ipv6cp' should do the trick, I'll check
  this ASAP.
 
 Yesterday, I've had a brand new 6.2-PRERELEASE Oct 4th box installed
 on T-Com ADSL, using the same ppp.conf from my previous post. I've just
 logged into this box and seen a successful disconnect/reconnect, as
 always after 24hrs. Everything seems all right with ppp and T-Com ADSL.

I guess it depends on the actual hardware on the other side. Different
POPs have different hardware (versions) and software (configuration).

Let's wait for another 24h to see if I found the solution.

Ulrich Spoerlein
-- 
A: Yes.
Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting frowned upon?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

ppp redial unsuccessful

2006-10-04 Thread Ulrich Spoerlein 
Hello all,

with my ADSL provider (a reseller of the german Telekom), I'm unable to
make ppp redial after the link has been lost. With Telekom, you usually
get disconnected every 24h hours, but you can simply reconnect  if
our ppp would support it.

Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase: deflink: open - lcp
Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase: Received NGM_PPPOE_CLOSE
Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase: deflink: Device disconnected
Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase: deflink: Disconnected!
Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase: deflink: lcp - logout
Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase: deflink: Disconnected!
Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase: deflink: logout - hangup
Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase: deflink: Connect time: 120 
secs: 395 octets in, 131 octets out
Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase: deflink: 3122183 packets in, 
3135772 packets out
Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase:  total 4 bytes/sec, peak 72 
bytes/sec on Wed Oct  4 20:37:53 2006
Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase: deflink: hangup - opening
Oct  4 20:39:51 coyote ppp[57670]: tun0: Phase: deflink: Enter pause (3) for 
redialing.
Oct  4 20:39:54 coyote ppp[57670]: tun0: Phase: deflink: Connected!
Oct  4 20:39:54 coyote ppp[57670]: tun0: Phase: deflink: opening - dial
Oct  4 20:39:54 coyote ppp[57670]: tun0: Phase: deflink: dial - carrier
Oct  4 20:39:55 coyote ppp[57670]: tun0: Phase: Received NGM_PPPOE_ACNAME (hook 
HN-XDSL)
Oct  4 20:39:55 coyote ppp[57670]: tun0: Phase: Received NGM_PPPOE_SESSIONID
Oct  4 20:39:55 coyote ppp[57670]: tun0: Phase: Received NGM_PPPOE_SUCCESS
Oct  4 20:39:55 coyote ppp[57670]: tun0: Phase: deflink: carrier - login
Oct  4 20:39:55 coyote ppp[57670]: tun0: Phase: deflink: login - lcp
Oct  4 20:39:55 coyote ppp[57670]: tun0: Phase: deflink: his = CHAP 0x05, mine 
= none
Oct  4 20:39:55 coyote ppp[57670]: tun0: Phase: Chap Input: CHALLENGE (23 bytes 
from BRUN-FX-0001-01-01)
Oct  4 20:39:55 coyote ppp[57670]: tun0: Phase: Chap Output: RESPONSE 
(06109724173)
Oct  4 20:39:56 coyote ppp[57670]: tun0: Phase: Chap Input: SUCCESS
Oct  4 20:39:56 coyote ppp[57670]: tun0: Phase: deflink: Already in NETWORK 
phase
Oct  4 20:39:56 coyote ppp[57670]: tun0: Phase: deflink: lcp - open
Oct  4 20:41:48 coyote ppp[57670]: tun0: Phase: Clearing choked output queue
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase: deflink: open - lcp
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase: Received NGM_PPPOE_CLOSE
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase: deflink: Device disconnected
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase: deflink: Disconnected!
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase: deflink: lcp - logout
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase: deflink: Disconnected!
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase: deflink: logout - hangup
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase: deflink: Connect time: 121 
secs: 395 octets in, 131 octets out
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase: deflink: 3122213 packets in, 
3135778 packets out
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase:  total 4 bytes/sec, peak 72 
bytes/sec on Wed Oct  4 20:39:56 2006
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase: deflink: hangup - opening
Oct  4 20:41:55 coyote ppp[57670]: tun0: Phase: deflink: Enter pause (3) for 
redialing.
Oct  4 20:41:58 coyote ppp[57670]: tun0: Phase: deflink: Connected!
Oct  4 20:41:58 coyote ppp[57670]: tun0: Phase: deflink: opening - dial
Oct  4 20:41:58 coyote ppp[57670]: tun0: Phase: deflink: dial - carrier
Oct  4 20:41:59 coyote ppp[57670]: tun0: Phase: Received NGM_PPPOE_ACNAME (hook 
HN-XDSL)
Oct  4 20:41:59 coyote ppp[57670]: tun0: Phase: Received NGM_PPPOE_SESSIONID
Oct  4 20:41:59 coyote ppp[57670]: tun0: Phase: Received NGM_PPPOE_SUCCESS
Oct  4 20:41:59 coyote ppp[57670]: tun0: Phase: deflink: carrier - login
Oct  4 20:41:59 coyote ppp[57670]: tun0: Phase: deflink: login - lcp
Oct  4 20:41:59 coyote ppp[57670]: tun0: Phase: deflink: his = CHAP 0x05, mine 
= none
Oct  4 20:41:59 coyote ppp[57670]: tun0: Phase: Chap Input: CHALLENGE (31 bytes 
from BRUN-FX-0001-01-01)
Oct  4 20:41:59 coyote ppp[57670]: tun0: Phase: Chap Output: RESPONSE 
(06109724173)
Oct  4 20:41:59 coyote ppp[57670]: tun0: Phase: Chap Input: SUCCESS
Oct  4 20:41:59 coyote ppp[57670]: tun0: Phase: deflink: Already in NETWORK 
phase
Oct  4 20:41:59 coyote ppp[57670]: tun0: Phase: deflink: lcp - open


My ppp.conf looks like this:

default:
 set log Phase Chat LCP IPCP CCP tun command
 ident user-ppp VERSION (built COMPILATIONDATE)
 set device /dev/cuad1
 set speed 115200
 set dial ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \
   \\ AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT
 set timeout 180# 3 minute idle timer (the default)
 enable dns # request DNS info (for resolv.conf)

alice:
  resolv readonly
  set log Phase tun command

Re: ppp redial unsuccessful

2006-10-04 Thread cpghost 
On Wed, Oct 04, 2006 at 08:51:48PM +0200, Ulrich Spoerlein wrote:
 Hello all,
 
 with my ADSL provider (a reseller of the german Telekom), I'm unable to
 make ppp redial after the link has been lost. With Telekom, you usually
 get disconnected every 24h hours, but you can simply reconnect  if
 our ppp would support it.

Have you added this to /etc/rc.conf?

ppp_mode=ddial

 Ulrich Spoerlein

Regards,
-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ppp redial unsuccessful

2006-10-04 Thread Ulrich Spoerlein 
cpghost wrote:
 On Wed, Oct 04, 2006 at 08:51:48PM +0200, Ulrich Spoerlein wrote:
  Hello all,
  
  with my ADSL provider (a reseller of the german Telekom), I'm unable to
  make ppp redial after the link has been lost. With Telekom, you usually
  get disconnected every 24h hours, but you can simply reconnect  if
  our ppp would support it.
 
 Have you added this to /etc/rc.conf?
 
 ppp_mode=ddial

Yes of course, as you can see, ppp(8) is not exiting, but entering an
redial endless loop ...

Ulrich Spoerlein
-- 
A: Yes.
Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting frowned upon?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ppp redial unsuccessful

2006-10-04 Thread Ivan Voras 
Ulrich Spoerlein wrote:
 Hello all,
 
 with my ADSL provider (a reseller of the german Telekom), I'm unable to
 make ppp redial after the link has been lost. With Telekom, you usually
 get disconnected every 24h hours, but you can simply reconnect  if
 our ppp would support it.

As a victim of almost-the-same company, I know they (at least nowadays)
sell modems that can also work in 'router mode' if persuaded enough, and
in that mode handle PPPoE by themselves while exporting pure IP over
Ethernet (NAT-ed) on the user end. Maybe this will help you :)

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ppp redial unsuccessful

2006-10-04 Thread Nick Gustas 

Ulrich Spoerlein wrote:

cpghost wrote:
  

On Wed, Oct 04, 2006 at 08:51:48PM +0200, Ulrich Spoerlein wrote:


Hello all,

with my ADSL provider (a reseller of the german Telekom), I'm unable to
make ppp redial after the link has been lost. With Telekom, you usually
get disconnected every 24h hours, but you can simply reconnect  if
our ppp would support it.
  

Have you added this to /etc/rc.conf?

ppp_mode=ddial



Yes of course, as you can see, ppp(8) is not exiting, but entering an
redial endless loop ...

Ulrich Spoerlein
  
Not that it helps you much, but I do see working pppoe redial behavior 
with Yahoo/ATT dsl at a client site in the US. I can unhook the dsl 
line and it will autoreconnect as soon as it's plugged in again. In the 
event of a provider outage it comes back up on its own. The current ppp 
session has been running for 59 days, longest session was 353 days, but 
the server had to be moved for remodeling.



ppp.conf :
---
default:
ident user-ppp VERSION (built COMPILATIONDATE)
set device PPPoE:dc0
set log Phase Chat LCP IPCP CCP tun command
set dial
set ifaddr 10.0.0.1/0 10.0.0.2/0
add default HISADDR# Add a (sticky) default route
set login
enable dns # request DNS info (for resolv.conf)

papchap:
set authname x
set authkey 

---

ppp commandline:
/usr/sbin/ppp -quiet -ddial -nat papchap


uname -a:
FreeBSD .lan 4.11-STABLE FreeBSD 4.11-STABLE #1: Tue Apr 26 
13:45:16 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/  i386


current trimmed px axu:
USER  PID %CPU %MEM   VSZ  RSS  TT  STAT STARTED  TIME COMMAND
root   55  0.0  1.5  2840  896  ??  Ss5Aug06  32:10.11 
/usr/sbin/ppp -quiet -ddial -nat papchap






___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ppp redial unsuccessful

2006-10-04 Thread cpghost 
On Wed, Oct 04, 2006 at 03:37:37PM -0400, Nick Gustas wrote:
 On Wed, Oct 04, 2006 at 08:51:48PM +0200, Ulrich Spoerlein wrote:
 
 with my ADSL provider (a reseller of the german Telekom), I'm unable to
 make ppp redial after the link has been lost. With Telekom, you usually
 get disconnected every 24h hours, but you can simply reconnect  if
 our ppp would support it.
   
 Have you added this to /etc/rc.conf?
 
 ppp_mode=ddial
 
 
 Yes of course, as you can see, ppp(8) is not exiting, but entering an
 redial endless loop ...
   
 Not that it helps you much, but I do see working pppoe redial behavior 
 with Yahoo/ATT dsl at a client site in the US. I can unhook the dsl 
 line and it will autoreconnect as soon as it's plugged in again. In the 
 event of a provider outage it comes back up on its own. The current ppp 
 session has been running for 59 days, longest session was 353 days, but 
 the server had to be moved for remodeling.

Same here. I've got some 6.1-STABLE boxes running since 70 days
uninterrupted on german T-Com ADSL (PPPoE). ppp redials automatically
without any problems there.

The question is: did something change in the source of ppp or ng_pppoe
in the mean time to cause breakage? I have currently no *physical*
access to a fresh box on T-Com to confirm that previously working setup
is now broken.

 ppp commandline:
 /usr/sbin/ppp -quiet -ddial -nat papchap

Regards,
-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ppp redial unsuccessful

2006-10-04 Thread Ulrich Spoerlein 
cpghost wrote:
 On Wed, Oct 04, 2006 at 03:37:37PM -0400, Nick Gustas wrote:
  Not that it helps you much, but I do see working pppoe redial behavior 
  with Yahoo/ATT dsl at a client site in the US. I can unhook the dsl 
  line and it will autoreconnect as soon as it's plugged in again. In the 
  event of a provider outage it comes back up on its own. The current ppp 
  session has been running for 59 days, longest session was 353 days, but 
  the server had to be moved for remodeling.
 
 Same here. I've got some 6.1-STABLE boxes running since 70 days
 uninterrupted on german T-Com ADSL (PPPoE). ppp redials automatically
 without any problems there.

I maintain three FreeBSD boxes from 4.11 to 6.1-RELEASE and 6-STABLE.
They have been showing this for at least 1 or 2 years. So it is/was also
present in the 5.x line.

I usually work around this by having a cron job that restarts ppp every
day at 04:00 or somewhere around that.

So either I'm just unlucky or I'm doing something fundamentally wrong.

Could someone paste me the snippet from ppp.log of a successful 24h
disconnect + redial?

Thanks.

Ulrich Spoerlein
-- 
A: Yes.
Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting frowned upon?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ppp redial unsuccessful

2006-10-04 Thread cpghost 
On Wed, Oct 04, 2006 at 11:39:09PM +0200, Ulrich Spoerlein wrote:
 I maintain three FreeBSD boxes from 4.11 to 6.1-RELEASE and 6-STABLE.
 They have been showing this for at least 1 or 2 years. So it is/was also
 present in the 5.x line.
 
 I usually work around this by having a cron job that restarts ppp every
 day at 04:00 or somewhere around that.
 
 So either I'm just unlucky or I'm doing something fundamentally wrong.
 
 Could someone paste me the snippet from ppp.log of a successful 24h
 disconnect + redial?

Here we go (sorry, it's a bit lengthy):

Oct  4 03:07:03 fw ppp[219]: LCP: deflink: RecvEchoReply(58) state = Opened
Oct  4 03:07:14 fw ppp[219]: LCP: deflink: RecvEchoRequest(0) state = Opened
Oct  4 03:07:14 fw ppp[219]: LCP: deflink: SendEchoReply(0) state = Opened
Oct  4 03:07:17 fw ppp[219]: Phase: Received NGM_PPPOE_CLOSE
Oct  4 03:07:17 fw ppp[219]: Phase: deflink: Device disconnected
Oct  4 03:07:17 fw ppp[219]: CCP: deflink: State change Stopped -- Closed
Oct  4 03:07:17 fw ppp[219]: CCP: deflink: State change Closed -- Initial
Oct  4 03:07:17 fw ppp[219]: LCP: deflink: LayerDown
Oct  4 03:07:17 fw ppp[219]: LCP: deflink: State change Opened -- Starting
Oct  4 03:07:17 fw ppp[219]: Phase: deflink: open - lcp
Oct  4 03:07:17 fw ppp[219]: IPCP: deflink: LayerDown: 111.222.111.222
Oct  4 03:07:17 fw ppp[219]: IPCP: Using trigger address 0.0.0.0
Oct  4 03:07:17 fw ppp[219]: IPCP: deflink: State change Opened -- Starting
Oct  4 03:07:17 fw ppp[219]: IPCP: deflink: LayerFinish.
Oct  4 03:07:17 fw ppp[219]: IPCP: Connect time: 86399 secs: 1659445914 octets 
in, 662415224 octets out
Oct  4 03:07:17 fw ppp[219]: IPCP: 167362746 packets in, 154080745 packets out
Oct  4 03:07:17 fw ppp[219]: IPCP:  total 26873 bytes/sec, peak 123304 
bytes/sec on Tue Oct  3 23:11:04 2006
Oct  4 03:07:17 fw ppp[219]: IPCP: deflink: State change Starting -- Initial
Oct  4 03:07:17 fw ppp[219]: Phase: bundle: Terminate
Oct  4 03:07:17 fw ppp[219]: LCP: deflink: LayerFinish
Oct  4 03:07:17 fw ppp[219]: LCP: deflink: State change Starting -- Initial
Oct  4 03:07:17 fw ppp[219]: Phase: deflink: Disconnected!
Oct  4 03:07:17 fw ppp[219]: Phase: deflink: lcp - logout
Oct  4 03:07:17 fw ppp[219]: Phase: deflink: Disconnected!
Oct  4 03:07:17 fw ppp[219]: Phase: deflink: logout - hangup
Oct  4 03:07:17 fw ppp[219]: Phase: deflink: Connect time: 86403 secs: 
1655294933 octets in, 666526906 octets out
Oct  4 03:07:17 fw ppp[219]: Phase: deflink: 167928154 packets in, 154647096 
packets out
Oct  4 03:07:17 fw ppp[219]: Phase:  total 26872 bytes/sec, peak 125048 
bytes/sec on Tue Oct  3 23:11:29 2006
Oct  4 03:07:17 fw ppp[219]: Phase: deflink: hangup - opening
Oct  4 03:07:17 fw ppp[219]: Phase: bundle: Establish
Oct  4 03:07:17 fw ppp[219]: Phase: deflink: Enter pause (3) for redialing.
Oct  4 03:07:20 fw ppp[219]: Phase: deflink: Connected!
Oct  4 03:07:20 fw ppp[219]: Phase: deflink: opening - dial
Oct  4 03:07:20 fw ppp[219]: Phase: deflink: dial - carrier
Oct  4 03:07:22 fw ppp[219]: Phase: Received NGM_PPPOE_ACNAME (hook 
DSSX43-erx)
Oct  4 03:07:22 fw ppp[219]: Phase: Received NGM_PPPOE_SESSIONID
Oct  4 03:07:22 fw ppp[219]: Phase: Received NGM_PPPOE_SUCCESS
Oct  4 03:07:22 fw ppp[219]: Phase: deflink: carrier - login
Oct  4 03:07:22 fw ppp[219]: Phase: deflink: login - lcp
Oct  4 03:07:22 fw ppp[219]: LCP: FSM: Using deflink as a transport
Oct  4 03:07:22 fw ppp[219]: LCP: deflink: State change Initial -- Closed
Oct  4 03:07:22 fw ppp[219]: LCP: deflink: State change Closed -- Stopped
Oct  4 03:07:23 fw ppp[219]: LCP: deflink: LayerStart
Oct  4 03:07:23 fw ppp[219]: LCP: deflink: SendConfigReq(58) state = Stopped
Oct  4 03:07:23 fw ppp[219]: LCP:  MRU[4] 1460
Oct  4 03:07:23 fw ppp[219]: LCP:  MAGICNUM[6] 0xff621829
Oct  4 03:07:23 fw ppp[219]: LCP: deflink: State change Stopped -- Req-Sent
Oct  4 03:07:23 fw ppp[219]: LCP: deflink: RecvConfigReq(209) state = Req-Sent
Oct  4 03:07:23 fw ppp[219]: LCP:  MRU[4] 1492
Oct  4 03:07:23 fw ppp[219]: LCP:  AUTHPROTO[4] 0xc023 (PAP)
Oct  4 03:07:23 fw ppp[219]: LCP:  MAGICNUM[6] 0x60a9a23e
Oct  4 03:07:23 fw ppp[219]: LCP: deflink: SendConfigAck(209) state = Req-Sent
Oct  4 03:07:23 fw ppp[219]: LCP:  MRU[4] 1492
Oct  4 03:07:23 fw ppp[219]: LCP:  AUTHPROTO[4] 0xc023 (PAP)
Oct  4 03:07:23 fw ppp[219]: LCP:  MAGICNUM[6] 0x60a9a23e
Oct  4 03:07:23 fw ppp[219]: LCP: deflink: State change Req-Sent -- Ack-Sent
Oct  4 03:07:23 fw ppp[219]: LCP: deflink: RecvConfigAck(58) state = Ack-Sent
Oct  4 03:07:23 fw ppp[219]: LCP:  MRU[4] 1460
Oct  4 03:07:23 fw ppp[219]: LCP:  MAGICNUM[6] 0xff621829
Oct  4 03:07:23 fw ppp[219]: LCP: deflink: State change Ack-Sent -- Opened
Oct  4 03:07:23 fw ppp[219]: LCP: deflink: LayerUp
Oct  4 03:07:23 fw ppp[219]: LCP: deflink: SendEchoRequest(0) state = Opened
Oct  4 03:07:23 fw ppp[219]: LCP: deflink: SendIdent(102) state = Opened
Oct  4 03:07:23 fw ppp[219]: LCP:  MAGICNUM ff621829
Oct  4 03:07:23 fw ppp[219]: LCP:  TEXT user-ppp 3.4.2 (built Jul 22

Re: ppp redial unsuccessful

2006-10-04 Thread Nick Gustas 

Ulrich Spoerlein wrote:

cpghost wrote:

On Wed, Oct 04, 2006 at 03:37:37PM -0400, Nick Gustas wrote:
Not that it helps you much, but I do see working pppoe redial behavior 
with Yahoo/ATT dsl at a client site in the US. I can unhook the dsl 
line and it will autoreconnect as soon as it's plugged in again. In the 
event of a provider outage it comes back up on its own. The current ppp 
session has been running for 59 days, longest session was 353 days, but 
the server had to be moved for remodeling.

Same here. I've got some 6.1-STABLE boxes running since 70 days
uninterrupted on german T-Com ADSL (PPPoE). ppp redials automatically
without any problems there.


I maintain three FreeBSD boxes from 4.11 to 6.1-RELEASE and 6-STABLE.
They have been showing this for at least 1 or 2 years. So it is/was also
present in the 5.x line.

I usually work around this by having a cron job that restarts ppp every
day at 04:00 or somewhere around that.

So either I'm just unlucky or I'm doing something fundamentally wrong.

Could someone paste me the snippet from ppp.log of a successful 24h
disconnect + redial?

Thanks.

Ulrich Spoerlein


If all of those boxes are with the same provider I have to wonder if 
it's something on their end preventing the redial. I don't have physical 
access to the client box to pull the cable and I've only seen a drop in 
the event of an outage. Every time it has dropped, manually or 
otherwise, it gets a new IP address, and she generally has the same IP 
for months. 

My ppp.log only goes back 9 days because I've apparently been logging my 
LCP keepalives, so I don't have any reconnects in it.


Sep 26 10:02:10 xxx ppp[55]: tun0: LCP: deflink: RecvEchoRequest(19) 
state = Opened
Sep 26 10:02:10 xxx ppp[55]: tun0: LCP: deflink: SendEchoReply(19) 
state = Opened


^^ 9 days of that.



However, I forced a reconnect by doing a

ifconfig dc0 down ; sleep 30 ; ifconfig dc0 up

in a screen session


here's the resulting ppp.log, note the Connect time: 5195480 secs: or 
60.133 days.



Oct  4 19:00:43 xxx ppp[55]: tun0: LCP: deflink: 
RecvEchoRequest(122) state = Opened
Oct  4 19:00:43 xxx ppp[55]: tun0: LCP: deflink: SendEchoReply(122) 
state = Opened
Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: write (fd 1, len 
86): Network is down
Oct  4 19:02:30 xxx ppp[55]: tun0: CCP: deflink: State change 
Stopped -- Closed
Oct  4 19:02:30 xxx ppp[55]: tun0: CCP: deflink: State change Closed 
-- Initial

Oct  4 19:02:30 xxx ppp[55]: tun0: LCP: deflink: LayerDown
Oct  4 19:02:30 xxx ppp[55]: tun0: LCP: deflink: State change Opened 
-- Starting

Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: open - lcp
Oct  4 19:02:30 xxx ppp[55]: tun0: IPCP: deflink: LayerDown: 
64.149.135.98
Oct  4 19:02:30 xxx ppp[55]: tun0: IPCP: deflink: State change 
Opened -- Starting

Oct  4 19:02:30 xxx ppp[55]: tun0: IPCP: deflink: LayerFinish.
Oct  4 19:02:30 xxx ppp[55]: tun0: IPCP: Connect time: 5195480 secs: 
1934412196 octets in, 540652575 octets out
Oct  4 19:02:30 xxx ppp[55]: tun0: IPCP: 3723224 packets in, 2819374 
packets out
Oct  4 19:02:30 xxx ppp[55]: tun0: IPCP:  total 476 bytes/sec, peak 
178816 bytes/sec on Tue Oct  3 15:25:50 2006
Oct  4 19:02:30 xxx ppp[55]: tun0: IPCP: deflink: State change 
Starting -- Initial

Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: bundle: Terminate
Oct  4 19:02:30 xxx ppp[55]: tun0: LCP: deflink: LayerFinish
Oct  4 19:02:30 xxx ppp[55]: tun0: LCP: deflink: State change 
Starting -- Initial

Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: Disconnected!
Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: lcp - logout
Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: Disconnected!
Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: logout - hangup
Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: Connect time: 
5195483 secs: 1927138891 octets in, 546464385 octets out
Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: 3740513 packets 
in, 2836661 packets out
Oct  4 19:02:30 xxx ppp[55]: tun0: Phase:  total 476 bytes/sec, peak 
177877 bytes/sec on Tue Oct  3 15:25:49 2006

Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: hangup - opening
Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: bundle: Establish
Oct  4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: Enter pause (3) 
for redialing.

Oct  4 19:02:30 xxx ppp[55]: tun0: Chat: deflink: Reconnect try 1 of 0
Oct  4 19:02:33 xxx ppp[55]: tun0: Chat: deflink: Redial timer expired.
Oct  4 19:02:33 xxx ppp[55]: tun0: Phase: deflink: Connected!
Oct  4 19:02:33 xxx ppp[55]: tun0: Phase: deflink: opening - dial
Oct  4 19:02:33 xxx ppp[55]: tun0: Phase: deflink: dial - carrier
Oct  4 19:02:35 xxx ppp[55]: tun0: Phase: Received NGM_PPPOE_ACNAME 
(hook 62031030047548-)

Oct  4 19:02:38 xxx ppp[55]: tun0: Phase: deflink: Disconnected!
Oct  4 19:02:38 xxx ppp[55]: tun0: Phase: deflink: carrier - hangup