@Joseph-TP 

This seems to be a general problem with TP-Link Router firmware.

 

Got the same with the current BETA Firmware for the TP-LINK ARCHER VR-2100v version 1.

 

With Tp-Link Router:

0-20% of all QUIC packages got a respond.

With Fritzbox Router:

99% of all QUIC packages got a respond.

With neighbor WiFi (Speedport from Deutsche Telekom)

100% of all QUIC packages got a respond.

Back again to Tp-Link:

0-20% got a respond.

 

How did i test it:

https://github.com/microsoft/quicreach

This tool helps with the QUIC development and this will help your developer team too.

You can test it with google.com or other QUIC enables webservers.

 

Why did i test it:

I suspected first the Webservers and Star Citizen (Game) which uses QUIC as the main transport.

But for some reasons it just happened with my DSL Line... which is used with the Tp-Link Router.

With the neighbor WiFi if was working, with mobile hotspot it was working.... but not with the TP-Link Router.

 

What did i test as settings:

Disable of IP4/IP6 SPI firewall.

Parental Settings (nearly everything)

Put my PC as a DMZ (yes, i know what this means and the danger from it)

Added port forwarding, even if i can just use UDP and no choice for QUIC.

 

 

 

So without TP-Link in my network it works.

 

Maybe your team can test it with a device like the ARCHER VR2100v and the quicreach tool.

If you have a new beta firmware, i can test it for you... but for now i banned all tplink equipments out of 3 networks due to the massive problem with QUIC.

  @Joseph-TP 

Ok it seems like the infos i provided here is not enough.

So i will add this:

 

This even happens if the Archer is JUST a router without the functionality of beeing a modem too.

I was trying the fritzbox as a dedicated modem (which works, even with a OpenWRT VM and two lan ports) and configures the archer router to accept the dsl modem at lan port 1.

Everything worked as before, except of course for the QUIC protocol.

Every QUIC test failed again with 0 up to 20% success rate instead of >99%.

 

So no, it's not a DSL problem.

For the beta firmware, i'm using the provided firmware here: https://community.tp-link.com/en/home/threads/topic/793934

 

If there is no intend/time to investigate or fix it for the archer device, could your team just provide the DIFF file, so we can try to fix it for ourself?

I already created a working bin, but this kills the IPV6 again... which was fixed with the beta firmware.