Page MenuHomeFreeBSD

net/zerotier: wait for ONLINE status before booting

Authored by dch on Dec 12 2018, 7:09 PM.
Referenced Files
Unknown Object (File)
Fri, May 31, 10:37 PM
Unknown Object (File)
May 15 2024, 9:14 AM
Unknown Object (File)
May 7 2024, 11:13 PM
Unknown Object (File)
May 2 2024, 12:34 AM
Unknown Object (File)
May 2 2024, 12:08 AM
Unknown Object (File)
May 2 2024, 12:08 AM
Unknown Object (File)
May 1 2024, 11:08 PM
Unknown Object (File)
May 1 2024, 11:08 PM

Diff Detail

rP FreeBSD ports repository
Lint Not Applicable
Tests Not Applicable

Event Timeline

The underlying issue I'm trying to fix is to get the interfaces up and have an
IP available *before* we allow pf|ipfw to run. I'm pretty sure that this doesn't
actually do what I want at present, but I've not figured out a good way of
debugging things that early in the boot phase.

dch edited the summary of this revision. (Show Details)
  • updated diff removes hardcoded paths, cleaned for rclint
  • confirmed it really does work when zerotier is newly installed and after joining a secure network
  • found it blocks the boot completely if the environment uses static IP rather than DHCP
  • see for community feedback
38 ↗(On Diff #52239)

This is probably wrong, and should be PREFIX.

44 ↗(On Diff #52239)

PREFIX here too, no?

merge in DHCP handling and fix nits

handle wait loop vars correctly

dch marked 2 inline comments as done.May 21 2019, 12:30 PM

remove local.conf we do not want to provide one but we refer people
to online docs in pkg-message instead.

seems we have doubled up, D19229 is the place to B....SD.

facepalm nope need this, wrong browser tab :(

poudriere testport 11.2/12.0 i386/amd64 pass. rclint reports one error about clobbering blank values for non-mandatory variables : ${zerotier_wait_for_net:=NO}, but this seems reasonable.

This revision is now accepted and ready to land.May 22 2019, 4:29 PM
This revision was automatically updated to reflect the committed changes.