17
edits
Changes
→Tinc problems
Using the default venet0:0 interface on the container, tinc seems to have problems as it complains the port 655 is already used on 0.0.0.0.
Netstat shows that the port 655 is available:
<pre>
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 4831020 /var/run/uml-utilities/uml_switch.ctl
</pre>
Starting the Tincd daemon:
<pre>
root@132 / [4]# tincd -n mondialvpn
root@132 / [5]# tail -f /var/log/syslog
Jul 26 14:57:42 132 -- MARK --
Jul 26 15:08:01 132 /USR/SBIN/CRON[15178]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jul 26 15:11:23 132 tinc.mondialvpnmyvpn[15139]: Got TERM signalJul 26 15:11:23 132 tinc.mondialvpnmyvpn[15139]: TerminatingJul 26 15:11:37 132 tinc.mondialvpnmyvpn[15191]: tincd 1.0.8 (Aug 14 2007 13:51:23) starting, debug level 0Jul 26 15:11:37 132 tinc.mondialvpnmyvpn[15191]: /dev/net/tun is a Linux tun/tap device (tun mode)Jul 26 15:11:37 132 tinc.mondialvpnmyvpn[15191]: Can't bind to 0.0.0.0 port 655/tcp: Address already in useJul 26 15:11:37 132 tinc.mondialvpnmyvpn[15191]: Ready
^C
root@132 / [6]#
