From: Richard Lamont <richard@lamont.me.uk>
To: lartc@vger.kernel.org
Subject: [LARTC] Luser seeks tc syntax clue
Date: Tue, 05 Aug 2003 19:05:12 +0000 [thread overview]
Message-ID: <marc-lartc-106011060731604@msgid-missing> (raw)
I'm trying to set a box up that rate limits everything sent to the
outside world, but not limit stuff to my own LAN, using tbf.
I don't really understand what I'm doing, and I could do with some
help to make this script work.
(Please don't bother referring me to the usual documentation. I've read
it. And please don't tell me that I want to do something completely
different. I don't!)
-----------------------------------8<----------------------------------
#!/bin/bash
DEV=eth0
LAN\x192.168.1.0/24
RATE 0kbit
LIMIT\x10000
BURST"000
# Clear out old settings
tc qdisc del dev $DEV root
tc qdisc del dev $DEV ingress
# Start loading new stuff
tc qdisc add dev $DEV root handle 1: prio
# Stuff addressed to LAN goes straight through
tc qdisc add dev $DEV parent 1:1 handle 10: prio
# Stuff addressed to big wide world gets shaped
tc qdisc add dev $DEV parent 1:2 handle 20: tbf limit $LIMIT burst $BURST rate $RATE
# Filter on LAN destination address
tc filter add dev $DEV parent 10: protocol ip u32 match ip src $LAN flowid 1:1
# Default filter for everything else
tc filter add dev $DEV parent 20: protocol ip flowid 1:2
-----------------------------------8<----------------------------------
When I run this script, it says:
RTNETLINK answers: No such file or directory
Unknown filter "flowid", hence option "1:2" is unparsable
Any help gratefully received. TIA.
--
Richard Lamont
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-08-05 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 19:05 Richard Lamont [this message]
2003-08-05 22:09 ` [LARTC] Luser seeks tc syntax clue Steffen Moser
2003-08-05 22:54 ` Richard Lamont
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=marc-lartc-106011060731604@msgid-missing \
--to=richard@lamont.me.uk \
--cc=lartc@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