[Battlemesh] tinc.vpn: Already connected without actually being
gui at altermundi.net
Tue Jul 22 06:43:22 CEST 2014
On 17/07/14 20:05, cmsv wrote:
> Recently started to play with tinc and although there are quiet a few
> pages online with tinc setups none of them is quite well organized or
> complete. Also none is fully dedicated to openwrt.
> The plan:
> Simple/basic tinc vpn connectivity. No need to forward to the lan.
> daemon.notice tinc.vpn: tincd 1.0.21 (Feb 10 2014 23:44:53)
> starting, debug level 1
> daemon.info tinc.vpn: /dev/net/tun is a Linux tun/tap device (tun
> daemon.notice tinc.vpn: Listening on 0.0.0.0 port 655
> daemon.notice tinc.vpn: Ready
> daemon.info tinc.vpn: Already connected to router2
> And the setup is not even complete.
> Current setup
> # uci show tinc
*your own name* is router2.
so it's basically saying it is already connected to itself.
change the name to something else (probably you meant router1 there)
More information about the Battlemesh