similar to: NSS vs OpenSSL

i have a switched and bridged tincd node with two addresses, each with a different port. Address = 37.70.156.168 28655 Address = 192.168.2.228 655 i was having trouble reliably connecting to it / thru it and noticed that a log from a remote tincd node indicated it may have mixed up the ports. It doesn't appear to use the 28655 port that would be needed for remote access. Before i

[This email is either empty or too large to be displayed at this time]

c:\APPS\TINC\tincd.exe --mlock --net=mynet --config=C:\APPS\tinc\mynet Without --mlock, the service starts OK. With --mlock, the service fails to start.

Would it be extremely difficult to do multicast over tinc? How about reliable multicast over tinc? This would be more traffic than multicast dns, but not _necessarily_ a great deal more. It would be for syncing some information among freeipa domain controllers. Would the tinc nodes need to be in all in switch or maybe even hub mode? EthernetOverIP over tinc?

Currently, i have nodes with PMTUDiscovery =yes and ClampMSS = yes. When the server does not receive a PMTU request back from one of the clients even when the packet size is very small (say 164), then it reverts to TCP. Should i turn off PMTUDiscovery or should it be ok to leave on? It takes a very long time to do simple pings (1 second or so), so i wonder what else i can do?

Hello, I have tried for days on end with no success on this, so I thought I would post it here and see if someone can help me at all. *Here's the scenario:* I have 1 PC with a Static IP/Domain (a dyndns.org account - myserver.homeip.net) connected to a router, which in turn is the gateway to the internet. It also has a static local IP (192.168.1.2). I will call this the "server"

ping times to ConnectTo machine are often over a second or at least 300 milliseconds. Hundreds or thousands of times slower than other nodes from same physical location.

The documentation is very clear that multicast over tinc does not work in router mode. Why?

On Fedora 11 (yes, with SELINUX enabled and enforcing) setting tinc.conf's ProcessPriority=high prevents tincd from starting. Anybody have an answer? tinc was compiled by me, didn't come from Fedora's rpm repo.

googling "site:tinc-vpn.org wince" results in nothing. Has there been any attempt to port it to wince based devices?

How does one specify two different ports in the same host file? When lapops are hardwired versus when mobile on a totally different lan. address0 71.17.72.27 address1 192.168.2.27 port0 22755 port1 655

Have anything to do with firewall locations, meaning home vs work vs public vs lockdown. Probably not it at all. On Jul 13, 2016 3:22 PM, "Etienne Dechamps" <etienne at edechamps.fr> wrote: > That's strange. Can you post a detailed log from the affected node (run > tincd -d5 -D), especially the initialization phase? > > On 13 July 2016 at 16:17, Petr Man <petr

> Currently, i have nodes with PMTUDiscovery =yes and ClampMSS = yes. Hello, these features were introduced in 1.0.13 correct ?? I also understand that the two settings are by default "yes" if not explictly set to "no" in the config file. what may happen if I have a network with mixed versions from 1.0.11 and 1.0.13, where the older daemons do not implement that feature

You might want to try with https://github.com/gsliepen/tinc/pull/120 - that said, this bug probably doesn't explain everything because tinc is supposed to log a message from setup_vpn_in_socket() anyway, but there's no such message in your log. In addition, I really don't see any way the "Received UDP packet from unknown source" message could be logged if the UDP socket

Something tells me this was covered recently, but i didn't find it again in gmail. The nodes see each other but if i have something misconfigured that is decreasing my speed. All my nodes are behind NATs. i have a remote node that connects to a central node via port forwarding from public port 7777 to hp821 running on port 655. remoteNode ----> public ip 1.2.3.4:7777 ---->

I have the habit of putting the name of the host within the host file as a comment usually on the first line. Helps when files are renamed and tracking. The new version exports Name = victor and so the old comment style is not necessary. I would think the new version should still simply ignore lines that begin with the '#' character. For example, a normal host file named victor that

https://bugzilla.mindrot.org/show_bug.cgi?id=1676 Summary: Add NSS keys support Product: Portable OpenSSH Version: 5.3p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Smartcard AssignedTo: unassigned-bugs at mindrot.org ReportedBy: jchadima at

i use Fedora to build for Fedora and to build for Windows. These are some of my notes. README.git includes some additional packages. i added gcc-c++ but not sure OO actually is needed for any of the additional packages. There were many more mingw packages i installed having to do with development, but not sure all were necessary. Even though i yum installed some of these, openssl and lzo

Hi to everybody, Can anybody tell me what packages I need to install Tinc 1.1pre2 in a server that it had installed a previous version installed? I tried to install it and when I execute the "make" it give me a lot of errors. Best regards, Ramses

Window allows one to specify a DNS domain name and DNS server for a particular interface. So all DNS queries of your tinc interface are sent to a particular dns server. For instance windows tinc clients can use a particular dns server on a private LAN available only to clients inside that NAT or tinc clients. NetworkManager allows you to specify the same, but the tinc interface does not show up