Hi George,
Thanks a lot for the clarification.. Yeah, i was quite confused with
ipsec_set_policy - which has multiple definitions, one which converts the
human readable policy format and another one inside the kernel.. doing a
little bit of code walk through, it looks like the second one is called
HI Blue,
Thanks a lot for this info.. It helped me in understanding the difference..
Thanks,
Adityaa
On 7/26/07, blue <[EMAIL PROTECTED]> wrote:
>
> As far as I know, setkey is used for IPsec SP and SA configuration.
> ipsec_set_policy() could transfer a string to "policy request", which is
> def
At Thu, 26 Jul 2007 08:13:02 +0800,
blue wrote:
>
> As far as I know, setkey is used for IPsec SP and SA configuration.
> ipsec_set_policy() could transfer a string to "policy request", which is
> defined in RFC 2367 PF_KEY. Internally, setkey() will call
> ipsec_set_policy() to construct the m
As far as I know, setkey is used for IPsec SP and SA configuration.
ipsec_set_policy() could transfer a string to "policy request", which is
defined in RFC 2367 PF_KEY. Internally, setkey() will call
ipsec_set_policy() to construct the message then send it down to the
kernel. However, ipsec_set
Hi,
I was just trying to understand PF_KEY interface for ipsec settings. So,
setkey uses it to do that. but i could find another system call -
ipsec_set_policy. Could any body let me know why there are two interfaces to
configure ipsec?
Thanks,
Aditya
_
