search for: pmtu_discovery

Displaying 5 results from an estimated 5 matches for "pmtu_discovery".

2015 May 13
2
tinc 1.1 never seems to accept UDP packets from 1.0.24 hosts
...nd the remote side to trigger UDP path probing, and no blocking firewall on the way) # tinc info T: (tinc 1.0.24, directly connected) Node: T Node ID: 97e7a2ff259b Address: 1.2.3.4 port 4200 Online since: 2015-05-13 22:38:45 Status: validkey visited reachable Options: pmtu_discovery clamp_mss Protocol: 17.0 Reachability: directly with TCP # tinc info V: (tinc 1.0.24, no direct connect) Node: V Node ID: 80a618663578 Address: 2.3.4.5 port 20316 Online since: 2015-05-13 22:38:45 Status: validkey visited reachable Options: pmtu_discovery clamp_mss...
2013 Dec 17
1
Speed issue in only one direction
Hi all, I'm back again with my speed issues. The past issues where dependant of network I used. Now I run my tests in a lab, with 2 configurations linked by a Gigabit switch : node1: Intel Core i5-2400 with Debian 7.2 node2: Intel Core i5-3570 with Debian 7.2 Both have AES and PCLMULQDQ announced in /proc/cpuinfo. I use Tinc 1.1 from Git. When I run an iperf test from node2 (client) to
2016 Nov 17
1
Windows tinc network no data despite tinc connection
...ed for IP 10.42.100.2, subnet 255.255.0.0. Pulling tinc info client on the server gives the following: Node: client Node ID: xxx928356yyy Address: public IP university network port 655 Online since: 2016-11-17 13:04:03 Status: validkey visited reachable sptps Options: pmtu_discovery clamp_mss Protocol: 17.7 Reachability: directly with TCP Edges: serverwin Subnets: Pulling tinc info serverwin on the client gives the following: Node: serverwin Node ID: xxx168af2859yyy Address: public IP company network port 655 Online since: 2016-11-17 13:04:03 Sta...
2014 Feb 25
3
PMTU = 1518 over local network at 1500 MTU
...! So nodes can ping each other but larger data does not go. test1=sllm1 test2=sllm2 test1:/usr/src/tinc# tinc -n coppint info sllm2 Node: sllm2 Address: 192.168.0.202 port 655 Online since: 2014-02-25 13:36:39 Status: validkey visited reachable sptps udp_confirmed Options: pmtu_discovery clamp_mss Protocol: 17.3 Reachability: directly with UDP PMTU: 1518 Edges: host1 host3 host4 host6 sllm1 Subnets: 1a:26:ce:e3:fb:13 6e:de:af:13:55:bf root at test2:~# tinc -n coppint info sllm1 Node: sllm1 Address: 192.168.0.200 port 655 Online since: 2014-02-...
2013 Dec 15
1
graphviz
Hi, I propose that the "ad-hoc connections" (localdiscovery) are also displayed in the graph (graphdumpfile) as it is useful for debugging. I find the command-line tooling a bit cumbersome to find out where the problem is - maybe a web-interface can be added to tincd? Implementing a http server is trivial I found out. Folkert van Heusden -- Curious about the inner workings of your