All of lore.kernel.org
 help / color / mirror / Atom feed
From: malware@t-online.de (Michael Mueller)
Cc: netfilter@lists.netfilter.org
Subject: Re: Matching IPSEC encapsulated traffic with connection tracking
Date: Tue, 04 Jan 2005 10:16:33 +0100	[thread overview]
Message-ID: <41DA5EF1.7050306@t-online.de> (raw)
In-Reply-To: <41DA5373.5080404@gmx.net>

Hi,

Robert Dahlem wrote:
> The problem is to combine these two scenarios: make both netfilter and
> IPSEC active at the same time.
[...]
> # SYN packet
> HostA kernel: Debug INPUT:IN=eth1 OUT=
>     MAC=00:0a:5e:4d:0f:12:00:0a:5e:4d:10:42:08:00
>     SRC=10.133.127.197 DST=10.133.126.6
>     LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=5559 DF
>     PROTO=TCP SPT=1023 DPT=22 WINDOW=5840 RES=0x00 SYN URGP=0

This packet causes the problem because the encapsulated TCP (transport 
mode) or IP packet (tunnel mode) is not inspected and due the connection 
tracking does not know of.

Robert, you may want to look into the mailing list archive of the 
developer list (https://lists.netfilter.org/pipermail/netfilter-devel/) 
and/or the current patch-o-matic. January last year there was a 
discussion on the developer list with the topic "NAT before IPsec with 
2.6" which caused  Harald Welte to produce a patch which may be of help 
to you. I have no idea of the current state of this.


Michael


  reply	other threads:[~2005-01-04  9:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-04  8:27 Matching IPSEC encapsulated traffic with connection tracking Robert Dahlem
2005-01-04  9:16 ` Michael Mueller [this message]
2005-01-06 16:29 ` Jason Opperisano

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=41DA5EF1.7050306@t-online.de \
    --to=malware@t-online.de \
    --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 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.