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

Joe0x7F

Hello Everyone,

My new 4200 came in Thursday (yay!), and I just got a chance to set it up via the quick setup Getting Started steps this morning. I plugged my WAN connection into (“1”), and I plugged my computer into LAN connection (“2”). Everything seemed to be working fine. I could browse the web with my computer fine.

This afternoon/tonight, I decided to try a System Update from (24.11) to (25.07.1). The upgrade seemed to go fine:

....
....
Finished updating ESP

Done.

Copying upgrade log...done.
Unmounting upgraded boot environment...done.
Activating default for the next boot only...done.
System is going to be upgraded. Rebooting in 10 seconds.
Success

When the 4200 came back up, my WAN port “1” was no longer working and still isn’t.

Status --> Interfaces

PORT1WAN Interface (wan, igc3)
Status
no carrier

PORT2LAN Interface (lan, igc2)
Status
up

I tried “Reset to factory defaults”, and that reset seemed to go fine. Then, I went back through the same steps with the same settings I originally used via the “Quick Start” setup and that seemed to go fine too.

However, my WAN port is still not working.

PORT1WAN Interface (wan, igc3)
Status
no carrier

I have confirmed that the WAN connection (not on the 4200) to the outside world still works by connecting my computer directly into it.

Help, please.

Joe0x7F

There are no lights/LEDs on on the WAN port ("1") with a live cable plugged in, like there is on the LAN port ("2").

Of course, I have tried turning off the power and disconnecting the cables until it looked like the 4200 was booted all the way back up again.

Still no luck. WAN port ("1") is not working.

WN1X

@Joe0x7F Have you tried a different ethernet cable for your WAN connection?

patient0

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

I plugged my WAN connection into (“1”)
...
PORT1WAN Interface (wan, igc3)
Status
no carrier

'no carrier' mains that port 1 on the 4200 and the WAN could not establish a link on cable level. As @WN1X wrote could it be a cable issue but also that something changed in the driver for the ports that makes speed negotiations fails with the WAN device.

What is the WAN device you are connecting to?
If WAN is 1 Gbps you can try set the speed for port 1 of the 4200 manually in the Interface settings, 'Speed and Duplex' to 1 Gbps. If that doesn't help, try also setting the WAN port on the WAN device to 1 Gbps

Joe0x7F

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

patient0

@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.

FSC830

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

Joe0x7F

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

Gertjan

@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 ?

SteveITS

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?