On 10/23/2013 01:06 PM, Guus Sliepen wrote: > > That's correct, those files are generated by running: > > autoreconf -fsi > > Afterwards, just run ./configure and make as usual. See also the README.git > file. > >
Thank you, it's OK. But... with Tinc 1.1 (git), I have a big MTU problem... Tinc does not seem to handle packets of 1500 bytes... ping -s 1400 is OK ping -s 1500 is not OK. with 1.0.23, both were OK. 1469 bytes packet is OK, 1470 is not. Same parameters (defaults, except addresses of hosts). In logs, it does not seem to get errors but I can see that : Oct 23 15:46:15 host2 tinc.tincnetwork[8999]: Got MTU probe request 1518 from host1 (192.168.0.71 port 655) Oct 23 15:46:15 host2 tinc.tincnetwork[8999]: Got MTU probe request 1518 from host1 (192.168.0.71 port 655) Oct 23 15:46:15 host2 tinc.tincnetwork[8999]: Got MTU probe request 1518 from host1 (192.168.0.71 port 655) Oct 23 15:46:16 host2 tinc.tincnetwork[8999]: Sending MTU probe length 1518 to host1 (192.168.0.71 port 655) Oct 23 15:46:16 host2 tinc.tincnetwork[8999]: Sending MTU probe length 1518 to host1 (192.168.0.71 port 655) Oct 23 15:46:16 host2 tinc.tincnetwork[8999]: Sending MTU probe length 1518 to host1 (192.168.0.71 port 655) Oct 23 15:46:16 host2 tinc.tincnetwork[8999]: Got type 2 MTU probe reply 1518 from host1 (192.168.0.71 port 655) Oct 23 15:46:16 host2 tinc.tincnetwork[8999]: Got type 2 MTU probe reply 1518 from host1 (192.168.0.71 port 655) Oct 23 15:46:16 host2 tinc.tincnetwork[8999]: Got type 2 MTU probe reply 1518 from host1 (192.168.0.71 port 655) Oct 23 15:46:16 host2 tinc.tincnetwork[8999]: host1 (192.168.0.71 port 655) RTT 0.18 ms, burst bandwidth 476.235 Mbit/s, rx packet loss 100.00 % Interfaces are all MTU 1500... _______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
