Lines Matching refs:Conflict
1033 #define kProbingConflictPauseDuration mDNSPlatformOneSecond // Duration of probing pause after an allowed mcast conflict.
1107 // complete ownership of *all* types for this name, so *any* record type with the same name is a conflict.
1253 // (depending on the OS and networking stack it's using) that it might interpret it as a conflict and change its IP address.
1919 // If we found a conflict, we may still want to insert the record in the list but mark it appropriately
1928 LogRedact(MDNS_LOG_CATEGORY_STATE, MDNS_LOG_DEFAULT, "mDNS_Register_internal: Name conflict " PRI_S " (%p), InterfaceID %p",
2051 // conflict and run through the same series of names: name-2, name-3, name-4, etc.,
2268 if (drt == mDNS_Dereg_conflict) // If this was a conflict, see that all duplicates get the same treatment
2339 // immediately. When there is a conflict, we deregister all the conflicting duplicate records
2488 debugf("mDNS_Deregister_internal: Cannot have a conflict on a shared record! %##s (%s)",
3206 // owner, because these packets can cause some IPv6 stacks to falsely conclude that there's an address conflict.
4615 // When we have a late conflict that resets a record to probing state we use a special marker value greater
4635 // moments later that there's a name conflict, but applications have to be prepared to handle
8584 // Returns 0 if there is no conflict
8585 // Returns +1 if there was a conflict and we won
8586 // Returns -1 if there was a conflict and we lost and have to rename
8603 if (ourptr >= ourend && pktptr >= pktend) return(0); // If data identical, not a conflict
8628 // It indicates that there is no inherent conflict detection for the TXT record
8668 // 2a. If our record is marked as dependent on some other record for conflict detection, ignore this one.
8670 // points to our record, ignore this conflict (e.g. the packet record matches one of our
8673 // are members of the same RRSet, then this is not a conflict.
8676 // If not supposed to be unique, not a conflict
8679 // If a dependent record, not a conflict
8683 // If the pktrr matches a member of ourset, not a conflict
8690 // in our AuthRecords list is sufficient evidence of non-conflict
8694 // Okay, this is a conflict
8765 // When conflict happens, look for TSR loss.
8770 "ResolveSimultaneousProbe - deregistering " PRI_DM_NAME " type " PUB_S " on interface id: %p due to TSR conflict",
8857 // skip conflict check if there is no TSR record or no hashkey match
8865 mDNSBool conflict = mDNSfalse;
8893 LogRedact(MDNS_LOG_CATEGORY_MDNS, MDNS_LOG_DEFAULT, "ProbeRRMatchAndTSRCheck: Conflict with our ar %p rrtype: " PRI_S ", name: " PRI_DM_NAME PRI_S,
8895 conflict = mDNStrue;
8901 return (conflict && probeTSRWin);
9031 // saying itself -- because it can cause some IPv6 stacks to falsely conclude that there's an address conflict.
9159 // to keep our neighbours caches warm, and for ongoing conflict detection.
9200 "ProcessQuery - deregistering " PRI_DM_NAME " type " PUB_S " on interface id: %p due to TSR conflict",
9423 // for conflict detection, etc.
10671 // in conflict with the mDNS spec, because that spec says, "Multicast DNS Zones have no SOA record," so it's okay to cache
12064 // 1. Check that this packet resource record does not conflict with any of ours
12087 "mDNSCoreReceiveResponse - deregistering " PRI_DM_NAME " type " PUB_S " on interface %d due to TSR conflict",
12116 // else, the packet RR has different type or different rdata -- check to see if this is a conflict
12119 // Having a possible conflict, we should log the packet to check why it has possible
12130 // If this record is marked DependentOn another record for conflict detection purposes,
12131 // then *that* record has to be bumped back to probing state to resolve the conflict
12192 "spurious multicast conflict (%d/%u) via interface %d for " PRI_S,
12205 "will deregister " PRI_S " due to " PUB_S "cast conflict via interface %d",
12223 // record to avoid continued conflicts (as we do for a conflict on our Unique records) and get on with life.
12227 "mDNSCoreReceiveResponse: Unexpected conflict discarding " PRI_S,
12244 // Else, matching signature, different type or rdata, but not a considered a conflict.
12287 "mDNSCoreReceiveResponse - flushing cache group " PRI_DM_NAME " type " PUB_S " on interface %d due to TSR conflict",
13541 // Configd may use the OPT record if it detects a conflict with the BSP when the system wakes up
16421 // Also, in the event of a name conflict, one or more of our records will have been forcibly deregistered.
16508 else if (result == mStatus_NameConflict) msg = "Name conflict";
16529 // remedy the conflict, and a name that differs only in capitalization will just suffer the exact same conflict again.
17149 else if (result == mStatus_NameConflict) msg = "Name Conflict";
17158 // If we got a name conflict on either SRV or TXT, forcibly deregister this service, and record that we did that
17161 sr->Conflict = mDNStrue; // Record that this service set had a conflict
17188 if (sr->Conflict) result = mStatus_NameConflict;
17259 sr->Conflict = mDNSfalse;
17533 // If a service gets a conflict, then we set the Conflict flag to tell us to generate
17543 sr->Conflict = mDNSfalse;
17680 // didn't answer our three probes within three seconds then we'd announce and cause it an unnecessary address conflict.
17746 // For all types of ARP packet we check the Sender IP address to make sure it doesn't conflict with any AddressProxy record we're holding.
17748 // so by definition (and by design) they can never conflict with any real (i.e. non-zero) IP address).
17749 // We ignore ARPs we sent ourselves (Sender MAC address is our MAC address) because our own proxy ARPs do not constitute a conflict that we need to handle.
17752 // 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.
17850 // Pass 2: For all types of NDP packet we check the Sender IP address to make sure it doesn't conflict with any AddressProxy record we're holding.
Indexes created Tue Aug 04 00:24:20 UTC 2026