| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
significantly simpler way to move all of this logic entirely into the containing service, liberating the core from any concern over the nature of its pipe to the outside world.
|
|
fallback tunnel hostname.
|
|
|
|
|
|
|
|
and clean up service start/stop in installer.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
start on a NodeJS class for talking to the network controller.
|
|
|
|
convenience request in ControlPlane for scripted testing.
|
|
|
|
eliminating caching for now. We will re-add if it is needed.
|
|
that later. Should be able to re-use FreeBSD port for OpenBSD, but we will see.
|
|
it will be easier than retrofitting the old Qt client for the new API.
|
|
|
|
|
|
stuff and test.
|
|
|
|
control bus at all yet.
|
|
|
|
possibly other platforms) issue in Phy<>.
|
|
|
|
|
|
on shutdown, (3) cleanup in selftest, re-enable Phy and Http tests.
|
|
|
|
client. Need a cross-platform built-in one to do cli right.
|
|
|
|
and do a backward compatiable CLI in bash instead of as part of the executable.
|
|
|
|
be part of the whole OnePoint project anyway.
|
|
|
|
|
|
|
|
|
|
|
|
core, other bug fixes.
|
|
|
|
|
|
|
|
network request on network restore logic, and remember saved networks in service/One
|
|
|
|
|
|
|
