Dajka Tamas [dajka.ta...@upc.hu] wrote: > Assigning one of the phys devices as vlandev to a vlan is not working. I > mean, I can assign to them, but if vlan40 is assigned to hme2 and hme2 > failes, than vlan40 will be down and hosts in vlan40 are unreacheable. > > So: > > ifconfig hme2 up > ifconfig hme3 up > > ifconfig vlan40 create > ifconfig vlan40 vlandev hme2 > ifconfig vlan40 inet 192.168.240.1 255.255.255.0 > ifconfig vlan40 up > > ifconfig bridge1 create > ifconfig bridge1 add vlan40 > ifconfig bridge1 add hme2 > ifconfig bridge1 add hme3 > > ifconfig bridge1 stp hme2 > ifconfig bridge1 stp hme3 > ifconfig bridge1 stp vlan40 > ifconfig bridge1 spanpriority 61400 # avoid being the root bridge > ifconfig bridge1 up > > is not working :( > > I want a solution, what is working with just one VLAN, so the VLAN is not > dependent ont he phys interface. In your solution, if I don't pull up vlan41, > than hme3 won't be in the bridge. >
This makes no sense. You don't add hme2 and vlan40(parent vlan2) to the same bridge. That's crazy talk, boy. The trunk interface handles redundancy across NICs if that is your end goal. You could use the failover or lacp options depending on the capability of your switch. Unfortunately I'm not sure that the vlan driver can easily layer on top of trunk, a few tweaks may be required to make it work properly unless it mirrors if_capabilities from the parent interface (which isn't clear to me after quickly paging through if_trunk.c). I'm not sure that you are solving the right problem by asking for redundancy across NICs. You are probably better served by asking for redundancy across boxes using CARP and PFSYNC and multiple firewalls
