#tinc — Public Fediverse posts

@resingm #Tinc seems to do better with full #mesh networks. #WireGuard is fundamentally point-to-point. You can of course build any logical topology with point-to-point, so #WireGuard does scale

@resingm I don't have a lot of experience with #Tinc. We do have a lot of experience with #WireGuard. WireGuard is generally considered to be faster than Tinc, especially on high-speed optical networks. This is because WireGuard uses a kernel module to handle encryption and decryption, which reduces overhead and increases throughput. Because it is #OpenSource, it can be run on #ASIC hardware in routers and switches.

Anyone has experience with #tinc and can point me to some write-up about pros and cons when compared to #wireguard?

#VPN #networking

#VännäsKasino - Pay To Live! #music #punk #rock #Refused #Tinc #invsn youtu.be/NqSeYlOnijA?...

Vännäs Kasino - Pay To Live ...

Monday. #Smashitup! Have a great week. #Music #Hardcore #Punk #Rock #Tinc #Refused youtu.be/FyjmCg_VMU0?...

The (International) Noise Cons...

Playing around with #innernet to quench my thirst for a more modern meshnet VPN than my current one (#tinc). The READMEof the project is very promising, it should support everything I want, although it only allows for a single server to negotiate the mesh's state, which seems dangerous.

Additionally, while setting up that single server seems easy enough, creating CIDRs is simple enough, actually getting the nodes to join seems less simple. The configuration file it generates for me suggests using the network name for the interface name, and this just fails with failed to start the interface: [...] - Operation not supported (os error 95).. Not too useful on its own, but it appears if I instead name the interface to match wg\d+ it will work to create the interface at least.

Now it still can't redeem the invite, and I have no idea yet why its still upset now 😭

Playing around with #innernet to quench my thirst for a more modern meshnet VPN than my current one (#tinc). The READMEof the project is very promising, it should support everything I want, although it only allows for a single server to negotiate the mesh's state, which seems dangerous.

Additionally, while setting up that single server seems easy enough, creating CIDRs is simple enough, actually getting the nodes to join seems less simple. The configuration file it generates for me suggests using the network name for the interface name, and this just fails with failed to start the interface: [...] - Operation not supported (os error 95).. Not too useful on its own, but it appears if I instead name the interface to match wg\d+ it will work to create the interface at least.

Now it still can't redeem the invite, and I have no idea yet why its still upset now 😭

Playing around with #innernet to quench my thirst for a more modern meshnet VPN than my current one (#tinc). The READMEof the project is very promising, it should support everything I want, although it only allows for a single server to negotiate the mesh's state, which seems dangerous.

Additionally, while setting up that single server seems easy enough, creating CIDRs is simple enough, actually getting the nodes to join seems less simple. The configuration file it generates for me suggests using the network name for the interface name, and this just fails with failed to start the interface: [...] - Operation not supported (os error 95).. Not too useful on its own, but it appears if I instead name the interface to match wg\d+ it will work to create the interface at least.

Now it still can't redeem the invite, and I have no idea yet why its still upset now 😭

I have compared several self-meshing VPN solutions - especially in the context of a VIXP in dn42.

https://mk16.de/blog/comparison-of-self-meshing-vpns/

TLDR: The one VPN solution that meets all my criteria is the pre-release version of Tinc.

#VPN #Networking #dn42 #Tinc #n2n #Tailscale #Headscale #Zerotier #Nebula

Tinc, a VPN protocol and program that independently forms a mesh network (Layer 2/3), no longer appears to be actively developed.
I think this is a great pity, as the new version would include support for ChaCha20-Poly1305 with Ed25519, which is quite modern. Furthermore, Tinc is used in many areas such as ChaosVPN, Freifunk and dn42.
Unfortunately, there is virtually no alternative that is completely FLOSS and has the same features.

https://github.com/gsliepen/tinc/issues/443

#Tinc #VPN #Networking #FLOSS

#NixOS #help

Ich suche und probiere nun seit >1h. Wie bekomme ich denn mein manuell funktionierendes #tinc (#tinc_pre) in ein #systemd Konstrukt per #configuration.nix?

@[email protected] @[email protected] I really should look into replacing #tinc with a #WireGuard mesh VPN setup at some point. I've been told it should perform much better, but I've not yet found (or really looked) into making WireGuard a simple mesh network, in a way that I could completely automate using #Bashtard.

Argh, heck this. I used git-filter-repo to rewrite all this stuff. Also, changed my nginx/cgit config to only display some stuff...

Anyway...

