Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - queenkjuul

#1
I am extremely disheartened to learn that I will have to spend even more money on hardware, after already barely keeping my whole 2.5gb LAN upgrade under budget by buying Realtek NICs, which work just fine in all my other machines (which are all Linux or Windows) . However, I guess I can finally stop banging my head against the wall trying to solve my OPNsense config, so that's good.
#2
23.7 Legacy Series / Problems with HTTP3/QUIC
February 01, 2024, 06:59:24 PM
Ever since I set up my OPNsense router for the first time (new to OPNsense, not so new to networking, but replacing a standard consumer-grade off the shelf router) Youtube will not work for me.

At first I suspected something weird with IPv6 (mostly because I don't really understand IPv6) so I tried disabling all IPv6 in OPNsense (disabling the IPv6 gateway, turning off IPv6 in my LAN settings), but no dice.

I eventually traced the issue to HTTP3/QUIC. I can manually disable HTTP3 in the Firefox config flags, and that fixes youtube for me.

However, on my phone, I cannot access Firefox config flags in the Android build, and I can't modify the official Youtube app. Neither one works on my phone. I can confirm the problem because re-enabling HTTP3 in Firefox on ethernet clients breaks youtube in the same way. I get errors in dev tools about NS_BINDING_ABORTED and the youtube player just spins forever. I've left it for hours without it snapping to life, and I've tried obvious solutions like disabling ad blockers and clearing cache. All that works is disabling HTTP3 in Firefox.

So I'm now suspecting this has to be a router-level issue, if I can reproduce the issue on all clients both wifi and ethernet regardless of app (firefox or official youtube client both fail the same way).

I've done very little to modify the default settings of OPNsense, though. I've mostly just added DHCP reserved addresses, and enabled DHCP name resolution in Unbound.

This seems to have been broken since the day I installed OPNsense. Any ideas?

Type    opnsense    
Version    23.7.12_5    
Architecture    amd64    
Commit    847d88416    
Mirror    https://pkg.opnsense.org/FreeBSD:13:amd64/23.7    
Repositories    OPNsense    
Updated on    Thu Feb 1 11:49:06 CST 2024

System is a Dell thin client with a Pentium J005 and 8GB RAM, using a Realtek 4x2.5gbe NIC. I have no other issues - DNS works, DHCP name resolution works, I get full expected throughput. What is going on with QUIC then?