deon wrote to N1uro <=-
So things werent adding up for me with your explaination of what you
were doing. I think we were coming from 2 different contexts.
I was lead to believe that "the network" as 44/9 and that the OpenVPN server surved that subnet to clients. So as a client on the network,
your address would have been a /9. (I should have picked that up when
you gave your ping output.)
But in your message, you shared this:this
it like OpenVPN would do. So in the policy route table I have for 44/9
is one of hundreds of routes:
44.64.10.32/27 via 24.0.91.254 dev tunl0 proto 44 onlink window 840
So its not really a single /9 vpn network, its multiple networks, and
you have a /27 vpn network and you route 44/9 over it.
And given that 44.0.0.1 goes "offline" without loss of connectivity to
you to 44.88.0.9 that means that the other end of your OpenVPN link
also has an alternative link to 44.88.0.9 (directly or indirectly).
Anyway, OpenVPN is a viable "vpn" alternative - I agree, but I think it requires too many management points, sets of servers running OpenVPN
and configuration to multiple parts of the network to provide
redundancy. (Too much for a simple BBS network.)
In contrast (which is how this thread started), ZeroTier is peer to
peer and just requires you to run a client and me. Since I'm managing
"my" network, I'm using a personal "controller" (not zerotiers) - and
you find me by requesting the controllers network address. Once I authorise you on the network, you dont route your traffic through my controller, you connect direct to me point to point.
Where the concern also was, is that ZeroTier's root servers are
required for you to find me - implying if they turned them off you couldnt. That's not true however, since I can define a personal root server (called a moon and more for redundancy), which you configure to find me without ZeroTiers invovlement.
I recall reading at some point that ZeroTier were going to enable you
to advertise your own "root servers" (since the root server's address
is harded coded in the client - in much the same way that DNS servers
(the DNS analogy) have a standard root server configuration). If and
when they do that, then ZeroTier could turn off their root servers and
you would still be able to find me (and no moons required).
I agree. It also would not qualify as Open Source software /
license.
Just to try and help offer another possible solution to this issue as a network engineer:
Why not investigate OpenVPN?
A dedicated hub feed to a european hub
can set up DNS locally to feed a hub in europe over OpenVPN using either TCP or UDP and choose ports, and maintain custom certs that may have a
long expiration date on them... and then it'd be up to that european hub
to feed the rest of europe - insuring that their laws are followed.
Oli wrote to N1uro <=-
N1uro wrote (2021-05-14):
p2p connections work by default in ZeroTier. Does OpenVPN do any NAT
hole punching? A known and simpler alternative would be tinc. OpenVPN
has also become kind of old-tech. Is there anything wireguard wouldn't
do simpler and better (for our use case)?
Personally I'm not interested in a top-down approach with admin(s) maintaining certs and granting and revoking access. I would call it unnecessary centralization (bullshit power & small bus factor). FTN are
on the lower layer decentralized and designed as "cooperative anarchy".
It's not that I don't appreciate your initiative to setup OpenVPN for
the network, I just doubt that standard VPNs are a good fit for FTN.
(not sure what the European hub and laws part is about)
Oli wrote to deon <=-
I agree. It also would not qualify as Open Source software / license.
Why not investigate OpenVPN? A dedicated hub feed to a european hub
deon wrote to N1uro <=-
OpenVPN is not point to point, but rather point to Hub. And sure an OpenVPN network could be created so that each hub was an OpenVPN hub,
but then me communicating to you (eg: crashing something to you) is dependant on our hubs being up.
ZeroTier is peer to peer - so if you are a node, and I am a node, we
can find each other. While we find each other via the root nodes
(called planets) provided by zerotier itself - we could also find each other via "our" roots (called moons) - and each hub could be a moon as well as anybody else who wanted to be one.
You only need to find one active moon to find me.
deon wrote to N1uro <=-
So I dont agree with you.
So I dont agree with you.That's perfectly fine and I'm happy to accept this. I will however
say that what you describe is not how I've had OpenVPN working in a
major corporate environment nor is it how IP works when you factor in the netmask of a subnet.
I'm on a subnet of 44/9 which is somewhat of a vpn minus the encryption. 44.0.0.1 is the host and where BGP is announced. My IP is
44.88.0.9 however
my path to a point in New Jersey does NOT go to 44.0.0.1, it is direct:
traceroute to wb2snn.ampr.org (44.64.10.33), 30 hops max, 60 byte packets
1 gw.n1uro.ampr.org (44.88.0.1) 5.670 ms 6.102 ms 6.095 ms
2 wb2ona.ampr.org (44.64.255.225) 41.601 ms 45.571 ms 46.421 ms
deon wrote to N1uro <=-
Its direct via the "hub" though right?
44/9 includes both 44.88.0.9 and 44.0.0.1 (and 44.64.10.33)
Network: 44.0.0.0/9 00101100.0 0000000.00000000.00000000 HostMin: 44.0.0.1 00101100.0 0000000.00000000.00000001 HostMax: 44.127.255.254 00101100.0 1111111.11111111.11111110 Broadcast: 44.127.255.255 00101100.0 1111111.11111111.11111111
If you did a tcpdump -ni tun0 on 44.0.0.1 you would see the packets
coming in (from your real IP) and going out again (to the other IP). Traceroute doest show it because you are not technically traversing a router (because it is a /9 network).
traceroute to wb2snn.ampr.org (44.64.10.33), 30 hops max, 60 byte packets
1 gw.n1uro.ampr.org (44.88.0.1) 5.670 ms 6.102 ms 6.095 ms
2 wb2ona.ampr.org (44.64.255.225) 41.601 ms 45.571 ms 46.421 ms
So, if you turn off 44.0.0.1, can you still ping 44.64.10.33 from 44.88.0.9?
Further the performance of your network traffic to 44.64.10.33 is
limited by the your link, 44.0.0.1's link and 44.64.10.33. If any of
those links gets "busy", especially 44.0.0.1 your peformance is
impacted.
it like OpenVPN would do. So in the policy route table I have for 44/9 this is one of hundreds of routes:
44.64.10.32/27 via 24.0.91.254 dev tunl0 proto 44 onlink window 840
traceroute to wb2snn.ampr.org (44.64.10.33), 30 hops max, 60 byte packets
1 gw.n1uro.ampr.org (44.88.0.1) 5.670 ms 6.102 ms 6.095 ms
2 wb2ona.ampr.org (44.64.255.225) 41.601 ms 45.571 ms 46.421 ms
Sysop: | Gary Ailes |
---|---|
Location: | Pittsburgh, PA |
Users: | 132 |
Nodes: | 5 (0 / 5) |
Uptime: | 110:15:55 |
Calls: | 733 |
Files: | 2,171 |
Messages: | 81,487 |