3 ms·

> We also expose simple controls for managing egress firewall rules. Unless user-tracking telemetry is blocked, in which case, apparently your CLI tools stop w

> We also expose simple controls for managing egress firewall rules. Unless user-tracking telemetry is blocked, in which case, apparently your CLI tools stop working? https://news.ycombinator.com/item?id=31542047 https://news.ycombinator.com/item?id=31542047 Edit: dunno if that comment was deleted because the author was wrong about their PiHole blocking telemetry causing commands to fail, if they were harassed into deleting it, or what. I guess I'll give you the benefit of the doubt that there was something else going on with their network that caused commands to fail, but you're still getting side-eye for engaging in telemetry/usage tracking.

SadTrombone 4y ago
The post you're linking to seems to have been deleted.
xanaxagoras 4y ago
Hi, I deleted that post because it had something in it I didn't want forever recorded on the internet. Nobody harassed me and I wasn't wrong. One of my pihole blocklists includes telemetry.* which matches some network call made by the command you run to update the Firezone config. Pihole returns "0.0.0.0" for hostnames it blocks and the error that's raised ends up coming form openssl. Later I discovered there are 2 options at the bottom of the /etc/firezone/firezone.rb config file, commented out, that allow you to disable the telemetry. With these options turned on the error no longer occurs.
jamilbk 4y ago
We don't actively block any functionality when a user blocks telemetry -- that's definitely an unintended side effect and bug. You'll have more luck disabling telemetry in the config file with `default['firezone']['telemetry']['enabled'] = false` documented here: https://docs.firezone.dev/docs/reference/configuration-file/ https://docs.firezone.dev/docs/reference/configuration-file/ We could definitely clarify how to disable telemetry better and we should make sure nothing breaks when telemetry is blackholed instead of disabled. I've opened https://github.com/firezone/firezone/pull/658 https://github.com/firezone/firezone/pull/658 to get these addressed.

SadTrombone 4y ago

The post you're linking to seems to have been deleted.

xanaxagoras 4y ago

Hi, I deleted that post because it had something in it I didn't want forever recorded on the internet. Nobody harassed me and I wasn't wrong. One of my pihole blocklists includes telemetry.* which matches some network call made by the command you run to update the Firezone config. Pihole returns "0.0.0.0" for hostnames it blocks and the error that's raised ends up coming form openssl. Later I discovered there are 2 options at the bottom of the /etc/firezone/firezone.rb config file, commented out, that allow you to disable the telemetry. With these options turned on the error no longer occurs.

jamilbk 4y ago

We don't actively block any functionality when a user blocks telemetry -- that's definitely an unintended side effect and bug. You'll have more luck disabling telemetry in the config file with `default['firezone']['telemetry']['enabled'] = false` documented here: https://docs.firezone.dev/docs/reference/configuration-file/ https://docs.firezone.dev/docs/reference/configuration-file/ We could definitely clarify how to disable telemetry better and we should make sure nothing breaks when telemetry is blackholed instead of disabled. I've opened https://github.com/firezone/firezone/pull/658 https://github.com/firezone/firezone/pull/658 to get these addressed.