Thanks for all the clarifications. Regards, Pranjal On 6/7/06, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: > > Peter Stuge wrote: > > On Tue, Jun 06, 2006 at 09:45:38AM -0700, Stephen Hemminger wrote: > > > >>>In Linux implememtation a bridge means a broadcast domain, so for > >>>example if I need to support all 4096 vlans then I need to create > >>>4096 bridging entities and attach the specific subports like > >>>eth01.2, eth01.3 etc to bridge for that vlan. > > > > > > To clarify further, if you want to bridge all VLANs on eth0 with eth1 > > just add eth0 and eth1 to the bridge. But that will assume that all > > VIDs are the same on both ports. > > > > If eth0.2 should be bridged with eth1.3 and so on, then you will need > > one bridge per VLAN. Remember to set: > > vconfig set_name_type DEV_PLUS_VID_NO_PAD > > > > ..if it isn't already set. > > > > ..and what happened to the vconfig set_bind_mode option that was > > required for this? (Or did PER_DEVICE become the default, I seem to > > recall this being the case?) > > VLAN always uses the BIND_PER_DEVICE behaviour now. > > Ben > > > > > > > //Peter > > _______________________________________________ > > Vlan mailing list > > Vlan@xxxxxxxxxxxxxxxxxxx > > http://www.candelatech.com/mailman/listinfo/vlan > > > > > -- > Ben Greear <greearb@xxxxxxxxxxxxxxx> > Candela Technologies Inc http://www.candelatech.com > > _______________________________________________ > Vlan mailing list > Vlan@xxxxxxxxxxxxxxxxxxx > http://www.candelatech.com/mailman/listinfo/vlan > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://ns2.lanforge.com/pipermail/vlan/attachments/20060609/f8da8c60/attachment.html
