(1) Fix updating of network revision counter on member change.

(2) Go back to timestamp as certificate revision number. This is simpler
    and more robust than using the network revision number for this and
    forcing network revision fast-forward, which could cause some peers
    to fall off the horizon when you don't want them to.
This commit is contained in:
Adam Ierymenko 2015-07-23 17:18:20 -07:00
parent a493fc23f4
commit d647a587a1
3 changed files with 17 additions and 15 deletions

View file

@ -158,7 +158,7 @@
/**
* Maximum number of packet fragments we'll support
*
*
* The actual spec allows 16, but this is the most we'll support right
* now. Packets with more than this many fragments are dropped.
*/
@ -216,7 +216,7 @@
/**
* Maximum number of ZT hops allowed (this is not IP hops/TTL)
*
*
* The protocol allows up to 7, but we limit it to something smaller.
*/
#define ZT_RELAY_MAX_HOPS 3