Bug #12895
closed
pfSense single interface upload speed bug
0%
Description
Reporting a very straightforward bug and it is easy to reproduce.
Tested on 2.4.X 2.5.X 2.6.0, I believe it is also affecting older versions....
Let say my home router IP address is 192.168.1.1 and I deploy pfsense with IP 192.168.1.254, pfsense default gateway point to my home router.
And my PC use pfsense IP as default gateway and go for internet speed test. The upload speed will become less than 0.2 Mbps.
I have tried this bug with Hardware or VM, it is still affecting.
I deployed the pfsense from scratch, then just adding GW IP address and Firewall Rule "Any to Any allow all". So I guess it shouldn't be configuration related issue.
Updated by pf bug about 3 years ago
One more thing to mention, if I run OpenVPN on my PC and connect with some vpn services provider. The upload speed became reasonable. I can't say the speed is "back to normal" because it routed through a third party vpn services provider so pfsense might be still somehow capping the speed, but it is definitely faster than 0.2Mbps, it become around 40Mbps is my case with my ISP.
Updated by Jim Pingle about 3 years ago
- Status changed from New to Rejected
Sounds like you have a configuration problem (like needing a lower MTU on WAN).
This site is not for support or diagnostic discussion.
For assistance in solving problems, please post on the Netgate Forum or the pfSense Subreddit .
See Reporting Issues with pfSense Software for more information.
Updated by pf bug about 3 years ago
I can't confirm if this is configuration problem but I don't think it is, this is because I have tried to mess around with lots of settings, including lowering the MTU but it is not working. When I setup pfsnse in VM with two interface with a new subnet and speedtest on guest VM, then it was working properly.
Updated by Jim Pingle about 3 years ago
It's not happening to anyone else but you. It's working fine for thousands of other people. If it's not a configuration issue, it's something in your environment. Not a bug. The forum is the best place to figure out the cause.
Updated by pf bug about 3 years ago
Thanks. If you are confirming this is working for everyone then it is good to know, this is because I was doing this setup on two different physical location(different ISP, different hardware)and same situation is happening so I was reporting it.
Updated by pf bug about 3 years ago
Just had more tests, tried the same setup with opnsense, which is also freebsd based is also facing the same issue. However, it is working properly with DD-WRT and fortigate. So this is a possible a bug that related to freebsd instead. Just leaving a additional note here to save others time when come through this post by Google.
Updated by pf bug about 3 years ago
After testing for few days, finally got what is wrong with it. I have to run "pfctl -d" to disable pfsense firewall feature to let pfsense run as a pure route based router. That is also explaining why DD-WRT and fortigate are working but not pfsense and opnsense.
For the one who are reading this, perhaps you might say this is due to configuration issue, this is with a clean installation, and I can tell you even you have chosen "Disable Outbound NAT option" and "create a allow any-to-any rule", the issue is still here UNLESS you disabling the whole firewall with the above command.
So at this point, I have confirmed there is bug related to freebsd core, there is nothing pfsense development team can do. So for the one who need a setup as me, all you can do is just stay tuned for the new version.........