Windows binaries

[AnthonyBe]

Given you have MacOS binaries, any chance of Windows binaries as I would like to run this on a Windows server.

[ameshkov]

It can be compiled for Windows, but it does not work at the moment, we didn't have enough time to figure the exact reason. We will, though:)

[hmage]

Hi.

As of now, we can't support Windows because the DNS server library we're using has an outstanding bug -- coredns/coredns#2002.

I'm not saying it will never happen, and there's a possibility we will switch from coredns to another solution if neccessary.

[ameshkov]

Lol, apparently, Eugene had enough time :)

Actually, there're a lot of people demanding windows build so we might need to figure a workaround and not wait for it to be fixed in coreDNS.

[Daist]

Hi, have you tried running this software in WSL (Windows Subsystem for Linux)?

[hmage]

@Daist not yet, but it could work there, yes.

[TPS]

If possible, if y'all could test WSL & give us modified instructions via a wiki page, that would answer for techies when in v0.9, while y'all work on a shiny v1.0 native Windows edition.

[hmage]

@TPS Thanks for understanding.

Once I get ahold of windows machine I’ll do test it under WSL.

[TPS]

NP, but my Disqus post on the AGHome announcement asks for a lot more! 😚

[hmage]

It does work under WSL.

🎉

[AnthonyBe]

One major downside with relying on WSL is that it is only included in Windows 10 and Windows Server Insider Preview Build (aka. Windows 2019) so that heavily restricts where it could be used.

Reference: https://docs.microsoft.com/en-au/windows/wsl/about

It would be much better (obviously) if it could run natively on any currently supported version of Windows client or server OS. I do appreciate the blocker at the moment (if I'm not mistaken) is in the Go dependency which takes control of this problem out of your hands to a large degree.

[TPS]

@AnthonyBe Of course, you're right, but this is just meant to be a quick-&-dirty hack so enthusiasts can try it out on Windows. I'm reasonably sure @AdguardTeam is reserving v1.0 for an official native Windows release.

@hmage Any wiki so we don't have to go through (what looks to be, based on posts' time-difference) ~2 hours of trial-&-error?

[AnthonyBe]

Agreed! I have a Win10 box on permanently I'd love to try this out on 😁 Given I have over 40 devices on my network I'm very interested to see what AGH can pick up!

[ewrogers]

If you want something working today on v0.9, use Docker:

• Windows 10 x64 Pro/Enterprise/Education users can simply Install Docker for Windows. This can run containers natively using Hyper-V.

• Legacy Windows users can install Docker Toolbox. This will use the docker-machine VM behind the scenes to run your containers.

• Alternatively, use VirtualBox with your choice of Linux distro (Ubuntu would be friendly for most).

• For older Windows XP/7/8 machines, consider Ubuntu Wubi which allows installation side-by-side with Windows (and can be uninstalled easily).

My AdGuard Docker images can be found here:

• Linux x86 - 32-bit

• Linux x86 - 64-bit

• Linux ARM - Raspberry Pi

If running on your own computer (not a dedicated device), you may want to use -p 3000:3000 instead when running the container.

[hmage]

Under WSL it also works today.

[TPS]

@hmage Did you get to post a wiki w/ your steps to install/run AdGuardHome via WSL?

[AnthonyBe]

@hmage Which Linux distro did you use in WSL?

[ilgrank]

...still hoping for an update :) 👍

[AnthonyBe]

me too! :)

While I do have it running on my Win10 PC using WSL, I'm finding that the average processing time is consistently >140ms and I'm definitely noticing the impact on general web page opens/loads. Given my PC hardware is Core i7, 16GB RAM, etc. and not under any load, I can only assume there is an overhead in the WSL layer so having native Windows binaries (and ideally x64 binaries) will, I hope, improve performance significantly.

[ameshkov]

It seems that we'll be able to do it in v0.92 btw.

I'm finding that the average processing time is consistently >140ms

It's possible that the upstream is too slow.

[AnthonyBe]

That's wonderful news!

[ameshkov]

Resolved in the master branch