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

    Igb & altq

    Scheduled Pinned Locked Moved 2.1.1 Snapshot Feedback and Problems - RETIRED
    15 Posts 4 Posters 3.4k 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.
    • J
      jasonlitka
      last edited by

      I suspect the troubles have more to do with FreeBSD 8.x.  We're not exactly talking about the newest code here (FreeBSD 8.0 was originally released in late 2009) and I'm pretty sure that the newest drivers were backported from ones Intel wrote for FreeBSD 9.x and 10.x.  I think most of the issues we've been having with the newer Intel parts will go away with pfSense 2.2.

      I can break anything.

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

        The next snapshots should be fine with regards to ALTQ and the new drivers imported.

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

          @ermal:

          The next snapshots should be fine with regards to ALTQ and the new drivers imported.

          Great. Is there a specific date I should be looking for on the snapshot or are they ready now?

          I can break anything.

          1 Reply Last reply Reply Quote 0
          • A
            adam65535
            last edited by

            Thanks ermal.  Will new installations with igb have to change something to get altq to work or will the default work?

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

              @Jason:

              @ermal:

              The next snapshots should be fine with regards to ALTQ and the new drivers imported.

              Great. Is there a specific date I should be looking for on the snapshot or are they ready now?

              There is a set that is uploading now that is from just before his change. The next set after this will be fixed.

              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
              • E
                eri--
                last edited by

                No tweaking as expected.
                Next coming snapshot should have it.

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

                  @jimp:

                  @Jason:

                  @ermal:

                  The next snapshots should be fine with regards to ALTQ and the new drivers imported.

                  Great. Is there a specific date I should be looking for on the snapshot or are they ready now?

                  There is a set that is uploading now that is from just before his change. The next set after this will be fixed.

                  Great, thanks guys.  I'll give it a try on my backup box as soon as I see the next snapshot.

                  I can break anything.

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

                    I just installed the latest snapshot and altq works.  I didn't lose the multiple queues in the process either so I think this is a win-win.  Now I just need 2.1.1 to go gold so I can upgrade my master system as well as my backup and bring up some 10Gbe goodness.

                    I can break anything.

                    1 Reply Last reply Reply Quote 0
                    • A
                      adam65535
                      last edited by

                      I also upgraded a non critical but used heavily cluster yesterday.  I upgraded the backup member yesterday to…

                      2.1.1-PRERELEASE (amd64)
                      built on Wed Jan 22 16:56:12 EST 2014
                      FreeBSD 8.3-RELEASE-p14

                      and no issues for a day and altq still worked.  I upgraded the primary about 3 hours ago which got the 23rd snapshot.  No issues but I upgraded them from an old 2.1.0 RC1 candidate from several months ago.

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

                        @adam65535:

                        I also upgraded a non critical but used heavily cluster yesterday.  I upgraded the backup member yesterday to…

                        2.1.1-PRERELEASE (amd64)
                        built on Wed Jan 22 16:56:12 EST 2014
                        FreeBSD 8.3-RELEASE-p14

                        and no issues for a day and altq still worked.  I upgraded the primary about 3 hours ago which got the 23rd snapshot.  No issues but I upgraded them from an old 2.1.0 RC1 candidate from several months ago.

                        You're running both members of a production cluster on 2.1.1 snapshots?  I ask because I've had a few instaboots on my backup box.

                        I can break anything.

                        1 Reply Last reply Reply Quote 0
                        • A
                          adam65535
                          last edited by

                          I had 1 cluster member on 1.2.1 prerelease and the other on 1.2.0 RC1 for about a day with the backup (1.2.1) as master.  I just upgraded both to 1.2.1 pre-release.  We will see how it goes.

                          This network doesn't have any complex configuration but I do use it to test new things I want to use in other production environments.  It is mainly to offload web traffic to a cable modem and some other non-critical uses that does stress the connection at times.  I have redundancies built into the proxy setup I implemented internally so that any downtime will shift the traffic to the production internet connection within about 10 seconds of web requests timing out (perl script that runs constantly and switches out proxy configs to a backup link if it fails).

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