Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Feb 2001 18:49:00 -0500
From:      James FitzGibbon <james@targetnet.com>
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   kern/25464: if_xl.so kld does not work with "options BRIDGE"
Message-ID:  <E14YGL6-000K2v-00@wrk-149.tor1.targetnet.pvt>

next in thread | raw e-mail | index | archive | help

>Number:         25464
>Category:       kern
>Synopsis:       if_xl.so kld does not work with "options BRIDGE"
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb 28 15:50:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     James FitzGibbon
>Release:        FreeBSD 4.2-STABLE-20010227-JPSNAP
>Organization:
Targetnet.com Inc.
>Environment:

PIII system
4x 3c905B ethernet cards
attempting to set up a two cluster bridge
kernel configured to use miibus and if_xl as modules
/etc/sysctl.conf configured for bridging

>Description:

I was attempting to build a bridge using the above configuration.  Packets
were visible on either side of the bridge, but nothing would go across the
interfaces.  'netstat -p bdg' showed nothing but the header, and ifconfig of
the interface did not show the 'PROMISC' flag.

After some hours, I went back to the start and build a new kernel based on
GENERIC with just 'options BRIDGE' added.  This worked.  After attempting to
give myself a concussion on the desk, I compared the kernel configs line for
line and could only notice that the miibus and if_xl drivers were in-kernel
in the successful config and modular in the failing config.  Making the
drivers in-kernel in my original kernel config made bridging work.

>How-To-Repeat:

Build a bridging machine with the miibus and xl drivers but do not build
them into the kernel.  Reboot and attempt to pass packets over the bridge.

>Fix:

Build the drivers into the kernel as a stopgap solution and document the
fact that this step is required.  Long term, figure out why the driver
doesn't work in this configuration.
>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E14YGL6-000K2v-00>