Network Speed Concern

[lmannyr]

Your FreeNAS interfaces seem to be going up and down, which isn't good. And it looks like you've configured a LAGG group? Try removing the LAGG group and see if you can get reasonable performance from a single interface.

EDIT: definitely remove the LAGG group; you're using unmanaged switches and LAGG requires LACP support and configuration on the switch.

If will be helpful if you provide us with all of the details of your network setup for both your FreeNAS server and desktop workstation: static/DHCP? Netmask? Gateway? Nameserver(s)? Have you installed any FreeNAS tunables? Have you optimized the NIC settings on your desktop? etc.

Lastly, it may not be the source of your problem... but Intel NICs are reasonably priced these days, so I suggest replacing the no-name NIC you're using in your desktop.

The LAGG was setup in "Failover" mode. But to help resolve the UP/DOWN/UP/DOWN/UP/DOWN nonsense I removed the lagg interface and disconnected one ether cable leaving one still connected as pictured on the post above.

pfSense has the static mappings outside the range. let me put up some screen shots for the rest of your requests..

 

[lmannyr]

If you're not using the server for anything, I think it might be time for a reboot after having messed with LAGG.

All of that UP/DOWN noise has happened since the last reboot, so it would be nice to see dmesg come up clean.

the UP/DOWN was happening before the recent reboot...but I'll restart anyways now.

 

[Mlovelace]

When was the last time you power cycled any of the unmanaged switches? You've got an unmanaged switch connected to an unmanaged switch connected to a wifi router (essentially unmanaged switch), they can get squirrelly and fail over time. I ask because you're not seeing the same behavior on the wifi network, which takes these other switches out of the picture.

 

[lmannyr]

Your FreeNAS interfaces seem to be going up and down, which isn't good. And it looks like you've configured a LAGG group? Try removing the LAGG group and see if you can get reasonable performance from a single interface.

EDIT: definitely remove the LAGG group; you're using unmanaged switches and LAGG requires LACP support and configuration on the switch.

If will be helpful if you provide us with all of the details of your network setup for both your FreeNAS server and desktop workstation: static/DHCP? Netmask? Gateway? Nameserver(s)? Have you installed any FreeNAS tunables? Have you optimized the NIC settings on your desktop? etc.

Lastly, it may not be the source of your problem... but Intel NICs are reasonably priced these days, so I suggest replacing the no-name NIC you're using in your desktop.

No tunables
255.255.255
/24

 

[lmannyr]

 

[lmannyr]

This is post reboot, No LAGG, one NIC connected to ethernet (IPMI is also connected to ethernet)

dmesg | grep igb


igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xc000-0xc01f mem 0xf7400000-0xf747ffff,0xf7480000-0xf7483fff irq 18 at device 0.0 on pci5


igb0: Using MSIX interrupts with 5 vectors


igb0: Ethernet address: 0c:c4:7a:6a:e0:be


igb0: Bound queue 0 to cpu 0


igb0: Bound queue 1 to cpu 1


igb0: Bound queue 2 to cpu 2


igb0: Bound queue 3 to cpu 3


igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb000-0xb01f mem 0xf7300000-0xf737ffff,0xf7380000-0xf7383fff irq 19 at device 0.0 on pci6


igb1: Using MSIX interrupts with 5 vectors


igb1: Ethernet address: 0c:c4:7a:6a:e0:bf


igb1: Bound queue 0 to cpu 4


igb1: Bound queue 1 to cpu 5


igb1: Bound queue 2 to cpu 6


igb1: Bound queue 3 to cpu 7


igb0: link state changed to UP


igb0: link state changed to DOWN


igb0: link state changed to UP


igb1: promiscuous mode enabled


igb0: link state changed to DOWN


igb0: promiscuous mode enabled


igb0: link state changed to UP


igb1: link state changed to UP


igb1: link state changed to DOWN


igb0: link state changed to DOWN


igb0: link state changed to UP


igb1: link state changed to UP


igb1: link state changed to DOWN


igb1: link state changed to UP


igb0: link state changed to DOWN


igb1: link state changed to DOWN


igb1: link state changed to UP


igb0: link state changed to UP


