Link Aggregation Groups (LAG)

Follow

Comments

7 comments

  • Avatar
    Matt Niswonger

    When you say “All ports in a LAG must be assigned to the same network.”, does this mean that multiple networks configured as VLANs cannot be assigned to the same LAG?

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    This means if you use port 1 and port 2 as one LAG, then they can't be used by anything else. VLAN over LAG is supported on 1.9731 

    0
    Comment actions Permalink
  • Avatar
    Matt Niswonger

    This means if you use port 1 and port 2 as one LAG, then they can't be used by anything else. VLAN over LAG is supported on 1.9731 

    I'm still not clear on this.  I'm trying to get clarification on whether or not I can assign multiple networks that are setup as tagged VLANs on the Firewalla to the same LACP group like I can on a switch.  I route traffic across VLANs internally so I can inspect things between my primary trusted networks and my IoT network for example, and it would be advantageous to not be bottlenecked by a single interface (yes I know a single TCP stream won't span more than 1 physical port).

    0
    Comment actions Permalink
  • Avatar
    Support Team

    Yes, you will be able to assign multiple VLANs to the same LAG, but it requires box version 1.9731, which is currently in early access release. 

    0
    Comment actions Permalink
  • Avatar
    Joshua Wood

    Any ETA to stable relase. I set up VLANs last night assuming the Firewalla had LAG currently to be sadly disappointed :(

    0
    Comment actions Permalink
  • Avatar
    Joshua Wood

    Or, how do I get access to this build?

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    VLAN over LAG is now supported in 1.9731 release. As the time of this message, 1.9731 is in beta and hopefully soon be in production.

    0
    Comment actions Permalink

Please sign in to leave a comment.