Tons of "Failed to decrypt and verify packet"

[Lance Fredrickson]

Yes, this was my problem. All my nodes including my single windows node
were all running 1.1pre10. In this scenario my windows node would not
connect to any linux nodes.

When reverting all linux nodes and the windows node back to 1.1pre9, then
there is no issue, all while using the  identical config files.
-Lance
On Mar 9, 2014 10:06 AM, "hshh" <hunreal at gmail.com> wrote:

> The problem is, windows node is not compatible with linux/unix node with
> 1.1pre10 ( all nodes is running same version, 1.1pre10).
>
>
> On Sun, Mar 9, 2014 at 11:13 PM, Guus Sliepen <guus at tinc-vpn.org> wrote:
>
>> On Wed, Mar 05, 2014 at 03:05:11PM -0700, Lance Fredrickson wrote:
>>
>> > Yes, for me too. That's what I've reverted to using. 1.1pre10 is
>> > where Windows builds don't want to play with the rest of the Linux
>> > mesh.
>>
>> 1.1pre9 is not compatible with 1.1pre10. If you are mixing the two
>> versions,
>> you will indeed get failed to decrypt errors.
>>
>> The new protocol might still change until the release of 1.1.0. If you
>> still
>> want to use 1.1preX, but if for some reason it is not possible to upgrade
>> all
>> nodes at the same time, I suggest that you set "ExperimentalProtocol =
>> no" in
>> the tinc.conf of all those nodes. I'm sorry for the inconvenience.
>>
>> --
>> Met vriendelijke groet / with kind regards,
>>      Guus Sliepen <guus at tinc-vpn.org>
>>
>> _______________________________________________
>> tinc mailing list
>> tinc at tinc-vpn.org
>> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>>
>>
>
>
> --
> @hshh
>
> _______________________________________________
> 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/20140309/ca88a055/attachment.html>