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

feature: tunnel client character limit warning #11

Closed
r1de opened this issue Apr 3, 2020 · 1 comment · Fixed by #137
Closed

feature: tunnel client character limit warning #11

r1de opened this issue Apr 3, 2020 · 1 comment · Fixed by #137
Assignees

Comments

@r1de
Copy link
Contributor

r1de commented Apr 3, 2020

Ran into an issue with long node names and tunnels.
It's driven me insane for a week...
Same issue as this:
https://www.arednmesh.org/comment/7412#comment-7412

I did not verify the known limit though. 23 seems reasonable from what I have seen.

There probably isn't an easy way to change this limitation, as it comes from pretty far upstream.
So... I propose, at the very least, a warning on the tunnel pages about this.
At the most, a way to change the "username" that the vtund client uses so that they can be shortened to fit within the limit without having to change the nodes actual name.

@k1ky
Copy link

k1ky commented Sep 9, 2020

Ditto - this has been an issue for quite some time. I believe I have mentioned and possibly opened issue(s) on this in the past.

@ae6xe ae6xe transferred this issue from aredn/aredn_ar71xx Dec 16, 2020
r1de added a commit to r1de/aredn that referenced this issue Jul 20, 2021
fixes aredn#11
also fixes: https://www.arednmesh.org/comment/7412#comment-7412
(which has been hanging around for um... _years_!!)
dman776 pushed a commit that referenced this issue Jul 20, 2021
fixes #11
also fixes: https://www.arednmesh.org/comment/7412#comment-7412
(which has been hanging around for um... _years_!!)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants