Subj : Re: ZT at hubs
To   : MeaTLoTioN
From : Deon George
Date : Wed Apr 24 2019 14:27:39

On 24 Apr 2019, MeaTLoTioN said the following...
 Me> internet also... but if ALL hubs that mine connects to all use ZT, I can
 Me> set it to only use ZT interface?

Technically you shouldnt need to "set" anything - ahh, the next question...

 Me> Next question is... How do I make sure that a) Mystic uses the ZT
 Me> interface, and b) if/when Al uses ZT, I can make sure that ONLY ZT
 Me> interface is used for relaying between the hubs?

a) The zt interface represents a "network", so any traffic destined for an
address in that network will go down that interface. Any other traffic will
go down the default route interface (if it isnt covered by another network
interface).

b) Yes - if you relay to fd00:0:f1d0:0:539:... that wont work on the greater
internet - and as long as your network interface is up, it will only ever be
tried down it. So in short, make sure the hubs resolve to it...

I was thinking too - since the network assigned addresses are by definition
static, and linked to your FTN address (that's what I'm doing anyway), you
could host them all in your DNS. eg: *.zt.erb.pw. I've started work on a UI
to the ZT controller - which if I can get it working, you'll be able to
assign nodes their network address and connect them to the ZT network, and
assign their ZT address - and since I know you use cloudflare, it could also
create their DNS entry... Might be pretty funky to use?

....deon

 _--_|\   | Deon George
/      \  | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/  | 
      V   | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A43 2019/02/23 (Raspberry Pi/32)
 * Origin: Chinwag | MysticBBS in Docker! (1337:2/101)

.