Displaying 20 results from an estimated 7000 matches similar to: "two tinc hosts behind same NAT"
2014 Dec 05
0
two tinc hosts behind same NAT
Hi Eric,
Which version are you using? I have similar issues with the newest 1.1pre10.
Did you check out the ?LocalDiscovery? option?
For 1.1, you also can get more information about the actual connection mode by using the ?info [node]? command.
Cheers,
Steffen
> Am 05.12.2014 um 12:26 schrieb Eric Feliksik <feliksik at gmail.com>:
>
> Dear all,
>
> I have 3 nodes: A, B
2015 Sep 25
2
Tinc clients behind a NAT, tunnels get unstable
Hi Guus,
Am Freitag, den 25.09.2015, 17:04 +0200 schrieb Guus Sliepen:
> Ok, that means by default the UDP NAT timeout on the Cisco is extremely
> short.
>
> > I check the manual of the the Cisco NAT for any TCP/UDP
> > timeout settings, but there is no way to modify anything like "keeps
> > TCP/UDP connections alive".
>
> It wouldn't be called
2015 Sep 26
2
Tinc clients behind a NAT, tunnels get unstable
Am Freitag, den 25.09.2015, 22:45 +0200 schrieb Marcus Schopen:
> Hi Guus,
>
> Am Freitag, den 25.09.2015, 17:46 +0200 schrieb Marcus Schopen:
> > Hmmm ... I've tried "LocalDiscovery = yes"
> > in /etc/tinc/mytunnel/tinc.conf already, but that didn't help. Config on
> > client A is:
> >
> > ---------------
> > Name = clienta
>
2015 Sep 25
2
Tinc clients behind a NAT, tunnels get unstable
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
> >
2014 Dec 27
6
[Announcement] Tinc version 1.1pre11 released
With pleasure we announce the release of tinc version 1.1pre11. Here is
a summary of the changes:
* Added a "network" command to list or switch networks.
* Switched to Ed25519 keys and the ChaCha-Poly1305 cipher for the new
protocol.
* AutoConnect is now a boolean option, when enabled tinc always tries
to keep at least three meta-connections open.
* The new protocol now
2014 Dec 27
6
[Announcement] Tinc version 1.1pre11 released
With pleasure we announce the release of tinc version 1.1pre11. Here is
a summary of the changes:
* Added a "network" command to list or switch networks.
* Switched to Ed25519 keys and the ChaCha-Poly1305 cipher for the new
protocol.
* AutoConnect is now a boolean option, when enabled tinc always tries
to keep at least three meta-connections open.
* The new protocol now
2015 Sep 26
1
Tinc clients behind a NAT, tunnels get unstable
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
2013 Nov 10
2
Not seeing any more LocalDiscovery broadcasts
Hi,
I am playing with LocalDiscovery again and have noticed that I do not
see any LocalDiscovery broadcasts anymore.
I am using tinc 1.1-pre9 in switch mode and have set LocalDiscovery =
yes in tinc.conf. I do not see any broadcasts on any network and I also
do not see anything in the debug output.
What to do?
-nik
--
# apt-assassinate --help
Usage: apt-assassinate [upstream|maintainer]
2017 Feb 14
4
LocalDiscovery flip flopping and network design tips
We are testing tinc inside Google Compute within a single region and an
external region. Two boxes are created as follows:
/etc/tinc/test/tinc_test_1
Subnet = 10.240.0.0/16
Subnet = 10.240.0.4/32
Address = 104.154.59.151
/etc/tinc/test/tinc_test_2
Subnet = 10.240.0.0/16
Subnet = 10.240.0.5/32
Address = 104.197.132.141
/etc/tinc/test/tinc.conf
Name = $HOST
AddressFamily = ipv4
Interface = tun0
2013 Apr 04
2
LocalDiscovery detecting nodes through tunnel
Hi,
I have tried the LocalDiscovery feature of tinc.
The problem is that it also sends broadcast probes out the CPN interface
*and* detects nodes on the VPN. A connection is then established through
the tunnel, which effectively breaks connectivity between the two nodes.
I do not think that discovering hosts on the VPN makes sense in any way.
How can it be disabled?
I could easily netfilter
2016 Sep 01
1
LocalDiscovery
Hello tinc users!
Has anyone been able to get LocalDiscovery to work properly?
I'm not quite sure what I need to do other than enable it in tinc.conf, and
it doesnt seem to be working.
Has anyone else tried it?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20160901/5698fc86/attachment.html>
2013 Jul 15
1
Packet loss with LocalDiscovery
Hi,
I believe I have found a bug with regard to the LocalDiscovery feature.
This is on tinc-1.1pre7 between two Windows nodes.
Steps to reproduce:
- Get two nodes talking using LocalDiscovery (e.g. put them on the same
LAN behind a NAT with no metaconnection to each other)
- Make one ping the other.
Expected result:
- The two nodes should ping each other without any packet loss,
hopefully at
2008 Jul 06
3
Routing and keying Questions
Hello!
I use tincd to interconnect 3 LANs: A, B and C. So long, it works fine:
everybody reaches everybody. But I want a different behavior: A and B should
be allowed to talk, as should B and C. I tried to simply delete the
host-files on the nodes that should not be allowed to talk to eachother:
A has a hostfile from B
B has a hostfile from A and C
C has a hostfile from B
But this is no
2012 Dec 06
1
LAN discovery issue
Hi there,
Following situation:
3 nodes, Alpha (Home fileserver), Beta (regular PC), Gamma (Notebook).
All three in a NATed LAN usually, though the notebook also gets
carried around and connects from the outside from time to time. Tinc
should help me keep my other 2 PCs reachable from Gamma, even when I'm
not at home. Also I plan on maybe adding more nodes to that in the
future.
I have set
2013 Mar 03
2
[Announcement] Tinc version 1.0.20 released
With pleasure we announce the release of tinc version 1.0.20. Here is a
summary of the changes:
* Use /dev/tap0 by default on FreeBSD and NetBSD when using switch mode.
* Minor improvements and clarifications in the documentation.
* Allow tinc to be cross-compiled with Android's NDK.
* The discovered PMTU is now also applied to VLAN tagged traffic.
* The LocalDiscovery option now
2013 Mar 03
2
[Announcement] Tinc version 1.0.20 released
With pleasure we announce the release of tinc version 1.0.20. Here is a
summary of the changes:
* Use /dev/tap0 by default on FreeBSD and NetBSD when using switch mode.
* Minor improvements and clarifications in the documentation.
* Allow tinc to be cross-compiled with Android's NDK.
* The discovered PMTU is now also applied to VLAN tagged traffic.
* The LocalDiscovery option now
2018 Jan 05
3
Using keyring on tinc
Hi all!
Is there any way to make tinc use keys from a keyring or similar?
I'm trying to find a way to manage multiple server, making it easier to
register a new user to the network.
Thanks!
--
Martin Iñaki Malerba
inakimmalerba at gmail.com
inaki at satellogic.com
2015 Oct 09
1
LocalDiscovery starts to work after ping
Hi,
I'm using LocalDiscovery = yes to let tinc clients connect directly
behind a NAT. Problem is that clients only start to talk directly after
pinging each client from each client. Is there way to force direct
connection after starting the tunnel.
Ciao!
2018 Apr 30
1
Slow Speed
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
2017 May 22
6
Advertising a Public IP address
Hi all
I feel like I should know the answer to this question, like I read it
someplace sometime, but it evades me right now.
It's also an opportunity to say hello to the list and many thanks for
writing and supporting tinc vpn! We make great use of it at rhizomatica.
So,
Let's take this example setup.
I have two tinc nodes (A and B) behind a firewall
NodeA and NodeB have 192.168.1.2