<html><head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"><meta http-equiv="X-UA-Compatible" content="IE=11"><style></style></head><body style="font: 10pt/normal Segoe UI; font-size-adjust: none; font-stretch: normal;"><div class="GroupWiseMessageBody" id="GroupWiseSection_1528798293000_robert@gainplus.asia_0AE2278002F000008C53A30038005B00_"><div>Hi Thanks</div><div><br></div><div>removing the first line "ip tuntap add dev $INTERFACE mode tun" seems to have helped regarding the tun error, however it is not connecting. If I stop the tinc service and then run:</div><div><br></div><div><a href="mailto:root@web3">root@web3</a>:~# tincd -n gainplus -d -D<br>tincd 1.0.33 starting, debug level 1<br>/dev/net/tun is a Linux tun/tap device (tun mode)<br>Listening on 10.130.69.123 port 655<br>Ready<br>Trying to connect to db1 (10.130.39.180 port 655)<br>Timeout from db1 (10.130.39.180 port 655) during authentication<br>Could not set up a meta connection to db1<br>Trying to re-establish outgoing connection in 5 seconds<br>Trying to connect to db1 (10.130.39.180 port 655)<br>^\Got QUIT signal<br>Statistics for Linux tun/tap device (tun mode) /dev/net/tun:<br> total bytes in: 0<br> total bytes out: 0<br>Closing connection with db1 (10.130.39.180 port 655)<br>Closing connection with web3 (MYSELF)<br></div><div><br></div><div>db1 firewall is OK (existing tinc traffic connecting and PF rule for this server in place) and I wonder whether the message </div><div>Timeout from db1 (10.130.39.180 port 655) during authentication</div><div>indicates a connection failing authentication</div><div><br></div><div>Both 18.04 servers indicating same problem</div><div><br></div><div>thanks<br></div><div><br></div><div><br></div>
<meta name="Generator" content="Novell Groupwise Client (Version 14.2.2 Build: 126868)">
<span style="margin-bottom: 5px; display: block;"><br></span>
<meta name="Generator" content="Novell Groupwise Client (Version 14.2.2 Build: 126868)">
<div><br></div><div class="GroupWiseMessageBody" id="GroupWiseSection_1528681404000_robert@gainplus.asia_0AE2278002F000008C53A30038005B00_"><span class="GroupwiseReplyHeader">>>> "Robert Horgan" <robert@nsasia.co.th> 11-Jun-18 8:43 AM >>><br></span><div>I currently am using tinc 1.0.33 on a 4 node Ubuntu 14.04 server network at Digital Ocean connecting on the Eth1 private network interfaces. This works great.</div><div><br></div><div>Recently I added two more Ubuntu 18.04 servers at the same location and attempted to link them to the Tinc mesh already established. The 18.04 servers do not allow me to use the net-tools ipconfig command and so I have adapted my tinc-up commands to use iproute2 commands.</div><div><br></div><div>#!/bin/sh<br># tinc-up<br>ip tuntap add dev $INTERFACE mode tun<br>ip addr add 10.0.0.3/24 dev $INTERFACE<br>ip link set dev $INTERFACE up</div><div><br></div><div>However, when I run this command I get the error <br>Error: either "name" is duplicate, or "tun" is a garbage.<br>Command line is not complete. Try option "help"<br>Cannot find device "up"</div><div><br></div><div>I have tried variations of the commands in the tinc-up file, but cannot get a result without errors.</div><div><br></div><div>my /etc/tinc/vpn/tinc.conf file:<br>Name = web3<br>AddressFamily = ipv4<br>BindToAddress = 10.132.115.166 (changed)<br>Interface = tun0<br>ConnectTo = db1</div><div><br></div><div>systemctl status tinc:<br>tinc.service - Tinc VPN<br> Loaded: loaded (/lib/systemd/system/tinc.service; enabled; vendor preset: enabled</div><div><br></div><div>Question, when using iproute2 on ubuntu 18.04 should I use a different configuration for tinc-up?<br><br><br></div></div></div></body></html>