New issue
Advanced search Search tips

Issue 740626 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Investigate 464xlat compatibility in chromoting

Project Member Reported by sergeyu@chromium.org, Jul 10 2017

Issue description

T-Mobile deploys IPv6 only with 464xlat on for some clients. As result connection fails when host has only IPv4 address. Investigate if this problem can be fixed somehow.
 
Components: Services>Chromoting
Owner: ----
Status: Untriaged (was: Assigned)
TURN servers support IPv4 and IPv6. I've verified that with WebRTC and TURN chromoting can connect even if the peers use different IP protocols. So the client will work on 464xlat networks once we transition it to WebRTC protocol. This is a good reason to prioritize enabling WebRTC in the mobile clients.

Status: WontFix (was: Untriaged)
Will be fixed by the transition to WebRTC, but we don't plan on fixing independently for the old protocol.

Sign in to add a comment