28.04.2018 12:49, Abdullah Tariq wrote: You still top-posting. Please don't.
> > And please do not top-post and reply to the list, not privately. > Thank you. > > sorry for that. > > They do but that's not what you need. You deal with untagged frames > on igb5, > > so do not create any vlan on top on igb5 but use it directly: > > ifconfig bridge10 create addm igb5 addm vlan3 up > > so if i need 2 ports with same vlan tags to communicate with each other > > i create 2 bridges > > ifconfig vlan2 create vlan 5 vlandev igb5 > > ifconfig vlan3 create vlan 5 vlandev igb6 > > ifconfig bridge10 create addm igb5 addm vlan3 up > > ifconfig bridge11 create addm igb6 addm vlan2 up > > is this the right way? > No. If you have two ports that should carry untagged frames and form > single vlan > and this vlan has no other ports carrying tagged frames, then > this vlan effectively has *no* tag number, or better say, its tag number > does not matter. > In that case, do not create any vlan interfaces for the vlan at all but > bridge ports directly: > ifconfig bridge10 addm igb5 addm igb6 > So it is not possible to replicate behaviour of standard L2 switches > using freebsd where we have different VLANs, access and trunk ports? It is possible to replicate *behaviour* but not configuration style. Unless you have real embedded switching chip in your system like many ARM or MIPS-based routers do, in which case you can use etherswitch(4) and etherswitchcfg(8) to create vlans and configure ports of such chip similar to L2 switches. _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
