Date: Thu, 15 Jun 2000 15:25:08 -0700 From: Steve Khoo <steve@gordian.com> To: freebsd-stable@freebsd.org Subject: 4.x-stable(~ June 8) fxp driver and KAME problem Message-ID: <394957C4.3AAA628A@gordian.com>
next in thread | raw e-mail | index | archive | help
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? - 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. KAME/OpenBSD: fxp driver, workaround is in KAME tree (sys/net/if.c) KAME/BSDI3: exp driver, status unknown KAME/BSDI4: exp driver, workaround is in KAME tree (sys/i386/pci/if_exp.c) I'd appreciate any help. Thanks! SEK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?394957C4.3AAA628A>