WAN slow with ASROCK J3455B and intel quad nic

[spants]

Just joined the opnsense train and having a couple of problems...

I am using 18.7.1_3-amd64 on the ASROVK J3455B board (bare metal), 8GB ram, SSD with an 9Y6138 39Y6137 IBM OEM Intel PRO 1000 PT Quad Port PCIE Server NIC and I am seeing traffic bounce around 40-60% of my normal speed.
(normal = ASUS router before this setup, which gave 80mbs down and 20mbs up)

I use a BT Openreach Modem which has 100full duplex connection, the port connected to it shows 100 full duplex.
The port connected to my wifi ap is running at 1000full duplex. I test the speed using wired and wireless on speedtest.net.

 Hardware CRC    Disable hardware checksum offload
 Hardware TSO    Disable hardware TCP segmentation offload
 Hardware LRO   Disable hardware large receive offload
..are all ticked.
I have disabled VT-d.

The system shows almost 100% idle.

No extra modules are loaded/enabled... just straight out of the box.
To enable it to boot, I had to use:
Set hint.hpet.0.clock = 0
Set hint.ahci.0.msi = 2
Set hint.ahci.1.msi = 2
..and this is now in my Tunables.

I am stumped! anyone have a clue?

[spants]

some more testing...

I tried pfsense 2.4.x and had exactly the same slow speed.
I then tried pfsense 2.3.5-RELEASE-p2 (amd64) and get the full speed....

So, something has changed between the pfsense versions.... Can I download the previous Opnsense version I wonder?

[marjohn56]

No you can't. 


I'm running on Zen, which is the same as BT only taking a different route. If I could get 80/20 on my line my system would handle it quite happily. Tested internally I can exceed 630Mbps, I think anything above that may be a driver issue on certain intel NICs, however you should have zero issues getting 80/20.

[spants]

Its not the internet provider.... after lots of testing and trying the same with PFsense that I am trying to migrate from:

pfsense 2.3.5-RELEASE-p2 works well...
an "upgrade" or clean install to 2.4.x cuts the speed to the same that I see with opnsense.

It must be a driver issue, but I'm not clever enough to fix
Looks like i will have to stay on pfsense 2.3.5

**edit to add 2.4.x version that doesn't work properly!**

[marjohn56]

Odd, seems it could be an 11.1 issue if it's also affecting pf, we'll be on the migration path soon to 11.2 - hopefully that will fix it.

[franco]

Not entirely a NIC driver issue as we have the 11.2 Intel drivers, but something else that is related, maybe pf indeed.


Cheers,
Franco

[spants]

Just to update everyone..... I tried the 2.4.4rc version of pfsense and that works fine so it may be an 11.1 issue.
Looking forward to using an updated opnsense!