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----- I also installed the tinc-up script, which adds the dialinserver interface to the bridge. 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. After that I get a lot of: $ Read packet of 60 bytes from Linux tun/tap device (tap mode) $ Learned new MAC address 0:80:87:34:5a:68 $ Broadcasting packet of 60 bytes from dialinserver (MYSELF) $ ... This looks good to me. Now the client side. This is the tinc.conf there: Name=mezzubook ConnectTo = dialinserver Device = /dev/net/tun My hosts file: -----BEGIN RSA PUBLIC KEY----- ... -----END RSA PUBLIC KEY----- the tinc-up script looks like that: #!/bin/sh ifconfig $INTERFACE 192.168.139.55 netmask 255.255.255.0 (in the future this should be changed to DHCP I guess) I did not install a bridge or anything there. Just a modprobe tun. That's all. When I start tincd there I get this: tincd -n dialin -d5 -D tincd 1.0.8 (Nov 2 2007 17:40:21) starting, debug level 5 /dev/net/tun is a Linux tun/tap device (tun mode) Executing script tinc-up Listening on :: port 655 Can't bind to 0.0.0.0 port 655/tcp: Address already in use Ready Trying to connect to dialinserver (192.168.139.49 port 655) 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 Writing packet of 102 bytes to Linux tun/tap device (tun mode) Here I'm lost again. Why can't it route to 192.168.139.49. Is it because I'm using the same subnet for vpn and normal network at the moment? My routes looks like that, when tincd is up: 192.168.139.0 0.0.0.0 255.255.255.0 U 0 0 0 dialin 192.168.139.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 192.168.139.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0 0.0.0.0 192.168.139.11 0.0.0.0 UG 0 0 0 eth0 Thanks again for helping out! Matthias _______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
