search for: kusr2

1. Is there any tools/command, we can show the subnet where a certain tinc nodes learnt? So that I can know the weight for certain subnet(in real time), instead of go back to the node’s (who advertise the subnet) configuration file to check. 2. So far in order to change the weight of a subnet, or something else, I have to reset the tinc daemon( tincd -k -n myvpn and then tincd -n myvpn) in

...e ICMP > packets... :( (rp_filter settings) > > You can see it here : https://mellowd.co.uk/ccie/?p=5662 Ok... well that's just silly then. > > Can you check what tinc thinks the PMTU is in each of these cases? With > > tinc 1.0.24, you do "tincd -n <netname> -kUSR2", and it will send a list > > of nodes to the syslog. The MTU should be in it. > > For the 3 servers, Tinc reports 1459 as pmtu for each other. Ok. And for the client? > Something strange, why pmtu for the MYSELF host is 1518 ? Nowhere I have > network with MTU larger than...

SIGHUP (-kHUP) should reload that config for you and SIGURS2 (-kUSR2) will drop currently known subnets (etc) to syslog. This will not work on Windows. Both of these are in the tinc manual (http://tinc-vpn.org/documentation/tinc.pdf). From: tinc [mailto:tinc-bounces at tinc-vpn.org] On Behalf Of Bright Zhao Sent: Saturday, May 6, 2017 9:33 AM To: tinc at tinc-vpn....

A relatively recent update (1-2 months) has introduced a fairly major issue where connection issues seem to cause tinc to decide that there's another node of the same name on the VPN, leading to it quitting. It seems that it's detecting itself somehow, through an older connection, perhaps? The daemon stopping itself is a major problem, though, as it has to be manually restarted. I would

...where > its PMTU is 1462, upload is successful. > When the same client is accessing our network from another network where > its PMTU is 1500, upload requests fail. Can you check what tinc thinks the PMTU is in each of these cases? With tinc 1.0.24, you do "tincd -n <netname> -kUSR2", and it will send a list of nodes to the syslog. The MTU should be in it. > I know that situation is very particular, I don't know if I explain well > the facts... It would be good to see a diagram of the network path between the client and the backend server, which parts of the r...

A gentoo based server running running tinc for years serving some dozens clients has problems after upgradng from 1.0.7 to 1.0.8 using official gentoo ebuilds. The clienst are running linux and windows with different version of tinc. The clients still get a connect but sending data results in just no answer from the (updated) server side. The server log shows this for an example (IP changed):

Still experimenting with the automesh function. In the midst of that, I encountered a new problem. Of the 6 linux boxes in my tinc VPN, 3 were RedHat 9, 1 was Suse 9 Pro, 1 was Fedora Core 1, and one was RedHat 8.0. All was well. They were running a mix of the static binary and locally compiled-from-source binaries. I updated two of the RedHat 9 boxes to Fedora Core 1, about 3 days

Hello, I am experiencing system hangs when running NFSv4 over a tinc VPN. I don't know if the problem is with NFS or tinc and would appreciate any suggestions on how to narrow down the culprit. Unfortunately I cannot simply run NFS directly over TCP -- the participating systems are connected only over an open network. The configuration is as follows: I have a master server

Hi, I upgraded some of my Tinc nodes from 1.0.8 recently and found something strange. All of a sudden, the vpn would not work as a full-mesh. Certain nodes were not contactable. I re-generated my rsa-keys, and checked my configuration. My vpn uses the following in tinc.conf, as I am routing both ipv4 and v6. === name = node1 mode = switch AddressFamily = any PMTU = 1280 PMTUDiscovery = yes

Hi everyone , i have a few questions/problems with tinc , which i need to address ASAP , so i'll make it brief . i have 33 sites , connected with each other using wan , in each site , there are two linux firewalls + 3-4 more servers , i preferred to have a full mesh within my network , but unfortunately it was not possible , when i wanted every site to be connected to every other , as the