Use actual port in tincd logs / tinc get Port / invitations
authorKirill Isakov <bootctl@gmail.com>
Thu, 21 Apr 2022 12:22:32 +0000 (18:22 +0600)
committerKirill Isakov <bootctl@gmail.com>
Thu, 21 Apr 2022 12:22:32 +0000 (18:22 +0600)
commit0289162552cd85375605044c696e2a3294e7aa9a
treeafba1eea9179cfc0e5abd4c66e9af1fe9111d904
parent421aa3815645b2835c89799e4db91cf35466542b
Use actual port in tincd logs / tinc get Port / invitations

If Port 0 option is used (which makes tincd bind to a port chosen
by the operating system), tinc and tincd used to print that value as
it is instead of whatever port was actually allocated.

https://github.com/gsliepen/tinc/issues/363
19 files changed:
src/control.c
src/invitation.c
src/meson.build
src/net.h
src/net_setup.c
src/net_socket.c
src/netutl.c
src/netutl.h
src/pidfile.c [new file with mode: 0644]
src/pidfile.h [new file with mode: 0644]
src/protocol_auth.c
src/tincctl.c
src/utils.c
src/utils.h
test/integration/invite.py
test/integration/testlib/proc.py
test/unit/meson.build
test/unit/test_netutl.c [new file with mode: 0644]
test/unit/test_utils.c [new file with mode: 0644]