On 28/4/18 8:28 pm, Eugene Grosbein wrote:
28.04.2018 19:10, Abdullah Tariq wrote:
However, we still have several ways to bridge tagged traffic
by means of creation multiple bridges (one per vlan) or using
ng_vlan+ng_bridge to do the same.
bridge1 will contain vlan 1
bridge2 will containn vlan2
and bridge3 should have bridge1 and bridge2?
No, its simplier: single bridge contains all interfaces corresponting to ports
of single vlan.
You can bridge plain igb* interfaces for untagged ports; or bridge interface
igbX with interface vlanY
when one port carries untagged frames of vlan and another ports carries tagged
frames of the same vlan;
or bridge interface vlans together when all of them carry tagged frames of the
vlan.
If not, can you please give some instructions/guidelines for
ng_vlan+ng_bridge?
I still think you should not dive into building complex netgraph structures
while the task can be solved simplier. But if you want to take that path, start
by
reading man ng_vlan, man ng_ether, man ng_bridge and man ng_eiface and try
examples therein.
and read this:
https://people.freebsd.org/~julian/netgraph.html
_______________________________________________
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"
_______________________________________________
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"
