[tor-dev] Potential regression when binding sockets to interface without default route

[grarpamp]

On Mon, Sep 19, 2016 at 9:14 AM, René Mayrhofer <rm at ins.jku.at> wrote:
> Sep 19 11:37:41.000 [warn] I have no descriptor for the router named
> "ins1" in my declared family; I'll use the nickname as is, but this may
> confuse clients.
> Sep 19 11:37:41.000 [warn] I have no descriptor for the router named
> "ins2" in my declared family; I'll use the nickname as is, but this may
> confuse clients.
> Sep 19 11:37:41.000 [notice] Your Tor server's identity key fingerprint
> is 'ins0 01A9258A46E97FF8B2CAC7910577862C14F2C524'
> Sep 19 11:38:34.000 [warn] You specified a server "ins1" by name, but
> the directory authorities do not have any key registered for this
> nickname -- so it could be used by any server, not just the one you
> meant. To make sure you get the same server in the future, refer to it
> by key, as "$CD9FD887A4572D46938640BA65F258851F1E418B".
> Sep 19 11:38:34.000 [warn] You specified a server "ins2" by name, but
> the directory authorities do not have any key registered for this
> nickname -- so it could be used by any server, not just the one you
> meant. To make sure you get the same server in the future, refer to it
> by key, as "$7C3AF46F77445A0B1E903A5AF5B730A05F127BFC".

A side note, unless you have a reason not to, or the other nodes
are offline, you should fix up the MyFamily lines in the configs of
your nodes, to at least save noise in your logs.