config help & pid file not existing issue
Lars Kruse
lists at sumpfralle.de
Tue May 7 01:11:38 CEST 2019
Hallo David,
Am Mon, 6 May 2019 16:43:28 +0800
schrieb David Penn <px920906 at gmail.com>:
> *tinc.conf
> Name = envy13
> Device = /dev/net/tun
I think, you do not need to specify "Device".
(I never did)
> ConnectTo = main
>
> *hosts/main
> Address = <my vps ext ip address>
> Port = 655
> Subnet = 10.0.0.1/32
>
> *hosts/envy13
> Port = 655
> Subnet = 10.0.0.2/32
>
> *tinc-up
> #!/bin/sh
> ip link set myvpn up
> ip addr add 10.0.0.2/32 dev myvpn
> ip route add 10.0.0.0/24 via 10.0.0.2
I understand the above as "route the subnet through myself".
This is not what you want, or?
I guess, the following lines would be sufficient?
ip link set myvpn up
ip addr add 10.0.0.2/24 dev myvpn
> I have ufw allowed 655. What did i miss?
You can always verify the active connections by sending USR1:
tincd -n myvpn --kill=USR1
Afterwards you can take a look at your daemon log (e.g. /var/log/daemon.log).
There you will find the list of currently connected peers.
Cheers,
Lars
More information about the tinc
mailing list