azimov

Internals

Alpha

Alpha software under active development. It has not been audited. Use at your own risk.

What is true today

  • Kernel interface (utun on macOS, az0 on Linux). Opening it needs an administrator. One /128 per peer in fd00:1776::/64, and one galaxy-assigned /32 in 10.176.0.0/16. The interface does not take the default route.
  • Login is a wallet, a master ticket, or a key from a running ship, then the node is up. Later, az up connects that node. az down disconnects it and leaves the daemon running. az start and az stop start and stop the daemon.
  • Inbound starts closed. az mesh add puts a point on pending. They accept before either side dials. A member reaches the overlay address. A yes is the whole address.
  • az exit use sends public traffic through a joined exit. The interface does not take the default route.
  • SSH runs the host ssh client. The node accepts the session from a mesh member. The shell is the account registered on that machine. Host-key checking stays on.
  • az ping reports the magicsock path. ping6 to the overlay address is the host check. An installed peer also answers as zod and zod.azimov.network. A pending peer does not. ~zod is not a label.
  • Relay: sponsor galaxy, then nut.relay.azimov.network (~nut) fallback. Cafe-NAT via a galaxy is the actual promise. Path is still often relay in live dogfood.
  • Install is Apple Silicon and Linux (x86_64 and arm64). Releases are on the changelog. Windows is coming soon. az shadows Homebrew’s Azure CLI, so install tnd/az/az.