<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Netgate SG-4860: Hardware Limitation or Misconfiguration]]></title><description><![CDATA[<p dir="auto">Hi all</p>
<p dir="auto">Please have look at the picture to get an overview of my setup.<br />
pfSense is the routing instance of both VLAN's 103 &amp; 104.</p>
<p dir="auto"><img src="/assets/uploads/files/1586611393368-drawing_pfsense.png" alt="drawing_pfsense.png" class=" img-fluid img-markdown" /></p>
<p dir="auto"><strong>Problem description</strong><br />
If I copy large files from my workstation to the synology nas, cpu usage is very high and throughput is only ~45MByte.<br />
Ping latency to the internet is increasing dramatically and cpu usage of the pfSense is very high.</p>
<p dir="auto"><strong>What I did</strong></p>
<ol>
<li>
<p dir="auto">Separate LAGG for VLAN 103<br />
I moved VLAN 103 to a separate LAGG (1) that incoming and outgoing traffic is separated physically.</p>
</li>
<li>
<p dir="auto">System Tunables<br />
I have disabled the EEE settings on all interfaces.<br />
See this post https://community.spiceworks.com/topic/1221309-periodic-packet-loss-constant-carp-switchovers-with-intel-nics-i350-igb for details.</p>
</li>
</ol>
<pre><code>[2.4.5-RELEASE][root@pfsense]/root: sysctl dev.igb | grep eee
dev.igb.5.eee_disabled: 1
dev.igb.4.eee_disabled: 1
dev.igb.3.eee_disabled: 1
dev.igb.2.eee_disabled: 1
dev.igb.1.eee_disabled: 1
dev.igb.0.eee_disabled: 1
</code></pre>
<p dir="auto"><strong>Question</strong><br />
Is this behavior because of hardware limitations, or do I have a misconfiguration of my setup?<br />
I thought that a Netgate SG-4860 Appliance can handle 1GByte throughput without any limitations.</p>
<p dir="auto">Thanks in advance for your support!</p>
<p dir="auto">Some pfSense top -aSH outputs:</p>
<pre><code>  PID USERNAME     PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND
   11 root         155 ki31     0K    64K RUN     1 936:47  59.19% [idle{idle: cpu1}]
   11 root         155 ki31     0K    64K CPU3    3 935:25  52.52% [idle{idle: cpu3}]
   11 root         155 ki31     0K    64K RUN     0 937:59  45.01% [idle{idle: cpu0}]
   12 root         -92    -     0K   704K WAIT    0   0:45  27.15% [intr{irq272: igb4:que 0}]


  PID USERNAME     PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND
    0 root         -92    -     0K   864K CPU2    2   2:06 100.00% [kernel{igb3 que (qid 0)}]
   11 root         155 ki31     0K    64K RUN     3 935:26  45.91% [idle{idle: cpu3}]
   11 root         155 ki31     0K    64K RUN     1 936:48  44.13% [idle{idle: cpu1}]
   12 root         -92    -     0K   704K WAIT    0   0:45  42.56% [intr{irq272: igb4:que 0}]
   11 root         155 ki31     0K    64K RUN     0 937:59  35.26% [idle{idle: cpu0}]


  PID USERNAME     PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND
   11 root         155 ki31     0K    64K CPU3    3 935:33  94.23% [idle{idle: cpu3}]
   11 root         155 ki31     0K    64K CPU1    1 936:55  88.77% [idle{idle: cpu1}]
   11 root         155 ki31     0K    64K RUN     0 938:04  70.96% [idle{idle: cpu0}]
   12 root         -92    -     0K   704K WAIT    0   0:49  25.32% [intr{irq272: igb4:que 0}]
   12 root         -92    -     0K   704K WAIT    0   0:15   0.34% [intr{irq267: igb3:que 0}]
</code></pre>
<p dir="auto">Ping from workstation to 8.8.8.8 while copying a large file:</p>
<pre><code>Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3057ms TTL=52
Reply from 8.8.8.8: bytes=32 time=5ms TTL=52
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=2495ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1007ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3007ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=9ms TTL=52
Request timed out.
Reply from 8.8.8.8: bytes=32 time=2630ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3ms TTL=52
</code></pre>
]]></description><link>https://forum.netgate.com/topic/152418/netgate-sg-4860-hardware-limitation-or-misconfiguration</link><generator>RSS for Node</generator><lastBuildDate>Fri, 10 Apr 2026 16:19:22 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/152418.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 11 Apr 2020 13:54:50 GMT</pubDate><ttl>60</ttl></channel></rss>