similar to: Can tinc traffic be identified by Deep Packet Inspection?

Hi, I´m using Tinc for several years, but I didn´t fix a performance problem. There a about 20 nodes in this network. Master: 10.0.0.12 (dedicated host in a datacenter, debian, 100mBit port) tinc.conf: Name = TincKnoten12 AddressFamily = ipv4 Interface = tun ProcessPriority=high mode = router #DirectOnly = no Compression=0 PMTUDiscovery = yes #IndirectData = yes #ReplayWindow = 64 #ConnectTo

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)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Guus, On 04/30/2015 03:42 PM, Guus Sliepen wrote: > On Thu, Apr 30, 2015 at 02:55:59PM +0200, Armin Schindler wrote: > >> we are using tinc 1.0.24 with 6 hosts (endpoints). Quality of service >> is used with prio qdisc on all network interfaces. This means depending >> on the TOS value of the IP header IP-packets will

Hello. I'm living in the country side where the communications are very very poor. My only choice is Satellite connection throw the French company Eurona which uses the network deployed by Skylogicnet. In general the latency is very bad (~800ms) and the network is very unstable. I have been investigating in the ISP routers which are in my path and there are many hops which are done in a

Hello all, we are using tinc 1.0.24 with 6 hosts (endpoints). Quality of service is used with prio qdisc on all network interfaces. This means depending on the TOS value of the IP header IP-packets will get a priority queue on the network interface. Packets from TINC (UDP 655) maybe reordered using these queues to send out high-prio (VoIP) packets first. Could this create a problem on the

On Thu, Apr 30, 2015 at 02:55:59PM +0200, Armin Schindler wrote: > we are using tinc 1.0.24 with 6 hosts (endpoints). > Quality of service is used with prio qdisc on all network > interfaces. This means depending on the TOS value of the IP header > IP-packets will get a priority queue on the network interface. > > Packets from TINC (UDP 655) maybe reordered using these queues

Hi! I have som problems with my vpn tunnel. I have 6 nodes in the network. Three of them is running tinc 1.1pre5 Three of them is running tinc 1.0.19 I also have vlan tagging between the nodes running tinc 1.1pre5 The problem is that get a bunch of errors in the log like the messages below (logs is attached in the email): Got late or replayed packet from JOTPOS ("internal ip" port

On Mon, May 18, 2015 at 12:08:53PM +0200, Armin Schindler wrote: > We didn't change that [ReplayWindow] setting, so the default is 16. > What exactly will happen if tinc gets a packet which should have arrived > 20 packtes before (because of the TOS prio queues)? With the default setting of 16, up to 128 packets can be arbitrarily reordered without problems. If a packet arrives that

Hello, I am a happy user of tinc in multiple environments. It is beautiful - thank you! Today I noticed that a network of around 20 nodes suffered from a flood of packages like the following: IP6 fe80::e4eb:74b6:57e0:c3e1 > ff02::2: ICMP6, router solicitation, length 8 For the first ten hours these nodes (even the usually completely idle ones) have seen incoming traffic of around 1 MBit/s

Guus, Below a segment of a log file. I am trying to analyse why the satellite link goes down and up all the time (sometimes 10 to 15 times an hour, sometimes not for a day. My guess is that this indicates packet loss on the satelllite link and tinc not really recovering from that. Where I inserted an empty line the log basically stopped and was silent for I guess for 14 minutes? Would setting

Hi Guus, Am Freitag, den 25.09.2015, 09:36 +0200 schrieb Guus Sliepen: > On Fri, Sep 25, 2015 at 08:41:06AM +0200, Marcus Schopen wrote: > > > I'm running some tinc clients behind a NAT (masquerading, Cisco Router) > > connecting to a host outside on a public IP in a different network. The > > tunnels get unstable every few minutes and I see packet loss when > >

--- doc/tinc.conf.5.in | 3 +++ src/linux/device.c | 7 +++++++ 2 files changed, 10 insertions(+), 0 deletions(-) diff --git a/doc/tinc.conf.5.in b/doc/tinc.conf.5.in index 2bfd5fe..01f7f81 100644 --- a/doc/tinc.conf.5.in +++ b/doc/tinc.conf.5.in @@ -255,6 +255,9 @@ a lookup if your DNS server is not responding. This does not affect resolving hostnames to IP addresses from the host

Hi, I'm running some tinc clients behind a NAT (masquerading, Cisco Router) connecting to a host outside on a public IP in a different network. The tunnels get unstable every few minutes and I see packet loss when pinging the clients on their internal tunnel IPs from the host side. Before putting the tinc clients behind the NAT they were running on public IPs too (clients and host in

Hello, response time: how is it possible to increase the response time on Tinc VPNs. When I use tinc over a fast or giga-bit network connection the ping-response time is normally about 1800 to 2000 ms. Sometimes I get ping response times at about 2.500 to 3.000 ms over a normal Ethernet Connection or a television-cable connection within the same providers-network in the same city. The ping-time

I'm stuck behind a corporate NAT that I obviously have absolutely no control over. The nice thing is that the firewall rules, AFAIK, are very nice. I've had tinc running before from behind nazi firewalls with no NAT. Been fiddling with tinc for many hours, but have been SOL. The local machine is the client (has ConnectTo in the conf), and remote is the server (has Listen in the conf).

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?

Hi, We've been running tinc for a while now but, have started hitting a bottleneck where the number of packets/sec able to be processed by our Tinc nodes is maxing out around 4,000 packets/sec. Right now, we are using the default cipher and digest settings (so, blowfish and sha1). I've been testing using aes-256-cbc for the cipher and seeing ~5% increases across the board. Each Tinc node

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

Hi: I'm having some trouble connecting to the tinc VPN I've setup for my client. Basically I would like to connect to the LAN of my client (as I'm currently thousands of miles away and won't be back for a month and a half) to continue with the development of an in-house ERP. I've setup the router (a Linksys router running the stock firmware) to forward both TCP and UDP

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