Matěj Laitl

> Perhaps this is a good time to do a minor version bump as well? Oh yeah!

@make-github-pseudonymous-again exactly as you describe. Better NAT traversal and (optional) UPnP support is where we'd welcome contributions from the community.

Hi @boehs, innernet already assigns human hostnames like `myhost.mynet.wg` for each peer (unless disabled). It currently does it by editing `/etc/hosts` (or equivalent), but that's an implementation detail that can...

I fear that providing bare `myhost` names would not be general enough for `innernet` (multiple interfaces could then clash). But you should be able to emulate the same effect by...

Hi, the 25 second interval is currently hard-coded in code: https://github.com/tonarino/innernet/blob/bb6bac3964737b270c8673fa2b3f9e6b690ffe34/shared/src/lib.rs#L22 Should be possible to make it configurable, but I think some logic (like NAT candidate traversal) might assume this...

Hi @kevenwyld, sorting the lines added to hosts file would be a good idea! I'm looking at the code, it should be a matter of changing `HostsBuilder`'s `HashMap` to `BTreeMap`:...

Hi, @anarchy89, I'm successfully running innernet on Raspberry 4B, so I think it should work. I've compiled from sources by installing the Rust toolchain on the Pi and then running...

Thanks a lot, @tommie! Do you want we link your builds from the README?

> In particular, I would like it to populate its own `/etc/hosts` and also be reachable using its own hostname instead of just `innernet-server`. If there's interest in those features,...

This actually looks like a duplicate of #45? I'm not sure about supporting joining as a peer from the server machine, but we can surely make the server name configurable...