search for: pinginterv

...s" [1] to the host's config file and since then all tunnels > > seem to work stable again, but I can't explain this to me as the NAT > > should handle UDP connections. Any ideas? > > 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 = 30" on each client behind the NAT. The tunnels from the host side were still unstable u...

...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 LAN latencies. Actual result: - I'm experiencing packet loss every (PingInterval) seconds. Each packet loss "episode" lasts roughly 1 second and during that time all packets are lost. Apparently it happens each time the nodes are exchanging PMTU probes. Packet loss correlates with "Sending/Got MTU probe" messages. It also materializes in the form of &q...

...as something on the local side needs to sent traffic to the office side, the local Tinc node sends new outbound UDP packets, the router re-establishes the virtual session between the two nodes, and all traffic resumes passing normally (at least until the next period of inactivity). I see that the PingInterval setting allows me to set a minimum inactivity period on the metadata connection, and that seems to be enough to prevent the TCP session from timing out in the router... but I haven't found any way cause Tinc to ensure the data/UDP "session" also stays active. (I'm currently usi...

....1.0.0/16 owner home 10.2.0.0/16 owner node1 10.3.0.0/16 owner node2 10.4.0.0/16 owner node3 10.5.0.0/16 owner node4 # cat /etc/tinc/home/tinc-up ifconfig $INTERFACE 10.2.0.10 netmask 255.0.0.0 ifconfig $INTERFACE up # cat tinc.conf Name = node1 ConnectTo = home Mode = router AddressFamily = ipv4 PingInterval = 600 PingTimeout = 15 4 out of 5 nodes work just fine. Node 2 however has issues. It does work fine for 5-30m and then pauses my connection to it. It's still up. I can't ping it over the "pause time" with 0% packet loss. Any TCP connection over the link just pauses for a while...

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

...uot;. > > It wouldn't be called something like that, rather a "nat translation > timeout" or something similar. Shame on me. Deep in the configuration of the NAT I found that UDP timeout is set to 30 seconds by default. I increased the value to 120 seconds. And disabled the PingIntervall completely on the clients behind the NAT. Tunnels got unstable again. Then I put "PingIntervall = 30" to the client's config back again (before it was set to 10 seconds) and this seems to works. > > So should I keep this UDP configuration or would you go back to > > TC...

...command in tinc-up so the work node is aware of the other tinc network. This seems to work much better with the new router. I'm guessing the constant flow and overhead (arps and such) of TAP is helping to keep the sonicwall device from dropping/closing the connection. I tried playing with PingInterval and lowered it to 30 seconds while previously using tun so the work node might stay better connected. I didn't see any better results, maybe even lower is necessary. If I were to try to use tun again, would this be the route to go? lowering the ping time? It seems like the connection nee...

...ral Node (10.0.0.1) configurations: ============================================================================== --------------------------------------- tinc.conf --------------------------------------- Name=central Mode=router AddressFamily=any BindToInterface=eth0 MaxTimeout=333 KeyExpire=888 PingInterval=88 PingTimeout=4 #Forwarding=kernel TunnelServer=yes --------------------------------------- hosts/central --------------------------------------- Compression=10 PMTUDiscovery=yes Subnet=10.0.0.0/28 Subnet=0.0.0.0/0#10 ===========================================================================...

...ata socket read error" thread, Gus suggested that it may be caused by the router in front of the server that ran out of memory keeping track of the outgoing connections. The server is indeed behind a NAT router. It's a reasonably (ASUS) high end consumer grade router. We have tried adding PingInterval in the host configuration file, but it doesn't seem to resolve the problem. Is there anything else that we can do to stop the vpn from crashing. As it is, when any one of the client is logged to be flushing, the whole vpn becomes unusable. -------------- next part -------------- An HTML attac...

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 = 30" on each client > behind the NAT. The tunnels from the host s...

"PrivateKeyFile" as this is default, otherwise configuration is quite minimal. ======= Configuration ========= Server Side =========== # cat tinc.conf Name = fsvpns3f30 Mode = switch Device = /dev/net/tun AddressFamily = ipv4 PingInterval = 30 PrivateKeyFile = /etc/tinc/fsvpn/rsa_key.priv # cat tinc-up #!/bin/sh ifconfig $INTERFACE 10.10.100.30 netmask 255.255.0.0 # cat hosts/fsvpns3f30 Address = xyz.dyndns.org Port=655 Compression=9 Subnet=10.10.0.0/16 TCPonly=yes -----BEGIN RSA PUBLIC KEY----- ... -----END RSA PUBLIC KEY-----...

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

