similar to: can't connect to clients using hostnames

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?

On Tue, Oct 27, 2015 at 02:08:36PM +0100, Guus Sliepen wrote: > > I wonder why tinc tries to resolve host names before connection even > > with configured (socks5) proxy which fails behind restrictive firewalls. > > [...] I'll try to change tinc so it will allow connections via SOCKS5 > even if it cannot resolve the hostname itself. I added the ability for tinc to

Beste tinc-developer, Ik moet van mijn baas een aantal VPN's aanleggen en ben nu thuis bezig om te testen. Ik heb 2 computers in een thuisnetwerkje (totaal 6 computers) geinstalleerd met SuSe 7.3, daar de klanten dit ook hebben. De computers zijn verbonden met een switch. Dit is de inhoud van mijn bestanden: Op computer 1 genaamd suse met ip 192.168.0.99 netmask 255.255.255.0

Here is some examples of using templates for TINC configurations and settings: In your startup script, BEFORE starting TINC VPN, put a number of entries to configure your VPN: sh ./templatewriter.sh LAN LOSI101 8540 255.255.255.0 0.0.0.0 10.99.0.11 10.98.0.11 ConnectTo=LOSI102 ConnectTo= ConnectTo= **PUT MORE ENTRIES HERE FOR MORE COMPLEX VPN setups ######Templatewriter.sh #!/bin/bash

Hi, I'am using a script which manages the setup of nodes. This depends on zeroconf and so the tinc node name and the hostname must match. But tinc doesn't allow dashes in node names. Is this really is necessary? Dashes in hostnames are not really uncommon. Is there something which prevents appling such a diff?: ----- start diff ----- diff -ruNp tinc-1.0.13/src/protocol.c

I am using tinc to connect together VPCs in AWS across multiple regions and accounts to provide secure communication. For the most part, it works great. A few times, I have seen issues where something got into an unstable state that didn't seem to resolve itself. Shutting down tinc on all hosts and restarting seemed to do the trick, but I'd like to see if there is something that I can

Hello list, I wonder why tinc tries to resolve host names before connection even with configured (socks5) proxy which fails behind restrictive firewalls. Is there any "workaround"? Thanks in advance! Regards Uwe -------------- n?chster Teil -------------- Ein Dateianhang mit HTML-Daten wurde abgetrennt... URL:

hallo, today I have updated the first node of our tinc clout (33 tinc nodes currently) to 1.0.12 - all the others still use 1.0.10 or 1.0.11. It seems the whole tinc link to already activated connections pauses when there is a name resolution or authentication timeout. Feb 5 14:44:29 fwhh tinc.chaos[16262]: Already connected to royksopp Feb 5 14:45:00 fwhh tinc.chaos[16262]: Error while

On 11 April 2018 at 11:30, Hans de Groot <hansg at dandy.nl> wrote: > Hello again :) > > Thank you all for your reply's. Below are the config files of the 3 hosts. > I use tinc in router mode. I do not have a kernel mode config lines > anywhere so tinc must be using the default settings here. > > I added the ipaddressx to subnets on hostc and this works. Traffic

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

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

With pleasure we announce the release of tinc version 1.1pre12. Here is a summary of the changes: * Added a "--syslog" option to force logging to syslog even if running in the foreground. * Fixes and improvements to the DecrementTTL function. * Improved PMTU discovery and UDP keepalive probes. * More efficient relaying of UDP packets through intermediate nodes. * Improved

With pleasure we announce the release of tinc version 1.1pre12. Here is a summary of the changes: * Added a "--syslog" option to force logging to syslog even if running in the foreground. * Fixes and improvements to the DecrementTTL function. * Improved PMTU discovery and UDP keepalive probes. * More efficient relaying of UDP packets through intermediate nodes. * Improved

Hi, I?m fighting with a silly problem: my syslog tells me tinc cannot route a packet. I can use a telnet or the good ol ping, it is the same effect. When I?m pinging from the laptop (172.16.11.2) the network address (172.16.11.0) or any address numerically lower than the laptops address, the packet gets routed, otherwise not. And when I ping the network address, I get the reply twice, as to be

Hello all, I am new to this and I hope this is an easy question. I would like to use tinc to set up a connection from my home to my office. I am running windows 7 on both PCs. The home PC have internet connection via time warner & the office PC via AT&T DSL. My goal is to be able to share a folder on the home PC with the office PC to keep data in one place. I know I can set up port

Hello Guus, thanks for Your fast reply. Does it mean only socks is affected and http proxy should work? If this is the case then this may be a temp. solution. Thanks and regards! Uwe Am 27.10.2015 14:08:36, schrieb Guus Sliepen: > On Tue, Oct 27, 2015 at 12:33:35PM +0000, Uwe Werler wrote: > > > I wonder why tinc tries to resolve host names before connection even > > with

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

Hi, We are trying to set up tinc for playing lan games over the internet. The three of us are running tinc, can ping each other and browse shared folders. yes, windows :| However we cannot connect because we don't show up in the game lobby. The games usually require udp ports to be open, but I think these are all open once we establish the tinc tunnel. Also, testing with all computers in

Hi, I've set up Tinc in switch-mode on the three nodes "gw", "rb493g" and "v900w", but the nodes "rb493g" and "w900v" do not connect to each other. On each node port 655 is opened with TCP and UDP. "gw": static IPv4- and IPv6 address listed in the hosts-file "gw" hosts-files: "gw",

Currently, the tinc application which is part of tinc 1.1 does not support the ability to handle `Name = $HOST` lines in tinc.conf. This set of patches refactors get_name in order to be able to support this configuration option in the tinc binary. After having read through the codebase, it seems like we could really do for a heavy refactoring as there is a lot of poorly coupled and duplicated