All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Anderson <jon-anderson@rogers.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bridge + TC
Date: Tue, 16 Mar 2004 01:00:46 +0000	[thread overview]
Message-ID: <405651BE.4010203@rogers.com> (raw)
In-Reply-To: <40559064.6000400@rogers.com>

Roy Walker wrote:

>I posted out on this problem some time ago and could never get 2.4.25 or any 2.6 kernel to work with TC + Bridging.  If anyone has this working and has actually tested it (I am actually just doing IP based iptables filtering from my bridge interface) please let us know what version of iproute you used and what patches you applied and with which version of the kernel.
>
>The older 2.4.2x kernel's seem to work fine for this (I am currently running 2.4.22).
>  
>
I just got this working under 2.4.25 on a different test rig (with only 
2 interfaces) - installed Debian Testing, patched and compiled a kernel 
with relevant stuff, start the bridge, apply tc rules, and *poof* 
packets get filtered/classified properly. All within 1.5 hrs.

`tc -s class show dev eth0` shows the right stuff going through the 
right filters at the right rate.

Versions/patches:
    iproute-20010824-13, from Debian testing
    iptables-1.2.9, from Debian testing (Used: iptables -t mangle -A 
PREROUTING -i eth1 -j MARK --set-mark 0x4 --> no ebtables needed)
    ebtables-brnf-5-vs-2.4.25 patch from ebtables.sourceforge.net
    kernel-2.4.25, with above ebtables patch

Hopefully it'll still work with 3 interfaces when I get 2.4.25 on the 
original test rig!

Cheers,

jon
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-03-16  1:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15 11:15 [LARTC] Bridge + TC Jon Anderson
2004-03-15 15:28 ` Jon Anderson
2004-03-15 17:14 ` Jeroen Vriesman
2004-03-15 21:03 ` miller69
2004-03-15 22:11 ` Roy Walker
2004-03-16  1:00 ` Jon Anderson [this message]
2004-03-16  9:45 ` miller69

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=405651BE.4010203@rogers.com \
    --to=jon-anderson@rogers.com \
    --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.