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

Steamcache not working with IPv6 on #24

Open
tiramon opened this issue Jan 12, 2018 · 4 comments
Open

Steamcache not working with IPv6 on #24

tiramon opened this issue Jan 12, 2018 · 4 comments

Comments

@tiramon
Copy link

tiramon commented Jan 12, 2018

Issue Description:
I installed steamcache-dns and steamcache/generic and everthing works fine, but only if i turn ipv6 off.
If i have ipv6 on it always walks that way and ignores my ipv4 dns and steam cache...

Is ipv6 support still missing or am i just too stupid to get it working right?

Docker Run Command:

sudo docker run --name steamcache-dns -p 192.168.178.150:53:53/udp -e STEAMCACHE_IP=192.168.178.150 -e BLIZZARDCACHE_IP=192.168.178.151 -e UPSTREAM_DNS=8.8.8.8  steamcache/steamcache-dns:latest
@VibroAxe
Copy link
Member

Currently ipv6 is largely untested within the cache images. The steamcache-dns is intended as a simple solution to the dns interception and will NOT be supporting ipv6 anytime soon. If you want to use ipv6 you would need to implement your own dns solution for the time being i'm afraid

@teknoman117
Copy link

I just bumped into this as well. If it's still a wontfix, it would be helpful if there was a message in the README to disable IPv6 or at least DNS over IPv6.

If you have a network assigning IPv6 address and follow the readme, you only see traffic going to your cache sporadically. e.g. uklans/cache-domains#109

@astrolox astrolox self-assigned this Aug 27, 2019
@astrolox
Copy link
Member

Although I don't imagine we'll have full IPv6 support soon (i.e. content being downloaded via IPv6 addresses) and therefore not supporting IPv6 only networks (yet) ...

I fully expect it to work fine if you expose the lancache-dns image on an IPv6 address and set it as your DNS server in your IPv6 settings (the same as you have to do with your IPv4 settings).

@Candunc
Copy link

Candunc commented Sep 13, 2019

I fully expect it to work fine if you expose the lancache-dns image on an IPv6 address and set it as your DNS server in your IPv6 settings (the same as you have to do with your IPv4 settings).

I can confirm, IPv6 DNS lookup resolves down to the IPv4 served by Monolithic or whatever cache you are using. However, IPv6 support in docker is something I haven't looked into in a while, but it's not likely user friendly. The easiest solution is to simply disable IPv6 DNS, which shouldn't cause any issues since a IPv4 DNS server will respond with IPv6 addresses so your network will still work as intended.

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

No branches or pull requests

5 participants