From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Rules for Cisco VPN Client
Date: Thu, 10 Mar 2005 10:28:23 -0500 [thread overview]
Message-ID: <20050310152822.GA29914@bender.817west.com> (raw)
In-Reply-To: <20050310143608.M70602@tkevans.com>
On Thu, Mar 10, 2005 at 10:36:08AM -0400, Tim Evans wrote:
> Anyone have working iptables rules for supporting the Cisco VPN client? Thanks.
depends how the clients are configured.
you'll always need to allow UDP 500 for IKE.
then depending on the configuration of the clients you would need one
(or some, or all) of the following:
IP Proto 50 (ESP)
UDP 4500 (PIX NAT-T)
UDP 10000 (VPN CON NAT-T 1)
TCP 10000 (VPN CON NAT-T 2)
if the VPN server is a Concentrator--the encapsulation port can be set
to pretty much any arbitrary value--consult with the admin for details.
kitchen sink rules would be:
iptables -A FORWARD -i $INSIDE_IF -o $OUTSIDE_IF -p 50 \
-s $INSIDE_NET -d $VPN_GW -j ACCEPT
iptables -A FORWARD -i $INSIDE_IF -o $OUTSIDE_IF -p udp \
-s $INSIDE_NET -d $VPN_GW --dport 500 -j ACCEPT
iptables -A FORWARD -i $INSIDE_IF -o $OUTSIDE_IF -p udp \
-s $INSIDE_NET -d $VPN_GW --dport 4500 -j ACCEPT
iptables -A FORWARD -i $INSIDE_IF -o $OUTSIDE_IF -p udp \
-s $INSIDE_NET -d $VPN_GW --dport 10000 -j ACCEPT
iptables -A FORWARD -i $INSIDE_IF -o $OUTSIDE_IF -p tcp --syn \
-s $INSIDE_NET -d $VPN_GW --dport 10000 -j ACCEPT
again--if the TCP/UDP encapsulation port has been changed from the
default, you'd need to accommodate for that as well.
HTH...
-j
--
"Simpson, Homer Simpson, he's the greatest guy in his-tor-y. From
the town of Springfield, he's about to hit a chestnut tree....D'oh!"
--The Simpsons
prev parent reply other threads:[~2005-03-10 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 14:36 Rules for Cisco VPN Client Tim Evans
2005-03-10 15:28 ` Jason Opperisano [this message]
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=20050310152822.GA29914@bender.817west.com \
--to=opie@817west.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.