[lkml]   [2003]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] IPSec protocol application order

I believe that good documentation will also be required then. If it is
being decided that the user must enter the ipsec protocols in the proper
order using the setkey spdadd operation, then the user will need to know
what order in which to specify the arguments to setkey. Given that the
spdadd operation:

spdadd src-ip dst-ip any -P out ipsec ah/transport//require

would result in improper ordering of the AH and ESP headers and therefore
interoperability problems, while

spdadd src-ip dst-ip any -P out ipsec esp/transport//require

results in the proper order.

No where have I been able to find any user level documentation that says
what order the ipsec protocols need to be specified on the spdadd
operation. Without good documentation I believe support centers, both a
customer's own and/or a distributor's, may be getting a lot of unnecessary


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.022 / U:0.812 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site