Subj : Re: ZeroTier
To   : MeaTLoTioN
From : Alterego
Date : Tue Aug 27 2019 21:28:31

  Re: Re: ZeroTier
  By: MeaTLoTioN to Alterego on Tue Aug 27 2019 11:58 am

 Al>> So, I was thinking of using ZT:<ID>. Technically we should probably use
U,ZT: (I think is the syntax) since ZT is not an official flag - but
 Al>> then hey, this network is breaking the boundaries right :)
 Me> So you mean after the ,UMY flag for eg on my node (UMY for Mystic) we
could
 Me> add a ,ZT:<id> where the ID is the ZeroTier ID we get when we do the
`zerotier-cli status` command?

According to FTS-5001 (if we want to follow the standards), it should be
,U,ZT:xxxx (and use the ID as identified by zerotier-cli status).

 Me> That would be sweet if your ZT setup would read this and if a new node is
 Me> added to the nodelist with a ZT:<id> it could check to see if the <id> is
present and if not, automatically assign it to the network with the right IP
 Me> address based on the node number? Or is this already what you had planned?
 =)

Right - I'm hoping it can "auto approve" new connections.

So as somebody requests to join the network, they would popup in the network
with authorised:false. Then if I see their ID in the nodelist, it can enable
the connection with the appropriate address.

Likewise if folks disappear from the nodelist, they are removed from the
network.

I was hoping the API could tell me the last time they were connected to the
network as well, but it seems it doesnt have that. If you saw in my status,
there is a "network revision" field which I thought might tell me that, but no
(I dont know what its for now) :( I might have to do that another way ...
....лоег

.... The chief export of Chuck Norris is pain.
--- SBBSecho 3.08-Linux
 * Origin: Alterant | An SBBS in Docker on Pi! (1337:2/100)

.