Traffic Shaper w Codel not doing a thing in 2.5

[ryk48]

@nocling All ive got is the following in limiter info:

Limiters:
00001: 10.000 Mbit/s 0 ms burst 0
q131073 1000 sl. 0 flows (1 buckets) sched 65537 weight 0 lmax 0 pri 0 AQM CoDel target 5ms interval 100ms ECN
sched 65537 type FIFO flags 0x0 0 buckets 0 active
00002: 1.000 Mbit/s 0 ms burst 0
q131074 1000 sl. 0 flows (1 buckets) sched 65538 weight 0 lmax 0 pri 0 AQM CoDel target 5ms interval 100ms ECN
sched 65538 type FIFO flags 0x0 0 buckets 0 active

Schedulers:
00001: 10.000 Mbit/s 0 ms burst 0
q00001 50 sl. 0 flows (1 buckets) sched 1 weight 0 lmax 0 pri 0 AQM CoDel target 5ms interval 100ms ECN
sched 1 type FQ_CODEL flags 0x0 0 buckets 0 active
FQ_CODEL target 5ms interval 100ms quantum 1514 limit 10240 flows 1024 ECN
Children flowsets: 1
00002: 1.000 Mbit/s 0 ms burst 0
q00002 50 sl. 0 flows (1 buckets) sched 2 weight 1 lmax 0 pri 0 AQM CoDel target 5ms interval 100ms ECN
sched 2 type FQ_CODEL flags 0x0 0 buckets 0 active
FQ_CODEL target 5ms interval 100ms quantum 1514 limit 10240 flows 1024 ECN
Children flowsets: 2

Queues:
q00001 50 sl. 0 flows (1 buckets) sched 1 weight 0 lmax 0 pri 0 AQM CoDel target 5ms interval 100ms ECN
q00002 50 sl. 0 flows (1 buckets) sched 2 weight 1 lmax 0 pri 0 AQM CoDel target 5ms interval 100ms ECN

If by clearing states you mean to clear browser cache and or go into incognito mode to get a fresh session and try again, i have done that and to no affect. I have not tried rebooting PFSense but i wouldn't think that should be required each time you make a change to a floating firewall rule.

Ive also folowed netgate and Lawrence systems and its not like theres much to it but it just doesnt seemt to have any affect, be it i put my bandwidth at 1mbit or 100mbit

[tomashk]

@ryk48 clearing states means
Diagnostics -> States -> Reset states
then you click on
login-to-view
and Reset button to proceed.

[ryk48]

@tomashk just did that, no change to my bandwidth or bufferbloat

[tomashk]

@ryk48 so I see 2 possible changes:

• if you set 1Mbps, 5ms target won't work - I wrote about it here. For 1Mbps target should be 15ms. You can google for text I quote there and maybe you would be able to find more about and how to calculate it. Basically 5ms target is OK from a few Mbps up. Below it should be bigger value.
• I have read it in multiple places that "Queue Management Algorithm" should be "Tail drop" (for both limiters and queues). CoDel won't give anything there - I believe person responsible for fq_codel implementation in FreeBSD mentioned it (somebody correct me if I'm wrong). Of course scheduler is fq_codel

[ryk48]

@tomashk my actual bandwidth coming in is 1gbps down and 50mbps up cable modem docsis 3.1 but for testing i put the codel limiter at 10mbps down and 1mbps up to see if it would actually do anything and of course it did not, even after resetting the firewall state.

What Tail Drop settings should I be using?

[NOCling]

Why you don't set up your real connection speed and look how well it will work?

[ryk48]

@nocling i did that originally and it didnt seem to do anything so i thought well ill just put the speeds way off and for sure if its doing something ill notice, nope, didnt make any difference which tells me its not doing a darn thing.

[NOCling]

I use 1000/50 Cabel to and Codel works very nice.
If i run a NAS VPN Backup with full Upload, i don't recognize this.
No Bufferbload here.

To set the limiter speed, I use exactly the bandwidths from the provisioning file.

[ryk48]

@nocling ive used a range of bandwidth settings and queue length settings and none of them made a lick of difference, sometimes i felt like one of the settings had made a difference but when i tested again later nope, still buffer bloat issues. Which is why i thought i would wildly play with the bandwidth parameters to see if anything would make any changes and so far none seem to so i am at a loss as to why it doesnt work, what all do i need to check?

[NOCling]

