From: rowdy <rowdy@fishpuppy.com>
To: netfilter@lists.netfilter.org
Subject: Re: IPSec through my firewall
Date: Wed, 16 Feb 2005 01:29:26 -0800 [thread overview]
Message-ID: <200502160129.26423.rowdy@com> (raw)
In-Reply-To: <200502151715.j1FHFtfO029324@pepsi.fishpuppy.com>
On Tuesday 15 February 2005 09:15, Ola Nilsson wrote:
> I've got problems with getting IPSec (using NAT-T) traffic through my
> Linux 2.6.10 based firewall. I've now changed my iptables script to
> something rather simple:
>
> iptables -P INPUT ACCEPT
> iptables -P OUTPUT ACCEPT
> iptables -P FORWARD ACCEPT
> iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
I've been struggling with this as well. Take a look at
http://www.freeswan.org/freeswan_snaps/CURRENT-SNAP/doc/firewall.html .
I used this query to find this link and a number of others that could be
helpful: "esp ipsec firewall rule"
I added rules like the following (but to user chains that I then added to the
input, output and forward chains) to solve my hassles (clipped from the
freeswan link above):
# allow IPsec
#
# IKE negotiations
iptables -I INPUT -p udp --sport 500 --dport 500 -j ACCEPT
iptables -I OUTPUT -p udp --sport 500 --dport 500 -j ACCEPT
# ESP encryption and authentication
iptables -I INPUT -p 50 -j ACCEPT
iptables -I OUTPUT -p 50 -j ACCEPT
Good luck.
next parent reply other threads:[~2005-02-16 9:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200502151715.j1FHFtfO029324@pepsi.fishpuppy.com>
2005-02-16 9:29 ` rowdy [this message]
2005-02-16 10:27 ` IPSec through my firewall Georgi Alexandrov
2005-02-16 12:46 ` Ola Nilsson
2005-02-16 14:59 ` Jean Caron
2005-02-16 18:08 ` Ola Nilsson
2005-02-16 14:03 Samuel Jean
-- strict thread matches above, loose matches on Subject: below --
2005-02-15 10:25 Ola Nilsson
2005-02-15 14:46 ` Michael Gale
2005-02-15 15:15 ` Ola Nilsson
2005-02-15 15:38 ` Michael Gale
2005-02-15 15:07 ` Jason Opperisano
2005-02-15 22:00 ` Ola Nilsson
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=200502160129.26423.rowdy@com \
--to=rowdy@fishpuppy.com \
--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.