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 deck not using lancache #186

Open
bfenty opened this issue Dec 13, 2023 · 3 comments
Open

Steam deck not using lancache #186

bfenty opened this issue Dec 13, 2023 · 3 comments

Comments

@bfenty
Copy link

bfenty commented Dec 13, 2023

This is likely an issue with something on the deck as it works perfectly on my windows machines, but the deck doesn't use the cache. I have the domains configured in pihole to forward to my lancache. Deck just ignores the cache. Is there a fix for this?

@OverthinkingTech
Copy link

Same issue. Weirdly, the steamdeck finds lancache.steamcontent.com because it shows up in my DNS logs but it also looks for other servers and uses them instead. Attached is a screenshot of DNS showing the steamdeck is finding lancache.steamcontent.com
Blocking all other steam servers does not work in forcing the deck to use lancache. Also, I have tried disabling local file sharing, that had no impact of behavior.

Screenshot 2023-12-21 175104

@sgtxd
Copy link

sgtxd commented May 4, 2024

This Issue lines up with the Linux Steam Client not utilising lancache.steamcontent.com (ValveSoftware/steam-for-linux#7514)

@archer37
Copy link

For what its worth, testing from the Stemdeck today it has no issues connecting to and using LanCache for game downloads. No configuration on the deck necessary, just the network wide entry for lancache.steamcontent.com pointed to the local server, and I am able to hit speeds far in excess of my ISP connection; Proxmox and Grafana validate that the traffic is coming from the Lancache VM.

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

4 participants