similar to: TINC 2.0

Hello, Here is a patch for protocol_subnet.c with two modifications : - in tunnelserver mode, tinc must check subnets in the ".../hosts/owner" config file, not in "c->config_tree" (which is the configuration of the meta-connection from which we receive the ADD_SUBNET message). - this checking can be made before the check of the owner, especially before any

Hi, We want to deploy a tinc VPN, with more than 50 sites connected all arround the world. But we cannot trust all our sites with the same level, so the tinc solution (automatic full mesh) is "too automatic" for us : *any* node can add a new node which will be connected directly to others. A solution could be TLS (signing public keys), but create a PKI is another issue for us.

Hello, Sorry if this is a frequently-asked question - but I didn't find the answer on the tinc frequently-asked questions page :-) OK, the question is: * Given that tinc uses TCP for its metadata channel, and that tinc also uses the OpenSSL library, why doesn't tinc just open a TLS connection for its metadata channel? I'm sure there must be a good reason, but I can't think

On Tue, 5 Apr 2016, Andrew Bartlett wrote: > On Mon, 2016-04-04 at 14:48 -0600, Ochressandro Rettinger wrote: >> Hi, sorry. I have spent about 4 hours googling, and had no >> luck. >> I'm getting repeat core dumps out of smbd, and nothing I've gotten >> from >> the log file has successfully pointed me at any indication that >> anyone >> else

Hi, sorry. I have spent about 4 hours googling, and had no luck. I'm getting repeat core dumps out of smbd, and nothing I've gotten from the log file has successfully pointed me at any indication that anyone else has posted about this problem before. ------ libgcrypt selftest: binary (0): Selftest failed (/lib64/.libgcrypt.so.11.hmac) fatal error in libgcrypt, file visibility.c,

> That said, there are significant advantages to using external > libraries for this: some of them use heavily optimized (assembly, > tuned for SSE etc.) code for ChaCha-Poly1305, which is a big win for > tinc because it dramatically lowers CPU usage and increases maximum > achievable throughput. See > http://bench.cr.yp.to/impl-stream/chacha20.html This is quite a nice point,

ofcourse there is no freepbx, and there is no difference between the version of asterisk , ATM we are using asterisk 1.6.2.19 , i've also tried it on asterisk 1.10 , which resulted in the same way , does anyone have any ideas , why is it happening like this . thank you. On 9 January 2012 14:30, <tinc-request at tinc-vpn.org> wrote: > Send tinc mailing list submissions to >

see: To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba ;-) -----Oorspronkelijk bericht----- Van: klang at countyofdane.com [mailto:samba-bounces at lists.samba.org] Namens Klang, Marvin Verzonden: woensdag 15 april 2015 22:02 Aan: 'kseeger at samba.org'; 'samba-announce at lists.samba.org';

actually at the moment the setup is like this , it has the same ip address , both lan and tinc , but iax doesn't work at all , moreover , i want to be able to make an IAX trunk to the rest of the machines from different networks together . what happens is that , asterisk says that the request is sent , but nothing will be received . if you want i can try to make a tcpdump tomorrow , and send

Hello Mads, In case you never saw any mail from me, I'm tinc's co-author. It would be helpful if you'd subscribe to the tinc developpers mailing list. It's not high volume, but it eases communication. There's a problem with tinc's boot scripts (at least the debian one, but that's fixed now). The netmask of the tap devices should be larger than the one specified with

This is ready for review but needs a bit more real-world testing before I'd be happy about it going upstream. It also needs tests. It does interoperate with qemu, at least in my limited tests. Rich.

I noticed that the base64 functions in util.c don't produce the same results as other versions that implement RFC 1421 (and its successors). This results in PEM files that can only be decoded by tinc itself. Is this intentional? Below is a diff to make tinc's base64 functions match what everyone else does. This will break existing key files, though, which is unfortunate. - todd diff

===================================================================== "In this world nothing can be said to be certain, except death and taxes." Benjamin Franklin ===================================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.2. Changes since 4.2.0: -------------------- o

===================================================================== "In this world nothing can be said to be certain, except death and taxes." Benjamin Franklin ===================================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.2. Changes since 4.2.0: -------------------- o

Hi everyone , i have a large network , connected together by tinc , and the whole network is connected so that i can access all the devices through out the networks simply and easily , but when i try to interconnect my asterisk servers usin iax , it doesn't work , if i try to register to my server using the tinc's interface it's ok, the registry is done ok , and the connection works

Hi Parke, Thanks for replying. I mkdir it, kill tinc and restart, nothing in config changed, and it works! I don't know what's behind but I should've try system "kill" rather than tinc's stop/restart stuff... Parke <parke.nexus at gmail.com> 于2019年5月7日周二 上午5:12写道： > On Mon, May 6, 2019 at 2:12 AM David Penn <px920906 at gmail.com> wrote: > > > On

Dear I am very new to tinc and would like to ask any advice regarding tinc's throughput. I have been using OpenVPN for several years and found tinc as a simpler/scaler VPN using TUN/TAP device. I have tried to use tinc on WindowsXP and measured throughput in contrast to OpenVPN. My test revealed that tinc is faster in PING response (almost half of OpenVPN). However, when I tested with

Hey, Tinc developers! I'm not sure if anyone else has brought this up, but we've got a rather good reason for using TCP, even though UDP will actually form a working connection. Anyone on Comcast's "small business" service is forced to use an SMC cable modem/router. Its NAT implementation is capable of letting tinc's UDP tunnels work fine, but they limit a single UDP

Hi I'd like to make tincd work with other crypto apis than openssl/ libcrypt. I've learned from the subversion repository that an effort was started to port it to gnu-tls. I for myself would like to get tincd linking against xyssl (1) because it is very lightweight and thus an adequate option on devices with little memory and disk/flash space, i.e. embedded systems. Now i'm

v2: * Improved documentation. * Added a test (interop with qemu client).