From: Lane Powers <lpowers@mis.net>
To: netfilter@lists.netfilter.org
Subject: Re: kernel 2.6 IPsec and netfilter
Date: Mon, 29 Mar 2004 07:36:49 -0500 [thread overview]
Message-ID: <40681861.1030704@mis.net> (raw)
In-Reply-To: <4068040C.AA93F507@india.hp.com>
Well, it might not be perfect, but here is what I do, and it 'works for me'
In my ipsec.conf I use the updown script functionality of pluto, i.e. in
my conn default I put
leftupdown=/usr/local/bin/updown.sh
and then that script is responsible for setting netfilter rules for that
ip while the tunnel is up, i.e.
#!/bin/bash
if [ "$PLUTO_VERB" == "up-client" ] || [ "$PLUTO_VERB" == "up-host" ] ; then
iptables -N $PLUTO_CONNECTION;
iptables -A $PLUTO_CONNECTION -p tcp --dport 22 -j ACCEPT;
iptables -A $PLUTO_CONNECTION -p tcp --dport 23 -j ACCEPT;
iptables -A $PLUTO_CONNECTION -p tcp --dport 80 -j ACCEPT;
iptables -A $PLUTO_CONNECTION -p tcp --dport 443 -j ACCEPT;
iptables -A $PLUTO_CONNECTION -p tcp --dport 3389 -j ACCEPT;
iptables -A $PLUTO_CONNECTION -p tcp --dport 5900 -j ACCEPT;
iptables -A $PLUTO_CONNECTION -p icmp --icmp-type echo-reply
-j ACCEPT;
iptables -A $PLUTO_CONNECTION -p icmp --icmp-type echo-request
-j ACCEPT;
iptables -A $PLUTO_CONNECTION -j ACCEPT
iptables -I INPUT -s $PLUTO_PEER -j $PLUTO_CONNECTION;
iptables -I FORWARD -s $PLUTO_PEER -j $PLUTO_CONNECTION;
exit 0;
elif [ "$PLUTO_VERB" == "down-client" ] || [ "$PLUTO_VERB" ==
"down-host" ] ; then
iptables -D INPUT -s $PLUTO_PEER -j $PLUTO_CONNECTION;
iptables -D FORWARD -s $PLUTO_PEER -j $PLUTO_CONNECTION;
iptables -F $PLUTO_CONNECTION;
iptables -X $PLUTO_CONNECTION;
exit 0;
fi
exit 0;
obviously if you needed different rules per tunnel you could just move
the updown into the individual conn and define a seperate script per
connection with different rules. all of the $PLUTO_... stuff is set in
the ENV while the connection is being built... obviously for me, my
FORWARD chain is a default drop, so I am just inserting at the top and
allowing what I want for the duration of the tunnel.
Hope that helps.
Lane
Devaraj Das wrote:
> Hi,
> I wanted to know whether there is a working solution for the issue that
> was discussed sometime back:
> http://www.spinics.net/lists/netfilter/msg22099.html
> In short is there any solution to enable blocking selective ports in a
> machine running Linux 2.6.0 + in-kernel ipsec.
> I would be very helpful if I can get a working solution or some
> information on a possible solution.
> Thanks,
> Devaraj.
>
>
next prev parent reply other threads:[~2004-03-29 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 11:10 kernel 2.6 IPsec and netfilter Devaraj Das
2004-03-29 12:33 ` Thomas Lussnig
2004-03-29 15:13 ` Devaraj Das
2004-03-29 12:36 ` Lane Powers [this message]
2004-03-29 15:21 ` Devaraj Das
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 18:51 Dobersberger Dieter
2004-01-15 3:06 ` Dobersberger Dieter
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=40681861.1030704@mis.net \
--to=lpowers@mis.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox