Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steam using HTTPS not lancache #16

Closed
Glitch990 opened this issue Jul 3, 2020 · 2 comments
Closed

Steam using HTTPS not lancache #16

Glitch990 opened this issue Jul 3, 2020 · 2 comments

Comments

@Glitch990
Copy link

I can confirm this is still happening on Comcast. Steam is repeatedly defaulting to HTTPS. Fix #47 does not appear to be working anymore either. New docker images this morning.

Originally posted by @Glitch990 in lancachenet/lancache-dns#48 (comment)

@Glitch990
Copy link
Author

Shutting down SNIProxy some steam games are cached, but most will fail to wait for the HTTPS request/responses

@Glitch990
Copy link
Author

I came up with a temporary solution on my own, since this issue being well known is not being addressed.

I have figured out a "less than perfect" solution but it works surprisingly well. So I had to give up having my DNS resolver (Pfsense) do the forwarding, which is a big sacrifice. I am running SNIProxy, LANCache, and LANCache-DNS. I pointed my DHCP server at the LANCache-DNS for resolution. I have the SNIProxy, LANCache, and LANCache-DNS pointed to my router as the upstream. I then have two aliases in my firewall for the ComcastDNS addresses for both port 80 and 443 (I noticed that if any connection is made the subsequent connections try for HTTPS) and have those aliases blocked on the LAN side. This caches almost every game through LANCache (Battle Brothers does not cache).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant