Wired connection issues summarized. plz fix

stryk3z
Newbie

To clarify a few things regarding this issue.

-The issue started after a 1 hour service outage on wed 6/29 at 12 am.

-I confirmed with many others in my area the same

-I am 100% confident this is not a client side NIC issue. Otherwise this would've existed years ago for everybody. Something was obviously changed on Verizon's side during this service outage

-This issue only occurs specifically when a website determines your connection speed so the most commonly effected sites are video streaming and file upload like netflix/dropbox etc.


First off I know that @Cang_Household posted a fix to disable IPV6 TCP checksum and while this 'works' in that the page actually loads now it does not fix the issue in the phase where websites determine your connection speed. Therefore I end up with garbage quality video/audio on streaming services because it basically looks like they are sending video quality based on dial up speeds...Ironically the thumbnail video previews don't do this so the thumbs/previews are in HD but once you click the video it looks like its in 480 low res garbage

0 Likes
Reply
16 Replies
Cang_Household
Community Leader
Community Leader

Are you using an Intel NIC?

stryk3z
Newbie

If the issue was an intel NIC problem then 3/4 of America would have had this issue for years and not have it start after an outage on the 29th. This is not a valid problem or solution to say everyone with an Intel NIC will have bad service

0 Likes
Reply
Cang_Household
Community Leader
Community Leader
stryk3z
Newbie

Why don't you guys roll back an update that effects your entire network?

0 Likes
Reply
gs0b
Community Leader
Community Leader

@stryk3z wrote:

Why don't you guys roll back an update that effects your entire network?


Two reasons:

  • This is a peer-to-peer forum.  You're not talking to Verizon here, just other users.  Nobody here can change anything about Verizon's systems.  If you want an answer from them, call or chat with them.
  • IPv6 rollout is years in the making and is the future of the internet.  If some hardware out that can't properly support it, that's not Verizon's problem.
tonyvvvvv
Enthusiast - Level 2

The fix where you disable ipv6(tcp) via the device manager doesnt work for me.  I went into my router and disabled ipv6 under the advance router settings and everything works normal as before. Not sure how long I should leave it off for.  I dont know the difference between ip4 and ip6 but is there some sort of security risk.  On the device manager method there were 2 checksum options.  tcp and udp.  Should i have disabled them both or just the tcp one?  Can someone tell me any negative effects i will get from disabling ivp6 on the router itself?

Edit is this ok this seems to work as opposed to disabling the ipv6 via the router.

https://www.youtube.com/watch?v=STWhPpPm3Wo

Cang_Household
Community Leader
Community Leader

@tonyvvvvv wrote:

The fix where you disable ipv6(tcp) via the device manager doesnt work for me.  I went into my router and disabled ipv6 under the advance router settings and everything works normal as before. Not sure how long I should leave it off for.


You should leave it disabled as long as you haven't figured out where the actual problem is.

Could you screenshot your Adapter Settings page? I want to make sure you did not disable the wrong thing.

tonyvvvvv
Enthusiast - Level 2

image

This was the setting I turned off.  (Enable IPv6 Support)  I turned it back on.  I purchased a Realtek network card and installed it.  No problems with the Realtek nic so ill just use that for now. The video I linked was the method I was going to use until there was a firmware to fix the issue.

tonyvvvvv
Enthusiast - Level 2

Also thanks for the help in pointing me to the right direction.  I would have never figured it out.

tonyvvvvv
Enthusiast - Level 2

Just dawned on me you wanted the intel nic setting i disabled and it didnt work.image

This is the only thing I disabled at first and it didn't work for me.

Cang_Household
Community Leader
Community Leader

This also seems to be a known issue.

https://community.intel.com/t5/Ethernet-Products/Intel-I225-V-on-Asus-Z490-with-IPv6/m-p/1226342 

Specially for the I225-V. Will reach out to Intel if I have the time.

You could disable IPv6 completely on the computer as a scaled back fix, but don't disable IPv6 at the router.

Also, you see the Intel brief only includes 1GbE and 10GbE adapters, not the 2.5GbEs, so the 2.5GbEs could be no fix as I heard the TCP checksum offload is a hardware feature. If something is wrong with the hardware, you might need to dump the hardware.

Cang_Household
Community Leader
Community Leader

@tonyvvvvv wrote:

Just dawned on me you wanted the intel nic setting i disabled and it didnt work.image

This is the only thing I disabled at first and it didn't work for me.


Could you try disable the UDP Checksum Offload for IPv6 as well? I just realized that DHCP uses UDP. Thanks for testing.

tonyvvvvv
Enthusiast - Level 2

I disabled both TCP and UDP and that works.  No problems using the mobo Intel nic when both are disabled. 

Cang_Household
Community Leader
Community Leader

@gs0b wrote: If some hardware out there can't properly support it, that's not Verizon's problem.

Completely agreed. Since users with Intel NICs are experiencing this issue, why don't the users using Intel NICs to post over at their Forums?

Disabling IPv6 cuts you off from the IPv6-only part of the Internet. Disabling IPv6 also requires the use of NAT on IPv4 and introduces problems on multiplayer games.

tonyvvvvv
Enthusiast - Level 2

I have the same problem as well.  Wifi everything is ok.  Wired is where i have problems.  I have a Z690 motherboard Asus.  My problems started a couple of days ago as well.  I went to the device manager and disabled the tcp ipv6 checksum and still have the same problem.

gemcal
Enthusiast - Level 2

I have had the same issue with streaming services and downloading video files for my bicycle trainer. In repeated attempts at downloading video files I was successful once out of something like 25 attempts. If support is listening they need to fix this.

0 Likes
Reply