From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Can I Classify Non-IP Traffic?
Date: Thu, 02 Jan 2003 19:51:28 +0000 [thread overview]
Message-ID: <marc-lartc-104153726526311@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104152616513416@msgid-missing>
Jose,
If I read his query correctly, he wants to classify IPX or something else.
/etc/protocols is a mapping of identifiers for the contents of IP
packets, so in this case, /etc/protocols doesn't help him.
Seems like he needs a "protocol generic" (or better yet for him, "protocol
ipx"), which would allow him to count byte offsets in the manner of u32.
I know of no such tool.
-Martin
: > 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.
: >
: Well, you seem to be already using "iptables" and the "fw" filter to
: mark and categorize traffic. "iptables" can also match non-IP
: protocols, using "--protocolo PROTOCOL". You can't go deeper into these
: non-IP packets, but you can mark them by protocol, using any of the
: protocols in the "/etc/protocols" file.
:
: Hope it helps.
:
:
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
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 19:51 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
2003-01-02 19:41 ` Jose Luis Domingo Lopez
2003-01-02 19:51 ` Martin A. Brown [this message]
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-104153726526311@msgid-missing \
--to=mabrown-lartc@securepipe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox