From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: [OT] Was: ESP does not hit the nat table
Date: Wed, 4 Aug 2004 09:49:39 +0100 [thread overview]
Message-ID: <200408040949.39972.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <D5C9032B2B09C64EA2409D6214E91AC9051228@asimail2.alphanumeric.com>
On Tuesday 03 August 2004 1:42 pm, Jason Opperisano wrote:
> > My main problem however was that ESP packets do not hit the nat table,
> > but it does traverse mangle/filter table. Is this normal? I am mainly
> > looking at SNAT/MASQUERADING ipsec traffic and I am not able to find any
> > documentation on doing this, especially since there is no point in
> > putting a "iptables -t nat -A PREROUTING -p 50 -j SNAT --to-source <me>".
> > -p 50 means ESP as you can already guess. Am I missing something here?
> > How do I masquerade ipsec traffic? (assuming my ipsec-VPN client/server
> > is fine with it...)
>
> if i had to take a stab in the dark as to why you're having trouble--i
> would say that it's related to the fact that the outbound interface of your
> IPSec traffic needs to be specified as "-o ipsec0" (or whatever number your
> actual ipsec interface is), not ethX...
Actually, I thought the ipsecX interface was used for the plaintext traffic,
and ethX was used for the encrypted stream?
My model of frees/wan and netfilter is:
- encrypted packet arrives on ethX, passes through INPUT to local klips
process
- decrypted packet appears on ipsecX pseudo-interface, passes through
FORWARD, and goes to local client
- plaintext reply data comes in on standard ethernet from local network, gets
FORWARDed to ipsecX
- ipsecX has local process listening, captures plaintext and encrypts it
- encrypted packet getnerated by local process, passes through OUTPUT and
exists via ethX
Therefore I believe the TCP/UDP/ICMP traffic etc would be going in/out via
ipsecX, whereas the ESP traffic will be going in/out via ethX.
Regards,
Antony.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-08-04 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 12:42 [OT] Was: ESP does not hit the nat table Jason Opperisano
2004-08-04 8:49 ` Antony Stone [this message]
2004-08-05 4:36 ` Ming-Ching Tiew
-- strict thread matches above, loose matches on Subject: below --
2004-08-05 14:26 Kashyap Ashwin
2004-08-02 14:49 Kashyap Ashwin
2004-08-01 19:03 Jason Opperisano
2004-08-01 22:28 ` [OT] Was: " Antony Stone
2004-08-02 8:03 ` Jozsef Kadlecsik
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=200408040949.39972.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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