I did a restart so could I ask other vaults to also restart?
There were 7 entries in my routing table before the restart. The magic number! There’s five right now but if the others restart then that should bring it back up to 7.
Then it’s time to fire up your launchers!
By the way, I cheated a wee bit by dropping in a newly compiled safe_vault (from source code hot off github), still nominally at version 0.8.1. I saw how many commits they had done today to the routing crate and reasoned that it couldn’t hurt. The compile pulled down the latest routing as well as kademlia and one or two others. Not sure what is really new except for routing.
Then I started some other vaults with the same binary, but listening on different ports than 5843, but otherwise with identical configs pointing to the starter vault. That is, I changed the number in their configs, on the line ““tcp_acceptor_port”: 5483”. Again, I figure that it can’t hurt, what with all the powerful hole-punching, because before I did that I was seeing many errors of “address already in use” from the multiple vaults on one machine, I thought that it seemed it might help. And indeed, the logs seem less verbose, due to one of today’s commits to routing and I don’t see that particular error so much.
I have put that newly-compiled Linux safe_vault binary here if you happened to want to drop it into your safe_vault folder and then restart.
Don’t forget to make it executable, since that flag could be lost during download:
$ chmod +x ./safe_vault
Of course you know that you can download a file at the commandline, with:
$ wget "http://126.96.36.199/safe_vault"
Note: You DON’T need to use the binary I’m running, the one from the (testnet3) redistributable (linked to in the OP) will do fine. I put the self-compiled binary in to get a bit more performance, and to see how it ran.