Seems has some bug after use customized network name

[dzxx36gyy]

When use customized network name like "snet" rather than the default "dnet", it can create successfully with the standalone mode, but when try to add other node to it via command tinc-boot gen --network="snet" --token xxxxxx, it will failed with error "http://example.com:8665 can't open /etc/tinc/dnet/hosts/xxxx: no such file or directory". Seems the variable "network" didn't work properly.

[dzxx36gyy]

Also it seems the variable "name" with command tinc-boot gen --name="eu-fr-ovh-51" will remove the characters like dash and underline, so i will got the name "eufrovh51" in the end. However, i think it's means to make the hostname more readable, so i recommend to keep them.

[reddec]

"name" restriction came from tinc. Only [a-zA-Z0-9]+ symbols are allowed.

[dzxx36gyy]

"name" restriction came from tinc. Only [a-zA-Z0-9]+ symbols are allowed.

Okay, i know, but the first problem about "network" do existed.

[reddec]

Yes, I believe. Will check it soon.

[dzxx36gyy]

Also, i found another problem, seems when you setup an bootnode using tinc-boot bootnode --service --token xxxx, it will use the hostname by default, and it won't using the name in the first step tinc-boot gen --name abcde --standable -a 1.2.3.4.
So that will cause a problem, when another node try to join the bootnode, the different name and hostname will cause the bootnode try to find /etc/tinc/dnet/hosts/hostname rather than the expected /etc/tinc/dnet/hosts/name. Then it will cause the new node can't decrypted the information and finally got the error "all boot nodes failed".