Quentin McGaw

Try with `DNS_KEEP_NAMESERVER=on` it should only append the nameserver to the bottom of /etc/resolv.conf. Although the latest image might still be building.

Yes, sorry the build has been failing... It's still building now ([here](https://github.com/qdm12/private-internet-access-docker/runs/861751170)) or wait for green mark instead of that orange dot next to the commit referenced above.

A few questions: 1. Do you need the nameserver thing or does this routing solves it by itself? 1. Is `10.244.1.32` the default gateway? (i.e. for me i get in...

1. Ok let's keep the DNS as it is now with the env variable 2. For now, the program does `ip route add via dev ` for each subnet specified...

Also there was a bug the last 1-3 days where the EXTRA_SUBNETS would just be ignored, which is fixed in #190 so that may had affected your testing.

- It says your local subnet is your default gateway `routing: local subnet found: 10.244.1.32/32`. In my standard Docker thing, it gives me the Docker network subnet i.e. `172.17.0.0/16`. Can...

Also the fix I just mentioned about `EXTRA_SUBNETS` I pushed it to the wrong branch, I just pushed it to master now, sorry about that. So it should show in...

There is actually an issue still (#194) which might be related. Sorry about that, I'll fix that one first and would probably ask you to test again then once it's...

Alright, found/pushed the fix! You could try now (or anytime later, no pressure). The routes were setup correctly but the firewall would be blocking everything. Not sure it's very relevant...

Hello, sorry I lost track a bit. Let's find how to make it work with the firewall on. Keeping it off disables the kill switch and might be dangerous i.e....