Displaying 2 results from an estimated 2 matches for "mynodename".
Did you mean:
_nodename
2015 Feb 02
2
Tinc1.1 generates Port automatically when port is occupied
I like the config generator of tinc 1.1! An issue to consider on the
default behavior:
It turns out 'tinc -n mynet init mynodename' makes up a default Port=...
when the standard port is taken:
"Warning: could not bind to port 655. Tinc will instead listen on port
22911".
It is nice that this is autodetected and warned, but I wonder whether it is
nice to let this automatic-adaptation a default behavior:
- if peop...
2015 Feb 02
0
Tinc1.1 generates Port automatically when port is occupied
On Mon, Feb 02, 2015 at 07:46:11PM +0100, Eric Feliksik wrote:
> I like the config generator of tinc 1.1! An issue to consider on the
> default behavior:
>
> It turns out 'tinc -n mynet init mynodename' makes up a default Port=...
> when the standard port is taken:
> "Warning: could not bind to port 655. Tinc will instead listen on port
> 22911".
The goal is to create a working setup as easily as possible.
> - if people are able to read it, you can just as well leave...