Hi,
not sure where else to post this. For a while now, I’ve unsuccessfully been trying to get WireGuard to work with Crunchyroll.
Setup is as follows:
- dedicated server hosts a wg-quick instance in [neighboring country]
- OPNSense acts as peer on a single IP
- I have a rule for routing the entire traffic of some source device via that IP
This works just fine. Handshake successful, traffic is routed via the server. traceroute shows the server as the hop immediately after my device’s local gateway. The connection is stable, and fast.
…except for Crunchyroll. The site / app itself is fine, but I can not, for the life of me, get a video to play. It just keeps loading forever.
I don’t think this is an issue with CR recognizing that I’m not where I say I am - looking online, it seems pretty easy to use CR with a VPN. I’ve also tried from multiple other devices, all with the same symptom.
If anyone has suggestions, I’d love to hear them 😅
EDIT: It was MTU. Had to manually set it to 1500 on both devices.
Nope, still the same issues. I was using the fallback interface there briefly.
EDIT: It WAS MTU related, I had to enable MSS clamping on the OPNSense.
You must log in or register to comment.
What does Wireshark or
tcpdumpshow on any relevant interfaces?Alright, this is weird. I ran
tcpdumpon the server, and checked both physical andwg0interface. For things like youtube, it’s a constant stream of packets coming in on the physical interface, then immediately being relayed throughwg0- just as it should be.But for Crunchyroll, there’s… Nothing. I get an initial burst of packets when opening the site containing the video I want to stream, and then packets just stop coming in once the page itself has fully loaded.
Do you run pfblocker-ng? Try using it with another DNS service
Hi,
no, sorry :(
I really don’t think it’s DNS (famous last words, I know)
Maybe DNS problem?
I’m able to resolve DNS requests from the device. But maybe I’m misunderstanding your question? 😅
Yeah I mean, are you using the same DNS resolver in the server and client?
Ah, alright. Yes, I’ve just double checked. The server end of the tunnel provides a dns server, and the client is configured to use that as its only dns server.
Have you confirmed that with something like https://www.dnsleaktest.com? DNS leaks are common so it’s good to check.
Yep, no leak.
