Shaper Pipe Delay not applying ?

Started by bobbis, January 21, 2021, 03:10:11 AM

Previous topic - Next topic
January 21, 2021, 03:10:11 AM Last Edit: January 21, 2021, 03:22:33 AM by bobbis
Hello,

opnsense 21.1 (nano)amd64

when i try to set on the webinterface, in this case called Pipename: "Download Pipe"(Firewall->Shaper->Pipes:(+Download pipe+), a delay like 10ms to the Pipe, it does not seems to apply the settings.
When i check out the output from ipfw list pipe then the "Download Pipe" or on the screenshot, called Pipe:"10000"... there is no delay, it shows "0 ms" for the "Download pipe".
If i add a pipe manually from the command line:
/sbin/ipfw -q pipe 1 config delay 10ms bw 2Mbit/s
then you can see the pipe "00001" has a delay from "10 ms" !



/usr/local/etc/ipfw.rules
...8-< snip
#======================================================================================
# define dummynet pipes
#======================================================================================
pipe 10000 config bw 40Mbit/s queue 2 buckets 1 type  fq_codel  delay 10  target 5  interval 100  ecn    quantum 1514   limit 1000   flows 1024
pipe 10001 config bw 1700Kbit/s buckets 1 type  fq_codel  delay 10  target 5  interval 100  ecn    quantum 1514   limit 1000   flows 1024
>-8 snip

after rebooting still "0 ms" ...

January 30, 2021, 01:51:57 AM #1 Last Edit: January 30, 2021, 03:26:42 AM by tswalker
sorry to necro this, but i have similar question...

seems like applying delay on pipe doesn't set anything


10000:  15.000 Mbit/s    0 ms burst 0
q75536  50 sl. 0 flows (1 buckets) sched 10000 weight 0 lmax 0 pri 0 droptail
sched 75536 type FIFO flags 0x0 0 buckets 0 active


[edit]...

while ipfw.rules clearly has this configured...

#======================================================================================
# define dummynet pipes
#======================================================================================
pipe 10000 config bw 15Mbit/s type  fq_codel  delay 100  ecn    quantum 300


seems something syntax wise is wrong maybe?

root@OPNsense:/usr/local/etc # ipfw pipe 10000 config bw 15Mbit/s type fq_codel delay 100 ecn quantum 300
delay is Invalid parameter
100 is Invalid parameter


[edit #2]
OK!  seems that the order is ver y particular and delay needs to immediately follow the config parameter to take effect such as this:

ipfw pipe 10000 config delay 100 bw 15Mbit/s type fq_codel ecn quantum 300


results:

root@OPNsense:/usr/local/etc # ipfw pipe 10000 show
10000:  15.000 Mbit/s  100 ms burst 0
q75536  50 sl. 0 flows (1 buckets) sched 10000 weight 0 lmax 0 pri 0 droptail
sched 75536 type FIFO flags 0x0 0 buckets 0 active

heya.. i've tested this parameter order and it does in fact work very well when preceeding the "config" flag for ipfw command line execution, otherwise you get an "Invalid" parameter error.

I believe the backing scripts that generate ipfw.rules file configurator need some correction to set this.

I've submitted a bug here. hopefully this I made right.
https://github.com/opnsense/core/issues/4650


fixed in patch, i tested and it is now applying delay settings:

opnsense-patch ff547eb


thanks you all