What's new

QUIC Issue

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

haoel

New Around Here
I currently use ASUS RT-AC68U 1900M router, and upgraded the RT-AC68U_380.61_0.trx firmware.

I active the VPN(PPTP) connection in router, and enable some static route rules and the dnsmasq.conf.add for different DSN servers.

Everything looks fine except to access the Google website by Chrome (Safari and Firefox no problem)

After I did some investigation, I found the Chrome uses QUIC protocol to access thewww.google.com or www.youtube.com website, and this cause the problem.

I made the following tests:

1) Using my laptop connect to the VPN directly, and Chrome can load the Google and Youtube website successfully via QUIC protocol. So, I think both my laptop and VPN haven't the problem.

2) I disabled the Chrome's QUIC protocol - chrome://flags/#enable-quic , and Chrome using HTTPS, everything's fine. (scenario: laptop -> router -> vpn -> Google)

So, I think the problem might be the router has some problem with QUIC protocol, and some articles said the router's QoS setting could make the QUIC problem, but I've never enabled the QoS setting in router.

Anyone can help on this?
 
I currently use ASUS RT-AC68U 1900M router, and upgraded the RT-AC68U_380.61_0.trx firmware.

I active the VPN(PPTP) connection in router, and enable some static route rules and the dnsmasq.conf.add for different DSN servers.

Everything looks fine except to access the Google website by Chrome (Safari and Firefox no problem)

After I did some investigation, I found the Chrome uses QUIC protocol to access thewww.google.com or www.youtube.com website, and this cause the problem.

I made the following tests:

1) Using my laptop connect to the VPN directly, and Chrome can load the Google and Youtube website successfully via QUIC protocol. So, I think both my laptop and VPN haven't the problem.

2) I disabled the Chrome's QUIC protocol - chrome://flags/#enable-quic , and Chrome using HTTPS, everything's fine. (scenario: laptop -> router -> vpn -> Google)

So, I think the problem might be the router has some problem with QUIC protocol, and some articles said the router's QoS setting could make the QUIC problem, but I've never enabled the QoS setting in router.

Anyone can help on this?
Please take into account that QUIC is very much experimental! So blaming a router for causing issues is not really realistic.

Regardless of that, no issues here with QUIC connections although not connected through VPN. VPN could also be the source of the issue...
 
Please take into account that QUIC is very much experimental! So blaming a router for causing issues is not really realistic.

Regardless of that, no issues here with QUIC connections although not connected through VPN. VPN could also be the source of the issue...
Hey, eddiez,I am not blaming router. Please don't get me wrong. As I mentioned, I use my laptop connect to VPN directly, and QUIC works fine. I just natively think it shouldn't be the problem of VPN.

Here, I just want to understand how the route deal with QUIC connection, I hope you can teach me how to investigate/debug this issue, guide me to do more deep investigation.
 
Hey, eddiez,I am not blaming router. Please don't get me wrong. As I mentioned, I use my laptop connect to VPN directly, and QUIC works fine. I just natively think it shouldn't be the problem of VPN.

Here, I just want to understand how the route deal with QUIC connection, I hope you can teach me how to investigate/debug this issue, guide me to do more deep investigation.

Use tcpdump (either on the router, your client, or both) to create a packet capture then use Wireshark to see what's happening.

Are other UDP-based protocols having problems or is QUIC the only one?
 
Just to jump in on this, looking at QOS per devices, QUIC is being shown as "Web Surfing" traffic and not "Video and Audio Streaming" if I go to youtube in Chome 56.0.2924.76 on an RT-AC5300 on 380.64_2

If I disable QUIC in Chrome using - chrome://flags/#enable-quic - it shows as Youtube traffic and is counted properly under "Video and Audio Streaming"
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top