Certainly.

man-aux# brconfig -a
bridge0: flags=41<UP,RUNNING>
        Configuration:
                priority 32768 hellotime 2 fwddelay 15 maxage 20
        Interfaces:
                vlan95 flags=2<DISCOVER>
                        port 13 priority 128
                fxp0 flags=2<DISCOVER>
                        port 1 priority 128
        Address cache (max cache: 100, timeout: 1200):
(I turned off learning because man-aux kept getting confused where the
mac address of the laptop [man-97-238] was - fxp0 or vlan95).

an-aux# ifconfig -a
fxp0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        address: 00:20:e0:60:0a:a5
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 169.229.97.248 netmask 0xffffff00 broadcast 169.229.97.255
        inet6 fe80::220:e0ff:fe60:aa5%fxp0 prefixlen 64 scopeid 0x1
fxp1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        address: 00:20:e0:60:0a:a6
        media: Ethernet autoselect (none)
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 33220
        inet 127.0.0.1 netmask 0xff000000
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
        inet6 ::1 prefixlen 128
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
ppp1: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296
sl1: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296
strip0: flags=0<> mtu 1100
strip1: flags=0<> mtu 1100
vlan95: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu
1500
        vlan: 95 parent: fxp0
        address: 00:20:e0:60:0a:a5
bridge0: flags=41<UP,RUNNING> mtu 1500

The bridge, I think, works fine.  My guess is that the VLAN is the
problem...  See, for example:

http://www.wanfear.com/pipermail/vlan/2002q4/002731.html

I think this describes my problem accurately.

Any other information you would like?

Thanks,
Dobromir Montauk
System Administrator
Office of Residential Computing, UC Berkeley

On Sun, 1 Dec 2002, Manuel Bouyer wrote:

> On Sat, Nov 30, 2002 at 04:20:15PM -0800, Dobromir Montauk wrote:
> > I've found a lot of information about bridging a VLAN with a regular LAN
> > (both on the same netcard), but can't find anything specific to NetBSD
> > 1.6.  Perhaps someone can help?  Here's my problem:
> >
> > Packets comming in on the regular LAN (fxp0) get bridged to the VLAN fine
> > -- the VLAN header is automatically added & they go out to the correct
> > computer (who gets them w/o the VLAN header, since our switches take them
> > off correctly as well).
> > But packets comming in FROM the VLAN do NOT get their header taken off &
> > correctly bridged to the regular LAN.  Instead, they get another header
> > tacked on!  It looks pretty funky: here's the tcpdump:
> >
> > 17:53:44.914785 hal.Rescomp.Berkeley.EDU >
> > man-97-238.Reshall.Berkeley.EDU: icmp: echo request
> >
> > 17:53:44.914794 802.1Q vlan#95 P0 hal.Rescomp.Berkeley.EDU >
> > man-97-238.Reshall.Berkeley.EDU: icmp: echo request
> >
> > 17:53:44.915153 802.1Q vlan#95 P0 man-97-238.Reshall.Berkeley.EDU >
> > hal.Rescomp.Berkeley.EDU: icmp: echo reply
> >
> > 17:53:44.915163 802.1Q vlan#95 P0 802.1Q vlan#95 P0
> > man-97-238.Reshall.Berkeley.EDU > hal.Rescomp.Berkeley.EDU: icmp: echo
> > reply
> >
> > I'm pinging from a host called hal to the host man-97-238 (which is
> > sitting on a VLAN port).  Clearly, the ping gets routed all the way to
> > man-97-238 just fine, since it gets it & responds.  But the response,
> > comming in on VLAN#95 (the third packet above) and supposedly going to
> > fxp0, instead has ANOTHER "802.1Q vlan#95 P0" tag attached.
> >
> > Needless to say, this prevents man-97-238 from communicating with the
> > outside world.
> >
> > The Linux people say that for THEIR version of the VLAN driver, there
> > exists an option to remove this header, just the way I want.  But I can't
> > find any info for such options in NetBSD.
> >
> > This seems to be a bug...  Or do I have something misconfigured?  Any help
> > most appreciated!
>
> Please post your configurations.
>
> --
> Manuel Bouyer <bouyer@antioche.eu.org>
>      NetBSD: 23 ans d'experience feront toujours la difference
> --
>