Hi Guys,

would anyone have an answer on this?
Thanks and appreciated.

I think this would need to be set on all client configurations. I'm not sure if the controller alone would handle it, or what happens if you didn't configure the controller in this way at all and had all clients configured with it. I don't see that documented, as they focus on "a device"...
 
I don't know if this helps or not. That setting is set in the local.conf file of the zerotier docker container. It may not yet be settable by the API or zerotier-cli, so ztnet may not be able to change it. In my case, that zerotier configuration is stored in the docker volume ztnet_zerotier. Use docker volume ls to see a list in your case.

In the docker-compose file for ztnet, the zerotier container has the environment variable ZT_OVERRIDE_LOCAL_CONF set to true. By looking at the zyclonite/zerotier container it seems that if this is the case it creates one and overwrites your local one. If this flag is false, and no local.conf exists, one will be created also. So if you were going to manually create or alter this you probably want to unset that ZT_OVERRIDE_LOCAL_CONF and be sure to include the equivalent to what is autocreated:

{
    "settings": {
        "primaryPort": ${ZT_PRIMARY_PORT:-$DEFAULT_PRIMARY_PORT},
        "portMappingEnabled": ${ZT_PORT_MAPPING_ENABLED:-$DEFAULT_PORT_MAPPING_ENABLED},
        "softwareUpdate": "disable",
        "allowManagementFrom": [${MANAGEMENT_NETWORKS}],
        "allowTcpFallbackRelay": ${ZT_ALLOW_TCP_FALLBACK_RELAY:-$DEFAULT_ALLOW_TCP_FALLBACK_RELAY}
    }
}

The local.conf file would be in the docker volume "zerotier". I also see one under networks.d/{networkid}.local.conf, so I'm not sure which is needed here. Looking at mine, the one in networks.d are settings like "allowManaged" and so forth which are set in the controller GUI and probably not relevant. So you probaby need the one at the top level only.

You can see the current config in a similar manner as to what I will suggest using to edit it:

docker run --rm -it -v ztnet_zerotier:/zt ubuntu cat /zt/local.conf

A hacky way to get in there to edit it though would be by launching a temporary ubuntu container, installing vi, and editing that file:

docker run --rm -it -v ztnet_zerotier:/zt ubuntu bash -c "apt update && apt install vim -y && vi /zt/local.conf"

Then you could add the required lowBandwidth as they document:

{
  "settings":
  {
    "lowBandwidthMode":true
  }
}

Are there better ways? I'm sure there are. But maybe this will help anyway. :)

I think this would need to be set on all client configurations. I'm not sure if the controller alone would handle it, or what happens if you didn't configure the controller in this way at all and had all clients configured with it. I don't see that documented, as they focus on "a device"...

Im not sure either, nor am i familiar with this parameter.
However, if its enough to just set this on the controller, i can add an option to set lowBandwidthMode.

It may not yet be settable by the API or zerotier-cli, so ztnet may not be able to change it

Ztnet is already making chagnes to the local.conf file, so adding an option to set lowBandwidthMode is quite trivial.

Are there better ways?

You can just open an editor directly in the zerotier folder if you need to edit config files.
example:
docker exec -it ztnet nano /var/lib/zerotier-one/local.conf

I should have linked to the documentation, but there isn’t much:

https://docs.zerotier.com/lbm/

https://www.reddit.com/r/zerotier/comments/1988664/comment/ki5lfpg/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

I changed the local.conf for all the nodes on our network, and on the ZeroTier hosted controller all of the online status information went away. They all show offline. On the ZTNet controller status page they come and go from online to offilne and many show RELAYED. I did change the local.conf on the controller docker container as well. Maybe that should have been left alone? Just trying to get a feel for it, but I obviously did not and could not change the ZeroTier hosted controller config. :)