Closed WesleyCRibeiro closed 4 months ago
Hello, I tried directly from cli and I can confirm the behavior.
I searched into pfsense forums and looks like they don't support speedtest package since they don't consider reliable testing speed from the firewall itself.
We can try ofc to report upstream and see if someone can help.
I am using the template and also observed the same behavior !
I just talked to a friend who is a pfSense developer, he managed to reproduce the problem and was going to see something about it.
Let's wait :-)
@perlporter If possible, keep us updated with their feedback!
My friend told me, that he talked to the pf maintainer, who said that this behavior started happening after a patch in pfSense 2.5.1 or 2.5.2. This behavior should also be seen in FreeBSD.
He should fix it in a couple of weeks (he is on vacation).
:-)
@perlporter If possible, keep us updated with their feedback!
now we have a ticket to track
https://redmine.pfsense.org/issues/13420
:-)
Hi,
As seen here -> https://redmine.pfsense.org/issues/13420
The problem has been solved and will come in the next version of pfSense (2.7.0 / 23.01)
Regards,
Fixed upstream
Hi, I don't know if you've been through this, see
In the environments that we tested the script to collect the speed of the internet link, we are having the correct result only in the link that is as default in pfsense, the secondary link always presents a download/upload speed in the average of 1Mb, we have already simulated the use default in pfsense routing with the link directly or with a gateway group and the behavior is the same,
When we invert the default link, the behavior reverses together, that is, the link that had an average of 1Mb starts to show the actual contracted speed and the other that had measurements within the contracted starts to show the same average of 1mb between download and upload,
Not sure if I'm the one who did something wrong or already caught this behavior,
It cost!