- From: docfaraday via GitHub <noreply@w3.org>
- Date: Wed, 27 May 2026 19:36:20 +0000
- To: public-webrtc-logs@w3.org
> And a fiddle merely emitting `.local` candidates does not trigger? That would suggest it is triggered by the attempt to do a MDNS resolution. You might want to grab a sysdiagnose for [@youennf](https://github.com/youennf) It isn't an mDNS resolution that is triggering this. Gathering an mDNS candidate means that the hostname must be *broadcast* to the local network (see https://datatracker.ietf.org/doc/html/rfc6762#section-8.1). No other peer connection needs to exist for this to happen. So, if there's an OS-level permission on whether this kind of broadcast is allowed, it's going to pop up. -- GitHub Notification of comment by docfaraday Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3109#issuecomment-4558032363 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 May 2026 19:36:20 UTC