Dmitry Spikhalskiy

Members
  • Posts

    53
  • Joined

  • Last visited

2 Followers

About Dmitry Spikhalskiy

  • Birthday 03/25/1990

Converted

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Dmitry Spikhalskiy's Achievements

Rookie

Rookie (2/14)

28

Reputation

  1. I'm going to - update to 1.8.x and - expose allowManaged, allowGlobal, allowDefault options in unRAID UI But no specific timelines. When I get some free hands on a weekend.
  2. Not I'm aware of, but I didn't spend any time resolving it. Stuff works just fine and it's safe to ignore. If it bothers you to the extend of looking for a solution, contributions are welcomed!
  3. Hey. Are you sure you are solving the problem from the right end? Quick look at articles and discussions like https://zerotier.atlassian.net/wiki/spaces/SD/pages/193134593/One+Port+Linux+Bridge https://www.google.com/amp/s/amp.reddit.com/r/zerotier/comments/dc03me/having_some_trouble_with_managed_routes_static/ makes me think that you should be playing with your router, not this zeroiter container on your unraid. This symptom “This makes it impossible to access the unraid server from LAN” especially points me in this direction. Playing with managed routes on unraid will change what can be accessed from the unraid. But it shouldn't affect availability of unraid for other computers in local network. This sounds like a router setting problem for me. Let me know. If you want to have basically ‘zerotier-cli set network_id allowManaged=0’ available through the image settings - I can do it for you, no biggie. But I don't think it's a root of your problem and there is a high chance you approach the problem from the wrong end.
  4. "no version information available" messages are fine, you can ignore them, it's not what causes the issue.
  5. The image was updated to use the latest 1.6.2 Zerotier version.
  6. So, you probably want to switch the discussion into Unraid main support threads, because it's a problem with your Unraid linux kernel configuration most likely. Unraid should have this device mounted by default. Some reference that could help: https://unix.stackexchange.com/questions/501403/tun-module-loaded-but-openvpn-dev-net-tun-no-such-file-or-directory I would examine: grep CONFIG_DEVTMPFS /usr/src/<whatever you have here>/.config and ensure that it's CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y (DEVTMPFS should auto-mount devices like /dev/net/tun) Also I would at least try to do rmmod tun modprobe tun to try to reload the module. I think that the output of these commands could be useful for the Unraid support thread anyway.
  7. > Edit: I should also point out that no files, data, etc. is present within the appdata folder for this container. This is ok, Zerotier can't start to put anything there yet. > Yup! Installed it straight from community apps, and it is set to run with privileges. No idea in that case for now. https://zerotier.atlassian.net/wiki/spaces/SD/pages/7536656/Running+ZeroTier+in+a+Docker+Container Here is Zerotier explanation about /dev/net/tun and what should be done to have an access to it. I pass required parameters "--device=/dev/net/tun --cap-add=NET_ADMIN --cap-add=SYS_ADMIN" here in the configuration of the container published in CA: https://github.com/Spikhalskiy/docker-templates/blob/master/zerotier.xml#L40 And usage of these parameters is allowed by Privileged: ON. You will have to debug your own configuration I afraid, because the problem is probably local to your setup and probably your kernel configuration. What does ls -la /dev/net/tun say if you run it in the server terminal?
  8. Did you install the container from CA? Do you run the container with "Privileged: ON"?
  9. @FreeMan I don't know to be honest, at least for me Zerotier by default assigns ZT clients the same IP addresses all the time, never happened that they changed. You need to do what you described just to manually assign the IP you want. But automatically assigned IP is also static, at least in my case.
  10. @Max > okay i somehow fixed it, the only wierd thing that i noticed was that somehow on network that i created on myzerotier website had my local ips too under advanced - managed routes. It's the reason and that why I included this in the manual in the header: "if ZeroTier "Managed routes" intersect with your physical local IPs - better change Zerotier range to be different". I will edit the manual to make it more noticeable. Looks like it's connected now and if it has "Online" status at the Zerotier website UI - everything is done right on the unraid side. Your diagnostic output looks also good. Does the computer you try to access your unraid server from also has "Online" status in the Zerotier UI? Is it Authorized there also? Which IP address do you try to use for your connection? You should use IP in Zerotier network, not in the local network. Anything interesting in the tracert and ping output when you ping unRaid Zerotier IP from your client computer?
  11. @Max I don't have this problem, if you can debug it by attaching a keyboard and a display to your server and investigate why it's unavailable - could be useful, maybe some Zerotier bug on your specific configuration. There is a bug report from one of the users that 1.4.6 misbehaves on MacOS for him: https://github.com/zerotier/ZeroTierOne/issues/1030 Also, if you use the default app config now - you use the latest Zerotier version 1.4.6. To use the old bugfixed one (1.2.12) you can specify 1.2.12 tag in your Zerotier app configuration like "Repository: spikhalskiy/zerotier:1.2.12". It could make sense to rollback this way and test if the old version has the same problem on your host.
  12. 1.4.6 is released for everybody, the CLI instructions in the topic header are updated for the new docker image layout.
  13. @Pducharme I published spikhalskiy/zerotier:1.4.6 with the latest version. If you need the latest release - you can test this tag. I will release it to everybody when I test it for multiple days and check that it's stable.