All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcello Scacchetti <marcello.scacchetti@nextrem.it>
To: "'netfilter@lists.netfilter.org'" <netfilter@lists.netfilter.org>
Subject: Re: ipsec & nat
Date: 11 Dec 2002 21:39:17 +0100	[thread overview]
Message-ID: <1039639156.25020.3.camel@nxitmirms1> (raw)
In-Reply-To: <CAFAAEC91CC8D511952000062938C6F12ECD92@ozlan.fcdomain.net>

Hi Doug,
i think your supposition is right, that's too general. Every packet
going out on eth0 will be natted and this is not what you want in case
of ipsec. Packet going out on the newly established vpn tunnel should
NOT be natted in any way. I can suggest you to nat what you really need
to nat so in this way you will get benefits on security side too.
If you know wich ip address will be assigned or are assigned on the
other side of the tunnel you can explicit disable nat on that
destination.

			Marcello


Il mer, 2002-12-11 alle 06:03, Simpson, Doug ha scritto:
> I have a redhat 7.3 box that is dualhomed.  It is my firewall and vpn
> server.  I can successfully vpn (with IPSEC) into it.  If I use the
> following command "iptables -t nat -I POSTROUTING -o eth0 -j MASQUERADE" I
> cannot use VPN, but my internal network can only receive email (POP3) and
> telnet after I use this command.
> I have set up squid so I proxy my www traffic.
> Can I NAT my pop3 and my telnet, and still VPN (IPSEC)?  
> I am guessing my command is too general and I need to be more specific -
> ports, source, etc defined.
> Thanks,
> Doug
-- 
Marcello Scacchetti <marcello.scacchetti@nextrem.it>


  reply	other threads:[~2002-12-11 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11  5:03 ipsec & nat Simpson, Doug
2002-12-11 20:39 ` Marcello Scacchetti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-07 16:08 ipsec nat robowarp
2005-08-03 21:12 ipsec + nat Aleksandar Milivojevic
2005-08-25  3:22 ` Trevor Cordes

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=1039639156.25020.3.camel@nxitmirms1 \
    --to=marcello.scacchetti@nextrem.it \
    --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.