Flent-users discussion archives
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: flent-users <flent-users@flent.org>
Subject: [Flent-users] ICMP prioritization
Date: Fri, 9 Feb 2018 13:10:56 +0100	[thread overview]
Message-ID: <0816A8DF-3B3A-47EB-B757-7FC849416B50@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1154 bytes --]

For interest, this is the first time I’m using Flent much over the Internet, and now I can clearly see how icmp is being prioritized somewhere. I just looked at my ISPs backhaul qos scripts now and I was mistaken earlier- there appear to be five strict priority classes (lower numbers get higher priority), and they’re prioritizing icmp. A few classifications are done with straight iptables and the rest with Linux’s layer7 stuff. Classes:

1: icmp, ospf, bgp, dhcp, dns, irc, jabber, snmp, whois
2: udp, quake-halflife, worldofwarcraft
3: tcp port 80
4: ftp, cvs, biff, h323, imap, live365, pop3, rtsp, shoutcast, smtp, ssl, tftp
5: bittorrent, directconnect, edonkey, http-itunes, soulseek

Hmm, I think I may soon be suggesting some improvements. I bet “cake besteffort dual-srchost” on the way out and “cake besteffort dual-dsthost” on the way in will outperform this system with very little additional work. These rules were written years, if not now decades ago, as is clear by some of the mostly defunct protocols listed. I may do a few more tests to netperf-eu.bufferbloat.net along the way to get this sorted out… :)


[-- Attachment #1.2.1: Type: text/html, Size: 1864 bytes --]

[-- Attachment #1.2.2: all_scaled.png --]
[-- Type: image/png, Size: 241113 bytes --]

[-- Attachment #2: Type: text/plain, Size: 151 bytes --]

_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org

                 reply	other threads:[~2018-02-09 12:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0816A8DF-3B3A-47EB-B757-7FC849416B50@gmail.com \
    --to=peteheist@gmail.com \
    --cc=flent-users@flent.org \
    --subject='Re: [Flent-users] ICMP prioritization' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox