Traffic Shaper: Limiter
-
It breaks at ipv6 address. That explained my situation
2.2.6-RELEASE (amd64)
-
High priority bug that has broken a key function in pfSense firewall has been unsolved for over a year now.
No proposals how to fix it. No descriptions on what actually broke, why it broke and what could be the best paths to solving the problem.
What is going on here? My faith in you is fading. Is this how you usually deal with High priority bugs? Who dares to take responsibility for this?
Sam
https://redmine.pfsense.org/issues/4326
-
Theres a workaround for squid with limiter But it breaks NAT reflection :(
-
High priority bug that has broken a key function in pfSense firewall has been unsolved for over a year now.
No proposals how to fix it. No descriptions on what actually broke, why it broke and what could be the best paths to solving the problem.
What is going on here? My faith in you is fading. Is this how you usually deal with High priority bugs? Who dares to take responsibility for this?
Sam
https://redmine.pfsense.org/issues/4326
I hear you. I'm eagerly waiting for this and https://redmine.pfsense.org/issues/4405 to be finally addressed so I can start using the traffic shaper again. Hopefully 2.3.2 is going to be it.
-
Not fixed yet. https://redmine.pfsense.org/issues/4326
Target version changed from to 2.2.4.
Done: 0% -
Is there another way to limit the bandwidth on each computer separately? as similar as to Limiter of <traffic shaper="">.
PfSense 2.3</traffic> -
Depends on how many computers/devices. HFSC allow up to 15 or 16 queues.
-
Is there another way to limit the bandwidth on each computer separately? as similar as to Limiter of <traffic shaper="">.
PfSense 2.3</traffic>If you created an HFSC queue for each IP and assign each queue the same (anything, it just needs to be the same; "1Kbit" for example) link-share bandwidth, and it would work almost exactly like your previous setup with limiters/ipfw.
Depends on how many computers/devices. HFSC allow up to 15 or 16 queues.
lol, actually it's 2048 at the moment. Close though… ::)
https://github.com/pfsense/FreeBSD-src/blob/RELENG_2_3_1/sys/contrib/altq/altq/altq_hfsc.h#L53 -
Is there another way to limit the bandwidth on each computer separately? as similar as to Limiter of <traffic shaper="">.
PfSense 2.3</traffic>If you created an HFSC queue for each IP and assign each queue the same (anything, it just needs to be the same; "1Kbit" for example) link-share bandwidth, and it would work almost exactly like your previous setup with limiters/ipfw.
Depends on how many computers/devices. HFSC allow up to 15 or 16 queues.
lol, actually it's 2048 at the moment. Close though… ::)
https://github.com/pfsense/FreeBSD-src/blob/RELENG_2_3_1/sys/contrib/altq/altq/altq_hfsc.h#L53Whole crap! Nice to know. I read something somewhere that said 16 was used because of computational costs, but maybe that was old or didn't apply to the FreeBSD implementation.
-
Is there another way to limit the bandwidth on each computer separately? as similar as to Limiter of <traffic shaper="">.
PfSense 2.3</traffic>If you created an HFSC queue for each IP and assign each queue the same (anything, it just needs to be the same; "1Kbit" for example) link-share bandwidth, and it would work almost exactly like your previous setup with limiters/ipfw.
Depends on how many computers/devices. HFSC allow up to 15 or 16 queues.
lol, actually it's 2048 at the moment. Close though… ::)
https://github.com/pfsense/FreeBSD-src/blob/RELENG_2_3_1/sys/contrib/altq/altq/altq_hfsc.h#L53Whole crap! Nice to know. I read something somewhere that said 16 was used because of computational costs, but maybe that was old or didn't apply to the FreeBSD implementation.
I know! FreeBSD defaults to 64. 2048 though… I like how pfSense plays. ;D
I kinda thought it was limited to ~16 because that is the highest priority in ALTQ. Of course, that means nothing in itself.
-
Hi, thanks Nullity and Harvy66…. this worked. It's not as practical like the limiter but it works too.
