Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - tfcb

Pages: [1]

20.1 Legacy Series / Re: Bufferbloat went to "F"

« on: April 27, 2020, 04:05:29 pm »

@AhnHEL Thanks for the link and info! Unfortunately I still receive an "F".

I have an AP running OpenWrt 19.07.2. Seems to me (being quite ignorant on this topic) that a reasonable test is to enable/disable SQM on the AP to see if that makes a difference. Sure enough the report goes from "F" to "A". Results using AP with SQM on/off:
on
http://www.dslreports.com/speedtest/62899222
http://www.dslreports.com/speedtest/62899528

off
http://www.dslreports.com/speedtest/62899335

This leads me to believe the issue is with Opnsense and/or my configuration. I assume others are receiving decent bufferbloat reports so this makes me think the issue is with my configuration. I've tried resetting and following the above linked instructions but no change.

Any #bufferbloat experts out there who know how to debug?

In case this helps...
# ipfw sched show
10000: 500.000 Mbit/s 0 ms burst 0
q75536 50 sl. 0 flows (1 buckets) sched 10000 weight 0 lmax 0 pri 0 droptail
sched 10000 type FQ_CODEL flags 0x0 0 buckets 1 active
FQ_CODEL target 5ms interval 100ms quantum 1000 limit 1000 flows 1024 ECN
Children flowsets: 10000
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 1008 0 0 0
10001: 20.000 Mbit/s 0 ms burst 0
q10001 50 sl. 0 flows (1 buckets) sched 10001 weight 10 lmax 0 pri 0 droptail
sched 10001 type FQ_CODEL flags 0x0 0 buckets 1 active
FQ_CODEL target 5ms interval 100ms quantum 1514 limit 10240 flows 1024 NoECN
Children flowsets: 10002 10001
0 ip 0.0.0.0/0 0.0.0.0/0 1 105 0 0 0

# ipfw queue show
q10000 50 sl. 0 flows (1 buckets) sched 10000 weight 100 lmax 0 pri 0 droptail
q10001 50 sl. 0 flows (1 buckets) sched 10001 weight 100 lmax 0 pri 0 droptail

20.1 Legacy Series / Re: Bufferbloat went to "F"

« on: April 26, 2020, 10:34:12 pm »

Anyone have insight on how to debug Codel shaping?

20.1 Legacy Series / Bufferbloat went to "F"

« on: April 24, 2020, 06:23:34 am »

I've been used the CoDel Shaper for several years with great results. Always reported as an "A". Today I noticed an "F". http://www.dslreports.com/speedtest/62749439 I'm running OPNsense 20.1.5-amd64.

My configuration follows. I haven't changed anything in quite some time. Any suggestions on how to debug?

