From owner-freebsd-questions@FreeBSD.ORG Thu Jan 27 05:27:09 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CB8016A4CE for ; Thu, 27 Jan 2005 05:27:09 +0000 (GMT) Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [65.75.192.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE59843D41 for ; Thu, 27 Jan 2005 05:27:08 +0000 (GMT) (envelope-from tedm@toybox.placo.com) Received: from tedwin2k (nat-rtr.freebsd-corp-net-guide.com [65.75.197.130]) j0R5R8j41526; Wed, 26 Jan 2005 21:27:08 -0800 (PST) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Stefan Pietsch" , Date: Wed, 26 Jan 2005 21:27:07 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <41F80A3B.977C7DF2@web.de> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal Subject: RE: ISDN connection problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jan 2005 05:27:09 -0000 owner-freebsd-questions@freebsd.org wrote: > Ted Mittelstaedt wrote: > >> The xl driver has been a pain in a lot of people's backside for >> years under earlier versions of FreeBSD. Quit torturing yourself >> and spend the $15 on another brand of network adapter card. > > > The problem is not the 3com card. The ethernet connection works fine > if I turn on promiscious mode. And if you keep dismissing avenues to try then your never going to fix the problem. One of the basics of trooubleshooting is that everything in the box is suspect, until the problem is fixed. It is just that some things are more suspect than others. For someone to make a definitive statement that "the problem is NOT" before the solution is known, is a mark of a closed mind. This is why you are having difficulty finding the fix. The problem may very well not be the 3com card. But unless you try swapping with a different ethernet card, you aren't going to have proof that it isn't - unless you stumble across the solution before you get desperate enough to actually try swapping the card. But, since you want to gamble on doing that, good luck to you. Ted