igb0: link state changed to DOWN


igb0: link state changed to UP


igb1: link state changed to DOWN


igb0: lagg_port_destroy: lp_ifflags unclean


igb0: link state changed to DOWN


igb1: lagg_port_destroy: lp_ifflags unclean


igb0: link state changed to UP


igb1: link state changed to UP


igb1: link state changed to DOWN


igb1: link state changed to UP


igb0: link state changed to DOWN


igb0: link state changed to UP


igb0: link state changed to DOWN


igb0: link state changed to UP


igb1: link state changed to DOWN


igb1: link state changed to UP


igb1: link state changed to DOWN


igb1: link state changed to UP


igb0: link state changed to DOWN


igb1: link state changed to DOWN


igb1: link state changed to UP


igb1: link state changed to DOWN


igb1: link state changed to UP


igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xc000-0xc01f mem 0xf7400000-0xf747ffff,0xf7480000-0xf7483fff irq 18 at device 0.0 on pci5


igb0: Using MSIX interrupts with 5 vectors


igb0: Ethernet address: 0c:c4:7a:6a:e0:be


igb0: Bound queue 0 to cpu 0


igb0: Bound queue 1 to cpu 1


igb0: Bound queue 2 to cpu 2


igb0: Bound queue 3 to cpu 3


igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb000-0xb01f mem 0xf7300000-0xf737ffff,0xf7380000-0xf7383fff irq 19 at device 0.0 on pci6


igb1: Using MSIX interrupts with 5 vectors


igb1: Ethernet address: 0c:c4:7a:6a:e0:bf


igb1: Bound queue 0 to cpu 4


igb1: Bound queue 1 to cpu 5


igb1: Bound queue 2 to cpu 6


igb1: Bound queue 3 to cpu 7


igb1: link state changed to UP


igb1: link state changed to DOWN


igb1: link state changed to UP


igb1: link state changed to DOWN


igb1: promiscuous mode enabled


igb1: link state changed to UP


FN@FNBOX:~ # dmesg | grep 100


AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>


Timecounter "TSC-low" frequency 1750032454 Hz quality 1000


Event timer "i8254" frequency 1193182 Hz quality 100


igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xc000-0xc01f mem 0xf7400000-0xf747ffff,0xf7480000-0xf7483fff irq 18 at device 0.0 on pci5


igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb000-0xb01f mem 0xf7300000-0xf737ffff,0xf7380000-0xf7383fff irq 19 at device 0.0 on pci6


umass0: SCSI over Bulk-Only; quirks = 0x8100


umass1: SCSI over Bulk-Only; quirks = 0x8100


AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>


AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>


Timecounter "TSC-low" frequency 1750037710 Hz quality 1000


Event timer "i8254" frequency 1193182 Hz quality 100


igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xc000-0xc01f mem 0xf7400000-0xf747ffff,0xf7480000-0xf7483fff irq 18 at device 0.0 on pci5


igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xb000-0xb01f mem 0xf7300000-0xf737ffff,0xf7380000-0xf7383fff irq 19 at device 0.0 on pci6


umass0: SCSI over Bulk-Only; quirks = 0x8100


umass1: SCSI over Bulk-Only; quirks = 0x8100


AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>

 

[lmannyr]

Did some hardware troubleshooting.

All ethernet cables passed testing with an ethernet tester.

Long story short, I get 950mbits/s with one switch. Both switches individually work at the same speed. Now with the old setup FN-->Switch-->Switch/router-->Desktop it was slow. With FN-->Switch/router-->Desktop iperf gives 950mbits/s.

I need 2 switches to connect everything to network. Is it because the 2 switches are from different manufactures? What do you all suggest? The pfsense box has 2 more ports.

Thinking of connecting both switches to the pfsense BOX like below.

FN<-->Switch<-->pfSense<-->Switch<-->Desktop

Suggestions?

 

[lmannyr]

FIXED!

I replaced the TP-Link Switch with a spare 4 port Netgear switch. Speeds are 950Mbits/s both ways.

Kept the old hardware config since the other 2 ports on the router seem to not be working (lighting strike a few years ago).

I appreciate everyones time and input.