Searched refs:responder (Results 1 – 10 of 10) sorted by relevance
189 int responder; variable318 responder = 1; in main()376 if (responder) in main()390 if (responder) in main()406 if (solicit && responder) { in main()430 if (responder) in main()507 if (responder && left_until_advertise <= 0) { in timer()745 if (responder) in pr_pack()834 if (!responder) in pr_pack()965 if (responder) { in finish()
143 rdisc: Make rdisc with responder support if configured.
211 To continue with the test you should start the responder in another216 This will start the responder and tell it to advertise a AppleShare224 Back in the responder window you can quit the responder cleanly using231 As the responder quits it will multicast that the "Foo" service is
42 # the configuration could makes racoon (as a responder)
79 o responder policy and initiator policy should be separated.
400 CertPathReviewer.ocspLocation.title = OCSP responder location401 CertPathReviewer.ocspLocation.text = OCSP responder location: {0}.402 CertPathReviewer.ocspLocation.summary = OCSP responder location: {0}.403 CertPathReviewer.ocspLocation.details = OCSP responder location: {0}.
64 Or, <command/rdisc/ can act as responder, if compiled with -DRDISC_SERVER.
212 ./ocsp-responder.sh&
727 does not know yet if the responder can handle IKE frag. However, in
241 This command sends a provision discovery response from responder side.