All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ipsec with 2.6.16-rc3-git6
Date: Thu, 16 Feb 2006 21:29:31 +0100	[thread overview]
Message-ID: <43F4E0AB.5080806@trash.net> (raw)
In-Reply-To: <BAY103-F938A1F933DD48F94C262EB2FB0@phx.gbl>

Marco Berizzi wrote:
> I'm running openswan 2.4.5 with 2.6.16-rc3-git6 on
> slackware 10.2 and I have a very strange problem.
> I don't know if this is the desired behaviour or a
> bug. I'm using iptables 1.3.5
> With the following rules I was running ipsec
> successfully with linux 2.6.15.1 to all our ipsec
> gateway. After I have upgraded to 2.6.16-rc3-git6
> I'm able to run ipsec only to venice_gateway.
> 
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> ACCEPT     all  --  venice_gateway       0.0.0.0/0
> ACCEPT     all  --  127.0.0.1            127.0.0.1
> ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state
> RELATED,ESTABLISHED
> red-me     all  --  0.0.0.0/0            0.0.0.0/0
> 
> Chain red-me (1 references)
> pkts bytes target     prot opt in     out     source              
> destination
>    0     0 ACCEPT     icmp --  *      *       0.0.0.0/0           
> 0.0.0.0/0           icmp type 3
>    0     0 ACCEPT     esp  --  *      *       0.0.0.0/0           
> 0.0.0.0/0
>    0     0 ACCEPT     udp  --  *      *       0.0.0.0/0           
> 0.0.0.0/0           multiport dports 500,4500
> 
> For now, I have workarounded the problem adding a rule for every ipsec
> gateway,
> but this is a problem for mobile users.

2.6.16-rc includes patches for proper netfilter IPsec handling.
Packets will now go through the chains once in plain text and
once encrypted, so you need to adapt your ruleset. There is a
new "policy" match, which allows to match on packets from/to
IPsec tunnels, with that it should be relatively easy to create
rules for your roadwarriors.

  reply	other threads:[~2006-02-16 20:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 15:28 ipsec with 2.6.16-rc3-git6 Marco Berizzi
2006-02-16 20:29 ` Patrick McHardy [this message]
2006-02-17  8:33   ` Marco Berizzi
2006-02-17  8:53     ` Patrick McHardy
2006-02-17  8:58       ` Marco Berizzi
2006-02-17  9:09         ` Patrick McHardy
2006-02-17  9:26           ` Marco Berizzi
2006-02-17  9:29             ` Patrick McHardy
2006-02-17  9:57               ` Marco Berizzi
2006-02-17 10:07               ` Marco Berizzi
2006-02-17 10:11               ` Marco Berizzi
2006-02-17 10:15                 ` Patrick McHardy
2006-02-17 10:35                   ` Marco Berizzi

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=43F4E0AB.5080806@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pupilla@hotmail.com \
    /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.