| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
tap driver. Seems to work. Now to see if the cleanup we did here gets rid of the zombie tap device issue on Windows.
|
|
what we did this for: a refactor of the Windows tap connector.
|
|
|
|
pretty well now!
|
|
|
|
|
|
non-privileged users can access them (if they have auth token).
|
|
authtoken.secret if system unreadable.
|
|
|
|
supernodes from resynchronizing unless explicitly ordered.
|
|
and there is no point in mallocing the TCP write buffer.
|
|
|
|
|
|
|
|
indeed learn incoming TCP paths. Otherwise the recipient of a TCP connection does not know to reply via TCP! Heh.
|
|
certificates of membership tagged onto them. This likely will not actually increase the number of fragments in practice much, since these are then subsequently compressed. But the buffer needs to be allocated with room for them, otherwise these packets get dropped with a range_error exception internally.
|
|
|
|
|
|
|
|
|
|
done on Windows (I think).
|
|
|
|
|
|
|
|
|
|
|
|
ssh://shub-niggurath.zerotier.com:222/git/ZeroTierOne into adamierymenko-dev
|
|
|
|
|
|
|
|
|
|
|
|
|
|
all paths are equally dead.
|
|
should not impact non-lame protocols.
|
|
multicasts that would exceed limits, for GitHub issue #55
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SocketManager. Also add FD_SETSIZE checking for the default select implementation of sockets.
|
|
|
|
|
