[Solved] In/out errors on LAN
-
Okay I've resolved the problem.
First thing I did today was get a proper Ethernet cable tester. I tested all my cables, they are all wired correctly and have excellent frequency response with no outside foreign frequencies detected.
Then I fitted a brand new switch. Problem still there.
So I'd ruled out my switch, my cables, and all four individual ports on my PFSense box. I'm using an Intel i340-T4 by the way.
So now it came time to remove the bridge. I did that and guess what? no more in/out errors. Completely gone. I tested every port on the i340-T4 individually by changing the LAN to each port and none of them shows any errors of any kind. Then I put the bridge back as it was before and the errors instantly came back.
I'm not sure if this is an igb driver issue, a pfsense issue or something along those lines. If anyone wants more information about the way I was running this setup feel free to ask.
Thank you Derelict and jahonix for your help. The forum is a great resource with people like yourselves willing to answer peoples questions.
-
Did it actually cause any issues? Might just be cosmetic. Haven't seen that, that's a pretty common type of configuration. Might also want to try on 2.2.
-
I'm on 2.2 RC. Have been the entire time.
It didn't seem to cause any problems. Network speed was consistent, everything worked fine. Just the errors kept climbing at a steady pace.
As I say though, removed the bridge, errors gone. Perhaps it was my fault in the way I set the bridge up?
-
I found the issue. It gives out errors because you have unused ports. I had the exact same issue but when I removed the 2 nics which didn't had a cable in them I stopped receiving those errors. So it seems to be a cosmetic thing.
-
Ahh.. File that one away. Thanks.
-
Found it by pure chance as I had the exact same thing. So I went to remove the 2 unused port so I could setup a static connection to see if it was a cable/nic issue. Just figured I might as well check the interfaces again after that and since then no errors.
I would suggest a second verification just to be sure.
-
I can't redo my network right now with this box as it's in production otherwise I would test to verify.
But based on what I saw when this was happening to me I think you're right. Hopefully this can be corrected in an update to PFSense so we don't get more threads like these with worried noobies like myself. ;D
-
I've built a new PFSense system and I'm having some In/out errors on my LAN. Is this normal or do I have a port/cable issue? (I've already changed the cable and the error rate stayed the same).
This is my config map.
Modem -> PFsense -> 4x1Gb Lan Bridged -> 1Gb Switch/Access Point (WiFi + 4 Ethernet Ports).
I'm only using one of the LAN ports on my PFSense system out of the four available. I bridged the four ports as I intended to use more than one.
Here is the information from the affected interface, this is the Bridge. No other interface is showing any In/Out Error or Colossians.
Based on this the error rate is about 1.06%
Is this something I should be concerned about? I'm not having any issues accessing the internet, the speed is what I should be receiving and is identical to my old equipment. But obviously seeing errors of any kind is worrying with a new system, this is my first PFSense build also.
Thank you for any replies. It is much appreciated.
I can verify the errors.. if you have bridget the ports and you have unused ports enabled.. you get errors on the bridge.. just unenable the unused ports and you are good.. this is still happening in 2.3 realice version.. :)
-
@toomas said in [Solved] In/out errors on LAN:
I've built a new PFSense system and I'm having some In/out errors on my LAN. Is this normal or do I have a port/cable issue? (I've already changed the cable and the error rate stayed the same).
This is my config map.
Modem -> PFsense -> 4x1Gb Lan Bridged -> 1Gb Switch/Access Point (WiFi + 4 Ethernet Ports).
I'm only using one of the LAN ports on my PFSense system out of the four available. I bridged the four ports as I intended to use more than one.
Here is the information from the affected interface, this is the Bridge. No other interface is showing any In/Out Error or Colossians.
Based on this the error rate is about 1.06%
Is this something I should be concerned about? I'm not having any issues accessing the internet, the speed is what I should be receiving and is identical to my old equipment. But obviously seeing errors of any kind is worrying with a new system, this is my first PFSense build also.
Thank you for any replies. It is much appreciated.
I can verify the errors.. if you have bridget the ports and you have unused ports enabled.. you get errors on the bridge.. just unenable the unused ports and you are good.. this is still happening in 2.3 realice version.. :)
New pfSense user here, sorry to revive an old thread but I can also verify that this is still a thing with version 2.4.4.
I bridged two of my LAN-ports today and immediately after that I began receiving output errors on the bridge-interface (with the other network cable unplugged).
-
I can verify that this issue is still present in 2.4.5-RELEASE-p1.
Unused ports connected to a bridge interface generate "Errors Out" in the Interface Statistics log.
-
Still present in pfsense + 2102 .
-
H Howler referenced this topic on
-
Still happening with 22.05-RELEASE (2.6). Although my setup is slightly different. I am using LAGG to combine port 1 and 2 on my 4 port Intel card (rebadged HP brand) to connect to the Motorola MB8600 Cable modem to make use of the higher speeds. It's not really affecting anything in terms of speed so not too concerned about it but would love to see the errors go away.
I may eventually replace the modem to get the 2.5 gig port instead of the four 1 gig ports to simplify things.
-
I went ahead and assigned the unused ports on the interface page and left them as disabled. So far no errors other than the 6 during boot which I am going to ignore. Still using LAGG.
I will keep checking and report back.
-
@darkk Interesting. I get a handful errors appearing on the Out interfaces for VLANs when there is a system restart. After that, they stop. Maybe related. I don't know.
