Bridging a 802.1Q VLAN-Trunk

From: Matthias Schuendehuette (msch_at_snafu.de)
Date: 01/24/04

  • Next message: Guohan Lu: "Bad "bad" retransmit recovery in TCP" 
    To: freebsd-net@freebsd.org
Date: Sat, 24 Jan 2004 19:46:00 +0100

    Hello,

    I have some difficulties to understand the bridge(4) man-page.

    I want to build a filtering bridge between two 802.1Q VLAN-Trunk
    interfaces and in the meantime I assume that I make some mistakes
    configuring the bridge...

    Actually I configured the bridge (for one VLAN only as an example)
    "bge0:1,bge1:1,vlan0:2,vlan1:2", where 'vlan0' has the parent interface
    'bge0' and the same for index 1. But I'm uncertain, if this is correct.

    First, the man-page says, "By putting both physical and logical
    (vlan(4)) interfaces in the same cluster, a FreeBSD box can also
    implement what in commercial terms is called a ``trunk'' interface."

    I understand this as "bge0:1,bge1:1,vlan0:1,vlan1:1,...."
    Does this keep the several VLANs isolated from each other?
    Have the parent interfaces to be in there?
    Why?

    Or is my original configuration correct to put each VLANs vlan(4)
    interfaces in their own cluster? Again, have the parent interfaces to
    have their own cluster? Have they to appear anyway? In an example in
    bridge(4) I read they must not appear to avoid loops...

    I must admit, I'm a bit confused :-}

    Can anybody explain this more clearly to me?

    Thanks a lot - Matthias 

    -- 
Ciao/BSD - Matthias
Matthias Schuendehuette	<msch [at] snafu.de>, Berlin (Germany)
PGP-Key at <pgp.mit.edu> and <wwwkeys.de.pgp.net> ID: 0xDDFB0A5F
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
  • Next message: Guohan Lu: "Bad "bad" retransmit recovery in TCP"

    Relevant Pages

    • Re: distributed bridging [script]
      ... >> I'm trying to create a configuration that would bridge interfaces on ... Each host would have at least two interfaces, ... here's a completely untested script. ...
      (freebsd-net)
    • Re: bridge with access on both interfaces
      ... >>'inside' and 'outside' IPs separately on each bridge interface, ... Some tcpdumps on both in and outside interfaces suggest an ARP ... > If you want to use IP while bridging, ... and net4801 is that the 3 ethernet controllers now share one interrupt. ...
      (freebsd-net)
    • [BUG][debian-2.6.20-1-686] bridging + vlans + "vconfig rem" == stuck kernel
      ... I've managed to fairly reliably trigger a deadlock in some portion of the linux networking code on my Debian test box. ... I'm pretty sure that it's a race condition of some sort as it doesn't trigger if I ifdown the interfaces one by one, but if I run "ifdown -a" then it triggers halfway through reliably. ... Just for a bit of background on why this is so complex: When I get this networking problem sorted out I'm going to set up heartbeat and a dummy "world1" interface with a shared MAC which is added to the "world" bridge when the current system is the DHCP-client master. ...
      (Linux-Kernel)
    • Re: IPS-Builder
      ... I' d like to share with all, this script made by me based on root0 ... You need 3 network interfaces (One for management and two for the bridge) ... -This have a management interface. ...
      (Focus-IDS)
    • Re: FREEBSD between two trunks
      ... > interfaces without bridging parents - do not forget to put parent in up ... What I was thinking he was going to due was not bridge the vlans ... packets just as any other normal packet.. ...
      (freebsd-net)