What do you mean by "large"? From where are you downloading these large files? Have you tried any other download method (or browser) such as wget?
[root@server downloads]# wget http://ipv6.download.thinkbroadband.com/1GB.zip--2017-11-29 14:27:46-- http://ipv6.download.thinkbroadband.com/1GB.zipResolving ipv6.download.thinkbroadband.com (ipv6.download.thinkbroadband.com)... 2a02:68:1:7::1Connecting to ipv6.download.thinkbroadband.com (ipv6.download.thinkbroadband.com)|2a02:68:1:7::1|:80... connected.HTTP request sent, awaiting response... 200 OKLength: 1073741824 (1.0G) [application/zip]Saving to: ‘1GB.zip’100%[=====================================>] 1,073,741,824 45.0MB/s in 18s 2017-11-29 14:28:04 (57.7 MB/s) - ‘1GB.zip’ saved [1073741824/1073741824] [root@server downloads]# [root@server downloads]# wget http://ipv4.download.thinkbroadband.com/1GB.zip--2017-11-29 14:28:43-- http://ipv4.download.thinkbroadband.com/1GB.zipResolving ipv4.download.thinkbroadband.com (ipv4.download.thinkbroadband.com)... 80.249.99.148Connecting to ipv4.download.thinkbroadband.com (ipv4.download.thinkbroadband.com)|80.249.99.148|:80... connected.HTTP request sent, awaiting response... 200 OKLength: 1073741824 (1.0G) [application/zip]Saving to: ‘1GB.zip.1’100%[=====================================>] 1,073,741,824 28.2MB/s in 38s 2017-11-29 14:29:21 (26.8 MB/s) - ‘1GB.zip.1’ saved [1073741824/1073741824][root@server downloads]#
Unfortunately I'm not an expert on debugging this type of problem but it works fine for me using wget and the same for a browser, I have a fibre connection:Code: [Select][root@server downloads]# wget http://ipv6.download.thinkbroadband.com/1GB.zip--2017-11-29 14:27:46-- http://ipv6.download.thinkbroadband.com/1GB.zipResolving ipv6.download.thinkbroadband.com (ipv6.download.thinkbroadband.com)... 2a02:68:1:7::1Connecting to ipv6.download.thinkbroadband.com (ipv6.download.thinkbroadband.com)|2a02:68:1:7::1|:80... connected.HTTP request sent, awaiting response... 200 OKLength: 1073741824 (1.0G) [application/zip]Saving to: ‘1GB.zip’100%[=====================================>] 1,073,741,824 45.0MB/s in 18s 2017-11-29 14:28:04 (57.7 MB/s) - ‘1GB.zip’ saved [1073741824/1073741824] [root@server downloads]# [root@server downloads]# wget http://ipv4.download.thinkbroadband.com/1GB.zip--2017-11-29 14:28:43-- http://ipv4.download.thinkbroadband.com/1GB.zipResolving ipv4.download.thinkbroadband.com (ipv4.download.thinkbroadband.com)... 80.249.99.148Connecting to ipv4.download.thinkbroadband.com (ipv4.download.thinkbroadband.com)|80.249.99.148|:80... connected.HTTP request sent, awaiting response... 200 OKLength: 1073741824 (1.0G) [application/zip]Saving to: ‘1GB.zip.1’100%[=====================================>] 1,073,741,824 28.2MB/s in 38s 2017-11-29 14:29:21 (26.8 MB/s) - ‘1GB.zip.1’ saved [1073741824/1073741824][root@server downloads]# My OPNsense is installed in ESXi using the vmxnet3 driver (with real Intel i350 NICs. What type of connection do you have; how much RAM; have you disabled all the NIC offload functions; what make of NIC; was the speed any better prior to using OPNsense? What sort of hardware are you using?
I guess those hardware specs are sufficient. I have a very similar configuration for my OPNsense VM and until I recently had FTTH installed I had an ADSL connection and still didn't see any problems with downloads not working correctly. For the 'offload' functions I meant in OPNsense, you'll find them at Interfaces/Settings - I'm not 100% convinced they do anything for me but I haven't tested it yet and some people recommend it for a virtualized firewall. If you haven't modified those settings it may be worth a try.PS The offload settings for all the physical hardware NICs are still enabled on my systems.
I actually had this issue happen to me twice while I was on pfSense. Never was able to diagnose the issue and fresh re-installs fixed the problems both times.