similar to: Public Key format

Fantastic, having it in the CLI would great. It is for the reason of users losing the pub key that I ask, writing some docs for an internal network. Ah interesting, I finally found openssl does not have the 25519 curve in there(and no plans to do so looks like) but I was not aware there was non standard priv key format either. Would it make sense for the tinc -n <netname> get

On Sat, 17 Jan 2015, Martin wrote: > I'm writing a storage app for storing the Ed25519 pub keys and want to do > some basic verification when a user submits their public key. > > Is it just A-Za-z0-9 ? or can it contain special chars as well? > > I'm assuming it will be in the range of printable characters? It is base64, so a handfull more characters are allowed, but

Hi everybody. Is there a way to have a list of reacheable partners and its connection status? I need to list all partners in any tinc instance, its status (connected / disconnected) and connection method (direct, relayed thru other partner, etc.) Thanks! -- *Ing. Guillermo Bisheimer* *B&S Sistemas de Control y Equipamientos* Av. de los Constituyentes 1172 (E3116CIX) Crespo, Entre Ríos

On Tue, 5 May 2020 13:32:50 +0100 Jonathan Plews <SRS0=286U=6T=yahoo.co.uk=pl3w5y at mijnuvt.nl> wrote: > I didn't study the internals but maybe changing DirectOnly, Forwarding > and IndirectData will have an impact on per packet performance and > speed stability by disabling some of the meshing features? I will definitely try those. > Although it probably just hit the CPU

On Sat, 16 May 2015, Guus Sliepen wrote: > On Sat, May 16, 2015 at 12:09:52AM +0200, Sven-Haegar Koch wrote: > > > This change is not so good: > > > > Connection with aaa_vpnhub1 (1.2.3.4 port 443) activated > > Error while translating addresses: ai_family not supported > > > > (And then the tinc process exists) > > Hm, I couldn't reproduce

Hi all, As title, is that possible to develop a python version of tinc, that will be interesting:) Tks. Cong -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc-devel/attachments/20161213/fcd83914/attachment.html>

On Fri, 15 May 2015, Guus Sliepen wrote: > On Fri, May 15, 2015 at 10:26:46PM +0200, Sven-Haegar Koch wrote: > > > Another strange and difficult to understand thing - seems like all the > > easy bugs in 1.1 are gone ;) > [...] > > Got ADD_EDGE from aaa_vpnhub1 (1.2.3.4 port 443) for haegar_tokamak > > -> igor which does not match existing entry (Local

Hallo, I have a couple of tinc hosts in the same network, some using the latest tinc 1.1 git and some using 1.0.24. It seems like traffic between 1.1 and 1.0 nodes is always transfered using TCP (and an intermediate node, if not directly connected), never with UDP. Viewed from host W (tinc 1.1): (All after successfully pinging an IP behind the remote side to trigger UDP path probing, and

Hi - Thanks to Sven-Haegar and Donald, but still having issues setting up with Windows. Machine1 can't ping the VPN address of machine2. Regular IPv4 address for both machines in 192.168.1.xxx range. Router: Forwarding port 655 to 101.102.103.1, UDP and TCP Forwarding port 656 to 101.102.103.2, UDP and TCP Tinc.conf on machine user1 just three lines: Name = vpnuser1 ConnectTo =

Hallo, Another strange and difficult to understand thing - seems like all the easy bugs in 1.1 are gone ;) waehring (1.1) | +-------------------+--------------+ | | | vpnhub1 (1.1) igor (1.1) turing (1.0) | | | +-------------------+--------------+ | tokamak Whenever another node outside of the graph connects to vpnhub or igor

Hi, Thanks to John Wice for helping me with an earlier question. My two PCs behind the same router are still having problems connecting. Would appreciate thoughts on what I?m doing wrong? Router: Port 655 forwarded to 192.168.1.45, both TCP and UDP Port 656 forwarded to 192.168.1.51, both TCP and UDP Machine #1. ========== Local IP address on LAN = 192.168.1.45 Windows Firewall

With pleasure we announce the release of tinc version 1.1pre11. Here is a summary of the changes: * Added a "network" command to list or switch networks. * Switched to Ed25519 keys and the ChaCha-Poly1305 cipher for the new protocol. * AutoConnect is now a boolean option, when enabled tinc always tries to keep at least three meta-connections open. * The new protocol now

With pleasure we announce the release of tinc version 1.1pre11. Here is a summary of the changes: * Added a "network" command to list or switch networks. * Switched to Ed25519 keys and the ChaCha-Poly1305 cipher for the new protocol. * AutoConnect is now a boolean option, when enabled tinc always tries to keep at least three meta-connections open. * The new protocol now

Saverio My current tinc 1.0.35 is running fine on CentOS, and recently and I upgrade the OpenSSL of the OS to 1.1.1a. After the upgrade, tinc works fine, but since the OpenSSL library is on a separate folder compared with previous version, I doubt tinc doesn’t use the new OpenSSL. Also, I doubted about whether tinc 1.0.35 support OpenSSL 1.1.1a as well, should I use the lastest tinc 1.1pre7 to

Hi , I am currently a user of tinc 1.0.36 , i want to switch to tinc 1.1 because of the udp hole punching . Using 1.1.pre17 is safe ? All nodes in the mesh must run the same version ? Do we have a release date for 1.1 ? Regards, -- Erwan MAS

Hi Sven, 2008/1/25, Sven Koch <haegar at sdinet.de>: > Package: nut > Version: 2.2.1-1 > Severity: normal > > I am using a Mustec PowerMust 1000 USB, connected with a USB cable to > the PC. > > With nut 2.2.0-2.1 everything works without problems - but since the > 2.2.1-1 update the "upsdrvctl start" from the init script just fails, > executing the

Hello tinc users, i have the follow configuration: 1 client/server called master, it is always reachable from internet (with dyndns) 5 clients, that connects to the master and the other clients (all behind a router (NAT)) master-hosts-file: Address = ... Port = ... Subnet = ... Compression = 0 ---- key ----- client-hosts-files: Compression = 0 Subnet = ... ----- key ----- tinc.conf Name = ....

On Thu, May 4, 2017, at 09:04, Guus Sliepen wrote: > It is currently unspecified what tinc will do when you have two nodes > with exactly the same Subnet. The only guarantee currently is that > traffic goes to one of the nodes that is online. > > The implementation currently has the effect that, from the set of nodes > that is online, tinc will choose the one that has the lowest

https://bugzilla.mindrot.org/show_bug.cgi?id=3195 Bug ID: 3195 Summary: ssh-keygen unable to convert ED25519 public keys Product: Portable OpenSSH Version: 8.2p1 Hardware: amd64 OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh-keygen Assignee:

>> >> Nice hint, but it's not this simple. Libvirt complains about the >> network not the interface. The interfaces have different names already. >> It seems like tinc bind the subnet on startup and libvirt doesn't >> like it > Well, if it's about the subnet, then it's up to you to change the > Subnets in the host config files (and change