From owner-freebsd-isdn Wed Mar 17 23:52:44 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from linteuto.teuto.de (linteuto.teuto.de [194.77.23.26]) by hub.freebsd.org (Postfix) with ESMTP id 5F6F414C2E for ; Wed, 17 Mar 1999 23:52:40 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (root@rumolt.teuto.de [212.8.203.81]) by linteuto.teuto.de (8.8.7/8.8.7) with ESMTP id IAA00191; Thu, 18 Mar 1999 08:52:17 +0100 Received: from martins (hwart.teuto.de [212.8.203.83]) by rumolt.teuto.de (8.8.8/8.8.7) with SMTP id IAA06806; Thu, 18 Mar 1999 08:40:15 +0100 (MET) From: "Martin Husemann" To: Cc: , Subject: RE: got a isdntrace and tcpdump trace of unsucceessful dialup attempts Date: Thu, 18 Mar 1999 08:40:12 +0100 Message-ID: <001601be7112$8e655c30$53cb08d4@martins.teuto.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: <19990317083255.A1595@finesse.paul-magazin.de> Importance: Normal Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Problem: In your case, the remote access device did not like your > login. So this was an authorization failure. Seemed to be a provider > problem (broken radius, tacacs, or whatsoever). That's exactly what I was seeing on a system connecting to t-online. PAP login was rejected, and that's what my patch uses to configure the interface down to prevent frequent redials. Usualy after a few minutes the problem "just goes away" and a new connection can be established. Maybe a firmware bug in the AS5200, as Andreas told us the radius logs showed "access granted" ??? The only way to trace this down will be a PPP log of a failing connection from the AS5200. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message