From owner-freebsd-current@FreeBSD.ORG Mon Feb 23 02:20:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48CA816A4DE for ; Mon, 23 Feb 2004 02:20:26 -0800 (PST) Received: from email04.aon.at (WARSL402PIP2.highway.telekom.at [195.3.96.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 6730A43D2F for ; Mon, 23 Feb 2004 02:20:20 -0800 (PST) (envelope-from shoesoft@gmx.net) Received: (qmail 98162 invoked from network); 23 Feb 2004 10:20:17 -0000 Received: from m095p017.dipool.highway.telekom.at (HELO ?62.46.1.209?) ([62.46.1.209]) (envelope-sender ) by qmail7rs.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 23 Feb 2004 10:20:17 -0000 From: Stefan Ehmann To: freebsd-current@freebsd.org Content-Type: text/plain Message-Id: <1077531650.834.27.camel@shoeserv.freebsd> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 23 Feb 2004 11:20:51 +0100 Content-Transfer-Encoding: 7bit Subject: Fritz!Card PCI ppp troubles X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 10:20:26 -0000 I posted this a while ago on some other mailing list but got no response - I promise this is my final attempt. I'm using ifpi(4) with the configuration supplied in ppp.conf.isdn and isdnd.rc in /usr/share/examples/ppp/. It's basically working fine but there are some troubles. Especially when the hard disk load is high (e.g. doing a massive portupgrade), the connection drops out. Sometimes it recovers after some time, sometimes only a reconnect helps If I can see Queued packets in pppctl it's unrecoverable and only a reconnect helps. There are still packets coming in but none going out according to pppctl. Sometimes only small packets like pings or irc work and all other traffic is impossible. I've also tried running ethereal and saw a lot of invalid packets. In this situation the connection gets normal again after some time. It's probably mainboard related since another user reported to me that his problems have gone away since switching mainboard. dmesg can be found here: http://stud4.tuwien.ac.at/~e0125637/fbsd/dmesg