Simple Dial In Setup

[Guus Sliepen]

On Thu, Nov 19, 2009 at 01:53:32PM +0100, Matthias Redl wrote:

> OK, thanks for your help Donald! On the "server" it seems to work (at
> least partially.
> 
> the tinc.conf is:
> 
> Name=dialinserver
> Mode=switch
> Device = /dev/net/tun
> 
> my host file:
> Address=192.168.139.49 (will be changed to the external ip as soon as it
> works)
> Subnet=192.168.139.0/24
> -----BEGIN RSA PUBLIC KEY-----
> ...
> -----END RSA PUBLIC KEY-----
> 
> 
> Server starting up:
> $ tincd 1.0.8 (Nov  4 2007 09:57:13) starting, debug level 5
> $ /dev/net/tun is a Linux tun/tap device (tap mode)
> $ Executing script tinc-up
> $ Listening on 0.0.0.0 port 655
> $ Can't bind to :: port 655/tcp: Address already in use
> 
> What I don't understand here is only the last row. Why can't it bind?
> There is no other tincd running.

This is harmless (caused by Linux binding IPv6 sockets to IPv4 as well). Newer
versions of tinc will not show that message anymore, since they will tell Linux
not to bind one socket to both protocols.

> Now the client side. This is the tinc.conf there:
> 
> Name=mezzubook
> ConnectTo = dialinserver
> Device = /dev/net/tun

You have to add Mode = switch here as well, otherwise:

> Read packet of 74 bytes from Linux tun/tap device (tun mode)
> Cannot route packet from mezzubook (MYSELF): unknown IPv4 destination
> address 192.168.139.49

It thinks it has to route packets, but it doesn't know any IPv4 Subnets.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20091120/5a8b7554/attachment.pgp>