From owner-freebsd-stable Sat Jun 24 10: 2:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id 6F3E537BC8F; Sat, 24 Jun 2000 10:02:32 -0700 (PDT) (envelope-from se@freebsd.org) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout1.freenet.de with esmtp (Exim 3.14 #3) id 135tK2-0006Fq-00; Sat, 24 Jun 2000 19:02:22 +0200 Received: from [213.6.110.42] (helo=StefanEsser.FreeBSD.org) by mx3.freenet.de with esmtp (Exim 3.14 #3) id 135tJz-0000Ld-00; Sat, 24 Jun 2000 19:02:19 +0200 Received: by StefanEsser.FreeBSD.org (Postfix, from userid 200) id BEC01D1C; Sat, 24 Jun 2000 18:49:04 +0200 (CEST) Date: Sat, 24 Jun 2000 18:49:04 +0200 From: Stefan Esser To: Steve Khoo Cc: freebsd-stable@FreeBSD.ORG, Stefan Esser Subject: Re: 4.x-stable(~ June 8) fxp driver and KAME problem Message-ID: <20000624184904.A47446@StefanEsser.FreeBSD.org> Reply-To: Stefan Esser References: <394957C4.3AAA628A@gordian.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <394957C4.3AAA628A@gordian.com>; from steve@gordian.com on Thu, Jun 15, 2000 at 03:25:08PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-06-15 15:25 -0700, Steve Khoo wrote: > I was trying to get KAME working on 4.x-stable box and ran into some > problems. In searching for answers I came across this little note in > the release notes for the latest(20000613) KAME snapshot. It claims > there is a problem with fxp driver. Is this a known problem? Is there > a fix for it? There was a work.-around, that was put into -current soem time ago. You may want to check the CVS logs of the fxp driver ... > - FreeBSD/Openbsd/BSDI Intel EtherExpress Pro driver has some problem > with > the initialization sequence KAME is using. This is because these > drivers use interrupts for multicast filter setup, and KAME code calls > multicast initialization code in splimp() or splnet(). > It is not KAME problem, it is problem in drivers. These drivers > should > be corrected not to use interropts in initialization sequence. > > KAME/FreeBSD: fxp driver, no workaround available. I developed a workaround, which de-activated the fxp card and then (after sleeping for a second) re-initialized it in some particular order (don't remember the order of steps, i.e. whether the IPv6 or IPv4 functionality was re-enabled first). You may want to play with "ifconfig inet x.x.x.x delete" and "ifconfig inet6 x::y:z delete" followed by ifconfig command that restore working parameters for inet and inet6 (in either order). I had this in a file in /usr/local/etc/rc.d, but the problem was solved by adding some work-around to 5.0-current, which I was using at the time. I've downgraded the system to 4.0-stable, and it still works with 3 EtherExpress 100 Pro cards. Will have to see, whether I have kept the script that worked for me. (Can only do that next wednesday.) Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message