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

[SOLVED] Errors In, but no Errors Out and No Collisions on both WAN

Scheduled Pinned Locked Moved Hardware
24 Posts 5 Posters 4.3k 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.
  • S
    Sergei_Shablovsky
    last edited by Sergei_Shablovsky Nov 17, 2021, 7:54 AM Nov 4, 2021, 6:08 AM

    Hi. pfSense Gurus!

    Recently see the Errors in errors on a WAN Statistic Dashboard.

    No “Errors Out” and no “Collisions”.

    Both WAN ports are on physically different NICs, and both WAN ports are Speed & Duplex forced, MTU 1350.

    —
    CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
    Help Ukraine to resist, save civilians people’s lives !
    (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

    G 1 Reply Last reply Nov 4, 2021, 1:32 PM Reply Quote 0
    • G
      Gertjan @Sergei_Shablovsky
      last edited by Gertjan Nov 4, 2021, 1:34 PM Nov 4, 2021, 1:32 PM

      @sergei_shablovsky

      Strange.
      I started to thinks that these erros/collisions were not shown any more, as I only have seen them being '0' :

      7f4bc75f-90be-4317-b780-348bb41e0e82-image.png

      What is a "Errors In" ? It's the result between the checksum present in the packet, put in there by the sending NIC, and the checksum build by the local driver (or NIC-chip).
      If "Errors Out" start to be non zero, then the drivers is adding wrong checksums to the packets ? ( ! )
      Or the driver knows that the packet will get altered further along on the line (in the future ?)
      Or is it the receiving NIC who sends back to our NIC that he sends packets with errors.

      "Error in" / "Error out" =
      Failing NIC chip,
      Failing Transceiver,
      Failing connector,
      Failing uplink cable(s)
      Failing upstream devices.
      And many other reasons.

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

      S 1 Reply Last reply Nov 5, 2021, 1:56 AM Reply Quote 1
      • S
        stephenw10 Netgate Administrator
        last edited by Nov 4, 2021, 2:29 PM

        How many errors? Out of how much total data?

        Has the WAN been disconnected at all?

        It's common to see some errors if the cable was removed or something upstream was rebooted etc. That's not normally a problem.

        Steve

        S 1 Reply Last reply Nov 5, 2021, 3:48 PM Reply Quote 1
        • S
          Sergei_Shablovsky @Gertjan
          last edited by Sergei_Shablovsky Nov 5, 2021, 1:59 AM Nov 5, 2021, 1:56 AM

          @gertjan said in Errors In, but no Errors Out and No Collisions on both WAN:

          @sergei_shablovsky

          Strange.
          I started to thinks that these erros/collisions were not shown any more, as I only have seen them being '0' :

          7f4bc75f-90be-4317-b780-348bb41e0e82-image.png

          What is a "Errors In" ? It's the result between the checksum present in the packet, put in there by the sending NIC, and the checksum build by the local driver (or NIC-chip).
          If "Errors Out" start to be non zero, then the drivers is adding wrong checksums to the packets ? ( ! )
          Or the driver knows that the packet will get altered further along on the line (in the future ?)
          Or is it the receiving NIC who sends back to our NIC that he sends packets with errors.

          Thank You for a beautiful explanation!
          Appreciate Your help here!

          "Error in" / "Error out" =
          Failing NIC chip,
          Failing Transceiver,
          Failing connector,

          Check all of this. Sure on 99,999% all are ok.

          But when coming to this stage

          Failing uplink cable(s)
          Failing upstream devices.

          and especially this stage

          And many other reasons.

          something interesting happened,- when ISP's engineer coming, I receive a lot of news from inside ISP's life:

          • recent engineer goes to another company due low income ;)
          • ISP's start to shorting the stuff because need to redirect financing on new applience and PR;
          • new youth(!) engineer come to site to exchange/upgrade ISP's applience, and of course because of lack of knowledge unable to properly upload and tuning settings on a applience, and no one from Service Dept able to help him;

          Due all of this my settings pushed to 100TX full-duplex on WANs interfaces on this pfSense become wrong and after setting to “100TX half-duplex” the numbers of “Errors In” dramatically reduced, but “Errors Out” and “Collisions” come in.

          When I try to set all WANs speed&control to “automatic”, physically link exist and up, but no DHCP received, so nothing working at all...

          —
          CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
          Help Ukraine to resist, save civilians people’s lives !
          (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

          1 Reply Last reply Reply Quote 0
          • S
            stephenw10 Netgate Administrator
            last edited by Nov 5, 2021, 12:29 PM

            If the ISP device you're connected to is set at fixed 100Mb you would need to match that setting in the pfSense NIC. If it's a 1G NIC and you leave it as auto-select it will fail to negotiate a link speed and fall back to it's default which it sounds like is 100M half-duplex.
            With that duplex mismatch you will certainly see errors/collisions.

            Steve

            1 Reply Last reply Reply Quote 1
            • S
              Sergei_Shablovsky @stephenw10
              last edited by Sergei_Shablovsky Nov 5, 2021, 3:50 PM Nov 5, 2021, 3:48 PM

              @stephenw10 said in Errors In, but no Errors Out and No Collisions on both WAN:

              How many errors? Out of how much total data?

              I reboot the system, and make some measurements. Please look:
              (data from pfSense GUI Status -> Interfaces)

              Uptime for this data 5h 20min.
              Network loading are quite small for this branch today. (Just nothing)

              WAN_1
              MTU
              1350
              Media
              100baseTX <half-duplex>
              In/out packets
              490641/359474 (541.09 MiB/33.24 MiB)
              In/out packets (pass)
              490641/359474 (541.09 MiB/33.24 MiB)
              In/out packets (block)
              4864/803 (663 KiB/144 KiB)
              In/out errors
              107/107
              Collisions
              56365

              WAN_2
              MTU
              1350
              Media
              100baseTX <half-duplex>
              In/out packets
              170677/150218 (101.52 MiB/13.74 MiB)
              In/out packets (pass)
              170677/150218 (101.52 MiB/13.74 MiB)
              In/out packets (block)
              4827/1650 (826 KiB/211 KiB)
              In/out errors
              14/14
              Collisions
              13684

              —
              CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
              Help Ukraine to resist, save civilians people’s lives !
              (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

              1 Reply Last reply Reply Quote 0
              • S
                stephenw10 Netgate Administrator
                last edited by Nov 5, 2021, 4:04 PM

                Yeah, you can't have that running at half-duplex. The number of collisions there are expected in that situation.

                S 1 Reply Last reply Nov 5, 2021, 9:21 PM Reply Quote 1
                • S
                  Sergei_Shablovsky @stephenw10
                  last edited by Sergei_Shablovsky Nov 5, 2021, 9:57 PM Nov 5, 2021, 9:21 PM

                  @stephenw10 said in Errors In, but no Errors Out and No Collisions on both WAN:

                  Yeah, you can't have that running at half-duplex. The number of collisions there are expected in that situation.

                  Stephen, thank You for patience! ;)

                  So, I doing some tests and here the result:

                  Both WANs (mean 1st port on each of NICs) set in pfSense In Interfaces -> WAN_X in
                  100baseTX <full-duplex>

                  The output in **Status -> Interfaces”

                  WAN_1
                  MTU
                  1350
                  Media
                  100baseTX <full-duplex>
                  In/out packets
                  266980/253695 (299.20 MiB/34.30 MiB)
                  In/out packets (pass)
                  266980/253695 (299.20 MiB/34.30 MiB)
                  In/out packets (block)
                  740/285 (73 KiB/46 KiB)
                  In/out errors
                  12123/0
                  Collisions
                  0

                  WAN_2
                  MTU
                  1350
                  Media
                  100baseTX <full-duplex>
                  In/out packets
                  15759/16785 (1.62 MiB/777 KiB)
                  In/out packets (pass)
                  15759/16785 (1.62 MiB/777 KiB)
                  In/out packets (block)
                  1301/0 (181 KiB/0 B)
                  In/out errors
                  281/0
                  Collisions
                  0

                  Both WANs (mean 1st port on each of NICs) set in pfSense In Interfaces -> WAN_X in
                  100baseTX**

                  The output in **Status -> Interfaces”

                  WAN_1
                  MTU
                  1350
                  Media
                  100baseTX <half-duplex>
                  In/out packets
                  58191/43464 (55.42 MiB/7.11 MiB)
                  In/out packets (pass)
                  58191/43464 (55.42 MiB/7.11 MiB)
                  In/out packets (block)
                  208/0 (13 KiB/0 B)
                  In/out errors
                  2/2
                  Collisions
                  6407

                  WAN_2
                  MTU
                  1350
                  Media
                  100baseTX <half-duplex>
                  In/out packets
                  5461/5977 (726 KiB/320 KiB)
                  In/out packets (pass)
                  5461/5977 (726 KiB/320 KiB)
                  In/out packets (block)
                  177/0 (8 KiB/0 B)
                  In/out errors
                  0/0
                  Collisions
                  217

                  Need to add, that on any other interfaces any other NICs (which are identical and we buy at one time from one supplier) there are no In/Out Errors or Collisions

                  —
                  CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
                  Help Ukraine to resist, save civilians people’s lives !
                  (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

                  1 Reply Last reply Reply Quote 0
                  • S
                    stephenw10 Netgate Administrator
                    last edited by stephenw10 Nov 5, 2021, 10:08 PM Nov 5, 2021, 9:36 PM

                    The MTU there is very low.

                    What changed here? Were those ever linked at 1G?

                    If you set a fixed speed it must match the other end of the link.
                    If you set half duplex you will always get collisions even if the other end does match.

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • S
                      Sergei_Shablovsky
                      last edited by Sergei_Shablovsky Nov 5, 2021, 10:37 PM Nov 5, 2021, 10:31 PM

                      @stephenw10 said in Errors In, but no Errors Out and No Collisions on both WAN:

                      The MTU there is very low.

                      We need this value for uplink, just ignore it.
                      Anyway, I make the test for both 100TX and 100TX full duplex, with MTU 1350, 1500 and 1420, and looks like MTU no such involved in this issue...

                      What changed here? Were those ever linked at 1G?

                      I try each settings for interface from automatic to highest 1000TX full duplex on Interfaces - WAN_X webpage of pfSense GUI, the result You able to see above...

                      Shortly to say, only on 100TX (mean 100TX half-duplex), all pfSense updates are ok, no connection reset by server due 1,5-2h connect time, all working.
                      But I still have In Errors.

                      —
                      CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
                      Help Ukraine to resist, save civilians people’s lives !
                      (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

                      1 Reply Last reply Reply Quote 0
                      • S
                        stephenw10 Netgate Administrator
                        last edited by Nov 5, 2021, 11:36 PM

                        With half duplex you mat well get errors, you will definitely see collisions.

                        Nothing is half-duplex these days not since hubs and 10base2! What is it connected to? It seems like something must be configured wrong.

                        Steve

                        S 1 Reply Last reply Nov 6, 2021, 1:02 AM Reply Quote 1
                        • S
                          Sergei_Shablovsky @stephenw10
                          last edited by Sergei_Shablovsky Nov 6, 2021, 4:26 AM Nov 6, 2021, 1:02 AM

                          @stephenw10 said in Errors In, but no Errors Out and No Collisions on both WAN:

                          With half duplex you mat well get errors, you will definitely see collisions.

                          Nothing is half-duplex these days not since hubs and 10base2!

                          Heh ;)

                          What is it connected to?

                          I start thinking “connected to a piece of sh****t” ;)
                          (Some Huawei applience)

                          It seems like something must be configured wrong.

                          Also make the same conclusion. But anyway before to start complaining the ISP, I need to be sure that all ok on my end of cable ;)
                          So, if You have some suggestions, I would be thankful to read it :)

                          —
                          CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
                          Help Ukraine to resist, save civilians people’s lives !
                          (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

                          G 1 Reply Last reply Nov 6, 2021, 10:05 AM Reply Quote 0
                          • G
                            Gertjan @Sergei_Shablovsky
                            last edited by Nov 6, 2021, 10:05 AM

                            @sergei_shablovsky
                            Put a switch between the ISP device, and pfSense.
                            First, hook up ,the switch to WAN-pfSense, and see that the connection negotiates a connection using 'auto on both side (the switch will only have the auto mode).

                            Then make the connection between the switch and the ISP device.

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

                            S 2 Replies Last reply Nov 6, 2021, 7:13 PM Reply Quote 2
                            • S
                              stephenw10 Netgate Administrator
                              last edited by Nov 6, 2021, 10:07 AM

                              Yup, that would be a good test.

                              1 Reply Last reply Reply Quote 0
                              • S
                                Sergei_Shablovsky @Gertjan
                                last edited by Nov 6, 2021, 7:13 PM

                                @gertjan said in Errors In, but no Errors Out and No Collisions on both WAN:

                                @sergei_shablovsky
                                Put a switch between the ISP device, and pfSense.
                                First, hook up ,the switch to WAN-pfSense, and see that the connection negotiates a connection using 'auto on both side (the switch will only have the auto mode).

                                Then make the connection between the switch and the ISP device.

                                Thank You, I'l try to doing this today. Really great idea, that I miss. (I little bit tied, may be need some sort of small vacation;)

                                —
                                CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
                                Help Ukraine to resist, save civilians people’s lives !
                                (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

                                1 Reply Last reply Reply Quote 0
                                • jimpJ
                                  jimp Rebel Alliance Developer Netgate
                                  last edited by Nov 9, 2021, 3:02 PM

                                  For future reference you can find out more detail about the cause of these errors in most cases from sysctl. The amount of information varies by driver.

                                  For example if you see errors on ix0, check sysctl dev.ix.0 and look at the counters, there are some which are obviously errors (marked with names that say error/err) and others that are less obvious like no_desc_avail. There will be counters under places like mac_stats as well as under various queues. Again, varying by driver.

                                  All of these should total up to the number you see in the status page for errors, but it varies too much for the GUI to attempt displaying the detail.

                                  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!

                                  S 1 Reply Last reply Nov 17, 2021, 7:51 AM Reply Quote 1
                                  • S
                                    Sergei_Shablovsky @Gertjan
                                    last edited by Nov 17, 2021, 7:36 AM

                                    @gertjan said in Errors In, but no Errors Out and No Collisions on both WAN:

                                    @sergei_shablovsky
                                    Put a switch between the ISP device, and pfSense.
                                    First, hook up ,the switch to WAN-pfSense, and see that the connection negotiates a connection using 'auto on both side (the switch will only have the auto mode).

                                    Then make the connection between the switch and the ISP device.

                                    Thank You for all suggestions and help here!

                                    So, the conclusion on testing: on a short (<30m) distance the NIC able to work on 1000Tx <full duplex> but on long distance (>80m) only 100TX <full duplex> possible + with a lot of “CRC In Errors”.

                                    —
                                    CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
                                    Help Ukraine to resist, save civilians people’s lives !
                                    (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      Sergei_Shablovsky @jimp
                                      last edited by Sergei_Shablovsky Nov 17, 2021, 7:53 AM Nov 17, 2021, 7:51 AM

                                      @jimp said in Errors In, but no Errors Out and No Collisions on both WAN:

                                      For future reference you can find out more detail about the cause of these errors in most cases from sysctl. The amount of information varies by driver.

                                      For example if you see errors on ix0, check sysctl dev.ix.0 and look at the counters, there are some which are obviously errors (marked with names that say error/err) and others that are less obvious like no_desc_avail. There will be counters under places like mac_stats as well as under various queues. Again, varying by driver.

                                      Thanks You for suggestions and help here!

                                      During testing various combinations NIC/cable/other appliance we see that “CRC In Errors” caused by impossibility of exact NIC to handle long (mean >80m) FTP Cat6e cable connection at 1000TX <full duplex> (1Gb/s).

                                      All of these should total up to the number you see in the status page for errors, but it varies too much for the GUI to attempt displaying the detail.

                                      Anyway the pfSense have a great GUI Dashboard.

                                      Only one I need from pfSense Dashboard: dividing on groups (similar to Grafana with options to Expand/Collapse):
                                      Section 1 - for frequently used info like WANs/LANs information, DNS info, VPNs info, netflow real-time graphics;
                                      Section 2 - for more static, or rarely changing information (whole system info, installed packets, services status, RSS news, etc);

                                      —
                                      CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
                                      Help Ukraine to resist, save civilians people’s lives !
                                      (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        Sergei_Shablovsky
                                        last edited by Sergei_Shablovsky Nov 17, 2021, 7:58 AM Nov 17, 2021, 7:57 AM

                                        Issue was resolved by replacing FTP Cat6 connection to ISP's applience on fiber 4-mode cable: no any collisions, no any errors in sending/receiving packets and in addition delay was decreased from 7-8ms to 3-4ms.

                                        —
                                        CLOSE SKY FOR UKRAINE https://youtu.be/_tU1i8VAdCo !
                                        Help Ukraine to resist, save civilians people’s lives !
                                        (Take an active part in public protests, push on Your country’s politics, congressmans, mass media, leaders of opinion.)

                                        M 1 Reply Last reply Nov 17, 2021, 11:53 AM Reply Quote 1
                                        • M
                                          mer @Sergei_Shablovsky
                                          last edited by Nov 17, 2021, 11:53 AM

                                          @sergei_shablovsky Amazing how often physical connectivity is the problem. Copper that works fine for 10M could have all kinds of problems at 10G. Fiber? Need to make sure everything matches.

                                          Lesson to take away:
                                          Check physical first :)

                                          S 1 Reply Last reply Nov 17, 2021, 1:10 PM Reply Quote 2
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                                            This community forum collects and processes your personal information.
                                            consent.not_received