Skip to content
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

router: check advertised address on startup #2722

Open
dovholuknf opened this issue Jan 31, 2025 · 0 comments · May be fixed by #2723
Open

router: check advertised address on startup #2722

dovholuknf opened this issue Jan 31, 2025 · 0 comments · May be fixed by #2723
Labels
enhancement New feature or request

Comments

@dovholuknf
Copy link
Member

it's insanely easy for users to start a router that won't work by having a mismatch between the config file advertise address and the pki being presented.

it'd be great if the router when it starts could attempt to probe it's own advertised addresses and ensure the advertised address returns a certificate that will be valid.

For example, if i start a router and with a pki using "my.router.local" in the SANS but set the advertise address of any of the bindings to "this.is.invalid", the router will start and advertise "this.is.invalid". If a client connects to this router, the certificate chain won't be able to be verified and a connection won't complete

@dovholuknf dovholuknf added the enhancement New feature or request label Jan 31, 2025
@dovholuknf dovholuknf changed the title check advertised address on startup router: check advertised address on startup Jan 31, 2025
dovholuknf added a commit that referenced this issue Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant