4200: System Update (24.11) to (25.07.1) caused WAN port to stop working
-
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
-
@FSC830 I already changed cables, and I already changed ports.
-
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 ?
-
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?
-
Hi @Gertjan, I just checked them with a flashlight and magnifying glass. All 8 conductors in all 4 ports look the same and perfect.
-
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.
-
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. -
I was presuming Joe0x7F already tried several different devices on the other side of the cable.
-
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.
-
@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 -
@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.
