Tinc on OsX, slowly getting there....

[Guus Sliepen]

On Wed, Nov 24, 2004 at 07:01:29PM +0000, Tincer wrote:

> I am unclear which routing can be provided by tinc and which routing 
> would I have to add manually.

Using the tinc-up script (or some other way), you have to tell the
kernel that everything for the VPN goes to the VPN interface. After that
tinc takes over, and routes packets to the other daemon(s) based on the
Subnets in the host config files.

> tinc-up
> #!/bin/sh
> ifconfig tun0 192.168.2.1 192.168.0.0 netmask 255.255.0.0
> 
> 
> tinc-up.pl
> #!/usr/bin/perl
> system "ifconfig tun0 192.168.2.2 192.168.0.0 netmask 255.255.0.0";
> system "route add 192.168.0.0/16  192.168.2.2";
> 
> 
> Logfile
> 
> 1101320682 tinc.OFFICES[452]: tincd 1.0.3 (Nov 11 2004 05:07:05) 
> starting, debug level 2
> 1101320682 tinc.OFFICES[452]: /dev/tun0 is a Generic BSD tun device
> 1101320682 tinc.OFFICES[452]: Executing script tinc-up
> 1101320682 tinc.OFFICES[452]: Script tinc-up exited with non-zero status 126
[...]
> -------------------------------------
> Specific questions:
> 
> - The tinc-up script does not do anything, and the log shows.
> "Script tinc-up exited with non-zero status 126"
> Thus I am running my Perl tinc-up.pl script. I assume this is a valid 
> substitution for tinc-up.

tinc always starts the file named "tinc-up", without any extensions. So
it will never run a file named "tinc-up.pl". The reason that it doesn't
run tinc-up properly is either because you forgot to make the script
executable or (but this would be really strange) /bin/sh does not exist.

>  Which local routing is tincd actually providing by default?

None.

> Which routing is tinc actually providing on Branch B after
> route add 192.168.0.0/16  192.168.2.2

The route command is part of MacOS/X, not of tinc. Read the manpage of
the route command for the details.

> I know that I have to provide a further IP address for BranchB to 
> connect to the local net, e.g. 192.168.2.1
> I have tried several methods but didn't get interface plus routing to 
> this address.
> Thus
> can 192.168.2.1 be on the same en0 interface as 10.20.30.1
> 
> Which routes would I have to add so that BranchB serves the local 
> 192.168.2.x net?

I don't know MacOS/X well enough to answer that.

-- 
Met vriendelijke groet / with kind regards,
    Guus Sliepen <guus at sliepen.eu.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20041124/90db656d/attachment.pgp