Zerotier initial bring-up rocky, down after reboot #247
Comments
|
I did some digging on 1.1 - when it's not working after initial setup, |
|
@obrienmd Sounds like an issue in the FreeBSD package. Will check tomorrow. |
|
It looks like this is simply because of zerotier-one not being started unless a network is configured and applied.
Traditionally, off by default is sensible, but in other plugins we have a global "enabled" flag to allow a zero-config service run.
Does that make sense? I haven't reproduced yet, just looked at the code.
… On 4. Sep 2017, at 20:38, David Harrigan ***@***.***> wrote:
Hi,
Thanks for the feedback @obrienmd. @fichtner happy to work with you on this one (tbh, I think I noticed the same thing yesterday - the service didn't start cleanly after an install - but was investigating the other issue so didn't delve further).
-=david=-
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
@fichtner thanks. now working on an implementation to allow global activation of zerotier service. |
|
I'm the freebsd zerotier port maintainer, let me know if I can help out here. Also, it might be time to move my firewall over to opnsense to take advantage of this new package. |
|
@dch Hi Dave, it might have just been a misconception, sorry for the trouble! zerotier-one isn't started yet so zerotier-cli complains (rightfully) about /var/db/zerotier-one not being ready. Thanks, |
|
Hi, That's very kind of you thank you. I'm presently working on fixing this issue (making the code better), but I'll be happy to reach out @dch if (when!) I need some assistance! :-) So far, zerotier on FreeBSD works amazingly well - been using it for quite a while, on bare metal and within Jails without issue :-) -=david=- |
|
@fichtner Hi, yes, part of my code cleanup is to only do zerotier-cli stuff when the zerotier-one service is running. Still cleaning things up. -=david=- |
|
@obrienmd hi - would you like to help me test the updated plugin out-of-band? Ping me on IRC if interested :) |
|
Sure! Pinging... |
#247 This commit improves upon the way that Zerotier starts and stops and how networks are added/removed and activated/deactivated. There is now a "Global" tab on the Zerotier page that enables or disables the service which is honoured between reboots. Additionally, the service needs to be active in order for networks to be added and removed. If the service is not active, then the tab "Networks" will be disabled and the user will not be able to add/remove or activate/deactivate Zerotier networks. This should fix the observed problems raised in the issue. The "Global" tab will be extended later to include further information and actions, especially when Zerotier API usage is developed. -=david=-
|
I think this can be closed now. @obrienmd reach out to me on irc to talk about this if you need to :) |
#247 This commit improves upon the way that Zerotier starts and stops and how networks are added/removed and activated/deactivated. There is now a "Global" tab on the Zerotier page that enables or disables the service which is honoured between reboots. Additionally, the service needs to be active in order for networks to be added and removed. If the service is not active, then the tab "Networks" will be disabled and the user will not be able to add/remove or activate/deactivate Zerotier networks. This should fix the observed problems raised in the issue. The "Global" tab will be extended later to include further information and actions, especially when Zerotier API usage is developed. -=david=- (cherry picked from commit 3fdca05) (cherry picked from commit e933dfb)
|
Agreed, looking forward to the new version hitting repo!
…On Sep 11, 2017 2:37 AM, "David Harrigan" ***@***.***> wrote:
I think this can be closed now. @obrienmd <https://github.com/obrienmd>
reach out to me on irc to talk about this if you need to :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#247 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAWl98IU-ISLvDCyXbj4g6SboP8WINBwks5shP9agaJpZM4PMF6g>
.
|
Per the issue on binding interfaces #239, I was able to get OSPFv2 working as expected over a ZeroTier "switch" built in the OPNSense UI with static IPs :) Thanks @dharrigan !
During this testing, I found the following to report:
The initial bring-up is a little rocky:
After a reboot, the ZeroTier interface does not come up as expected:
zerotier-cli listnetworksat the command line, but the network does show in the ZeroTier web UI list.The text was updated successfully, but these errors were encountered: