Tinc on MacOs X
Tincer
tincer at btconnect.com
Fri Nov 19 04:24:04 CET 2004
Upon startup of the logfile as shown below is produced, and indicates
some errors.
The aim is to connect from a laptop "BranchB" to the main office "BranchA",
The laptop (iBook G4) is running OsX 10.3.5,
Tun was installed from http://www-user.rhrk.uni-kl.de/~nissler/tuntap
My questions:
Shouldn't tinc-up exit with status 0?
Why is an "Invalid name for outgoing connection in
/usr/local/etc/tinc/OFFICES/tinc.conf line 2" reported?
Thanks
------------------
/usr/local/etc/tinc/OFFICES/tinc-up
#!/bin/sh
ifconfig en0 192.168.82.1 netmask 255.255.0.0
/usr/local/etc/tinc/OFFICES/tinc.conf
Name = BranchB
ConnectTo = BranchA
Device = /dev/tun0
PrivateKeyFile = /usr/local/etc/tinc/OFFICES/rsa_key.priv
/usr/local/etc/tinc/OFFICES/hosts/BranchA
Subnet = 192.168.81.0/16
Address = 111.222.111.7
TCPOnly = yes
-----BEGIN RSA PUBLIC KEY-----
........
-----END RSA PUBLIC KEY-----
LogFile
1100829148 tinc.OFFICES[366]: tincd 1.0.1 (08/14/03 18:39:17)
starting, debug level 5
1100829148 tinc.OFFICES[366]: /dev/tun0 is a MacOS/X tun device
1100829148 tinc.OFFICES[366]: Executing script tinc-up
1100829148 tinc.OFFICES[366]: Script tinc-up exited with non-zero status 126
1100829148 tinc.OFFICES[366]: Listening on :: port 655
1100829148 tinc.OFFICES[366]: Listening on 0.0.0.0 port 655
1100829148 tinc.OFFICES[366]: Ready
1100829148 tinc.OFFICES[366]: Invalid name for outgoing connection in
/usr/local/etc/tinc/OFFICES/tinc.conf line 2
1100829245 tinc.OFFICES[366]: Got TERM signal
1100829245 tinc.OFFICES[366]: Closing connection with BranchB (MYSELF)
1100829245 tinc.OFFICES[366]: Statistics for MacOS/X tun device /dev/tun0:
1100829245 tinc.OFFICES[366]: total bytes in: 0
1100829245 tinc.OFFICES[366]: total bytes out: 0
1100829245 tinc.OFFICES[366]: Terminating
$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::20a:95ff:feb9:16f4 prefixlen 64 scopeid 0x4
inet 111.222.111.3 netmask 0xffffffc0 broadcast 111.222.111.255
ether 00:0a:95:b8:16:f4
media: autoselect (100baseTX <full-duplex>) status: active
supported media: none autoselect 10baseT/UTP <half-duplex>
10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback>
100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX
<full-duplex,hw-loopback>
en1: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether 00:0a:95:f8:5d:f5
media: autoselect (<unknown type>) status: inactive
supported media: autoselect
fw0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:0a:95:ff:fe:b8:16:f4
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
tun0: flags=851<UP,POINTOPOINT,RUNNING,SIMPLEX> mtu 1500
open (pid 394)
tun1: flags=851<UP,POINTOPOINT,RUNNING,SIMPLEX> mtu 1500
closed
More information about the tinc
mailing list