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

    4200: System Update (24.11) to (25.07.1) caused WAN port to stop working

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    17 Posts 7 Posters 17.4k Views 8 Watching
    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 Offline
      Joe0x7F
      last edited by

      Thanks for the ideas. That helped a lot to get it to work, but I had to set the Speed low in order to do that. Something must have changed from (24.11) to (25.07.1) affecting this area of the code. Autoselect is apparently not working.

      https://192.168.1.1/interfaces.php?if=wan
      Interfaces
      PORT1WAN (igc3)
      Speed and Duplex
      10baseT/UTP full-duplex <---- !!!!!!
      Explicitly set speed and duplex mode for this interface.

      I was getting these numbers in speed tests (https://www.speedtest.net/) yesterday morning:

      Download Mbps = 94.31
      Upload Mbps = 11.35

      Now, I’m getting these numbers:

      Download Mbps = 8.94
      Upload Mbps = 9.37

      patient0P 1 Reply Last reply Reply Quote 0
      • patient0P Offline
        patient0 @Joe0x7F
        last edited by

        @Joe0x7F that is only 10 Mbps, way too low for any meaningful work. 1 Gbps didn’t work? Try setting pfSense to Auto and the WAN device interface to 1 Gbps fix.
        There has to be a faster speed possible.

        1 Reply Last reply Reply Quote 0
        • F Offline
          FSC830
          last edited by

          Just a dump idea: if -for what reasons ever- a wire inside the cable is broken ar lost contact this will result in a fast ethernet (100mb / 10Mbps) connection.
          So what is about the question about replacing the cable? Did you already checked this out?

          Regards

          J 1 Reply Last reply Reply Quote 0
          • J Offline
            Joe0x7F @FSC830
            last edited by

            @FSC830 I already changed cables, and I already changed ports.

            GertjanG S 2 Replies Last reply Reply Quote 0
            • GertjanG Offline
              Gertjan @Joe0x7F
              last edited by

              @Joe0x7F

              When you change - re assign - WAN and LAN on pfSense, the rpoblem goes to LAN ?
              In that case, you're getting close to a 'broken port' on pfSense.

              Check the inside of the port, the 8 metal contact strips are ok ?

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

              J 1 Reply Last reply Reply Quote 0
              • S Offline
                SteveITS Rebel Alliance @Joe0x7F
                last edited by

                FWIW the 4200 has this note:
                https://docs.netgate.com/pfsense/en/latest/solutions/netgate-4200/io-ports.html#networking-ports

                "The igc(4) network interfaces on this device do not support fixed speed operation. These interfaces emulate a speed/duplex choice by limiting the values offered during autonegotiation to the speed/duplex value selected in the GUI.

                When connecting different devices to these interfaces the peer should typically be set to autonegotiate, not to a specific speed or duplex value. The exception to this is if the peer interface has the same limitation, in which case both peers should select the same negotiation speed."

                Not sure if that's helpful at all. Maybe power off the ISP router?

                Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
                Upvote 👍 helpful posts!

                J 1 Reply Last reply Reply Quote 0
                • J Offline
                  Joe0x7F @Gertjan
                  last edited by

                  Hi @Gertjan, I just checked them with a flashlight and magnifying glass. All 8 conductors in all 4 ports look the same and perfect.

                  1 Reply Last reply Reply Quote 0
                  • J Offline
                    Joe0x7F @SteveITS
                    last edited by

                    Hi @SteveITS , the problem is I did not change or move any of the cables at all. They were working perfectly. Then, I did a System Update from (24.11) to (25.07.1), and it stopped working. That is all.

                    I don't see anything here that violates the text you have cited.

                    But, I think this was a good idea too.

                    1 Reply Last reply Reply Quote 0
                    • w0wW Offline
                      w0w
                      last edited by

                      Maybe I missed something, but what is connected to the other end of the cable plugged into the WAN port? Is it some kind of modem or what?
                      This is actually a known issue, and it’s unlikely that the pfSense version is to blame — it’s more likely a link auto-negotiation problem. It just happened to work correctly on 24.11.
                      Most likely, forcing the link speed on the upstream device connected to that port will help, or simply putting a cheap unmanaged switch between the WAN port and the upstream device.

                      GertjanG J 2 Replies Last reply Reply Quote 0
                      • GertjanG Offline
                        Gertjan @w0w
                        last edited by

                        @w0w

                        I was presuming Joe0x7F already tried several different devices on the other side of the cable.

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

                        1 Reply Last reply Reply Quote 0
                        • J Offline
                          Joe0x7F @w0w
                          last edited by

                          Ding. Ding. Ding. Looks like we have a winner.

                          “This is actually a known issue” <----- This is what I wanted to hear. Is there a reference # in the Release Notes?

                          Of all the devices and computers I have plugged into my Cisco/Linksys hub through the years, this is the first device not able to auto-negotiate or run at 100-BaseT. I’ll need to remember this and prepare for when I have to move the 4200 around on my job.

                          I had to pull the cable from downstairs over to the 4200, and then it was able to auto-negotiate to 1000-BaseT.

                          w0wW 1 Reply Last reply Reply Quote 1
                          • w0wW Offline
                            w0w @Joe0x7F
                            last edited by

                            @Joe0x7F said in 4200: System Update (24.11) to (25.07.1) caused WAN port to stop working:

                            Is there a reference # in the Release Notes?

                            This is not Netgate, this is Intel issue, don't know about the reference... But here is the community answer
                            https://community.intel.com/t5/Ethernet-Products/Intel-I226-V-Connection-Issues/td-p/1465810

                            J 1 Reply Last reply Reply Quote 1
                            • J Offline
                              Joe0x7F @w0w
                              last edited by

                              @w0w Thanks very much for the details/info. I will look through it and see if they say anything about mitigation.

                              It does not matter whose fault it is. It still reflects badly on Netgate, too.

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