From: Jose Luis Domingo Lopez <lartc@24x7linux.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Classifying IPv6 tunnel traffic
Date: Mon, 01 Sep 2003 19:27:13 +0000 [thread overview]
Message-ID: <marc-lartc-106244452722419@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106243721415155@msgid-missing>
On Monday, 01 September 2003, at 19:25:13 +0200,
Thilo Schulz wrote:
> Currently, I have got an ipv6 tunnel, that has sit0 as interface.
> Since the Tunnel wrapping stuff is still ipv4 traffic that goes over the ppp0
> interface, i wondered whether I can classify this kind of traffic and put
> into a class. (i dont need to do any ipv6 shaping), So I wondered, whether
> someone here can give me the filter directive to match these tunnel packets.
>
6to4 IP traffic (I think this is its name, IPv6 traffic encapsulated
into IPv4 packets) can be easily identified. They are regular IPv4
packets, with a "protocol" field of 0x29, or decimal 41.
So use iptables and match packets on protocol. What you can't do (to the
best of my knowledge) if going deeper into the packets, and see if IPv6
pakects inside the IPv4 ones are of some kind or another.
Regards,
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.6.0-test4-mm4)
_______________________________________________
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-09-01 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 17:25 [LARTC] Classifying IPv6 tunnel traffic Thilo Schulz
2003-09-01 19:27 ` Jose Luis Domingo Lopez [this message]
2003-09-02 12:06 ` Thilo Schulz
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-106244452722419@msgid-missing \
--to=lartc@24x7linux.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