From: Ivo De Decker <ivo@student.rug.ac.be>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Can I Classify Non-IP Traffic?
Date: Thu, 02 Jan 2003 17:05:11 +0000 [thread overview]
Message-ID: <marc-lartc-104152718814838@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104152616513416@msgid-missing>
On Thu, Jan 02, 2003 at 04:40:34PM +0000, Griff@BP3Web wrote:
> Background: Thanks to the LARTC howto, this list and Stef Coene's and
> devik's excellent web sites I now have an ethernet bridge (patch
> bridge-nf.0.0.7) happily prioritising traffic (12Mbit) into 10 queues
> (9 for IP and 1 for non-IP) using a combination of iptables (fwmark)
> and htb3 and sfq. Many thanks.
>
> At the moment I'm filtering all non-IP traffic by setting the default
> queue on the htb root qdisc to my non-IP class and having my last rule
> in iptables (POSTROUTING) marks all IP packets such that htb places
> these packets into my lowest priority IP queue (note this is different
> from the default).
>
> My question is can classify the non-IP traffic? Ideally I'd like to be
> able create a queue for IPX traffic.I know the tc filters command has a
> protocol statement but I can't find any information about setting this
> to anything but ip or ipv6.
Using ebtables, it is possible to filter non-ip traffic.
It is merged into the 2.5 kernel. For the 2.4, you need patches.
http://users.pandora.be/bart.de.schuymer/ebtables/
Greetings,
Ivo De Decker
_______________________________________________
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-01-02 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 16:40 [LARTC] Can I Classify Non-IP Traffic? Griff@BP3Web
2003-01-02 17:05 ` Ivo De Decker [this message]
2003-01-02 19:41 ` Jose Luis Domingo Lopez
2003-01-02 19:51 ` Martin A. Brown
2003-01-03 3:00 ` Hannes Ebner
2003-01-03 5:36 ` Martin A. Brown
2003-01-03 21:23 ` Julian Anastasov
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-104152718814838@msgid-missing \
--to=ivo@student.rug.ac.be \
--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.