Link Aggregation Groups (LAG)

Follow

Comments

10 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
  • Avatar
    thernus

    I am trying to setup a LAG between FWG and SXR80 (Netgear SXK80 pair in bridge mode) and cant seem to get it work.

    I have the LAG group setup on the FWG across port 1 and 2 with VLAN's

    I have the SXR80 port 1 and 2 'bound' using the default trunk mode

    If I have one cable plugged in from the FWG to the SXR80 it works

    As soon as I plug in the second uplink cable from the FWG to the second bound port on the SXR80 it drops off.

    The SXK80 manual states - '802.3ad link aggregation for static LAGs' so I am thinking its not compatible, is the only way to have LAG working is to put in a switch between the FWG and SXR80 that supports LACP for the FWG and then Static LAG for SXK80 or am I missing something obvious?

    0
    Comment actions Permalink
  • Avatar
    Hoby Brenner

    Is there any chance that LAG and Bridge mode could work together?  Is there a technical limitation?  It would be nice for a bit more speed in inter-vlan routing.

    0
    Comment actions Permalink
  • Avatar
    Nathan Deleon

    I have an L3 switch and want to LAG all 4 ports on my gold unit together so my WAN can go through the switch isolated to my FW to filter and watch everything, but the app limits me to a maximum of 3 ports to be LAG'ed together. Why is it limited to 3? I want four to work with VLANS to make everything work and get the maximum throughput. 

    1
    Comment actions Permalink

Please sign in to leave a comment.