On Fri, 22 Jan 2016 11:51:45 -0800, Grant wrote: > > To talk to this computer from another of my machines over ZT I would > > use the 10.252... address. If you tried that address, you'd get > > nowhere as you are not connected to my network.
> So if 10.252.252.6 were configured as a router, could I join your ZT > network and use iptables to route my example.com 80/443 requests to > 10.252.252.6, thereby granting me access to my web apps which are > configured to only allow your machine's WAN IP? You don't need a bridge in a network to join it. If I want you to join it, I give you the network ID and you simply join it, although you can't actually connect to it until I authorise the connection. However, if this machine were configured as a bridge, then once you had joined my network you would have access to all of my LAN, rather like an OpenVPN connection. It seems that the man difference between this and a traditional VPN is that all of the setup work is done on the one computer, connecting extra clients is just a matter of connecting them to the network. Note that I haven't actually tried this, every machine on my LAN that I want to be able to connect to is running ZT so is directly accessible. > Is it possible (easy?) to run your own "core node" and so not interact > with the official core nodes at all? It is definitely possible, and you skip the "only ten clients for free" limit as that only applies to using their servers. Once again, it isn't something I've tried yet, but it is on my list of "things to do when I find some time". I'm quite happy using their discovery servers so this would be only an exercise in trying it "because I can". -- Neil Bothwick MUPHRY'S LAW: The principle that any criticism of the writing of others will itself contain at least one grammatical error.
pgpW52yseiUCN.pgp
Description: OpenPGP digital signature
