Bug #14684
open
Allowed IP Address does not control incoming speed in captive portal, PF Sense Release 2.7 Latest
0%
Description
Hi PF Sense Engineers, I like to report a bug. There is problem in captive portal in latest release 2.7, In captive portal it cannot control speed in Allowed Ip Addresses. <--- This is the problem which need to be fixed.
However captive portal mac based speed limitation but it should also work with Allowed IP Addreses.
Therefore as a PF Sense user I am requesting to kindly address this issue
I will be highly oblidged.
Files
| no restriction set.png (368 KB) no restriction set.png | iperf - no restriction set | ||
| 150 up, download unset.png (367 KB) 150 up, download unset.png | iperf - 150 up, download unset | ||
| 150 down, upload unset.png (365 KB) 150 down, upload unset.png | iperf - 150 down, upload unset |
Updated by Noman Haroon over 1 year ago
Dear PF Sense Engineers, I have shared a video, Kindly check it.
https://drive.google.com/drive/folders/1kVCGz0lYrItvGxy6muFJ05PSN0l2O5B4?usp=sharing
Updated by Noman Haroon over 1 year ago
I Also make a issue thread on forum.netgate.com, where Mr. Rcoleman-netgate advice me to address this bug
on this bug reporting form. I am thankful to him.
https://forum.netgate.com/topic/182169/allowed-ip-address-does-not-work-in-captive-portal
Updated by Chris W over 1 year ago
- File no restriction set.png no restriction set.png added
- File 150 up, download unset.png 150 up, download unset.png added
- File 150 down, upload unset.png 150 down, upload unset.png added
What I see on both 2.7 and 23.05.1 that applying an upload bandwidth limitation for Allowed IP Addresses has little effect but a download limit seems to work, though possibly irregularly. With an upload limit set but a download unset, the result was about a 10% speed reduction. With the download limit set and upload unset, I'd see iperf on the client receiving at just under the specified limit (150 Kib/s). Fast.com in Firefox would show well above this (tens of megabytes), but still limited and nowhere near the result if no limits were set at all (nearly 300 Mbps of my ISP plan). Setting both an up and down limit results in the same behavior as with just a download limit.
Setting the Per-user bandwidth restriction on the portal's Configuration tab, and limiting by MAC address both still work fine. Other than a portal zone name and turning off authentication (click-through was still necessary), the portal settings were left default and I set the bandwidth restriction to 150 Kib/s. Client was a Linux virtual machine behind a pfSense VM. Client was given a static IP address and set to use pfSense for a gateway and DNS.
Fast.com results were:
16 Mbps with limit 150 Kbit/s down, up unset
28 Mbps with 150 set for both both up and down
270 Mbps with 150 up, down unset