Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 4 Jan 2001 13:51:33 +0100
From:      Thomas Moestl <tmoestl@gmx.net>
To:        freebsd-isdn@freebsd.org
Subject:   Problems with ISDN SyncPPP in -CURRENT
Message-ID:  <20010104135132.A1052@crow.dom2ip.de>

next in thread | raw e-mail | index | archive | help
Hi,

I am trying to set up ISDN SyncPPP on a very recently cvsupped -CURRENT 
box, but can not get it to work.
I have got a AVM Fritz Card PCI, dmesg (sorry for over-long lines):

ifpi0: <AVM Fritz!Card PCI> port 0xcc 00-0xcc1f mem 0xefffeee0-0xefffeeff irq 12 at device 13.0 on pci0
ifpi0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2)
ifpi0: passive stack unit 0

I use isp0 for SyncPPP:

raven# ifconfig isp0
isp0: flags=a011<UP,POINTOPOINT,LINK1,MULTICAST> mtu 1500
        inet 0.0.0.0 --> 0.0.0.1 netmask 0xff000000 
        ether 00:00:00:00:00:00 

raven# ispppcontrol isp0
isp0:   phase=dead
        myauthproto=pap myauthname="XXX"
        lcp timeout: 3.000 s
        enable_vj: on

The ispppcontrol call to set the device up is:

ispppcontrol myauthproto=pap myauthname='XXX' myauthsecret='YYY' hisauthproto=none

Everytime I try to dial up isp0, the connection is established, the LCP
negotiation seems to be OK, but there is just no answer received on the
PAP authetication try:

isp0: lcp open(initial)
isp0: phase establish
isp0: Up event
isp0: lcp up(starting)
isp0: lcp output <conf-req id=0x5 len=10 05-06-7b-09-d6-0d>
isp0: lcp input(req-sent): <conf-req id=0x1 len=27 01-04-05-f4-03-04-c0-23-11-04-05-f4-13-0b-01-73-74-61-63-6b-69-6e-67>
isp0: lcp parse opts:  mru  auth-proto  lcp/0x11 [rej]  lcp/0x13 [rej]  send conf-rej
isp0: lcp output <conf-rej id=0x1 len=19 11-04-05-f4-13-0b-01-73-74-61-63-6b-69-6e-67>
isp0: lcp input(req-sent): <conf-ack id=0x5 len=10 05-06-7b-09-d6-0d>
isp0: lcp input(ack-rcvd): <conf-req id=0x2 len=12 01-04-05-f4-03-04-c0-23>
isp0: lcp parse opts:  mru  auth-proto 
isp0: lcp parse opt values:  mru 1524  auth-proto  send conf-ack
isp0: lcp output <conf-ack id=0x2 len=12 01-04-05-f4-03-04-c0-23>
isp0: lcp tlu
isp0: phase authenticate
isp0: pap output <req id=0x6 len=42 ...my auth data...>
isp0: pap peer TO
isp0: pap output <req id=0x7 len=42 ...my auth data...>
isp0: lcp down(opened)
isp0: phase terminate
isp0: Down event (carrier loss)
isp0: lcp close(starting)
isp0: phase dead

, and so forth, all PAP tries time out (the timeouts are reasonably long).
I have a -STABLE setup (on a different box) with a setup that is identical
as much as possible. Dialup works with the same auth data.
Toying with timeout and compression options does not help.
My ISP is T-Online in Germany.
I have not tried -STABLE on the same box, so I cannot confirm that this
is not caused by flaky hardware.

On some boots, I additionally get messages like:
Jan  3 23:57:06 raven /boot/kernel/kernel: i4b-L1 ifpi_isac_exir_hdlr: EXIRQ Rx Frame Overflow

But even on successful boots, I do not get past the PAP authentication.
Has anyone experienced similar problems? I suppose that my ISP's PPP 
implementation may be somewhat flawed.

Besides, there seems to be a small typo in usr.sbin/i4b/isdnd/rc_scan.l
that breaks the ppp-expect-* options. This patch should fix it:

*** usr.sbin/i4b/isdnd/rc_scan.l~	Mon Oct  9 16:22:39 2000
--- usr.sbin/i4b/isdnd/rc_scan.l	Thu Jan  4 00:29:44 2001
***************
*** 149,155 ****
  ppp-auth-paranoid		{ return PPP_AUTH_PARANOID; }
  ppp-expect-auth			{ return PPP_EXPECT_AUTH; }
  ppp-expect-name			{ return PPP_EXPECT_NAME; }
! ppp-expect-password		{ return PPP_EXPECT_NAME; }
  ppp-send-auth			{ return PPP_SEND_AUTH; }
  ppp-send-name			{ return PPP_SEND_NAME; }
  ppp-send-password		{ return PPP_SEND_PASSWORD; }
--- 149,155 ----
  ppp-auth-paranoid		{ return PPP_AUTH_PARANOID; }
  ppp-expect-auth			{ return PPP_EXPECT_AUTH; }
  ppp-expect-name			{ return PPP_EXPECT_NAME; }
! ppp-expect-password		{ return PPP_EXPECT_PASSWORD; }
  ppp-send-auth			{ return PPP_SEND_AUTH; }
  ppp-send-name			{ return PPP_SEND_NAME; }
  ppp-send-password		{ return PPP_SEND_PASSWORD; }


TIA,
	- thomas



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010104135132.A1052>