...ip route? I do have a subnet 0.0.0.0 at hostb so that is probably why traffic goes out via hostb when I do not have the specific subnet/ip at hostc Regards Hans de Groot configs at hosta tinc.conf Name = hosta Device =/dev/net/tun Hostnames = No connectto = hostb Mode = Router KeyExpire = 3600 PingInterval = 10 PingTimeout = 15 PrivateKeyFile = /etc/tinc/tincnet/rsa_key.priv ProcessPriority = high PMTUDiscovery = yes tinc-up #!/bin/bash ifconfig $INTERFACE 192.168.230.21 netmask 255.255.255.0 route add -net 192.168.230.0 netmask 255.255.255.0 gw 192.168.230.1 ip route add default via 192.168.230.1...

...onfiguration ? Home (OpenWrt Router) > > > >Tinc.conf > >name=Home > >Interface=tinc0 > >PrivateKeyFile=/etc/tinc/Home/rsa_key.priv > >Mode=router > >KeyExpire=3600 > >AddressFamily=ipv4 > >ProcessPriority=normal > >PingTimeOut=5 > >PingInterval=60 > > > >Tinc-up > >ifconfig $INTERFACE 10.0.0.1 netmask 255.255.255.0 > >route add -net 192.168.2.0 netmask 255.255.255.0 dev tinc0 > >route add -net 192.168.3.0 netmask 255.255.255.0 dev tinc0 > > > >home/hosts/Home > >Address=Home > >Sub...

...ia the tinc tunnel. My tinc.conf: ------------ Name=server AddressFamily=ipv4 Device=/dev/net/tun PrivateKeyFile=/etc/tinc/fvhglobalnet/rsa_key.priv GraphDumpFile=|/usr/bin/dot -Tpng -o /var/www/htdocs.keetweej.vanheusden.com/stats/tinc-fvh-network-graph.png Mode=switch KeyExpire=299 MACExpire=301 PingInterval=59 PingTimeout=6 My tinc-up is: ------------- #! /bin/sh /sbin/ifconfig $INTERFACE 172.16.0.1 netmask 255.240.0.0 /sbin/ifconfig $INTERFACE add 2001:888:13b3::1/64 /sbin/sysctl -w net.ipv6.conf.all.forwarding=1 /etc/rc2.d/S50radvd restart And my /etc/radvd.conf is: ------------------------- in...

...rt Router) b. Company ? TINC:10.0.0.2/32, LAN:192.168.2.1/32 (Windows 7 PC) TINC Configuration ? Home (OpenWrt Router) Tinc.conf name=Home Interface=tinc0 PrivateKeyFile=/etc/tinc/Home/rsa_key.priv Mode=router KeyExpire=3600 AddressFamily=ipv4 ProcessPriority=normal PingTimeOut=5 PingInterval=60 Tinc-up ifconfig $INTERFACE 10.0.0.1 netmask 255.255.255.0 route add -net 192.168.2.0 netmask 255.255.255.0 dev tinc0 route add -net 192.168.3.0 netmask 255.255.255.0 dev tinc0 home/hosts/Home Address=Home Subnet=10.0.0.1/32 Subnet=192.168.1.0/24 -----BEGIN RSA PUBLIC KEY----...

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

...ides better support for that use case: https://github.com/gsliepen/tinc/pull/166 > Regards > > Hans de Groot > > > configs at hosta > tinc.conf > Name = hosta > Device =/dev/net/tun > Hostnames = No > connectto = hostb > Mode = Router > KeyExpire = 3600 > PingInterval = 10 > PingTimeout = 15 > PrivateKeyFile = /etc/tinc/tincnet/rsa_key.priv > ProcessPriority = high > PMTUDiscovery = yes > > tinc-up > #!/bin/bash > ifconfig $INTERFACE 192.168.230.21 netmask 255.255.255.0 > route add -net 192.168.230.0 netmask 255.255.255.0 gw 192.168....

And, I ran a constant ping from the tinc client’s IP to the tinc server’s IP, it shows, the pings are all successfully back and forth, no any packet loss during the connection drop happens, so will this help to exclude any NAT/firewall cause the connection drop? And as you saw from the earlier screen shot, when it happens, it drop all tinc connections, and those connections are for different

...d > "TCPOnly = yes" [1] to the host's config file and since then all tunnels > seem to work stable again, but I can't explain this to me as the NAT > should handle UDP connections. Any ideas? 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. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 8...