Lines Matching defs:wake
578 // and then if the machine fails to wake, 3 goodbye packets).
774 // Given this, we'll do our best to wake for existing IPv6 connections, but we don't want to encourage
903 // When we wake up from sleep, we call ActivateUnicastRegistration. It is possible that just before we went to sleep,
4531 // signal whatever blocking primitive the main thread is using, so that it will wake up and execute one
4579 // 2. On wake from sleep
5195 // If the machine wakes and then immediately tries to sleep again (e.g. a maintenance wake)
5209 // on wake we go through our record list and clear updateid back to zero
5243 // track of passage of time while asleep, so on wake we refresh our NAT mappings
5244 // We typically wake up with no interfaces active, so there's no need to rush to try to find our external address.
5353 // we'll be put back to sleep forcibly without the chance to schedule the next maintenance wake.
5354 // Right now we wait 16 sec after wake for all the interfaces to come up, then we wait up to 10 seconds
5371 // Even when we have no wake-on-LAN-capable interfaces, or we failed to find a sleep proxy, or we have other
5372 // failure scenarios, we still want to wake up in at most 120 minutes, to see if the network environment has changed.
5373 // E.g. we might wake up and find no wireless network because the base station got rebooted just at that moment,
5678 rr->WakeUp.HMAC = zeroEthAddr; // Clear HMAC so that mDNS_Deregister_internal doesn't waste packets trying to wake this host
5717 rr->WakeUp.HMAC = zeroEthAddr; // Clear HMAC so that mDNS_Deregister_internal doesn't waste packets trying to wake this host
7347 // Given this, we'll do our best to wake for existing IPv6 connections, but we don't want to encourage
7417 rr->WakeUp.HMAC = zeroEthAddr; // Clear HMAC so that mDNS_Deregister_internal doesn't waste packets trying to wake this host
9515 // it here also handles the wake up case as the network link comes UP after waking causing
9516 // us to reconnect to the network. If we do this as part of the wake up code, it is possible
10234 // If the sender hardware address is *not* the original owner, then this is a conflict, and we need to wake the sleeping machine to handle it.
10352 mDNSBool wake = mDNSfalse;
10356 #define XX wake ? "Received" : "Ignoring", end-p
10364 // Plan to wake if
10366 // (b) packet is SYN, SYN+FIN, or plain data packet (no SYN or FIN). We won't wake for FIN alone.
10367 wake = (!(t->tcp.flags & 4) && (t->tcp.flags & 3) != 1);
10369 // For now, to reduce spurious wakeups, we wake only for TCP SYN,
10370 // except for ssh connections, where we'll wake for plain data packets too
10371 if (!mDNSSameIPPort(port, SSH) && !(t->tcp.flags & 2)) wake = mDNSfalse;
10388 wake = mDNStrue;
10394 if (datalen == 1 && end >= &t->bytes[9] && t->bytes[8] == 0xFF) wake = mDNSfalse;
10406 if (ike->ExchangeType == 5 || ike->ExchangeType == 34) wake = mDNSfalse;
10417 if (mDNSSameIPPort(port, ARD)) wake = (datalen >= 110 && end >= &t->bytes[10] && t->bytes[8] == 0x13 && t->bytes[9] == 0x88);
10436 if (wake)
10453 if (!r2 && mDNSSameIPPort(port, IPSECPort)) r2 = rr; // So that we wake for BTMM IPSEC packets, even without a matching SRV record
10577 LogSPS("mDNSCoreBeSleepProxyServer turning off from state %d; will wake clients", m->SPSState);