I use this Settings and it just works.

		<queue>
			<name>WAN-Down</name>
			<number>1</number>
			<qlimit>10000</qlimit>
			<plr></plr>
			<description><![CDATA[WAN-Down]]></description>
			<bandwidth>
				<item>
					<bw>1095680</bw>
					<burst></burst>
					<bwscale>Kb</bwscale>
					<bwsched>none</bwsched>
				</item>
			</bandwidth>
			<enabled>on</enabled>
			<buckets></buckets>
			<mask>none</mask>
			<maskbits></maskbits>
			<maskbitsv6></maskbitsv6>
			<delay>0</delay>
			<sched>fq_codel</sched>
			<param_fq_codel_target>5</param_fq_codel_target>
			<param_fq_codel_interval>100</param_fq_codel_interval>
			<param_fq_codel_quantum>1514</param_fq_codel_quantum>
			<param_fq_codel_limit>10240</param_fq_codel_limit>
			<param_fq_codel_flows>1024</param_fq_codel_flows>
			<aqm>codel</aqm>
			<param_codel_target>5</param_codel_target>
			<param_codel_interval>100</param_codel_interval>
			<ecn>on</ecn>
			<queue>
				<name>WAN-DownQ</name>
				<number>1</number>
				<qlimit></qlimit>
				<description><![CDATA[WAN-DownQ]]></description>
				<weight></weight>
				<enabled>on</enabled>
				<buckets></buckets>
				<mask>none</mask>
				<maskbits></maskbits>
				<maskbitsv6></maskbitsv6>
				<aqm>codel</aqm>
				<param_codel_target>5</param_codel_target>
				<param_codel_interval>100</param_codel_interval>
				<ecn>on</ecn>
			</queue>
		</queue>
		<queue>
			<name>WAN-Up</name>
			<number>2</number>
			<qlimit>500</qlimit>
			<plr></plr>
			<description></description>
			<bandwidth>
				<item>
					<bw>54784</bw>
					<burst></burst>
					<bwscale>Kb</bwscale>
					<bwsched>none</bwsched>
				</item>
			</bandwidth>
			<enabled>on</enabled>
			<buckets></buckets>
			<mask>none</mask>
			<maskbits></maskbits>
			<maskbitsv6></maskbitsv6>
			<delay>0</delay>
			<sched>fq_codel</sched>
			<param_fq_codel_target>5</param_fq_codel_target>
			<param_fq_codel_interval>100</param_fq_codel_interval>
			<param_fq_codel_quantum>1514</param_fq_codel_quantum>
			<param_fq_codel_limit>10240</param_fq_codel_limit>
			<param_fq_codel_flows>1024</param_fq_codel_flows>
			<aqm>codel</aqm>
			<param_codel_target>5</param_codel_target>
			<param_codel_interval>100</param_codel_interval>
			<ecn>on</ecn>
			<queue>
				<name>WAN-UpQ</name>
				<number>2</number>
				<qlimit></qlimit>
				<description><![CDATA[WAN-UpQ]]></description>
				<weight></weight>
				<enabled>on</enabled>
				<buckets></buckets>
				<mask>none</mask>
				<maskbits></maskbits>
				<maskbitsv6></maskbitsv6>
				<aqm>codel</aqm>
				<param_codel_target>5</param_codel_target>
				<param_codel_interval>100</param_codel_interval>
				<ecn>on</ecn>
			</queue>
		</queue>
	</dnshaper>

[ryk48]

@nocling Looks like that is what i am using as well. Is there something i am missing in my screenshots?
login-to-view
login-to-view
login-to-view
login-to-view
login-to-view
login-to-view
login-to-view
login-to-view
login-to-view

[NOCling]

Strange, i try the 10/1 MBit Settings and it works as expected.
Ping, Down, UP
login-to-view

But now i use 21.05. with so many fixed bugs. The CE will follow shortly. But try a Beta version in productiv is a risk, you have to balance.
If the limititer is important, you can give it a try.

[ryk48]

@nocling yeah that’s why I found it strange no matter what setting i changed it didn’t seem to have any affect.

I wonder if it has anything to do or doesn’t work well with HA being setup because I have two pfsense boxes running in case one goes down the other picks up. They are vms on different PCs.

[ryk48]

@ryk48 I’m running 2.5.1

[MagikMark]

For Q management use "Tail Drop" instead, as "Codel" has some bugs on it. The result is pretty much the same.

For scheduler use "FQ-Codel"

[ryk48]

@magikmark would i set this for both the limiter and its queue? When i set the queue to taildrop it doesn't like that ECN is enabled.

[ryk48]

@ryk48 assuming what i said was correct, i made those changes and did a dslreports test and once again made zero difference, like it might as well have never been enabled. With my bandwidth set so low i would have expected to see a significant drop in bandwidth when i ran the test, that way id know its actually doing something and I can set the bandwidth back to something more appropriate but no change.

[tomashk]

@ryk48 In the past I observed that the following made big difference while running test on dslreports:

• testing on wi-fi vs cable
• computer (so poor CPU, NIC and other parts)
• antivirus software - even if disabled there was some strange buffering that completely break results - uninstalling has given me normal results
• bufferbloat introduced by ISP's devices/software (it might be hard to change anything if your ISP doesn't know what to do to provide good connection :) )

I'm just thinking aloud and mention what I have seen when I have been trying to fix my bufferbloat.

[ryk48]

@tomashk computer is recent and fairly quick, I only run the browser when doing the test. It’s connected via 10gbit fiber to my switch, I’ve got mediacom 1000/50 cable service on a docsis 3.1 modem. I don’t run AV other than built in windows defender. Back when I had 300-500 mbit service the limiters used to work so I’m not sure what’s different now or why no matter what setting I change it seems to have no effect. Not sure if there’s a log I can check to see if it’s even using the limiters.

[tomashk]

@ryk48 to see if limiters are doing anything go to Diagnostics -> Limiter Info

login-to-view

Lines with red arrows don't appear if limiter/fq_codel is not doing anything. Or at least I understand it like that :)