similar to: 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 > >

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

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 >

On Fri, Sep 25, 2015 at 04:51:22PM +0200, Marcus Schopen wrote: > > Maybe the timeout for UDP NAT mappings is a bit short on your Cisco. Try > > adding PingInterval = 30 to the tinc.conf on those clients, perhaps that > > will help. > > Thanks for pushing me into the right direction. I disabled "TCPOnly = > yes" on the host and started with "PingInterval

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

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 > pinging the clients on their internal tunnel IPs from the host side. > Before putting the tinc

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 > AddressFamily = ipv4 > Interface = tun0 > ConnectTo = host > PingInterval = 30 > LocalDiscovery =

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 to be open on the clients to get "LocalDiscovery = yes" working? I don't see any blocked

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

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).

I have some tinc nodes behind a nat router. Which ipaddress should i use in de host file for the tinc nodes behind a nat router. The internet ipaddress or the private ipaddress ? Perry

Hi there, I am using tinc since some monthes. I think the basic idea of extending vpn to a mesh of systems via tun/tap is great. And I think it is one of the useable developments compared to the much more complex vpn solutions I had used in the past. Great work. Setting up tinc I have fought with the configuration (and with the concepts) for a while as I have found no example that covers my

Hi, I had some performance problems with TINC running on Windows XP. I had a VPN tunnel running over a wireless network to a Linux VPN server. Web browsing through the tunnel was a pain. Big web pages with lots of pictures loaded very slow compared to a plain network connection. When the VPN client was running on a Linux computer, and a Windows computer was browsing the web through the VPN

Hi, I have a tinc tunnel up and running. I connected 2 hosts with a net behind. Host A with static ip 1.2.3.4 with 192.168.1.0/24 Host B with dhcp connection with 192.168.2.0/24 the whole net is 192.168.0.0/16 I can reach at any time any host behind A from a host behind B. But I can reach a host behind B only, if traffic (keep alive like ping) from B goes continousliy from B to A. I am running

I'm running Tinc on a Linux machine inside my home network, connecting through a NATing router to a Tinc server out on the Internet. I've noticed that fairly frequently the SSH sessions I leave open (but unused) get aborted with a "Connection reset by peer" message. When I investigated closely, I found that after a period of inactivity my router times out the UDP

Recently the small business I work at replaced an aging linksys wrt style router with a SonicWall one. Ever since this change I have issues with this node falling back to TCP constantly. TCP for me ends up performing very sub-par, and most of the time unworkable. For some reason too the connection usually ends up being routed through another node. I created a new tinc instance using TAP

Hi! Me and two friends are trying to get a VPN working, but we cant get routing between two tunnels. This is how it looks, all servers (192.168.*.1) are running IP Masquerade to enable the other computers behind them to access the internet. Both elayne and glenn are connecting to melc, and the tunnel between melc and glenn are running TCPOnly because that glenn doesnt have a public IP (it's

Hey, Tinc developers! I'm not sure if anyone else has brought this up, but we've got a rather good reason for using TCP, even though UDP will actually form a working connection. Anyone on Comcast's "small business" service is forced to use an SMC cable modem/router. Its NAT implementation is capable of letting tinc's UDP tunnels work fine, but they limit a single UDP

Hi, I have successfully setup a tinc vpn between two machines, which is great, and now need do the same to a machine behind a firewall (I do not control the firewall, alas). The firewall will allow port 80 out (via an http proxy), so I wish to use GNU http-tunnel (or similar) to tunnel through the firewall. I have also successfully used http-tunnel to tunnel a simple ppp over ssh connection.

Hello, I am experiencing some weird problems in a setup with tinc where communication between the 'server' and the 'clients' occur over 3g connections. Let me describe briefly the setup: - The server, on a public IP, runs tinc 1.0.8, in router mode, and the whole setup uses one VPN network. All client's VPN addresses are on the same subnet, and each client has a seperate