From: Werner Almesberger <wa@almesberger.net>
To: lartc@vger.kernel.org
Subject: [LARTC] tcng version 8w
Date: Fri, 13 Sep 2002 07:46:10 +0000 [thread overview]
Message-ID: <marc-lartc-103190326327420@msgid-missing> (raw)
... is on SourceForge, http://tcng.sourceforge.net/#src
This one has the first steps towards getting non-IPv4 classification
right:
- I've added fields for skb meta-data (meta_protocol, etc.)
- if USE_META_PROTOCOL is #defined (tcc -D... or tcsim -Xc,-D...),
ip_hdr and ip6_hdr check the protocol number
- if_u32 generates distinct classifier branches for each protocol
- f_fw, f_tcindex, and f_u32 now default to ETH_P_ALL instead of
ETH_P_IP
The latter change affects how u32 classification works !
tests/protu32 illustrates how protocol-aware classification
is used.
What's missing:
- C and tcc-ext-match need to support meta_protocol too
- if_u32 does a few ugly things, and can also generate redundant
filter stubs
- remove USE_META_PROTOCOL :-)
The next version will make meta data classification visible at the
external interface, so if you're using this interface, this change
will probably break your program. If you don't want to add support
for meta fields to your program right now, you can simply work
around the problem by redefinition ip_hdr and ip6_hdr to their old
values (i.e. remove the if ... clause).
The full change log is below.
- Werner
---------------------------------- cut here -----------------------------------
Version 8w (13-SEP-2002)
------------------------
- added root of meta fields (__meta) and definitions for meta-fields in meta.tc
(included via fields.tc)
- added some layer > 2 protocol numbers to values.tc
- tcsim's send command now has a "protocol" attribute (default: ETH_P_IP)
- updated documentation according to above changes
- ip_hdr and ip6_hdr now check meta_protocol if USE_META_PROTOCOL is #defined
- added protocol selection support to if_u32.c (tests/protu32)
- filters fw, tcindex, and u32, now default to ETH_P_ALL instad of ETH_P_IP
- updated tests/cbqroot, tests/egress, tests/named, tests/selpath,
tests/selpathcbq, tests/selpathdup, and tests/setpathgred accordingly
- configure now detects and prints kernel extra version (e.g. pre7)
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-09-13 7:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-103190326327420@msgid-missing \
--to=wa@almesberger.net \
--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.