All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thilo Schulz <arny@ats.s.bawue.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Classifying IPv6 tunnel traffic
Date: Tue, 02 Sep 2003 12:06:15 +0000	[thread overview]
Message-ID: <marc-lartc-106250447701679@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106243721415155@msgid-missing>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 01 September 2003 21:27, Jose Luis Domingo Lopez wrote:
> 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.

Thank you, that was exactly the information I needed, though I could probably 
also have consulted /etc/protocols myself d'oh ..

> So use iptables and match packets on protocol.

"u32 match ip protocol 41 0xff"  does the job pretty well :)

> 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.

2. I wasn't planning on doing that ;)

- -- 
 - Thilo Schulz

My public GnuPG key is available at http://home.bawue.de/~arny/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/VIe/Zx4hBtWQhl4RAp47AKCD8PdEO3b7Qmfe3wNN2B0/mpb/RACghi7C
j3QnJTzFhmp7WsbA/CmO15U=9QBS
-----END PGP SIGNATURE-----

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

      parent reply	other threads:[~2003-09-02 12:06 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
2003-09-02 12:06 ` Thilo Schulz [this message]

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-106250447701679@msgid-missing \
    --to=arny@ats.s.bawue.de \
    --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.