Lines Matching full:probing
631 // In addition, when probing we send our questions with the wildcard type kDNSQType_ANY,
708 // go out synchronized with the first announcement for the other records that *are* probing.
711 // delayed by a few milliseconds, this announcement does not inadvertently go out *before* the probing is complete.
712 // When the probing is complete and those records begin to announce, these records will also be picked up and accelerated,
763 // For reverse-mapping Sleep Proxy PTR records we don't want to start probing instantly -- we
764 // wait one second to give the client a chance to go to sleep, and then start our ARP/NDP probing.
839 // If we're in the middle of probing this record, we need to start again,
1303 // No probing for LocalOnly records, Acknowledge them right away
2846 // because if some other host is probing at the same time, we each want to know what the other is
3003 if (!AuthRecord_uDNS(ar) && ar->resrec.RecordType == kDNSRecordTypeUnique) // For all records that are still probing...
3023 // IPv6 target address is address we're probing
3024 // Ethernet destination address is Ethernet interface address of the Sleep Proxy client we're probing
3030 // When we have a late conflict that resets a record to probing state we use a special marker value greater
3055 // else, if it has now finished probing, move it to state Verified,
4479 // We send queries next, because there might be final-stage probes that complete their probing here, causing
4481 // Finally, we send responses, including the previously mentioned records that just completed probing.
4484 // 7. Send Query packets. This may cause some probing records to advance to announcing state
4503 // 8. Send Response packets, including probing records just advanced to announcing state
5226 // 3. Retrigger probing and announcing for all our authoritative records
5622 // Instead we pause for one second, to give the other host (if real) a chance to establish its name, and then try probing again.
6698 // (apparently) local source address that pertain to a record of our own that's in probing state
6725 // then *that* record has to be bumped back to probing state to resolve the conflict
6734 LogInfo("mDNSCoreReceiveResponse: Already reset to Probing: %s", ARDisplayString(m, rr));
6736 LogMsg("mDNSCoreReceiveResponse: Ignoring response received before we even began probing: %s", ARDisplayString(m, rr));
6740 // If we'd previously verified this record, put it back to probing state and try again
6743 LogMsg("mDNSCoreReceiveResponse: Resetting to Probing: %s", ARDisplayString(m, rr));
6752 RecordProbeFailure(m, rr); // Repeated late conflicts also cause us to back off to the slower probing rate
6754 // If we're probing for this record, we just failed
9485 // Normally, after an interface comes up, we pause half a second before beginning probing.
9708 // Only pass on the NoError acknowledgement for the SRV record (when it finishes probing)
10163 // generating ARP conflicts with a waking machine, and set rr->LastAPTime so we'll start probing again in 10 seconds.
10173 // still going to sleep, so we just reset rr->ProbeCount so we'll continue probing until it stops responding.
10175 // we're more cautious and we wait ten seconds before probing it again. We do this because while waking from
10212 static const char msg1[] = "ARP Req from owner -- re-probing";
10246 LogSPS("%-7s ARP %s from owner %.6a %.4a for %-15.4a -- re-starting probing for %s", intf->ifname,
10295 static const char msg1[] = "NDP Req from owner -- re-probing";
10334 LogSPS("%-7s NDP %s from owner %.6a %.16a for %.16a -- re-starting probing for %s", intf->ifname,
