FQ_Pie no internet
-
Under limiters i created two rules one for upload and one for download
Queue Management Algorithm is "PIE"
Scheduler "FQ_Pie"Then i added the firewall rules under floating.
if i use these setting then i can get internet:
Queue Management Algorithm is "CoDel"
Scheduler "FQ_CoDel"Is there another setting you need to check off when using FQ_Pie?
-
Not sure I've ever tried that.
Do you see errors logged?
Do you see traffic in the pipe in Diag > Limiter info? -
Limiters:
00001: 900.000 Mbit/s 0 ms burst 0
q131073 3000 sl. 0 flows (1 buckets) sched 65537 weight 0 lmax 0 pri 0 droptail
sched 65537 type FIFO flags 0x0 0 buckets 0 active
00002: 38.000 Mbit/s 0 ms burst 0
q131074 1000 sl. 0 flows (1 buckets) sched 65538 weight 0 lmax 0 pri 0 droptail
sched 65538 type FIFO flags 0x0 0 buckets 0 activeSchedulers:
00001: 900.000 Mbit/s 0 ms burst 0
q00001 50 sl. 0 flows (1 buckets) sched 1 weight 0 lmax 0 pri 0 AQM type PIE target 15ms tupdate 15ms alpha 0.125 beta 1.25 max_burst 150ms max_ecnth 0.099 NoECN NoCapDrop DRE NoDerand
sched 1 type FQ_PIE flags 0x0 0 buckets 0 active
FQ_PIE target 15ms tupdate 15ms alpha 0.125 beta 1.25 max_burst 150ms max_ecnth 0.099 quantum 1514 limit 10240 flows 1024 ECN NoCapDrop DRE NoDerand
Children flowsets: 1
00002: 38.000 Mbit/s 0 ms burst 0
q00002 50 sl. 0 flows (1 buckets) sched 2 weight 0 lmax 0 pri 0 AQM type PIE target 15ms tupdate 15ms alpha 0.125 beta 1.25 max_burst 150ms max_ecnth 0.099 NoECN NoCapDrop DRE NoDerand
sched 2 type FQ_PIE flags 0x0 0 buckets 1 active
FQ_PIE target 15ms tupdate 15ms alpha 0.125 beta 1.25 max_burst 150ms max_ecnth 0.099 quantum 1514 limit 10240 flows 1024 ECN NoCapDrop DRE NoDerand
Children flowsets: 2
BKT Prot Source IP/port_ Dest. IP/port Tot_pkt/bytes Pkt/Byte Drp
0 ip 0.0.0.0/0 0.0.0.0/0 1 29 0 0 0Queues:
q00001 50 sl. 0 flows (1 buckets) sched 1 weight 0 lmax 0 pri 0 AQM type PIE target 15ms tupdate 15ms alpha 0.125 beta 1.25 max_burst 150ms max_ecnth 0.099 NoECN NoCapDrop DRE NoDerand
q00002 50 sl. 0 flows (1 buckets) sched 2 weight 0 lmax 0 pri 0 AQM type PIE target 15ms tupdate 15ms alpha 0.125 beta 1.25 max_burst 150ms max_ecnth 0.099 NoECN NoCapDrop DRE NoDerand -
@martin6734
As fare as i can tell i don't see any errors. -
Do you see the traffic in those pipe vary when you are trying to connect through those?
-
@martin6734
What am I checking for? Is there a particular place I should check on the firewall? Do you need to see my firewall rules? Thanks for the help.I’m running version 23.01 on a Netgate 6100.
I followed the instruction listed to setup fq_codel on the Netgate website. Everything is setup exactly as what was instructed.
-
Look at the Diag > Limiters screen when it's configured with CoDel and passing traffic as expected. You'll see traffic going into the pipes as the screens updates.
Now compare that with the Limiters configured using Pie. Do you still see traffic entering the pipes, any variation? -
The size of traffic going through pie is substantially smaller. Pie is 150bytes and codel is well over 1000bytes.
Before posting for help, I did some searching on the web. I couldn't find anybody that had gotten Pie working. Thanks for the help maybe someone else knows what could be wrong with pie. I will look into it further when version 23.01 is released out of RC.
Network setup:
1 netgate 6100 firewall
4 cisco small business switches
5 ubiquiti uap 6 lite
1 ubiquiti uap 6 lr -
Same here. I waited for 23.01 Stable and still when I send traffic to FQ_Pie limiters using floating rules, it breaks internet.
-
I noticed the same thing.
Fresh install as I wanted to test out FQ_PIE and once I setup this, it stopped passing any traffic to the internet.
I tried numerous things as rebooting / clearing all the rules and nothing worked as I thought I was doing something wrong.
I tested out all the same but changing FQ_PIE to FQ_CODEL for the scheduler and everything worked. I eventually gave up but definitely seems to be broken in 23.01 at least as I ran that with all the system recommended system patches.
-
https://redmine.pfsense.org/issues/13996
If your steps to reproduce differ from those shown you might want to comment there.
Steve
-
Is there any development on this? Issue still seen on 2.7.2
-
@milindhvijay
Still an issue on 23.09.1.