MagicDoubleM 108 Posted November 14, 2022 Posted November 14, 2022 I'm using the "LAN-networks" and "remote IP-adress" filters for whitelisting and client-separation. I have a few clients incoming through tailscale (works great btw) and since they are rolling out their magicdns, giving every client a dns-name, I think it's a good idea to use these instead of IPs. These IPs can change easily, even if taken care. This would also be nice for clients with a random IP but a dyndns-host. I haven't tried the 2nd use-case, but my tailscale-hostnames didn't work.
Luke 38823 Posted November 15, 2022 Posted November 15, 2022 HI, yes I think i vaguely recall this idea coming up once before. 1
MagicDoubleM 108 Posted November 16, 2022 Author Posted November 16, 2022 (edited) Another good place to restrict users to domain-names/IPs would be a field in the user-settings, in conjunction with the "allow remote connections"-tick. Probably even a better place now that I think about it. Edited November 16, 2022 by MagicDoubleM typo 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now