tinc - Jan 2010 - need an example with 2 different nets

Hi, thanks.
Sorry for the mess with my gmail account...

This made the route go away. But is this the right way to configure tinc?
To give the tinc interface an IP (with 255.255.255.255 subnetmask) from the
local (green)
network it does route the traffic to?

Does it make sense to give the tinc interface an 192.168.0.253 IP, when the
net here is 192.168.0.0/24 on eth1

I can not find such a sample, that clarifies where to use which net/ip.
In your documentation on
http://www.tinc-vpn.org/documentation/tinc_4.html#How-connections-work
why is there not route in tinc-up for "Branch A". This doc says
nothing
about routes anyway...

--
Hinnack




2010/1/19 Guus Sliepen <guus at tinc-vpn.org>
> On Tue, Jan 19, 2010 at 04:59:41PM +0100, Hinnack wrote:
>
> >> 2010/1/19 <tinc-owner at tinc-vpn.org>
> >>
> >>   You are not allowed to post to this mailing list, and your
message has
> >>   been automatically rejected.  If you think that your messages
are
> >>   being rejected in error, contact the mailing list owner at
> >>   tinc-owner at tinc-vpn.org.
> >
> > Why?
> > I did subscribe an got already a welcome message...
>
> I see you subscribed using "henrik.genssen at gmail.com" as your
email
> address,
> but you're now using "henrik.genssen at googlemail.com" to
send mail. The
> mailing
> list doesn't know gmail.com and googlemail.com is the same.
>
> > I have a routing problem resulting from my tinc config.
> > The tunnel itself works fine!
> > I have the following nets:
> > 10.9.8.0/24 on the one side
> > 192.168.0.0/24 on the other
> [...]
> > in tinc-up:
> > /sbin/ifconfig $INTERFACE 192.168.0.253 netmask 255.255.255.0
> > /sbin/ip route add 10.9.8.0/24 via 192.168.0.253
> > and my problem looks like this:
> > route shows this:
> > 192.168.0.0     *               255.255.255.0   U     0      0       
0
> eth1
> > 192.168.0.0     *               255.255.255.0   U     0      0       
0
> tinc-mf
> > 10.9.8.0        192.168.0.253   255.255.255.0   UG    0      0       
0
> tinc-mf
> > 1.2.3.0   *               255.255.252.0   U     0      0        0 eth0
> > default         0.0.0.0         UG    0      0        0 eth0
> > (the problem is, there are 2 routes for 192.168.0.0)
> > what am I doing wrong?
>
> You should change the ifconfig netmask in tinc-up to 255.255.255.255. On
> the
> other side you probably have to do the same.
>
> --
> Met vriendelijke groet / with kind regards,
>     Guus Sliepen <guus at tinc-vpn.org>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAktV3bwACgkQAxLow12M2nvLqwCePZOmog7er3Jm0y+g2X8ElOHW
> 08sAoIoo6ILO+4VF8UfMdbNvJfytKxDE
> =JNP/
> -----END PGP SIGNATURE-----
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20100119/5059f776/attachment.htm>

On Tue, Jan 19, 2010 at 07:49:21PM +0100, Hinnack wrote:
>> You should change the ifconfig netmask in tinc-up to 255.255.255.255.
> 
> This made the route go away. But is this the right way to configure tinc?
> To give the tinc interface an IP (with 255.255.255.255 subnetmask) from the
> local (green) network it does route the traffic to?
Yes.
> Does it make sense to give the tinc interface an 192.168.0.253 IP, when the
> net here is 192.168.0.0/24 on eth1
Sure. It would be even better to give the tinc interface the same IP address as
eth1.  Interfaces can share the same addresses and subnets, that is not a
problem at all. What ultimately matters is the routing table, as it decides
which packets go where.
> I can not find such a sample, that clarifies where to use which net/ip.
> In your documentation
> on http://www.tinc-vpn.org/documentation/tinc_4.html#How-connections-work
> why is there not route in tinc-up for "Branch A". This doc says
nothing
> about routes anyway...
There is no route command in tinc-up, since ifconfig with a netmask other than
255.255.255.255 will ensure a route is added automatically. The documentation
does briefly mention adding routes in section 7.2, but please understand that I
do not want to document all possible interface/route/firewall configurations in
tinc's manual.

-- 
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/20100119/ad5e85ef/attachment.pgp>