Summary: | Cannot gather srflx or relay ICE candidates on IPv6 network (ICE agent hangs?) | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Mark Roberts <mroberts> | ||||
Component: | WebRTC | Assignee: | youenn fablet <youennf> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | adam, commit-queue, eric.carlson, svein, webkit-bug-importer, youennf | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | Safari 11 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Mark Roberts
2017-12-19 16:25:32 PST
I can reproduce the bug as well. If a device has both an IPv4 address and an IPv6 address, will this issue affect both? In other words: Are no srflx and relay candidates gathered if the host is on a IPv6 network or does the issue affect only the IPv6 address? (In reply to sventy from comment #3) > If a device has both an IPv4 address and an IPv6 address, will this issue > affect both? Both host IPv4 and IPv6 should be gathered according my testing. > In other words: Are no srflx and relay candidates gathered if the host is on > a IPv6 network or does the issue affect only the IPv6 address? I would think this only affects the IPv6 addresses. My testing is limited at the moment though. To be noted that on that page, stun.l.google.com is used and does not have any IPV6 address. It seems therefore strange that a srflx candidate would be gathered. That said, we should not be timing out. Maybe the DNS resolution is timing out and we do not properly handle this error case. Or we are getting an IPv4 address and do not handle it properly. Created attachment 339224 [details]
Patch
Comment on attachment 339224 [details] Patch Clearing flags on attachment: 339224 Committed r231235: <https://trac.webkit.org/changeset/231235> All reviewed patches have been landed. Closing bug. Thanks, Youenn. I haven't seen this mentioned in any recent Safari Tech Preview release notes. Is it out yet? (In reply to Mark Roberts from comment #9) > Thanks, Youenn. I haven't seen this mentioned in any recent Safari Tech > Preview release notes. Is it out yet? The patch should be out since quite some time on Safari Tech Preview and is probably in latest Mac/iOS betas. |