Poor upload speed on WAN interface PFSense 2.7.0-RELEASE (amd64) built on Wed Jun 28 03:53:34 UTC 2023
-
@Aku said in Poor upload speed on WAN interface PFSense 2.7.0-RELEASE (amd64) built on Wed Jun 28 03:53:34 UTC 2023:
I go looking for a way to do a speedtest directly on the PFsense router. I
DONT.
pf sense is NOT a general purpose os and you shouldnt't isntall aribtrary packages like that.If you do want to get some traffic performance use the built in iperf server/client. and then keep a note that this WON"T perform at full speeds
pfsense is designed to pass traffic THROUGH.a. Run Iperf between your pc and pfsense lan
b. Put a host with iperf at the wan side of pf, and iperf through pfsense.
This will give you solid answers of where the issue is, and you take it from there.speedtest is a broad issue indicator but a very bad tool for troubleshooting.
-
For iperf3 WAN test on PfSense, just use a suitable public iperf server.
https://iperf.fr/iperf-servers.php
You have 1G, 10G as well as 40G & 100G servers to try, but be mindful that there will be other users out there.
Best to do it from the CLI in PfSense so you can watch the speeds vary. This example is on my 500/50 VirginMedia WAN.
/root: iperf3 -c paris.bbr.iperf.bytel.fr -p9220 -P5 -R
Connecting to host paris.bbr.iperf.bytel.fr, port 9220
Reverse mode, remote host paris.bbr.iperf.bytel.fr is sending
[ 5] local 192.168.0.253 port 43640 connected to 5.51.3.41 port 9220
[ 7] local 192.168.0.253 port 46797 connected to 5.51.3.41 port 9220
[ 9] local 192.168.0.253 port 23883 connected to 5.51.3.41 port 9220
[ 11] local 192.168.0.253 port 26657 connected to 5.51.3.41 port 9220
[ 13] local 192.168.0.253 port 57212 connected to 5.51.3.41 port 9220
[ ID] Interval Transfer Bitrate
[ 5] 1.00-2.00 sec 15.0 MBytes 126 Mbits/sec
[ 7] 1.00-2.00 sec 16.1 MBytes 135 Mbits/sec
[ 9] 1.00-2.00 sec 14.4 MBytes 121 Mbits/sec
[ 11] 1.00-2.00 sec 10.4 MBytes 87.0 Mbits/sec
[ 13] 1.00-2.00 sec 6.38 MBytes 53.5 Mbits/sec
[SUM] 1.00-2.00 sec 62.2 MBytes 522 Mbits/sec -
So I attempted this, and am also getting
iperf3: Command not found. -
@Aku Install the iperf package !!
-
@pwood999 That gets me back to this error: I go to run the pkg command to fetch it, and get the error ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg". That has now lead me to this reddit thread. I am currently working from home, so I won't be advancing past the certctl rehash, however the gui IS now recognizing that 2.7.2 is a thing, so progress!?
-
@Aku said in Poor upload speed on WAN interface PFSense 2.7.0-RELEASE (amd64) built on Wed Jun 28 03:53:34 UTC 2023:
That gets me back to this error: I go to run the pkg command to fetch it, and get the error ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg".
You don't need to fetch anything on the command line. iPerf3 can be installed via the package manager. Is there any reason you're using an outdated version of pfSense?
-
@w0w As far as I can tell "Something broke" My package Manager is unable to connect to the repository. I was able to get it to now recognize that 2.7.2 exists, and about to perform that upgrade.
-
So the upgrade is failing, claiming that
Number of packages to be reinstalled: 1 [1/1] Reinstalling pfSense-boot-2.7.2... [1/1] Extracting pfSense-boot-2.7.2: .......... done Updating the EFI loader install: //boot/efi/efi/boot/INS@DkJUW4: No space left on device pkg-static: POST-INSTALL script failed failed.I find that hard to believe:
I'm currently running SMART tests to see if the drive is failing
ETA: No errors found
-
The best approach is to back up your existing configuration and perform a fresh installation of 2.8.1 using the online installer.
Alternatively, you can install 2.7.2 from
https://atxfiles.netgate.com/mirror/downloads/
and then upgrade it to 2.8.1.
Don’t forget to install the System Patches package and apply all required patches. -
@w0w As I had feared and mentioned initially, in fact, the local USB upgrade did in fact resolve the issue
edit: I have not the reputation to give you the thumb
