From: trentbuck@gmail.com (Trent W. Buck)
To: netfilter@vger.kernel.org
Subject: Re: nftables and traffic control utility to QoS
Date: Thu, 30 Apr 2020 13:45:21 +1000 [thread overview]
Message-ID: <87wo5xvdpq.fsf@goll.lan> (raw)
In-Reply-To: a66c2c02-5966-3f1a-e902-3d12d167b5d2@mashtab.org
"d.gubin" <d.gubin@mashtab.org> writes:
> I need to setup QoS on Debian GNU/Linux.
> I am going to use nftables to modify DSCP field in IPv4 Header and tc
> to shape traffic.
>
> Where is packets come in first: in nftables or tc (iproute2) ?
I think this depends on the chain type/hook/priority.
Also, are you talking about egress QoS, or ingress QoS?
If you are completely new to QoS, for egress QoS, try tc-fq_codel
before you resort to hand-tuning DSCP/TOS bits for tc-pfifo_fast.
fq_codel is the default on some systems due to:
https://github.com/systemd/systemd/blob/master/sysctl.d/50-default.conf
If you want an easy test of just the tc qdisc part, OpenSSH sets DSCP bits by default:
ssh example.com # defaults to -o IPQoS=lowdelay
ssh example.com whoami # defaults to -o IPQoS=throughput
sftp example.com # likewise
rsync example.com: # likewise
prev parent reply other threads:[~2020-04-30 3:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 9:04 nftables and traffic control utility to QoS d.gubin
2020-04-30 3:45 ` Trent W. Buck [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wo5xvdpq.fsf@goll.lan \
--to=trentbuck@gmail.com \
--cc=netfilter@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox