From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] fwmark on bridge+htb
Date: Mon, 02 Jun 2003 16:53:50 +0000 [thread overview]
Message-ID: <marc-lartc-105457294511345@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105456966807290@msgid-missing>
On Monday 02 June 2003 17:59, Rajesh Srivastava wrote:
> Hi,
>
> Fw marking using IP Tables does not work on an Ethernet bridge. Is it
> possible to set up the mark using iptables so that the packet can be
> directly routed to a predefined class using a mark value?
>
> The advantage of this would be the one can use conntrack etc. to track
> connections and forward the packets to the correct class.
>
> Example:
>
> tc qdisc del dev eth0 root
> tc qdisc add dev eth0 root handle 1: htb default 10
>
> tc class add dev eth0 parent 1: classid 1:1 htb rate 512kbit ceil 512kbit
> tc class add dev eth0 parent 1:1 classid 1:10 htb rate 128kbit ceil 256kbit
> tc class add dev eth0 parent 1:1 classid 1:22 htb rate 64kbit ceil 256kbit
> prio 3
> tc class add dev eth0 parent 1:1 classid 1:80 htb rate 64kbit ceil 128kbit
> prio 3
>
> # traditional method of classifying traffic into flowids
>
> tc filter add dev eth0 parent 1:1 protocol ip prio 3 u32 match ip sport 22
> 0xffff flowid 1:22
> tc filter add dev eth0 parent 1:3 protocol ip prio 3 u32 match ip sport 80
> 0xffff flowid 1:80
>
> -------
>
> What I want to achieve is as follows
>
> #set predefined marks
> iptables -t mangle -A PREROUTING -i eth0 -p tcp --sport 22 -m state --state
> ESTABLISHED -j MARK --set-mark 22
> iptables -t mangle -A PREROUTING -i eth0 -p tcp --sport 80 -m state
> --state ESTABLISHED -j MARK --set-mark 80
>
> Now I want to be able to forward packets marked 22 to class 1:22 and those
> marked 80 sent to class 1:80 without using the tc fw filter ( as it does
> not work on bridges ).
>
> Any help or pointers shall be highly appreciated.
You can use ebtales on a bridge. I think it has the same syntax/features as
iptables.
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/
prev parent reply other threads:[~2003-06-02 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 15:59 [LARTC] fwmark on bridge+htb Rajesh Srivastava
2003-06-02 16:53 ` Stef Coene [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=marc-lartc-105457294511345@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.