From: bert hubert <ahu@ds9a.nl>
To: Andreas Jellinghaus <aj@dungeon.inka.de>
Cc: "netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: Re: ipsec without interface
Date: Tue, 1 Jul 2003 14:58:08 +0200 [thread overview]
Message-ID: <20030701125808.GA19408@outpost.ds9a.nl> (raw)
In-Reply-To: <1054235787.605.21.camel@simulacron>
On Thu, May 29, 2003 at 09:16:27PM +0200, Andreas Jellinghaus wrote:
> sure, the simple configurations work fine with kernel 2.5.* ipsec.
> But I miss the interface and things I did with it. How are these
> setups supposed to work without an interface?
>
> a) in iptables allow everything coming from ipsec0,
> allow only ssh and ipsec on eth0.
iptables can filter on ESP/AH presence.
> b) source address selection. put the default route on ipsec0,
Do you need a separate source address?
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2003-07-01 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 19:16 ipsec without interface Andreas Jellinghaus
2003-07-01 12:58 ` bert hubert [this message]
2003-07-01 13:33 ` Andreas Jellinghaus
2003-07-01 14:00 ` James Morris
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=20030701125808.GA19408@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=aj@dungeon.inka.de \
--cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).