The configuration files are untouched, but I have been adding nodes since last restart. The only thing I can think of is that it was installed on a Ubuntu server with automatic security updates turned on. Not that I understand why this would brake tinc.
After hours of searching and trying I came up with an idea: I installed tinc on a fresh Ubuntu installation and copied the config and all the keys from Node1 to the new server. Like magic all nodes connected again. Both 1.1pre10 and 1.1pre11 nodes. Now upgrading all nodes to 1.1pre11 :-) I understand that its not an good idea to mix protocol versions. But I dont think this is the reason all nodes went down. Åsmund 2015-05-19 5:06 GMT+02:00 Nathan Stratton Treadway <[email protected]>: > On Tue, May 19, 2015 at 00:09:40 +0200, Åsmund Rabbe wrote: > > All nodes was connected both 1.1pre10 and 1.1pre11 before "tinc -n vpn > > restart" at Node 1. > > Is there any chance some configuration file on Node 1 got changed > somehow after the previous time you started up the daemon, such that > when you restarted it recently it came up with a different configuration > than it had before? > > Nathan > > > > ---------------------------------------------------------------------------- > Nathan Stratton Treadway - [email protected] - Mid-Atlantic region > Ray Ontko & Co. - Software consulting services - > http://www.ontko.com/ > GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 > Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 > _______________________________________________ > tinc mailing list > [email protected] > http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc >
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
