From: Aidas Kasparas <a.kasparas@gmc.lt>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@oss.sgi.com, ipsec-tools-devel@lists.sourceforge.net
Subject: Re: [Ipsec-tools-devel] Re: [PATCH 2.6]: Check against correct policy list in ip_forward/ip6_forward
Date: Tue, 19 Oct 2004 18:57:19 +0300 [thread overview]
Message-ID: <4175395F.9050409@gmc.lt> (raw)
In-Reply-To: <417534F1.1010401@trash.net>
Patrick McHardy wrote:
> Aidas Kasparas wrote:
>
>> I'm sorry, what is wrong with racoon?
>
>
> When generate_policy is set to on racoon doesn't generate forward
> policies for tunnel mode SAs, so traffic forwarded from a tunnel
> is not subject to policy checks.
Patrick,
what _forward_ policies should racoon generate. And WHY?!
Could you please specify for the case when:
- remote host has address A.A.A.A
- security gateway have insecure adress B.B.B.B
- secured network is C.C.C.0/24, security gateway's address C.C.C.C
what policies in your oppinion has to be inserted into SPD for this
setup by racoon?
Thanks in advance.
>
> I have a patch which fixes this, I will post it a couple of days.
>
> Regards
> Patrick
>
--
Aidas Kasparas
IT administrator
GM Consult Group, UAB
next prev parent reply other threads:[~2004-10-19 15:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 15:48 [PATCH 2.6]: Check against correct policy list in ip_forward/ip6_forward Patrick McHardy
2004-10-17 21:23 ` Herbert Xu
2004-10-17 22:26 ` Patrick McHardy
2004-10-17 22:42 ` Patrick McHardy
2004-10-17 23:12 ` Herbert Xu
2004-10-18 20:34 ` Patrick McHardy
2004-10-18 21:43 ` [XFRM] Allow transport SAs even when there is no policy Herbert Xu
2004-10-19 14:16 ` Patrick McHardy
2004-10-19 21:25 ` Herbert Xu
2004-10-21 5:04 ` David S. Miller
2004-10-21 5:02 ` David S. Miller
2004-10-19 15:31 ` [Ipsec-tools-devel] Re: [PATCH 2.6]: Check against correct policy list in ip_forward/ip6_forward Aidas Kasparas
2004-10-19 15:38 ` Patrick McHardy
2004-10-19 15:57 ` Aidas Kasparas [this message]
2004-10-19 21:26 ` Herbert Xu
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=4175395F.9050409@gmc.lt \
--to=a.kasparas@gmc.lt \
--cc=ipsec-tools-devel@lists.sourceforge.net \
--cc=kaber@trash.net \
--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.