TerraMaster Official Forum

Hello, my whole environment is running on ZFS. I would like to use all the features of ZFS with my TNAS, like zfs send/receive etc. As the TOS has already Btrfs implemented, I guess having support for ZFS shouldn't be too different to achieve. Are there any plans on having ZFS on TOS? If not through...

I didn't automate the route changes after reboot yet, because the NAS is running pretty stable and the uptime is at about 40 days, so yeah. But instead of a cron job, I created a script in /etc/init.d/. The file name should be something like S99zzzmyscript, so that it will load at a later time (when...

I haven't set up any automation for now. Just form the theory of it, it should be enough having a service after reboot, which sets the route + ip to the interface. If I find the time in the next few days, I might post a tutorial for it.

@ JasonB: I would like to know, too, if the fans are running continously, or can you use them at auto level?

I've the same problem, how have you fixed It? Thanks! Hey nygage, yup, I've solved it. You can find more infos in my blog post under: https://blog.mukmuk.eu/2021/docker-reverse-proxy-and-services-on-f2-221/ The interesting part comes at "Changing the network interface and routes". As well...

If anyone is interested in the final setup, I've written two tutorials about it:

Docker network + Traefik:
https://blog.mukmuk.eu/2021/docker-reve ... on-f2-221/

Nextcloud:
https://blog.mukmuk.eu/2021/installing- ... on-f2-221/

Meh. Post editing ended again. :D What I've forgotten to mention is, that the mariadb container for nextclound is running inside its own internal network. It's specified in the docker-compose.yml file of nextcloud: networks: web: external: true # use the externally created web bridge internal: inter...

Yes, it's working now. Traefik is exposed to :80 and :443 and receives the request. It'll forward the request to other containers based on the domain name, that have been activated by docker-compose labels. So the structure is: - disable jumpd in /etc/nasips.ini to deactivate the redirect from :80 /...

Thanks for your reply. The web-bridge is needed for traefik to discover further services as well as using it via docker-compose. In the tutorial it reads: The docker provider enables Traefik to act as a proxy in front of Docker containers. You’ve configured the provider to watch for new containers o...

I'm aware of the 169-range. As soon as the container starts, the bridge gets routed over this subnet. But only when the first container starts... # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.178.1 0.0.0.0 UG 0 0 0 eth0 172.17.0.0 0.0.0.0 2...