similar to: TCPOnly is required since 1.0.13?

Hi, we are using Tinc in our Freifunk Network in Oldenburg for internode connections over the internet. So Tinc is running on OpenWrt 10.03 on Dlink Dir-300 Routers. We all have enough internet bandwith (1,6 MB/sec and more) but we only get a maximum speed of ~350KB/sec between two tinc nodes because then tinc uses 99% of the cpu. Is it possible to get more Speed with tinc on this machines?

> 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

Hello All, How are you all doing today? Good i hope. I am wondering if some one could please comment on the scalability limitations of Tinc as far as bandwidth usage and connections? Thinking about the documentation on Tinc suggests that if it is always trying to maintain a full mesh topology and if there would be many nodes, e.g. more than about 100 or so active at a give time, then Tinc

On Tue, Apr 10, 2018 at 03:36:08PM +0200, Hans de Groot wrote: > hosta  <--> hostb  <-->  hostc > > Hosta and hostc are not directly connected via tinc. But both are conncted > via hostb (I called my network tincnet). This works fine I can ssh from > hosta to hostc and vice versa without any problems. > > hostc is in a whitelisted iprange at some service

Hello, I'm upgrading to 1.0.14 I did some manual tricks in my Gentoo Portage because seems that upstream Gentoo did not update the portage yet, does anybody know how to Contact Gentoo Linux to have the package updated ? Question 1: I notice in my log file I had many entries like this with 1.0.13: 1307284053 tinc.ninux[15152]: Lost 251 packets from GREG1 (151.28.100.141 port 655)

Hi everyone, I'm setting up a VPN over IPv6, attempting to build an IPv4-over-IPv6 tunnel, but when I try to connect to the server, I got this: System call `getaddrinfo' failed: Address family not supported. Client runs WindowsXP, and I did almost exactly the same as http://www.tinc-vpn.org/examples/windows-install . Here is the configuration files: ------- tinc.conf ------- Name =

Hello! I have recently installed tinc on a linux 2.4 machine which has 192.168.0.0/24 private network connected to eth0 and registered ip on eth1. I also installed tinc on Windows 2000 machine on a remote location. for this moment I can establish connection, on Linux machine tincd says: Sep 26 21:10:50 hostname tinc.gscvpn[483]: Node home (y.y.y.y port 655) became reachable But i

Hi there! Today I've tried a FTP connection (me with TCPOnly send file to another no TCPOnly), but the upload bandwidth was about 20 kb/s, while connecting to the other directly (I upload a file to him via FTP) the connection was about 5 times faster... what's wrong? thanks

Hi there! Today I've tried a FTP connection (me with TCPOnly send file to another no TCPOnly), but the upload bandwidth was about 20 kb/s, while connecting to the other directly (I upload a file to him via FTP) the connection was about 5 times faster... what's wrong? thanks

If the concern is more about the reliability instead of throughput, should I add TCPonly = yes in the host configuration to make the VPN runs on TCP?

My intention is to set up tinc so that I can connect from home to an office network. All CPUs are running MacOs X, 10.2.8 or 10.3.5. I have read the tinc manual, tincd.8 and tinc.conf.5. However, I am still unclear about a few issues. First and foremost, how to I setup the VPN interfaces on the hosts, on MacOs X? Which file do I have to alter and what is the exact syntax on Os X to setup

Well i currently try to set up tinc between two hosts, one with normal dsl connection one behind some kind of unknown firewall (Note since OpenVp is able to connect when the normal one is the Server I guess tinc should be able, too) start.bat-------------------------------tincd -n Empire-Network -D -d4 --bypass-security (Bypass is only currently because tis not working yet)

Hi, I've successfully running tinc1.0pre4 between two locations on SuSE Linux 7.1 in a special masquerading Firewall environment, so that I'm using the TCPonly keyword in the host files to get a connection. Otherwise I would get the message 'Received UDP packet on port 655 from unknown source <ipaddress in hex:port>'. After upgrading to 1.0pre5 I'm getting this message

I agree with the in-effective of TCP transmission, but I wonder if the the UDP packet is dropped, the tinc VPN itself wouldn’t retransmit, and if the upper level application doesn’t handle the packet loss well, will this be the problem? Or the upper level application have very limited tolerance to packet loss(like RDP application, I guess if the packet loss go to certain threshold, the connection

Let me start with what I'm trying to accomplish. I use tinc mainly to get to subnets behind the daemons and I don't control those subnets and can't guarantee overlap. I was using routing mode and reconfiguring tinc every time i needed to get to a subnet behind a specific daemon. Then I came across switch mode that allowed me to simply add routes based on the IP address of the tinc

Hello, I'm trying to connect some windows machines together using tinc 1.0.6. The basic connectivity (ping) works fine as expected. But I'm getting really poor speeds over the tinc tunnel. The test machines are on the same switch and get values ranging from 6-9 MBytes/s speaking directly to each other. However over the tinc tunnel the speeds are in the range of 20-40 kbytes/s. The machines

Hi, I'm having some trouble trying to run tinc over GNU httptunnel. On server A I have: /etc/tinc/netname/tinc-up: #!/bin/sh ifconfig $INTERFACE 10.3.0.1 netmask 255.255.0.0 /usr/bin/hts -F localhost:655 8888 /etc/tinc/netname/hosts/A: Address = foo.com Subnet = 10.3.0.0/24 TCPonly = yes /etc/tinc/netname/hosts/B: ConnectTo = A Subnet = 10.4.0.0/24 TCPonly = yes

Guus, [tinc version 1.0.24] Consider the case where you have the following setup client - fw - server The client and server successfully setup a tunnel and UDP communication starts to happen. Then the client shuts up and the server only needs to send data to the client if the remote tool accesses the client?s UI. If the firewall times out the NAT UDP hole, the server has a problem: The UDP

Hi, I have successfully connected a network of about 60 nodes (many of which are virtual machines) with tinc 1.0 but encounter a severe bug when physical connectivity between two major locations is lost and then reconnected. From what I gathered, many nodes attempt to connect to many other nodes, causing 100% CPU load on all nodes, taking down the whole network with no node succeeding connecting

Hi, Am Samstag, den 26.09.2015, 15:45 +0200 schrieb Marcus Schopen: > Hi, > > Am Samstag, den 26.09.2015, 12:20 +0200 schrieb Marcus Schopen: > > Last Problem seems to be the local UFW Firewall on the clients whichs > > seems to block the Broadcast for LocalDiscovery = yes. Need to check the > > logs here. > > Puzzeling around with UFW firewall. What ports need