Vlan on lagg doesnt# work



  • we have have 4 network cards. we have group it by lagg mit mode fail over (later lacp). on lagg0 we have create different vlans. the clans interfaces are down, because parent interface are <none>.

    
    lagg0_vlan504: flags=8803 <up,broadcast,simplex,multicast>metric 0 mtu 1500
    	options=103 <rxcsum,txcsum,tso4>ether 00:00:00:00:00:00
    	inet6 fe80::221:9bff:fefd:2449%lagg0_vlan504 prefixlen 64 scopeid 0xf
    	inet 10.254.34.2 netmask 0xffffff00 broadcast 10.254.34.255
    	nd6 options=1 <performnud>vlan: 0 vlanpcp: 0 parent interface: <none>lagg0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
    	options=401bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,vlan_hwtso>ether 00:1b:21:9f:ca:f0
    	inet6 fe80::21b:21ff:fe9f:caf0%lagg0 prefixlen 64 scopeid 0xb
    	nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect
    	status: no carrier
    	laggproto failover
    	laggport: igb3 flags=0<>
    	laggport: igb2 flags=0<>
    	laggport: igb1 flags=0<>
    	laggport: igb0 flags=1 <master></master></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4,vlan_hwtso></up,broadcast,running,simplex,multicast></none></performnud></rxcsum,txcsum,tso4></up,broadcast,simplex,multicast> 
    

    any idea?</none>


  • Rebel Alliance Developer Netgate

    I've seen lagg+vlan working on numerous customer configs on 2.0.x and 2.1.

    What is the date on the 2.1 image you're running?

    Did you just configure the VLANs?

    Do they stay broken even after a reboot?



  • This does not seem good

    
    status: no carrier
    
    


  • at the moment it works. i didn't know if the update to the latest build does fix or the reboot of both firewalls.

    it is possible that the problem exists if we change something on lagg and you need every time a reboot after such changes?


  • Rebel Alliance Developer Netgate

    I've never seen that required for lagg in general. Unless it's a problem specific to the failover mode, it's not likely a general issue.
    At least with LACP, which is the most common, it usually just works without any fuss.