Lines Matching full:multicast
150 // Depending on whether this is a multicast or unicast question we want to set either:
780 // Set LastMCTime to now, to inhibit multicast responses
781 // (no need to send additional multicast responses when we're announcing anyway)
1924 // appropriate IPv6 solicited node multicast address, so we use that IPv6-layer destination address, even though
1935 // link with a pointless link-layer multicast.
1937 // Ethernet-layer address we're looking for, we'll need to send to the appropriate Ethernet-layer multicast address:
1978 // in multicast solicitations and SHOULD be included in unicast solicitations.
2348 // when we see our own multicast with the cache flush bit set, if we haven't set LastMCTime, then we'll get
2884 // *multicast* queries we're definitely going to send
3286 // For 802.11 WPA networks, where a sleeping target machine may have missed a broadcast/multicast
3425 // multicast or DNSServers did not change.
5215 // Restart unicast and multicast queries
5784 // The only queries that *need* a multicast response are:
5785 // * Queries sent via multicast
5788 // These queries need multicast responses because other clients will:
5791 // For other queries, we may still choose to send the occasional multicast response anyway,
5822 // NR_AnswerTo pointing into query packet means "answer via immediate legacy unicast" (may *also* choose to multicast)
5823 // NR_AnswerTo == (mDNSu8*)~1 means "answer via delayed unicast" (to modern querier; may promote to multicast instead)
5824 // NR_AnswerTo == (mDNSu8*)~0 means "definitely answer via multicast" (can't downgrade to unicast later)
5826 // but the multicast querier is not on a matching subnet (e.g. because of overlaid subnets on one link)
5827 // then we'll multicast it anyway (if we unicast, the receiver will ignore it because it has an apparently non-local source)
5830 // We only mark this question for sending if it is at least one second since the last time we multicast it
5831 // on this interface. If it is more than a second, or LastMCInterface is different, then we may multicast it.
5864 // for non-truncated multicast queries with multicast responses.
5876 // Note: Records larger than 1K are not habitually multicast, so don't expect those to be updated
6023 mDNSBool SendMulticastResponse = mDNSfalse; // Send modern multicast response
6026 // If it's been a while since we multicast this, then send a multicast response for conflict detection, etc.
6031 // multicast response instead (don't want to end up ALSO setting SendUnicastResponse in the check below).
6036 // If the client insists on a multicast response, then we'd better send one
6227 "%2d Question%s %2d Answer%s %2d Authorit%s %2d Additional%s %d bytes (Multicast, but no InterfaceID)",
6466 // InterfaceID non-NULL tells us the interface this multicast response was received on
6587 // All responses sent via LL multicast are acceptable for caching
6632 // If response was not sent via LL multicast,
6696 // We accept all multicast responses, and unicast responses resulting from queries we issued
6870 // Currently, we do this for for both multicast and unicast questions as long as the record
6871 // type is unique. For unicast, resource record is always unique and for multicast it is
7067 // When we're doing parallel unicast and multicast queries for dot-local names (for supporting Microsoft
7069 // Otherwise we just fill up our cache with negative entries for just about every single multicast name we ever look up
7070 // (since the Microsoft Active Directory server is going to assert that pretty much every single multicast name doesn't exist).
7075 // in conflict with the mDNS spec, because that spec says, "Multicast DNS Zones have no SOA record," so it's okay to cache
7605 // for multicast questions, we don't want to treat LongLived as anything special
7617 SameQTarget(q, question) && // and same unicast/multicast target settings
7804 // can be queries that can forced to multicast (ForceMCast) even though they don't end in these
