I've changed the zerotier prefix that we use.
Instead of fd00:0:f1d0:0:539::/80, I've changed it to fd00:f1d0:539::/80 - I think I should have set it up this way originally.
That way, if other networks use zerotier, then all ftn's can be held in the fd00:f1d0::/32 address space, and TQWnet is contained in
fd00:f1d0:539::/48 address space (if there was ever a reason to use IPv6 for more than just zerotier else).
So nodes now have addressing like fd00:f1d0:539:0:0:N:F:P, and thus making it easier to write an address in short form. Eg: The AU Hub
is fd00:f1d0:539::2:64:0.
At the moment, I've reconfigured zerotier so that nodes have the old and new addresses, but I'll delete the old addresses when you
update the DNS for the hubs.
Nobody needs to change anything, it should all continue to work as normal. (There arent that many nodes anyway using it).
Also, I realised, that I hadnt uploaded the firewall rules into zerotier - which I've also done. It will now only allow the following
traffic:
* TCP/23 - for telnet
* TCP/24554 to TCP/24564 - for BINKP (incase some folks have multiple binkp ports)
* UDP/53 - for DNS - I was playing around with DNS so that we can resolve *.tqwnet.ftn (using fd00:f1d0:539::1 as the DNS server)
Re: ZeroTier IPv6 Change
By: deon to MeatLotion on Sun Mar 27 2022 09:24 pm
Howdy,
Just want to double check that you saw this.
I'm going to delete the old prefix, but noticed that the DNS is still using addresses with it...
...
Sysop: | Shaun Ewing |
---|---|
Location: | Blue Mountains, Australia |
Users: | 195 |
Nodes: | 16 (0 / 16) |
Uptime: | 219:15:01 |
Calls: | 152 |
Files: | 187,817 |
Messages: | 328,119 |