From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] giving internal traffic a own queu
Date: Wed, 23 Apr 2003 18:04:20 +0000 [thread overview]
Message-ID: <marc-lartc-105112116613353@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105108064932053@msgid-missing>
On Wednesday 23 April 2003 08:48, k3ssl@k3ssl.de wrote:
> Hi
> Im using a Linux Router, sharing dsl for the lan.
> Now Im trying to set up one queue for each Computer conected from lan.
> Setting up the queues is easy, but making a rule that matches them not.
> tc filter add dev ppp0 parent 1: protocol ip prio 10 u32 \
> match ip src 10.0.0.2/32 \
> flowid 1:20
> that doesnt work at all. It produces no error, but they still use default
> (1:50) instead of 1:20.
> Now my question, how do you mark your internal traffic?
> I dont want to change anything at eth1 (internal net) because the router
> works as Fileserver too.
> How do I use eg. iptables? i ve found sth. calles --mark value, but nowere
> explained what "value" means and what values are legal and I dont want it
> to match any rule for the Router (eg. minimized delay or sth).
You have indeed to mark the packets with iptables when they enter your router.
That mark can be used by the fw filter to classify the packets.
For examples, see www.docum.org. I use that filter a lot in my test setups.
If you mark a packet, you give it a number that you choose. That number is
only valid in the linux kernel of the router. The fw filter can use that
number to classify the packets. So you can choose whatever number you want.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-04-23 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 6:48 [LARTC] giving internal traffic a own queu k3ssl
2003-04-23 18:04 ` Stef Coene [this message]
2003-05-01 3:59 ` Martin A. Brown
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-105112116613353@msgid-missing \
--to=stef.coene@docum.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.