From: Patrick McHardy <kaber@trash.net>
To: Greg Scott <GregScott@InfraSupportEtc.com>
Cc: netfilter-devel@lists.netfilter.org, Marco Berizzi <pupilla@hotmail.com>
Subject: Re: new iptables policy match
Date: Sat, 14 Jan 2006 17:22:43 +0100 [thread overview]
Message-ID: <43C92553.5010207@trash.net> (raw)
In-Reply-To: <925A849792280C4E80C5461017A4B8A26DBB@mail733.InfraSupportEtc.com>
Greg Scott wrote:
>>No, the tunnel endpoints are the hosts using the
>>tunnel-mode SA, so in this case both firewalls.
>
>
> OK, so now I'm confused. And admittedly, IPSEC has made
> me crazy for several years. Which NICs on the firewalls
> are the endpoints? Is this picture better and more accurate?
>
>
> LAN Internet LAN
> <----+--FW---+-------------+--FW---+----->
> | | | |
> NIC with NIC with NIC with NIC with
> private public public private
> IP IP <---------> IP IP
> SA
> Tunnel Tunnel
> endpoint endpoint
>
> So the public NICs are the tunnel endpoints?
Yes. Its very simple, the endpoints are the addresses you specify
in the policy in the tunnel section (x.x.x.x and y.y.y.y):
spdadd net/mask net/mask any ipsec out
tunnel/x.x.x.x-y.y.y.y/require;
next prev parent reply other threads:[~2006-01-14 16:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 21:18 new iptables policy match Greg Scott
2006-01-14 16:22 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-12 17:59 Greg Scott
2006-01-13 7:01 ` Patrick McHardy
2006-01-11 16:17 Marco Berizzi
2006-01-12 4:07 ` Patrick McHardy
2006-01-12 8:30 ` Marco Berizzi
2006-01-12 8:43 ` Patrick McHardy
2006-01-12 10:38 ` Marco Berizzi
2006-01-12 10:42 ` Patrick McHardy
2006-01-12 10:48 ` Marco Berizzi
2006-01-12 10:53 ` Patrick McHardy
2006-01-12 11:23 ` Marco Berizzi
2006-01-12 12:33 ` Patrick McHardy
2006-01-12 14:37 ` Marco Berizzi
2006-01-12 16:31 ` Patrick McHardy
2006-01-20 15:54 ` Tom Eastep
2006-01-22 13:38 ` Patrick McHardy
2006-01-12 9:41 ` Patrick McHardy
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=43C92553.5010207@trash.net \
--to=kaber@trash.net \
--cc=GregScott@InfraSupportEtc.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pupilla@hotmail.com \
/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.