Searched refs:CRYPTO_RESP (Results 1 – 4 of 4) sorted by relevance
97 * The CRYPTO_RESP bit is set to 0 for requests, 1 for responses.542 case CRYPTO_ASSOC | CRYPTO_RESP: in crypto_recv() 644 case CRYPTO_CERT | CRYPTO_RESP: in crypto_recv() 704 case CRYPTO_IFF | CRYPTO_RESP: in crypto_recv() 742 case CRYPTO_GQ | CRYPTO_RESP: in crypto_recv() 779 case CRYPTO_MV | CRYPTO_RESP: in crypto_recv() 813 case CRYPTO_COOK | CRYPTO_RESP: in crypto_recv() 884 case CRYPTO_AUTO | CRYPTO_RESP: in crypto_recv() 940 case CRYPTO_SIGN | CRYPTO_RESP: in crypto_recv() 976 case CRYPTO_LEAP | CRYPTO_RESP in crypto_recv() [all...]
1578 && (opcode & 0xffff0000) != (CRYPTO_ASSOC | CRYPTO_RESP)) { in receive()4321 CRYPTO_RESP, peer->associd, NULL); in peer_xmit()4324 CRYPTO_RESP, peer->associd, NULL); in peer_xmit()4377 CRYPTO_RESP, peer->assoc, NULL); in peer_xmit()4460 temp32 = CRYPTO_RESP; in peer_xmit()4825 temp32 = CRYPTO_RESP; in fast_xmit()
83 #define CRYPTO_RESP 0x80000000 /* response */ macro
1030 CRYPTO_ASSOC and CRYPTO_RESP packets, and in other places.1032 CRYPTO_RESP packets. Use FLAG_ASSOC, not CRYPTO_FLAG_ASSOC. More2374 CRYPTO_RESP and reorder the update of tstamp.