-
Notifications
You must be signed in to change notification settings - Fork 27
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
Autodetection not working, likely due to machine having multiple IP addresses #260
Comments
Hi Will, thanks for the report! I actually have ran into this myself when I was testing out adding another IP to my server, I just didn't bother fixing since nobody else ran into it yet 😆 I was able to reproduce this on my server, and I've written a fix for it. Since I was able to reproduce it, I've confirmed the fix as working on my machine. Would you mind giving this build another test just to confirm that it resolves your issue? |
Just given this a go, seems to be working brilliantly! With server's DNS set back to settings before the download starts and can see lancache being used. Thank you very much for looking into this so quickly.
And for completeness just double checked the old version still yields the error, build above definitely does fix it
|
Absolutely no problem! I will include this in the next release. |
Released in v1.9.1 |
I'm running prefill on the same machine as lancache, prefilling only works if I set the DNS resolver of that machine to itself. Without this it does not detect lancache.
I don't want to have this config as the machine is depending on itself for DNS. I went looking for an option to manually point prefill at the correct IP and it seems you did have a DNS override option (seen in #45) but it was removed in lieu of auto-detection.
My machines network setup is:
192.168.1.10/24
, this hosts many services and systemd's resolver192.168.1.11/24
this only runs the lancache DNS and HTTP serversI'm guessing autodetection isn't finding the second IP. Any ideas on best way to proceed?
The text was updated successfully, but these errors were encountered: