All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Alexander <jerrya@airmail.net>
To: netfilter-devel@lists.netfilter.org, Jerry <jerry@mavenir.com>
Subject: IPSec and Netfilter
Date: Thu, 13 Oct 2005 16:39:59 -0500	[thread overview]
Message-ID: <434ED42F.6040707@airmail.net> (raw)

Dear NF devel:

         Have just currently  written a user library to implement 
iptables filter and NAT commands.
         Also have written a kernel module that hooks into the PREROUTE 
hook to intercept
packets and collect stats on the IP packet addresses that have been 
entered into iptables.
         Manager just came by and asked me if  Netfilter is above or 
below where IPSEC
resides.    Only know the minimal about IPSEC at this time.  I believe 
his concern is
that  say in tunnel mode,  an IPSEC IP header is built and the contents 
are encrypted and
if Netfilter is below  IPSEC  routing and statistics gathering won't work.
         From browsing the internet,  it appears with the correct 
"iptables NAT command"
that the packet routing will occur correctly.
         I also assume that  when I try to read the packets at the 
PREROUTE point that
it will be the decrypted packet and my statistics gathering will work.
        So far the documentation I have found is not clear on this.
        Could someone knowledgeable in this area please clearify.

                                                                   Thanks,
                                                                             
Jerry

             reply	other threads:[~2005-10-13 21:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13 21:39 Jerry Alexander [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-14  5:08 IPSec and Netfilter Greg Scott
2009-02-10 19:42 ipsec and netfilter Joe Pruett
2009-02-19 12:57 ` Herbert Xu

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=434ED42F.6040707@airmail.net \
    --to=jerrya@airmail.net \
    --cc=jerry@mavenir.com \
    --cc=netfilter-devel@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 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.