Code: [Select]

 <TrafficShaper version="1.0.3">
      <pipes>
        <pipe uuid="1dfa8a95-516e-495c-98fc-8f88dd1913ef">
          <number>10000</number>
          <enabled>1</enabled>
          <bandwidth>500</bandwidth>
          <bandwidthMetric>Mbit</bandwidthMetric>
          <queue/>
          <mask>none</mask>
          <buckets/>
          <scheduler>fq_codel</scheduler>
          <codel_enable>1</codel_enable>
          <codel_target/>
          <codel_interval/>
          <codel_ecn_enable>1</codel_ecn_enable>
          <pie_enable>0</pie_enable>
          <fqcodel_quantum>1000</fqcodel_quantum>
          <fqcodel_limit>1000</fqcodel_limit>
          <fqcodel_flows/>
          <origin>TrafficShaper</origin>
          <delay/>
          <description>down pipe</description>
        </pipe>
        <pipe uuid="e11ecafc-949d-41da-a5c1-84cfe7cb910e">
          <number>10001</number>
          <enabled>1</enabled>
          <bandwidth>13</bandwidth>
          <bandwidthMetric>Mbit</bandwidthMetric>
          <queue/>
          <mask>none</mask>
          <buckets/>
          <scheduler>fq_codel</scheduler>
          <codel_enable>1</codel_enable>
          <codel_target/>
          <codel_interval/>
          <codel_ecn_enable>1</codel_ecn_enable>
          <pie_enable>0</pie_enable>
          <fqcodel_quantum/>
          <fqcodel_limit/>
          <fqcodel_flows/>
          <origin>TrafficShaper</origin>
          <delay/>
          <description>up pipe</description>
        </pipe>
      </pipes>
      <queues>
        <queue uuid="62908d10-5d61-4055-b712-0b8c2884e0f3">
          <number>10000</number>
          <enabled>1</enabled>
          <pipe>1dfa8a95-516e-495c-98fc-8f88dd1913ef</pipe>
          <weight>100</weight>
          <mask>none</mask>
          <buckets/>
          <codel_enable>1</codel_enable>
          <codel_target/>
          <codel_interval/>
          <codel_ecn_enable>1</codel_ecn_enable>
          <pie_enable>0</pie_enable>
          <description>down q</description>
          <origin>TrafficShaper</origin>
        </queue>
        <queue uuid="345fb9ee-d389-4a3e-964a-17c7529156cd">
          <number>10001</number>
          <enabled>1</enabled>
          <pipe>e11ecafc-949d-41da-a5c1-84cfe7cb910e</pipe>
          <weight>100</weight>
          <mask>none</mask>
          <buckets/>
          <codel_enable>1</codel_enable>
          <codel_target/>
          <codel_interval/>
          <codel_ecn_enable>1</codel_ecn_enable>
          <pie_enable>0</pie_enable>
          <description>up q</description>
          <origin>TrafficShaper</origin>
        </queue>
      </queues>
      <rules>
        <rule uuid="76274a54-b012-44fd-a163-db641f2a521c">
          <enabled>1</enabled>
          <sequence>1</sequence>
          <interface>wan</interface>
          <interface2/>
          <proto>ip</proto>
          <source>192.168.1.0/24</source>
          <source_not>0</source_not>
          <src_port>any</src_port>
          <destination>any</destination>
          <destination_not>0</destination_not>
          <dst_port>any</dst_port>
          <dscp/>
          <direction/>
          <target>345fb9ee-d389-4a3e-964a-17c7529156cd</target>
          <description>wan rule up</description>
          <origin>TrafficShaper</origin>
        </rule>
        <rule uuid="f440180f-f164-43df-86b1-232871465fe7">
          <enabled>1</enabled>
          <sequence>1</sequence>
          <interface>wan</interface>
          <interface2/>
          <proto>ip</proto>
          <source>any</source>
          <source_not>0</source_not>
          <src_port>any</src_port>
          <destination>192.168.1.0/24</destination>
          <destination_not>0</destination_not>
          <dst_port>any</dst_port>
          <dscp/>
          <direction/>
          <target>62908d10-5d61-4055-b712-0b8c2884e0f3</target>
          <description>wan rule down</description>
          <origin>TrafficShaper</origin>
        </rule>
      </rules>
    </TrafficShaper>

18.1 Legacy Series / Re: Static IP from DHCP Pool

« on: July 12, 2018, 11:42:43 pm »

Thanks for the detailed response. I was misinterpreting the instruction, "If no IPv4 address is given, one will be dynamically allocated from the pool."

18.1 Legacy Series / Static IP from DHCP Pool

« on: July 12, 2018, 06:14:24 pm »

Hi,

I'm attempting to understand how static ip addresses are allocated and presented. When clicking the "+" on Services: DHCPv4: Leases the instructions state:

If an IPv4 address is entered, the address must be outside of the pool.
If no IPv4 address is given, one will be dynamically allocated from the pool.

Unfortunately the IP address for a statically assigned device is always blank on the above-mentioned page and on Services: DHCPv4: [LAN]. How can I view the assigned IP address?

Thanks,

Tim

Pages: [1]