tinc - May 2017 - What's the weight means in the dump of edge info from USR2?

Thank you, that is very helpful. And actually I do have a few further questions
regarding this:

1. This weight is not the one specified in Subnet, this should be something
related to the host, where can I manually configure this?

2. The weight value is ONLY take round trip latency as the measurement, or
including CPU power and other factors into consideration?

3. I don't know how this Weight named, but let's say it Path-weight; So
in 1.1, tinc will first evaluate Subnet-weight, and if certain route have the
same Subnet-weight, they will compare the Path-weight for deciding which path to
forward(if direct not possible, and same hops to the destination)?

4. When will 1.1 been released as official version?

Sent from iPhone
> 在 2017年5月11日，上午2:02，Guus Sliepen <guus at tinc-vpn.org> 写道：
> 
>> On Wed, May 10, 2017 at 03:41:46PM +0800, Bright Zhao wrote:
>> 
>> abc to def at x.x.x.x port 655 options d weight 540
>> 
>> How’s the 540 weight been calculated? What does it mean? How can I
leverage this weight?
> 
> Unless you specify it manually (by using the Weight configuration
> option), tinc will use the time it takes to make a connection to a peer
> as the weight. So peers with a higher latency, lower bandwidth and/or
> lower CPU power will get a higher weight.
> 
> Weight is used for creating a minimum spanning tree for forwarding
> broadcast packets. With tinc 1.1, weight is also used to decide which
> node to forward packets to if direct communication with the destination
> node is not possible, if there is a tie between multiple paths with the
> same minimum number of hops.
> 
>> The d of after options mean direct?
> 
> d here means that PMTU discovery and MSS clamping is enabled.
> 
> -- 
> Met vriendelijke groet / with kind regards,
>     Guus Sliepen <guus at tinc-vpn.org>
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc

On Thu, May 11, 2017 at 08:03:02AM +0800, Bright Zhao wrote:
> 1. This weight is not the one specified in Subnet, this should be something
related to the host, where can I manually configure this?
Either in tinc.conf, then it applies to all connections made, or in
individual host config files, then it applies only to connections with
that host.
> 2. The weight value is ONLY take round trip latency as the measurement, or
including CPU power and other factors into consideration?
It takes into account the total time for doing the authentication
between two peers. That is not just latency, but also how fast the nodes
can do cryptography.
> 3. I don't know how this Weight named, but let's say it
Path-weight; So in 1.1, tinc will first evaluate Subnet-weight, and if certain
route have the same Subnet-weight, they will compare the Path-weight for
deciding which path to forward(if direct not possible, and same hops to the
destination)?
Tinc separately determines the final destination of a packet, and how to
route to that final destination. Subnet-weight is used for the former,
and path-weight for the latter.
> 4. When will 1.1 been released as official version?
I'm afraid my past predicitions have been meaningless, so I can't answer
this.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20170511/167f6860/attachment.sig>

> On 11 May 2017, at 1:46 PM, Guus Sliepen <guus at tinc-vpn.org>
wrote:
> 
> On Thu, May 11, 2017 at 08:03:02AM +0800, Bright Zhao wrote:
> 
>> 1. This weight is not the one specified in Subnet, this should be
something related to the host, where can I manually configure this?
> 
> Either in tinc.conf, then it applies to all connections made, or in
> individual host config files, then it applies only to connections with
> that host.
I checked tinc 1.1 documentation, I couldn’t find any weight configuration in
Main configuration(tinc.conf), instead, I found weight in the hosts
configuration, is this the one you referred to which apply to all connections?
looks not likely
> 
>> 2. The weight value is ONLY take round trip latency as the measurement,
or including CPU power and other factors into consideration?
> 
> It takes into account the total time for doing the authentication
> between two peers. That is not just latency, but also how fast the nodes
> can do cryptography.
> 
>> 3. I don't know how this Weight named, but let's say it
Path-weight; So in 1.1, tinc will first evaluate Subnet-weight, and if certain
route have the same Subnet-weight, they will compare the Path-weight for
deciding which path to forward(if direct not possible, and same hops to the
destination)?
> 
> Tinc separately determines the final destination of a packet, and how to
> route to that final destination. Subnet-weight is used for the former,
> and path-weight for the latter.
> 
>> 4. When will 1.1 been released as official version?
> 
> I'm afraid my past predicitions have been meaningless, so I can't
answer
> this.
No worries, I should bring the context of 1.0 earlier to avoid this
misunderstanding, but i’m interested for the new features you introduced to me,
i may get onto 1.1 quite soon.

> 
> -- 
> Met vriendelijke groet / with kind regards,
>     Guus Sliepen <guus at tinc-vpn.org>
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc