Zerotier failing to start after upgrade
-
@fuznutz04 Looks like the answer is in the details.
Either you can allow
nmap_low_allowed
or you can allow it anyways with 2 or you can report it as a bug.setsebool -P mmap_low_allowed 1
or
-
ausearch -c 'zerotier-one' --raw | audit2allow -M my-zerotierone
semodule -X 300 -i my-zerotierone.pp
-
Report it as a bug.
-
@DustinB3403 said in Zerotier failing to start after upgrade:
semodule -X 300 -i my-zerotierone.pp
Thanks Dustin. That did the trick!
-
no zerotier adapter on my laptop this is bad juju
-
This is definitely a bad deal. Anyone know if it has been reported to ZeroTier?
All better, but only on my laptop. All the remote systems with SELinux are going to be under the same problem.
-
Just confirmed. This also affects CentOS 7.
-
@JaredBusch said in Zerotier failing to start after upgrade:
Anyone know if it has been reported to ZeroTier?
Not sure, it was 1 of the 3 recommendations I made to @fuznutz04
-
Do an update. We released new binary builds for Linux that should address this.
-
@adam-ierymenko said in Zerotier failing to start after upgrade:
Do an update. We released new binary builds for Linux that should address this.
Yep, its working.
-
@adam-ierymenko said in Zerotier failing to start after upgrade:
Do an update. We released new binary builds for Linux that should address this.
Awesome
-
@adam-ierymenko said in Zerotier failing to start after upgrade:
Do an update. We released new binary builds for Linux that should address this.
Awesome, Thanks!
-
@adam-ierymenko said in Zerotier failing to start after upgrade:
Do an update. We released new binary builds for Linux that should address this.
Awesome, except all of my stuff alreadfy updated and is offline.
So I'm stuck for up to 24 hours until dnf-automatic rolls again. -
can the mac version be updated via
zerotier-cli
at all? -
@adam-ierymenko said in Zerotier failing to start after upgrade:
Do an update. We released new binary builds for Linux that should address this.
Sorry for resurrecting an old thread, but new installs are having the same selinux issue. Took some digging for me to figure out what was going on. Multiple attempts to install on Fedora 33.