Zerotierone: 1.6.0 bug roundup

Created on 24 Nov 2020  路  11Comments  路  Source: zerotier/ZeroTierOne

NEEDS TRIAGE

Most helpful comment

Personally I don't mind performance issues. I'm cut out of my remote nodes as ZT is unusable after update. No network adapters on Windows 10 and segmentation faults on Ubuntu.
It would be a disastrous update for me if not a backup Wireguard tunnel left in case of problems like these.

All 11 comments

There are many mysterious performance and routing misbehavior in this release.
Linux is mostly ok but it trashes Windows nodes network performance.
Suricata IPS goes nuts with these release too.

Personally I don't mind performance issues. I'm cut out of my remote nodes as ZT is unusable after update. No network adapters on Windows 10 and segmentation faults on Ubuntu.
It would be a disastrous update for me if not a backup Wireguard tunnel left in case of problems like these.

To end this disaster, I've done the following on all of my Linux/Debian nodes:
sudo apt install zerotier-one=1.4.6
sudo apt-mark hold zerotier-one

On windows, I had to look around hard for the older 1.4.6 installer.
(link removed. Not from https://download.zerotier.com)

On windows, I had to look around hard for the older 1.4.6 installer.
(link removed. Not from https://download.zerotier.com)

Here you go. https://download.zerotier.com/RELEASES/1.4.6/dist/ZeroTier%20One.msi

Linux binaries for 1.6.1 are now out.

Mac pkg can be found here: http://download.zerotier.com/RELEASES/1.6.1/dist/ZeroTier%20One.pkg

Still tracking down a Windows issue that doesn't seem to be related to 1.6.0 as it can be reproduced in 1.4.6 as well where after a certain number of joins/network adapter creations, Windows no longer recognizes the code signature of the driver as valid. Upon reboot, Windows loads the driver just fine for a while, and then goes back to not recognizing the code signature again.

Still tracking down a Windows issue that doesn't seem to be related to 1.6.0 as it can be reproduced in 1.4.6 as well where after a certain number of joins/network adapter creations, Windows no longer recognizes the code signature of the driver as valid. Upon reboot, Windows loads the driver just fine for a while, and then goes back to not recognizing the code signature again.

Thanks. Is there any temporary fix for that?

Thanks. Is there any temporary fix for that?

Rebooting when it happens is the only workaround we have at the moment.

1.6.1 is now out. Should fix windows, mac & linux issues.

Seems great! However every time a disconnect and reconnect a network, it shows up this:
image
And the network number keeps increasing.

Is that normal?

Yes. There's an issue open about it somewhere around here.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

AlexisTM picture AlexisTM  路  4Comments

Fastidious picture Fastidious  路  5Comments

bstin picture bstin  路  3Comments

kbumsik picture kbumsik  路  4Comments

coretemp picture coretemp  路  3Comments