pfSense 2.7.0 stop working now and then
-
So it looks like CRC errors:
dev.igc.0.mac_stats.crc_errs: 52083 dev.igc.0.mac_stats.recv_errs: 0 dev.igc.0.mac_stats.recv_jabber: 175 dev.igc.0.mac_stats.recv_oversize: 0 dev.igc.0.mac_stats.recv_fragmented: 418 dev.igc.0.mac_stats.recv_undersize: 0 dev.igc.0.mac_stats.recv_no_buff: 0 dev.igc.0.mac_stats.missed_packets: 0 dev.igc.0.mac_stats.defer_count: 0 dev.igc.0.mac_stats.sequence_errors: 0 dev.igc.0.mac_stats.symbol_errors: 0 dev.igc.0.mac_stats.collision_count: 52676Try disabling checksum hardware offloading in System > Advanced > Networking. You will need to reboot to apply that.
-
-
Looks promising!
no...
still errors and collisions... should I enable h/w CRC again?
My current settings;
-
Since it made no difference it likely doesn't matter. I would try swapping the NICs next. If it follows that then it's probably real incoming errors. I'd probably look at swapping out the media converter in that case though that might not be practical.
However I still don't think those errors/collisions would cause the traffic to stop entirely. At most those are symptoms of some other failure.
-
@stephenw10 said in pfSense 2.7.0 stop working now and then:
Since it made no difference it likely doesn't matter. I would try swapping the NICs next. If it follows that then it's probably real incoming errors. I'd probably look at swapping out the media converter in that case though that might not be practical.
However I still don't think those errors/collisions would cause the traffic to stop entirely. At most those are symptoms of some other failure.
I have contacted Digitus and asked them about issue, let see if they have to say about it.
-
Now I have a 2.5 Gbps switch on the LAN side, and there are no errors reported on that side. Therefore, the issue must be on the WAN side, and it appears to be related to the Digitus media converter, the only device connected in that segment. :(
-
Looks like you're still using the same NIC for the WAN though. I would try swapping the NIC assignments to be sure it's not a bad NIC.
-
@stephenw10 said in pfSense 2.7.0 stop working now and then:
Looks like you're still using the same NIC for the WAN though. I would try swapping the NIC assignments to be sure it's not a bad NIC.
Yes, i haven't change the NIC… how can I change NIC and keep the MAC-address?
-
You could spoof the MAC onto the other NIC. That should be fine since it's in a different l2 segment.
-
@stephenw10 said in pfSense 2.7.0 stop working now and then:
You could spoof the MAC onto the other NIC. That should be fine since it's in a different l2 segment.
same with another NIC... so then it must be the media converter... or?
-
Look at the error rate though. It's far far lower on igc3.
Did it still fail to pass traffic when using igc3 as WAN?
-
Root cause identified and resolved!
The issue was related to the Digitus Media converter, which didn't support mixed speeds. I had a 10 Gbps connection on one side and a 2.5 Gbps connection on the WAN side of pfSense.
However, after replacing the media converter with a switch that had both 10 Gbps and 2.5 Gbps ports, the collisions and errors ceased.
Case closed, and now my WAN data flows without any errors!