Here's my current #ansible repo state.
https://git.uvok.de/ansible/
I recently added some files to set up a #tinc host - Key generation still needs to be done manually, and the copy-file step is extremely slow. Still, enough for a quick start.

Probably I could look into triggers as well...

"#tinc is a #VPN daemon that uses tunnelling and #encryption to create a secure private network between hosts on the Internet. tinc is Free Software and licensed under the GNU General Public License version 2 or later. ...allows VPN sites to share information with each other over the Internet without exposing any information to others." ,,,its got some nice features like NAT traversal...neato.

https://www.tinc-vpn.org/

#FOSS #privacy

#dn42 #networking #tinc

Hm, tinc seems to max out at about 100 MBit/s. Not ideal... but I think I can live with that for my purposes.

(Babel runs over Tinc; since multicast discovery with more than 1 peer doesn't word in #wireguard )

Hmm, trying to get #tinc to work, by going through the NixOS wiki page on Tinc, but I don't really understand how it accesses the (private) keys. At the start of the article they're generated to be in /etc/tinc, but then later in the hostfile definition they're supposed to be in /root/secrets.

Does any more experienced #NixOS user know what's going on there? Is this incorrect in the wiki page, or is there some secret management magic going on that I have missed so far?

@kissane @sigridellis talk.bizarre on USENET. For me, it was the perfect conjunction of time of life, people, and subject matter. 35 years later, I am still friends with many of the folks I met there. I was going to tag them all but gave up when I hit 20, and that’s just the folks who are on Mastodon. #tinc

I wrote a deep dive about #mesh #VPN solutions, with #NAT traversal and such. Featured: #Yggdrasil, #tinc, #Tailscale, #Zerotier, #Nebula, #Netmaker. "Easily Accessing All Your Stuff with a Zero-Trust Mesh VPN" at https://changelog.complete.org/archives/10478-easily-accessing-all-your-stuff-with-a-zero-trust-mesh-vpn

Thanks to those that participated in the previous thread, and particularly @tailscale .

There are some interesting options these days and I hope to see them continue to gain traction!

Update: Looks like some candidantes include: #Tinc (sort of the OG mesh network VPN, which I didn't realize can do NAT traversal), #Tailscale (fully Open Source if the #Headscale frontend is used), #Nebula, #Netmaker (not entirely clear but I THINK this is also open source). Thanks for the suggestions everyone!

How to Set Up Peer-to-Peer #VPN with #Tinc on #Ubuntu #Linux 22.04 :ubuntu:
https://www.howtoforge.com/how-to-set-up-peer-to-peer-vpn-with-tinc-on-ubuntu-22-04/

@netopwibby So let's say you have a company with offices in five cities. You want the various networks to all see each other, seamlessly, and securely. A classic approach might involve VPNs. But then you quickly get into topology questions: who connects to whom? What happens if one site goes down - can all the others keep communicating between themselves? #tinc or #Yggdrasil can address this. 6/

@jvalleroy It has a few things in common with each of those, but is pretty distinct. #Yggdrasil is more similar to #cjdns and the #tinc VPN project. Compared with #Tor, strong anonymity is not a design goal of Yggdrasil, while performance and compatibility with existing software is. Yggdrasil may have some anonymity-enhancing properties over "mainnet", but not to the extent of Tor. However, they both share strong end-to-end encryption. 1/

@jvalleroy It has a few things in common with each of those, but is pretty distinct. #Yggdrasil is more similar to #cjdns and the #tinc VPN project. Compared with #Tor, strong anonymity is not a design goal of Yggdrasil, while performance and compatibility with existing software is. Yggdrasil may have some anonymity-enhancing properties over "mainnet", but not to the extent of Tor. However, they both share strong end-to-end encryption. 1/

@skobkin
Ха! Только я решил глянуть #tinc и на его аналоги, как тут же вижу, что аналоги уже сами начинают запрыгивать в поле моего зрения😊

Here's my NeoNetwork (a VPN network that is like DN42, but much smaller):

https://gitlab.com/Neo_Chen/NeoNetwork

#Tinc #OSPF #Networking #VPN

📰 Découvrez la lettre d'information de Worteks du mois d'octobre 2019 !

👉 https://mailchi.mp/0c70e0527ea9/newsletter-worteks-2019-247541

#Worteks #newsletter #RedHat #IdentityDays #LDAPCon #lemonldapng #openshift #freeipa #OpenLDAP #Tinc #OpenStack #OPNSense #LDAPToolBox #FreeSoftware #LogicielLibre

Putting a few hashtags out there for the benefit of undiscovered known collaborators: #tdotbee #tdotb #talkbizarre #readlearnevolve #tinc #thereisnocabal #plonk