Larklen

I'd love to see a few pictures or video of how it looks at night without the sun glare!

@Androidz Try removing the portion that is enabling a windows-cache, in my attempts we found out that windows-cache is no longer supported and when I removed that, it began to work as expected - I would check Cornelicorn's last post, he has my quote in it with some info as well, it shows the command I used to in the end to have it functioning. Hopefully this helps, I don't have direct experience with pfsense or any linux distro's so if the issue persists, hopefully someone with more knowledge than I can help!

@Cornelicorn I'll throw that in there when I get home! I'm willing to bet the inclusion of the windows-cache in the original statement is where it was screwing up, since its no longer supported. @Abromberek cut the command into a single line and try it again Using the example listed in OP, it'd be something like this: sudo docker run --restart unless-stopped -d --name steam-cache -v /home/USERNAME/cache/steam/data:/data/cache -v /home/USERNAME/cache/steam/logs:/data/logs -p 192.168.1.50:80:80 steamcache/generic:latest

@thedude4bides You pretty much got the main use for it! That's mentioned on the github as well that its primarily for LAN events and for popular games, yeah most people will have it. One spot where is can shine though is, say there is an unexpected game that any number of people want to play, normally everyone would then need to download it from the Internet, since they didn't expect to play it at the event. With this set up, once one person downloads it from the internet, everyone else immediately pulls from the cache, so anyone who wants it after the one person downloaded it can grab it at the cache speeds. @Norrah By default, this can be scaled down as far as you like I set it up in my location (mainly just to try it out as an experiment) and the set up its on it an older computer hooked into a router, which then runs to a switch and then to several computers. No need for any fancy equipment as the magic is in the software itself, equipment just lets you reach higher speeds (which makes more of a difference especially if you already have a great internet connection, since you might already be getting ~25MBps for example).

I had to remove the '-f' as it returned an error, but it seems that command worked! I got a response that I never did before. Curious to why the last command wasn't working, but this is a good step in the right direction! Not to get this working for Blizzard/Windows cache as well hah Edit: Got it for most all the caches, only one that gave an error was trying to create a windows cache, but I'm not overly concerned about that one. This was the final command I ran: docker run --name steamcache-dns -p 192.168.1.10:53:53/udp -e UPSTREAM_DNS=1.1.1.1 -e STEAMCACHE_IP=192.168.1.11 -e BLIZZARDCACHE_IP=192.168.1.12 -e FRONTIERCACHE_IP=192.168.1.13 steamcache/steamcache-dns:latest

Hey! Yup, the hello world worked and I did the whole off/on earlier as well as again before I wrote this (just to be certain. Definitely a good question, since that solves ~90% of issues ) Version result: Docker version 18.06.0-ce, build 0ffa825 This is the result from running nslookup on the machine with docker. >nslookup google.com 192.168.1.10 DNS request timed out. timeout was 2 seconds. Server: UnKnown Address: 192.168.1.10 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out And this is the command I used to start the steamcache-dns image: docker run --restart unless-stopped -d --name steamcache-dns -p 192.168.1.10:53:53/udp -e UPSTREAM_DNS=1.1.1.1 -e STEAMCACHE_IP=192.168.1.11 -e BLIZZARDCACHE_IP=192.168.1.12 -e FRONTIERCACHE_IP=192.168.1.13 -e WINDOWSCACHE_IP=192.168.1.14 steamcache/steamcache-dns:latest Greatly appreciate your assistance here I'm willing to best the problem lies with me, my knowledge and past experience with DNS is akin to essentially nothing.

Hey guys! Appreciate the responses! I've reviewed the Ars Technica page as well as re-read the instructions listed above by jakkuh_t as well as you Cornelicorn. As far as I can tell (besides the fact it isn't working as intended), I am following the steps properly - I believe my issue listed in the 'steamcache/steamcache-dns:latest: image which when I run docker ps - it shows the 'STATUS' constantly as 'Restarting (1) X second(s) ago' - so with this image constantly restarting, it'll make sense why I can't resolve anything on my local PC. Here is the 'docker ps' result: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9d481bae8265 steamcache/steamcache-dns:latest "bash /scripts/boots…" 14 seconds ago Restarting (1) 1 second ago steamcache-dns 107f95346619 steamcache/steamcache:latest "/scripts/bootstrap.…" About an hour ago Up About an hour 0.0.0.0:80->80/tcp steamcache f80025f0c99c steamcache/sniproxy:latest "sniproxy -f" About an hour ago Up About an hour 0.0.0.0:443->443/tcp sniproxy da9d20fd9ae5 steamcache/generic:latest "/scripts/bootstrap.…" 2 hours ago Up 2 hours 192.168.1.14:80->80/tcp windows-cache faf6db2fab9a steamcache/generic:latest "/scripts/bootstrap.…" 2 hours ago Up 2 hours 192.168.1.13:80->80/tcp frontier-cache e968dae6364a steamcache/generic:latest "/scripts/bootstrap.…" 2 hours ago Up 2 hours 192.168.1.12:80->80/tcp blizzard-cache 59c463a13cd6 steamcache/generic:latest "/scripts/bootstrap.…" 2 hours ago Up 2 hours 192.168.1.11:80->80/tcp steam-cache This is the command run to start the image - note: The internal IP Address of this PC is 192.168.10, I have tried this command with both that and 0.0.0.0 (just to test). docker run --restart unless-stopped -d --name steamcache-dns -p 192.168.1.10:53:53/udp -e UPSTREAM_DNS=1.1.1.1 -e STEAMCACHE_IP=192.168.1.11 -e BLIZZARDCACHE_IP=192.168.1.12 -e FRONTIERCACHE_IP=192.168.1.13 -e WINDOWSCACHE_IP=192.168.1.14 steamcache/steamcache-dns:latest I have confirmed (as best as I can without it working) that the drives are being shared with Docker. The IP range of 192.168.1.10 --> 192.168.1.14 can be reached by ping so they have been set up, as well as I have disabled IPv6 on both computers. Here is the ipconfig result if it'll help any: Ethernet adapter Ethernet: Connection-specific DNS Suffix . : IPv4 Address. . . . . . . . . . . : 192.168.1.10 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 192.168.1.11 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 192.168.1.12 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 192.168.1.13 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 192.168.1.14 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.254 I'm still digging and trying stuff on my end in hopes I can resolve this myself, but there are always smarter people out there than I and based on what I can see, the DNS image is the core issue.

Wonder if anyone else is planning to use this on a Windows machine. I have one of my home servers set up using Windows 10 Pro and have taken a quick stab at getting this setup to no avail - doesn't seem to be too much in the way of guides/other people setting it up so I suppose I'll have to fiddle around with it. If anyone else has experience, I'd love to poke a brain or two!