Home
last modified time | relevance | path

Searched refs:SADB_GETSPI (Results 1 – 6 of 6) sorted by relevance

/netbsd-src/sys/net/
H A Dpfkeyv2.h55 #define SADB_GETSPI 1 macro
/netbsd-src/crypto/dist/ipsec-tools/src/racoon/rfc/
H A Drfc2367.txt73 3.1.1 SADB_GETSPI .............................................. 32
480 (SPI) value from the kernel using the SADB_GETSPI message and then
500 used by followup SADB_GETSPI, SADB_UPDATE, and SADB_ADD messages, in
1422 One PF_KEY message, SADB_GETSPI, might need a range of acceptable SPI
1693 #define SADB_GETSPI 1
1759 3.1.1 SADB_GETSPI
1761 The SADB_GETSPI message allows a process to obtain a unique SPI value
1766 destination address in address extension. If the SADB_GETSPI message
1780 It is recommended that associations that are created with SADB_GETSPI
1785 The message behavior of the SADB_GETSPI message is:
[all …]
/netbsd-src/crypto/dist/ipsec-tools/src/setkey/
H A Dparse.y270 status = setkeymsg_add(SADB_GETSPI, $5, $3, $4);
1405 if (type == SADB_GETSPI && p_spi != 0) { in setkeymsg_add()
/netbsd-src/crypto/dist/ipsec-tools/src/racoon/
H A Dstrnames.c867 { SADB_GETSPI, "GETSPI", NULL },
/netbsd-src/crypto/dist/ipsec-tools/src/libipsec/
H A Dpfkey.c433 p = pfkey_setsadbmsg((void *)newmsg, ep, SADB_GETSPI, in pfkey_send_getspi_nat()
2098 case SADB_GETSPI: in pfkey_check()
/netbsd-src/sys/netipsec/
H A Dkey.c3304 case SADB_GETSPI: in key_newsav()
3334 if (mhp->msg->sadb_msg_type != SADB_GETSPI) { in key_newsav()
5359 * SADB_GETSPI processing is to receive
6769 * <base, src address, dst address, (SPI range)> with SADB_GETSPI
7817 key_api_getspi, /* SADB_GETSPI */
7935 case SADB_GETSPI: in key_parse()