tinc Digest, Vol 89, Issue 10

Fri Mar 16 13:36:48 CET 2012

i need forwarding off , cause i need a central node , which is connected
directly to all the network , directly , so it can usually upload content
directly , without slowing down other nodes in the network , i also don't
want it to act as a forwarder , since ,it only has 2mbps of bandwidth , and
i don't want it for that purpose ,
is there any other way to fix this problem ?

On 16 March 2012 14:30, <tinc-request at tinc-vpn.org> wrote:

> Send tinc mailing list submissions to
>        tinc at tinc-vpn.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
> or, via email, send a message with subject or body 'help' to
>        tinc-request at tinc-vpn.org
>
> You can reach the person managing the list at
>        tinc-owner at tinc-vpn.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of tinc digest..."
>
> Today's Topics:
>
>   1. random problems with Forwarding=off (Siavash Sameni)
>   2. Re: random problems with Forwarding=off (Guus Sliepen)
>
>
> ---------- Forwarded message ----------
> From: Siavash Sameni <siavash.sameni at gmail.com>
> To: tinc at tinc-vpn.org
> Cc:
> Date: Fri, 16 Mar 2012 13:51:56 +0330
> Subject: random problems with Forwarding=off
> Hi ,
> I've added one node to my tinc mesh , with forwarding off , and the
> network got splitted into several pieces !!,
> the thing is that , the node with forwarding off is connected to all hosts
> , directly with connect to ,
> and seems like that for some nodes the shortest path , that the tinc
> network can find is through the node with forwarding off ,
> here are the results of my first ping to all my hosts with the host with
> forwarding off present :
>  ./monitorhosts
> Host : 10.0.113.3 is down (ping failed) at Fri Mar 16 13:36:57  2012
> Host : 10.0.128.3 is down (ping failed) at Fri Mar 16 13:37:43  2012
> Host : 10.0.130.3 is down (ping failed) at Fri Mar 16 13:37:59  2012
> Host : 10.0.132.3 is down (ping failed) at Fri Mar 16 13:38:05  2012
> Host : 10.0.138.3 is down (ping failed) at Fri Mar 16 13:38:34  2012
> Host : 10.0.141.3 is down (ping failed) at Fri Mar 16 13:38:43  2012
>
> if i switch off the node with forwarding=off , the result is as follows :
> ./monitorhosts
> Host : 10.0.113.3 is down (ping failed) at Fri Mar 16 13:39:28  2012
> which is flawless (don't mind 113) ,
> when i reconnect the node with forwarding=off , the result changes to the
> following :
> ./monitorhosts
> Host : 10.0.113.3 is down (ping failed) at Fri Mar 16 13:44:49  2012
> Host : 10.0.141.3 is down (ping failed) at Fri Mar 16 13:46:06  2012
> . :D
> when i try to ping 10.0.114.3 i receive the following :
> ping 10.0.141.3
> PING 10.0.141.3 (10.0.141.3) 56(84) bytes of data.
> From 10.0.141.3 icmp_seq=1 Destination Net Prohibited
> From 10.0.141.3 icmp_seq=2 Destination Net Prohibited
> .
> the tinc version is 1.0.16 , running on centos 5.
> if anymore information needed i'd be happy to help ,
> also i should mention that , i have no problem reaching the nodes from the
> node with forwarding off .
> i have around 64 nodes in my tinc mesh ,
> i remember our previous admin told me that , when he made full mesh ,
> (connectto to everwhere) , the network became unstable , is there a limit ?
> should we experience slowdowns or something as the nodes grow ?
> thank you.
>
>
>
>
> ---------- Forwarded message ----------
> From: Guus Sliepen <guus at tinc-vpn.org>
> To: tinc at tinc-vpn.org
> Cc:
> Date: Fri, 16 Mar 2012 11:44:13 +0100
> Subject: Re: random problems with Forwarding=off
> On Fri, Mar 16, 2012 at 01:51:56PM +0330, Siavash Sameni wrote:
>
> > I've added one node to my tinc mesh , with forwarding off , and the
> network
> > got splitted into several pieces !!,
> > the thing is that , the node with forwarding off is connected to all
> hosts
> > , directly with connect to ,
> > and seems like that for some nodes the shortest path , that the tinc
> > network can find is through the node with forwarding off ,
>
> That is correct. And indeed with Forwarding = off, those packets are
> dropped,
> that is exactly what this option is meant to do. Why do you want to use
> Forwarding = off?
>
> > i have around 64 nodes in my tinc mesh ,
> > i remember our previous admin told me that , when he made full mesh ,
> > (connectto to everwhere) , the network became unstable
>
> 64 nodes is not an unusual number for tinc. In what way does the network
> become
> unstable?
>
> > is there a limit ?
>
> There is no limit in tinc itself, but if you have slow network connections
> it
> can take a while for tinc to exchange metadata between nodes. If it takes
> too
> long, it might close connections. You can try to increase the value of
> PingTimeout in that case.
>
> > should we experience slowdowns or something as the nodes grow ?
>
> It should not be noticably slower, but if you have a lot of nodes joining
> and
> leaving all the time it might.
>
> --
> Met vriendelijke groet / with kind regards,
>     Guus Sliepen <guus at tinc-vpn.org>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAk9jGX0ACgkQAxLow12M2nuP0gCfWpssVCMghqIKjDWeO/oLNKI6
> TLcAnR9BIsQDX5DUOZQakfUhdJF4lGVt
> =nfT+
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20120316/9c843346/attachment.html>