Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    2.2 LAN over LACP not showing in Traffic Shaper Interfaces

    Scheduled Pinned Locked Moved Traffic Shaping
    6 Posts 3 Posters 1.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      CoinTos
      last edited by

      Hi,

      Just installed a fresh copy of pfsense 2.2 and my LAN interface is not showing in the Traffic shaper interfaces. The LAN is setup over LACP LAGG, and there are 2 vlans on it. The 2 vlans show in the traffic shaper but not the LAN itself.

      Right now I have under the traffic shaper interfaces:
      WAN
      WAN2
      VLAN11
      VLAN31

      So this now begs the question, what I have setup wrong?

      1 Reply Last reply Reply Quote 0
      • C
        CoinTos
        last edited by

        So I restored my 2.1.5 backup as nothing I have tried on the fresh 2.2 config has worked. It restored all the queues for the interfaces but the LAN interface doesn't get any thing in it. All zeros. This is a supermicro server board with a INTEL PRO/1000 4 port gigabit onboard, so if it worked before I am guessing it is a driver change from the freebsd 8.3 to 10.1 base change.

        Does anybody have VLAN over there LAN (router on a stick) working with shaping without any form of lagg? That is my next attempt to remove the LACP, otherwise it's back to 2.1.5, the land of things working… till I get a plan on tackling it again.

        Thanks in advance.

        1 Reply Last reply Reply Quote 0
        • P
          pocket_geek
          last edited by

          I have 2.1.5 running on an Intel NUC plus managed switch as a router on a stick.  Traffic shaping works on all interfaces including vlan interfaces.  I've tested 2.2 and all but Layer7 seem to work in this configuration as well.

          I have not tested LAGG interfaces.

          1 Reply Last reply Reply Quote 0
          • C
            CoinTos
            last edited by

            Thanks for the reply pocket_geek, that is good news.

            So if I have fallback to no LAGG which isn't the end of the world, I now know of a router on a stick success with 2.2.

            Now, before I do this does anybody have any debugging tips that might help diagnose the reason why ALTQ doesn't like LAN over LACP but likes the VLANs on LAN over LACP, I am willing to try suggestion. If not, I will just dump it and revisit later.

            1 Reply Last reply Reply Quote 0
            • jahonixJ
              jahonix
              last edited by

              This might be related?

              1 Reply Last reply Reply Quote 0
              • C
                CoinTos
                last edited by

                Thanks jahonix, just tried turning strict off via that link and no change.
                Might have to retreat back to 2.1.5 anyways, openvpn is proving too flacky with my devices.

                Edit:
                Due to time constraints I have gone back to 2.1.5, I have not given up on 2.2 but will tackle this and my openvpn issues at a later day. Thanks you developers for your awesome backup and restore utility this was fun adventure, so no complaints from me. Thanks again for all who read and tried to help me figure it out.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.