[Battlemesh] tinc.vpn: Already connected without actually being

[Gui Iribarren]

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.
> 
> Problem:
> 
> daemon.notice tinc.vpn[1297]: tincd 1.0.21 (Feb 10 2014 23:44:53)
> starting, debug level 1
> daemon.info tinc.vpn[1297]: /dev/net/tun is a Linux tun/tap device (tun
> mode)
> daemon.notice tinc.vpn[1297]: Listening on 0.0.0.0 port 655
> daemon.notice tinc.vpn[1297]: Ready
> daemon.info tinc.vpn[1297]: Already connected to router2
> 
> And the setup is not even complete.
> 
> Current setup
> 
> # uci show tinc
> tinc.vpn=tinc-net
> tinc.vpn.enabled=1
> tinc.vpn.generate_keys=0
> tinc.vpn.key_size=2048
> tinc.vpn.AddressFamily=any
> tinc.vpn.DirectOnly=0
> tinc.vpn.Forwarding=internal
> tinc.vpn.Hostnames=0
> tinc.vpn.IffOneQueue=0
> tinc.vpn.Interface=tun
> tinc.vpn.Mode=router
> tinc.vpn.Name=router2

*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)

cheers!


>