From: Andreas Jellinghaus <aj@dungeon.inka.de>
To: "netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: ipsec without interface
Date: 29 May 2003 21:16:27 +0200 [thread overview]
Message-ID: <1054235787.605.21.camel@simulacron> (raw)
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.
b) source address selection. put the default route on ipsec0,
but the route to the tunnel endpoint on eth0 with the right gateway.
also I wonder why I see incoming packets before and after encryption,
but outgoing packets only before encryption.
Andreas
next reply other threads:[~2003-05-29 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 19:16 Andreas Jellinghaus [this message]
2003-07-01 12:58 ` ipsec without interface bert hubert
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=1054235787.605.21.camel@simulacron \
--to=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 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.