-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zerotier device names and MTU #38
Comments
How do the device names look like? Do you connect to a lot of different networks at once? Btw. in /etc/config/network you can add an interface section to pin a devices mac and mtu. |
On Sat, Dec 22, 2018 at 04:19:48PM -0800, Moritz Warning wrote:
How do the device names look like?
'ztbpafrgg3' on all devices (DIR-505 running openwrt) and even on
a Raspberry Pi (1&3 running raspbian).
Do you connect to a lot of different networks at once?
No. It gets hardly used because the main purpose of zerotier is
emergency backdoor access. It has to be reliably present.
At the moment I set the mtu by a cronjob every few minutes.
I need that cronjob anyway because the zerotier process always vanishes
after a while for no apparent reason. In openwrt that is.
A dip in the network connection maybe?
Btw. in /etc/config/network you can add an interface section
to pin a devices mac and mtu.
Good to know. I'll give it a try.
Regards, Wim.
|
Feel free to reopen the issue if the problem is not solved yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To prevent garbage device names I must keep a file /var/lib/zerotier-one/devicemap. On a start zerotier recreates a whole bunch, and on a stop it removes ALL of it. This makes it unmanagable and it forces needles writes. Please keep some configfile(s) that can set the device name and MTU of that device. (MTU must be low to keep an ssh connection (A-NAT--NAT-B) possible.)
BTW, zerotier on 18.06.0-rc1/2 and snapshot is disfunctional. I must use 18.06.0 now.
The text was updated successfully, but these errors were encountered: