-
Notifications
You must be signed in to change notification settings - Fork 69
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
README.md comment #44
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
first of all, I'd like to thank you for your great work!
I'd like comment the following statement in README.md, which might be true for most network configurations, but not always.
You can include additional common names for your certificate, so long as they resolve to the same WAN address:
In my opinion, it should read something like this:
You can include additional common names for your certificate, so long as they are configured on any interface of the router, accessible from internet.
I use IPv6 and I have an unique global IPv6 address configured on WAN and LAN interfaces of the router. So I could use WAN and LAN name in the certificate request without any trouble.
Also, static host names are not necessary, as soon as are resolved by configured DNS server.
The text was updated successfully, but these errors were encountered: