Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: Netfilter User Mailinglist <netfilter@lists.netfilter.org>
Subject: ipv4 and ipv6 tables
Date: Fri, 27 Aug 2004 17:08:20 -0500	[thread overview]
Message-ID: <412FB0D4.8080303@pbl.ca> (raw)

Ok, if I have good old ipv4 packet, or good new ipv6 packet they will go 
through respective chains in respective tables (either for ipv4 or 
ipv6).  But how about ipv6-in-ipv4 packets?  How is this handled when 
packet is forwarded (especially by ipv6 enabled host)?  How does the 
packet traverse tables and chains once it reach destination and is 
unwrapped from its ipv4 wrapper (does it go through both ipv4 and ipv6 
tables and chains)?  Any other special cases to watch for to prevent 
packets that should be blocked to go through ipv6 back door?

-- 
Aleksandar Milivojevic <amilivojevic@pbl.ca>    Pollard Banknote Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7


             reply	other threads:[~2004-08-27 22:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 22:08 Aleksandar Milivojevic [this message]
2004-08-27 22:30 ` ipv4 and ipv6 tables Alistair Tonner

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=412FB0D4.8080303@pbl.ca \
    --to=amilivojevic@pbl.ca \
    --cc=netfilter@lists.netfilter.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