LAGG LACP Behavior Change



  • Hello,

    i have upgraded pfsense to
    2.2.4-RELEASE (amd64)
    built on Sat Jul 25 19:57:37 CDT 2015
    FreeBSD 10.1-RELEASE-p15

    but i am facing problem with LACP.

    my switch (that was working prior this changes) probably doesnt' support LACP strict, but if
    i put the sysctl modify proposed here
    (net.link.lagg.0.lacp.lacp_strict_mode)
    https://doc.pfsense.org/index.php/Upgrade_Guide#LAGG_LACP_Behavior_Change

    at reboot this option doesn't get kept.
    can you please give me some information about that?


  • Banned

    You put it where?



  • i have upgraded pfsense to
    2.2.4-RELEASE (amd64)
    built on Sat Jul 25 19:57:37 CDT 2015
    FreeBSD 10.1-RELEASE-p15

    Congratulations!

    but i am facing problem with LACP.

    ??? Would this perhaps help you out with the right information?
    LAGG (LACP) Behavior Change
    LAGG LACP defaults to strict mode in FreeBSD >= 10

    my switch (that was working prior this changes) probably doesnt' support LACP strict,

    There are two different ways to set up a LAG (Link Aggregation Group)

    • dynamic LAGs automatically using the LACP (Link Aggregation Control Protocol)
    • static LAGs manually using "setting up" the LAG right and fully identically on both sides by hand
      Which mode your Switch is supporting?

    but if i put the sysctl modify proposed here
    (net.link.lagg.0.lacp.lacp_strict_mode)
    https://doc.pfsense.org/index.php/Upgrade_Guide#LAGG_LACP_Behavior_Change

    Ok you where now having created a so called work around to get your switch with limited LAG
    capabilities or functions working, is this correct?

    But did you also create a /boot/loader.conf.local file to store this informations for the next pfSense
    update or upgrade process? Because then all files will be new written and created and your small
    work around is gone! but if you were creating a loader.con.local file there are not gone!

    at reboot this option doesn't get kept.

    For sure! You are changing something at the system and this changes will be persist, for sure,
    it is a must be because after a reboot no one want to set it up once more and more and more again!

    can you please give me some information about that?

    The update or upgrade process will be write all or many files new! So that the former information is
    not there after this process. Create a /boot/loader.conf.local and put all the changes you made there in
    and then after an upgrade of the whole pfSense system, do a reboot and all changes will be made once
    more again automatically.


Log in to reply