From: "David S. Miller" <davem@davemloft.net>
To: Aidas Kasparas <a.kasparas@gmc.lt>
Cc: latten@austin.ibm.com, ipsec-tools-devel@lists.sourceforge.net,
netdev@oss.sgi.com
Subject: Re: [Ipsec-tools-devel] ipv4/ipv6 forwarding check
Date: Fri, 29 Oct 2004 00:04:47 -0700 [thread overview]
Message-ID: <20041029000447.4e7b68e3.davem@davemloft.net> (raw)
In-Reply-To: <4181EBC3.3020507@gmc.lt>
On Fri, 29 Oct 2004 10:05:39 +0300
Aidas Kasparas <a.kasparas@gmc.lt> wrote:
> 4) extend setkey's syntax to make explicit forward policy management
> possible and write docs for all the admins to change policies.
This is what we're advocating to happen.
There are reasons why people would want seperate INPUT, OUTPUT,
and FORWARD policies. So we're not taking that capability out
of the kernel. And by "auto-magically" making this happen
transparently you are taking the capability away, which is why
this idea won't fly either.
For the record, the freeswan tools handle all of this stuff
just fine.
next prev parent reply other threads:[~2004-10-29 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410300506.i9U56Yse005815@faith.austin.ibm.com>
2004-10-29 7:05 ` [Ipsec-tools-devel] ipv4/ipv6 forwarding check Aidas Kasparas
2004-10-29 7:04 ` David S. Miller [this message]
2004-10-29 7:23 ` Herbert Xu
2004-10-29 8:09 ` Aidas Kasparas
2004-10-29 9:27 ` Michal Ludvig
2004-11-05 10:27 ` Michal Ludvig
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=20041029000447.4e7b68e3.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.kasparas@gmc.lt \
--cc=ipsec-tools-devel@lists.sourceforge.net \
--cc=latten@austin.ibm.com \
--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).