Second VPN network fails to start

[Robert Horgan]

Hi Parke,

Thanks, no I had not run those commands, but after doing so, my VPN
address is not visible.  See below:

nsasia at db2:/etc/tinc$ sudo systemctl  enable  tinc at VPN1
Created symlink
/etc/systemd/system/tinc.service.wants/tinc at VPN1.service → /lib/								
systemd/system/tinc at .service.
nsasia at db2:/etc/tinc$ systemctl  start  tinc at VPN1
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to start 'tinc at VPN1.service'.
Authenticating as: NETsolutions (nsasia)
Password:
==== AUTHENTICATION COMPLETE ===
nsasia at db2:/etc/tinc$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group defaul								
t qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
	   valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP grou								
p default qlen 1000
    link/ether 42:dd:fe:41:26:2e brd ff:ff:ff:ff:ff:ff
    inet 206.189.47.8/20 brd 206.189.47.255 scope global eth0
	   valid_lft forever preferred_lft forever
    inet 10.15.0.10/16 brd 10.15.255.255 scope global eth0
	   valid_lft forever preferred_lft forever
    inet6 fe80::40dd:feff:fe41:262e/64 scope link
	   valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP grou								
p default qlen 1000
    link/ether a2:3e:cb:fb:50:cd brd ff:ff:ff:ff:ff:ff
    inet 10.130.17.192/16 brd 10.130.255.255 scope global eth1
	   valid_lft forever preferred_lft forever
    inet6 fe80::a03e:cbff:fefb:50cd/64 scope link
	   valid_lft forever preferred_lft forever
4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc
fq_codel state								
 UNKNOWN group default qlen 500
    link/none
    inet 10.0.0.51/24 scope global tun0
	   valid_lft forever preferred_lft forever
nsasia at db2:/etc/tinc$ sudo systemctl  enable  tinc
Synchronizing state of tinc.service with SysV service script with
/lib/systemd/s								
ystemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable tinc
nsasia at db2:/etc/tinc$ systemctl  start  tinc
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to start 'tinc.service'.
Authenticating as: NETsolutions (nsasia)
Password:
==== AUTHENTICATION COMPLETE ===
nsasia at db2:/etc/tinc$ ip r
default via 206.189.32.1 dev eth0 proto static
10.0.0.0/24 dev tun0 proto kernel scope link src 10.0.0.51
10.15.0.0/16 dev eth0 proto kernel scope link src 10.15.0.10
10.130.0.0/16 dev eth1 proto kernel scope link src 10.130.17.192
206.189.32.0/20 dev eth0 proto kernel scope link src 206.189.47

A restart after that does not change things.  I am expecting an
interface 10.1.0.0/24 on tun0.

regards
Robert

>>> Parke <parke.nexus at gmail.com> 16-May-19 3:00 AM >>>
On Wed, May 15, 2019 at 5:32 AM Robert Horgan <robert at gainplus.asia>
wrote:
> On the other side its pretty much the same.  However on a restart,
VPN1 does not initiate and no tunnel is created.  It is not  a firewall
issue as no connection is attempted (and firewall exceptions are in
place).  It just wont start the second instance!

Did you try:

systemctl  enable  tinc at VPN1
systemctl  start  tinc at VPN1

And additionally:

systemctl  enable  tinc
systemctl  start  tinc

-Parke

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20190516/f39fc018/attachment.html>