Zedmos

Documentation

The appliance manual

From a blank machine to a configured firewall, then through every page the menu can reach, then through the deployments people actually build. Every screenshot is of the running product.

⌘K

Start here

Install it

Which download to take, how to verify it, and the installer step by step.

Read

Configure it

Signing in, the uplink, the internal network, DHCP — and proving traffic flows.

Read

Run it

Backups, updates, certificates, and what to look at when something breaks.

Read

Contents

1. Getting startedZedmos installs on ordinary 64-bit x86 hardware — an appliance, a rack server, or a virtual machine. There is no hardware dongle and nothing to activate before the firewall works.
2. InstallationThis chapter installs the appliance from the installer media. If you wrote the ready-made image (zedmos.img) straight onto the target disk, there is nothing to install — skip to First boot.
3. The consoleThe console is the menu on the appliance's physical screen (or its serial line). It exists for the two situations the web panel cannot cover: the box is new and has no usable address yet, and something is wrong and the panel is unreachable.
4. First configurationHalf an hour, in order, from a freshly installed appliance to one you can leave running. There is no combined setup wizard: each step is its own page, and this chapter is the order to visit them in.
5. The control panel12 partsThe control panel is the whole product: everything the appliance can do is reachable from the sidebar, and everything the sidebar reaches is described in this chapter. This page explains the frame — the parts that behave the same everywhere — so the per-page sections that follow can stay short.
5.1 Dashboard5.2 Security and Policy5.3 Network5.4 Firewall5.5 VPN5.6 Services5.7 Hotspot5.8 Access5.9 System5.10 High Availability5.11 Console and SASE5.12 Power
6. Use casesWorked examples, each written as the order to do things in. They assume you have finished First configuration: a working uplink, an internal network, and clients that reach the internet.
7. MaintenanceWhat to do regularly, and how to do the things that only happen occasionally.
8. TroubleshootingSymptoms, in the order a support engineer would work through them. The principle underneath all of them: find the first place the truth differs from what you expect, and stop guessing there.