New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 632973 link

Starred by 4 users
Status: Archived
Owner: ----
Closed: Aug 2016
Cc:
█ tkonch...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Chrome giving priority to ipv4 connection over ipv6 connection.

Reported by bowerso...@gmail.com, Jul 30 2016 
<b>Chrome Version       : <Copy from: 'about:version'></b>
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
         IE:ok

What steps will reproduce the problem?
(1) in chrom, visit http://test-ipv6.comcast.net/
(2) view results (browser makes ipv4 a priority, if ipv6 connection is slow).
(3)

What is the expected result? faster ipv6 connection, consistently.


What happens instead? ipv4 connection occurs if ipv6 connection is slow (300ms)


Please provide any additional information below. Attach a screenshot if
possible.

Comment 1 by tkonch...@chromium.org, Aug 1 2016

Cc: tkonch...@chromium.org
Labels: Needs-Feedback
Tested the same on mac 10.11.5 chrome version 52.0.2743.82 and canary 54.0.2815.0 - ipv4 is set priority as shown in the screenshot

The same is observed in firefox browser as well

This doesn't seem to be chrome specific issue. Could you please recheck on other browsers and update the thread.
Screen Shot 2016-08-01 at 3.25.55 PM.png
462 KB View Download

Comment 2 by jkarlin@chromium.org, Aug 1 2016

Components: Internals>Network
Hi bowersoxee, thanks for filing a bug report. You're expect to see ipv6 connections but instead are seeing ipv4, is that correct?

Chrome will first try to connect to the ipv6 address, and if after 300ms that hasn't succeeded, it will try the ipv4 address in parallel. Whichever connects first wins.

If you're still seeing unexpected behavior, please attach a net internals log to this bug so that we can investigate. For information on net internals logs, please see https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details.

Comment 3 by mmenke@chromium.org, Aug 19 2016

Status: Archived (was: Unconfirmed)
Archiving issue - we have no way forward on this without a net-internals log.  If you're still having the problem, please file a new bug, with the requested log attached.
►

Sign in to add a comment