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

    What causes Wan "Error in"?

    Scheduled Pinned Locked Moved Hardware
    20 Posts 3 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.
    • L
      LoGman @stephenw10
      last edited by

      @stephenw10

      Yeah, I did each test one by one.

      I did Check Flow Control is Off on the switch

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

        Then you should disable it in pfSense for that interface. Or enable it in the switch.
        https://docs.netgate.com/pfsense/en/latest/hardware/tune.html#flow-control

        Steve

        L 1 Reply Last reply Reply Quote 0
        • L
          LoGman @stephenw10
          last edited by

          @stephenw10

          I disabled it to see if the problem is fixed.

          M 1 Reply Last reply Reply Quote 0
          • M
            MoonKnight @LoGman
            last edited by

            @logman
            Or maybe try it without your switch. Connect your computer directly to your pfSense LAN ports and run the tests again

            --- 24.11 ---
            Intel(R) Xeon(R) CPU D-1518 @ 2.20GHz
            Kingston DDR4 2666MHz 16GB ECC
            2 x HyperX Fury SSD 120GB (ZFS-mirror)
            2 x Intel i210 (ports)
            4 x Intel i350 (ports)

            L 1 Reply Last reply Reply Quote 0
            • L
              LoGman @MoonKnight
              last edited by LoGman

              @moonknight
              Already Done that.


              @stephenw10

              ~5h

              Only CRC errors

              [WAN] sysctl dev.ix.0 | grep "miss\|errs"
              dev.ix.0.mac_stats.checksum_errs: 12
              dev.ix.0.mac_stats.rx_missed_packets: 6468
              dev.ix.0.mac_stats.rec_len_errs: 0
              dev.ix.0.mac_stats.byte_errs: 0
              dev.ix.0.mac_stats.ill_errs: 0
              dev.ix.0.mac_stats.crc_errs: 0
              dev.ix.0.mac_stats.rx_errs: 6480
              

              Interface_time_0.42.PNG

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

                Ah, so good after the flow-control change?

                L 1 Reply Last reply Reply Quote 0
                • L
                  LoGman @stephenw10
                  last edited by

                  @stephenw10

                  Yes, when flow-control is disabled no anymore "missed packets" only "checksum errors".

                  [WAN] sysctl dev.ix.0 | grep "miss\|errs"
                  dev.ix.0.mac_stats.checksum_errs: 279
                  dev.ix.0.mac_stats.rx_missed_packets: 6468
                  dev.ix.0.mac_stats.rec_len_errs: 0
                  dev.ix.0.mac_stats.byte_errs: 0
                  dev.ix.0.mac_stats.ill_errs: 0
                  dev.ix.0.mac_stats.crc_errs: 0
                  dev.ix.0.mac_stats.rx_errs: 6747
                  

                  2.5.2022.PNG

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

                    Ok, so to be clear when it was logging missed packets flow control was on in pfSense but off in the switch?

                    That would make sense if pfSense was sending the 'stop sending' packets and the switch ignored it and kept sending.

                    Steve

                    L 1 Reply Last reply Reply Quote 0
                    • L
                      LoGman @stephenw10
                      last edited by

                      @stephenw10
                      Yeah, it was on as default.

                      1 Reply Last reply Reply Quote 1
                      • L
                        LoGman
                        last edited by LoGman

                        Why is Flow-control not persistent when set in "System Tunables"
                        Reboot FC gone.PNG

                        Reboot and settings again wrong.

                        Is this the only way?

                        So the correct way is "file: /boot/loader.conf.local hw.ix.flow_control="0" ?

                        And this Is not the correct way? 
                        /boot/loader.conf.local:
                        dev.ix.0.fc="0"
                        dev.ix.1.fc="0"
                        dev.ix.2.fc="0"
                        dev.ix.3.fc="0"
                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          You can set: hw.ix.flow_control=0 as a loader variable and it will apply the default to all ix NICs.

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