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

    Pfctl: igb0: driver does not support altq

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    9 Posts 5 Posters 3.9k 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.
    • L
      lboregard
      last edited by

      hi, i tried 2.2, but had to revert to 2.1.4, because of the following error

      there were error(s) loading the rules: pfctl: igb0: driver does not support altq - The line in question reads '[0']:

      i have hsfc traffic shaping set up with 2.1.4

      hopefully, you can look into this

      thanks in advance

      1 Reply Last reply Reply Quote 0
      • Raul RamosR
        Raul Ramos
        last edited by

        Have you Vlans and shaping enable?

        Probably the same problem on this thread  https://forum.pfsense.org/index.php?topic=78975.0.

        pfSense:
        ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
        Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
        NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

        1 Reply Last reply Reply Quote 0
        • L
          lboregard
          last edited by

          i dont have vlans, but i do have traffic shaping enabled

          by the way, it's running on a1sam-2550f-O supermicro motherboard.

          1 Reply Last reply Reply Quote 0
          • J
            jeffrapp
            last edited by

            @mais_um:

            Have you Vlans and shaping enable?

            Probably the same problem on this thread  https://forum.pfsense.org/index.php?topic=78975.0.

            It may be related, but it seems like a totally different thing.  I'm seeing the same problem, and no VLANs are defined.  Just a single WAN and LAN that I'm trying to enable traffic shaper on.

            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

              It's a similar issue but different root cause, fixing one would not solve the other.

              VLANs are missing ALTQ support in FreeBSD entirely, our patches add in support, but they do not work properly on 2.2 yet.

              The igb driver has ALTQ support but only when build a certain special way, which apparently isn't happening properly. If there is not a bug entry for that on https://redmine.pfsense.org/ please open a new bug report there about this.

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

              1 Reply Last reply Reply Quote 0
              • J
                jeffrapp
                last edited by

                Bug filed: https://redmine.pfsense.org/issues/3770

                1 Reply Last reply Reply Quote 0
                • L
                  lboregard
                  last edited by

                  hi, i was reading a bit more about this issue and i've seen references a good couple of years back.

                  from what i gather i recollect it has to do with both the freebsd version and the igb driver being used.

                  this has me wondering .. is the change to freebsd 10 enough to solve the altq issue ? i mean does the igb driver that ships with freebsd 10 support altq ?

                  i'm asking because im suffering packet loss … i've read posts about disabling hardware LRO (which i tried but didn't seem to make a difference) and TSO (which im trying now).

                  i'd just like to know how to move forward with the packet loss issue im facing.

                  1 Reply Last reply Reply Quote 0
                  • L
                    lboregard
                    last edited by

                    i need to tell that disabling TSO made a world of difference.

                    no packet loss manifestations (knock on wood)

                    i can happily live with 2.1.4 for the foreseeable future :)

                    1 Reply Last reply Reply Quote 0
                    • E
                      eri--
                      last edited by

                      It should be fixed on coming snaps.

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