[Webkit-unassigned] [Bug 233752] New: [iOS ]Safari looses Network access when establishing WebRTC session

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=233752

            Bug ID: 233752
           Summary: [iOS ]Safari looses Network access when establishing
                    WebRTC session
           Product: WebKit
           Version: Safari 15
          Hardware: iPhone / iPad
                OS: iOS 15
            Status: NEW
          Severity: Critical
          Priority: P2
         Component: WebRTC
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: david.goelzhaeuser at loxone.com
                CC: youennf at gmail.com

Some users of our Intercom noticed a strange behaviour regarding WebRTC calls on iPhones running iOS 15.
When trying to establish a connection with the intercom via WebRTC no network communication is possible anymore, Websockets and HTTPs requests will just run in a timeout.

After some investigation with Wireshark we noticed that it looked like the iPhone is not answering the DTLS Handshake correctly, as Wireshark shows "DTLS" instead of "DTLSv1.2" or "DTLSv1.0".
The iOS OS Log shows that boringssl successfully finishes, but shortly after I see the following messages:

08:48:15.515922+0100    com.apple.WebKit.Networking     nw_read_request_report [C35] Receive failed with error "Connection refused"
08:48:15.516001+0100    com.apple.WebKit.Networking     NetworkRTCUDPSocketCocoaConnections failed processing UDP data with error 61

There is something going on with UDP which would match the not finished DTLS handshake.

This issue described only affects srflx candidates, host or relay candidates would work, but we can't relay every iPhone user through our Relay server yet. 
As the feature is implemented for an Intercom (Door Camera) remote access via srflx is essential

I also found this thread which I think describes a similar issue: https://developer.apple.com/forums/thread/689293

Further Logs or dumps can be supplied if nessesary.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20211202/ba412f86/attachment.htm>