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

    Intel igb optimizations (EEE)

    Scheduled Pinned Locked Moved General pfSense Questions
    23 Posts 6 Posters 2.5k 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.
    • P
      Panja
      last edited by

      Is it still advised on pfSense v2.6 to add the following to the (System) Tunables:
      dev.igb.0.eee_disabled=1
      dev.igb.1.eee_disabled=1
      dev.igb.2.eee_disabled=1
      dev.igb.3.eee_disabled=1

      I'm using a 4 port igb NIC.

      Is this still needed or is it obsolete now?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        No, you should not need to do that. We don't set that on anything we ship with igb ports.

        That OID is now obsolete replaced by dev.igb.X.eee_control and that is set to 1 by default.

        Steve

        P 4 2 Replies Last reply Reply Quote 1
        • P
          Panja @stephenw10
          last edited by

          @stephenw10 Thanks!
          eee_control can not be found in system tunables, is that correct?

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Yes.

            P 1 Reply Last reply Reply Quote 0
            • P
              Panja @stephenw10
              last edited by

              Many thanks!

              1 Reply Last reply Reply Quote 0
              • 4
                4o4rh @stephenw10
                last edited by

                @stephenw10 "1" should be disabled but i can't find the "dev.igb.X.eee_control" setting documented anywhere.

                Freebsd lists it as "hw.em.eee_setting" with default as 1 for disabled

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  If you run sysctl -d dev.igb.0.eee_control you should get a decription of the value. I don't have access to anything to test it on right now.

                  4 1 Reply Last reply Reply Quote 0
                  • 4
                    4o4rh @stephenw10
                    last edited by 4o4rh

                    @stephenw10 said in Intel igb optimizations (EEE):

                    If you run sysctl -d dev.igb.0.eee_control you should get a decription of the value. I don't have access to anything to test it on right now.

                    yes: "dev.igb.0.eee_control: Disable Energy Efficient Ethernet" - but doesn't tell you if a 1 or a 0. I suppose common sense says true to "disable" but i am only curious why it is not consistent with the freebsd for 14 which has eee_setting

                    p.s. I understand that I should have TSO and LRO disabled, but what about checksum offloading? I have 8x I211 in a headless qotom. Is it safe to hw checksum offload?

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      One is em and the other is igb.

                      4 1 Reply Last reply Reply Quote 0
                      • 4
                        4o4rh @stephenw10
                        last edited by

                        @stephenw10 is it ok to enable hw checksum offloading, while leaving tso and lro disabled?

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Yes, any of the hardware off-loading options can be enabled individually. They are usually not of much benefit when forwarding packets though.

                          1 Reply Last reply Reply Quote 1
                          • A
                            axot
                            last edited by axot

                            Hi, I’m noticing link state changes with my Intel 211 card. Any advice on troubleshooting or workarounds? Thanks.

                            Oct 23 13:10:15 gw kernel: igb0: link state changed to DOWN
                            Oct 23 13:10:19 gw kernel: igb0: link state changed to UP
                            Oct 23 15:39:32 gw kernel: igb0: link state changed to DOWN
                            Oct 23 15:39:36 gw kernel: igb0: link state changed to UP
                            Oct 23 19:46:59 gw kernel: igb3: link state changed to DOWN
                            Oct 23 21:16:56 gw kernel: igb3: link state changed to UP

                            Version
                            2.7.2-RELEASE (amd64)
                            built on Sat Dec 9 5:55:00 JST 2023
                            FreeBSD 14.0-CURRENT

                            GertjanG 1 Reply Last reply Reply Quote 0
                            • GertjanG
                              Gertjan @axot
                              last edited by

                              @axot

                              Could be explained by a power dip that didn't really reach your pfSense, but did had an effect on the device attached to igb0 and igb3.

                              No "help me" PM's please. Use the forum, the community will thank you.
                              Edit : and where are the logs ??

                              A 1 Reply Last reply Reply Quote 0
                              • A
                                axot @Gertjan
                                last edited by

                                @Gertjan Thanks for the reply, How can I verify if a power dip is the cause? It seems that igb1 and igb2 have far fewer link state DOWN logs.

                                GertjanG 1 Reply Last reply Reply Quote 0
                                • GertjanG
                                  Gertjan @axot
                                  last edited by

                                  @axot

                                  Your pfSense usies an operating system (FreeBSD) with an (over) complex filesystem.
                                  Like your PC (any OS) or MAC. removing the power (cable) can create major issues in the file system.
                                  That's why 'mission' critical devices like your coffee machine an Internet access device are always fed by an UPS that filters out all power issues.
                                  I said all this so you now also have a way to see if there were any power issues : the UPS will signal this.
                                  And saving your devices while doing so.

                                  The connected devices to the pfSense on all your NICs are generally always switches (nad not end user devices), so hook these up to the UPS also and you'll never see any LINK UP/DOWN again.

                                  You still see them ? Then, for every interface, on each side of the wire, change the NIC.
                                  Or, it can happen : change the network cable.
                                  Or tell the kids to stop pulling cables.

                                  It can happen, NICs (cables) can go bad, but the chance you see two of them failing at the same moment ? No way.

                                  No "help me" PM's please. Use the forum, the community will thank you.
                                  Edit : and where are the logs ??

                                  A 1 Reply Last reply Reply Quote 1
                                  • A
                                    axot @Gertjan
                                    last edited by

                                    @Gertjan Thank you for pointing that out. I didn't even consider a power issue as a possible cause for the problem. Given that both NICs are experiencing the same issue, the possibility of a power issue seems more likely. Let me give it a try.

                                    1 Reply Last reply Reply Quote 0
                                    • stephenw10S
                                      stephenw10 Netgate Administrator
                                      last edited by

                                      What are those NICs connected to? Are those devices also showing the link go down? Are they rebooting?

                                      The time between those link change logs doesn't really look like flapping.

                                      A 1 Reply Last reply Reply Quote 0
                                      • A
                                        axot @stephenw10
                                        last edited by axot

                                        @stephenw10 Hi, here are the connections for each NIC, I’ve also tried changing the cable on igb0, but the issue persists.

                                        igb0: Connected to the ONU (PR-600MI)
                                        igb1: Connected to a WiFI Router
                                        igb2: Connected to NAS (can be woken up via magic packet and goes to sleep when inactive)
                                        igb3: Connected to Mac Studio (wakes up from sleep when needed)

                                        More Logs,
                                        Oct 25 17:07:08 gw kernel: igb2: link state changed to DOWN
                                        Oct 25 17:07:08 gw kernel: igb0: link state changed to DOWN
                                        Oct 25 17:07:15 gw kernel: igb0: link state changed to UP
                                        Oct 25 17:07:19 gw kernel: igb0: link state changed to DOWN
                                        Oct 25 17:07:33 gw kernel: igb0: link state changed to UP
                                        Oct 25 17:34:37 gw kernel: igb2: link state changed to UP
                                        Oct 26 00:26:59 gw kernel: igb0: link state changed to DOWN
                                        Oct 26 00:27:03 gw kernel: igb0: link state changed to UP
                                        Oct 26 11:59:35 gw kernel: igb0: link state changed to DOWN
                                        Oct 26 11:59:39 gw kernel: igb0: link state changed to UP
                                        Oct 26 12:37:45 gw kernel: igb0: link state changed to DOWN
                                        Oct 26 12:37:49 gw kernel: igb0: link state changed to UP
                                        Oct 26 14:00:45 gw kernel: igb0: link state changed to DOWN
                                        Oct 26 14:00:48 gw kernel: igb0: link state changed to UP

                                        A GertjanG 2 Replies Last reply Reply Quote 0
                                        • A
                                          axot @axot
                                          last edited by

                                          Unfortunately, my pfsense router won’t power on. I need to buy a new one. Can you recommend a stable brand that won’t break the bank? Thanks.

                                          N 1 Reply Last reply Reply Quote 0
                                          • N
                                            nimrod @axot
                                            last edited by

                                            @axot said in Intel igb optimizations (EEE):

                                            Unfortunately, my pfsense router won’t power on. I need to buy a new one. Can you recommend a stable brand that won’t break the bank? Thanks.

                                            Protectli.

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