All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Cc: mludvig@suse.cz,  guillaume@morinfr.org,  alex@samad.com.au,
	herbert@gondor.apana.org.au,  JMChandonia@lbl.gov
Subject: Netfilter+IPsec patches in pom-ng now
Date: Wed, 14 Apr 2004 04:30:32 +0200	[thread overview]
Message-ID: <407CA248.3000302@trash.net> (raw)

I've just commited the netfilter+ipsec patches to pom-ng.

The input patch is replaced with a new version which just
posts packets which are done with ipsec into the stack again
and lets them traverse the hooks at the usual places. The
advantage is the simplicity and transparency for netfilter,
the disadvantage is an extra pass through the stack.

Some bugs have been fixed since the last set of patches:

- IPIP packets decapsulated from IPsec missed the input hooks
- multiple other problems related to the old input patch
- compiles without CONFIG_NETFILTER
- icmp/igmp didn't traverse POST_ROUTING before encapsulation
- possible NULL-ptr dereference fixed

They still need some work but mostly cleanup, nothing critical.

The patches are split into four parts, but pom-ng does not handle
recursive dependencies when dependant patches change the same
piece of code and --dry-run fails, so the patches need to be
applied manually in the right order. The patches are named in
a way that they will appear in the correct order during "runme".

Regards
Patrick

PS: I've CCed some people who showed interest, but who I think
are not subscribed to the list. Please tell me in private if
you want don't want these mails.

             reply	other threads:[~2004-04-14  2:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14  2:30 Patrick McHardy [this message]
2004-04-20 10:48 ` Netfilter+IPsec patches in pom-ng now Alexander Samad
2004-04-20 13:20   ` Ivan Mitev
2004-04-20 21:34     ` Alexander Samad
2004-04-21  0:21 ` Alexander Samad

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=407CA248.3000302@trash.net \
    --to=kaber@trash.net \
    --cc=JMChandonia@lbl.gov \
    --cc=alex@samad.com.au \
    --cc=guillaume@morinfr.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=mludvig@suse.cz \
    --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.