The Defend-O-Tron is a defense between the internet and your public-facing firewall or router.
This is usually installed as a connection to your ISP and a customer edge device (CED): a switch, a DOCSIS modem, a GPON ONT or another media converter, with an Ethernet port that provides your internet. How you get your IP address depends on your ISP.
If your ISP puts your service behind NAT, you may seem to have a public IP, but the Defend-O-Tron cannot fully inspect incoming traffic. Ask your ISP.
ISP equipment that gives you only Wi-Fi will not work, unless it can bridge the internet to an Ethernet port. The Defend-O-Tron cannot inspect traffic that never leaves the ISP’s device. Ask your ISP or IT administrator for equipment with an Ethernet port.
You manage the Defend-O-Tron through its management port (mgmt0), which you connect to your local network. The device also uses this port for everything it sends out: updates, the CrowdSec community, time and support. The two ports in the traffic path have no address.
The device accepts management connections (the web interface and SSH) only from these private ranges:
10.0.0.0/8192.168.0.0/16If your management network uses another range, for example one in 172.16.0.0/12, add your own subnet on Detection → Firewall, on the Lists tab, to both Management networks and Management allowed addresses. Do this from a computer that can already reach the device. See Firewall.
Add only the subnet your computers really use, for example 172.16.10.0/24, not the whole 172.16.0.0/12. Every address in these lists can reach the device’s management ports, so a smaller list is safer.
Do not use
169.254.32.0/23(169.254.32.0to169.254.33.255) for your management network. The Defend-O-Tron uses that range for its own containers.
The Defend-O-Tron’s firewall lets the management port connect out on the ports below only. Your own firewall must allow the ones you use. If your network already allows normal client traffic, as most do, you need no changes.
| Port | What for |
|---|---|
| TCP 443 (HTTPS) | Firmware, container images, the CrowdSec community and its software, encrypted DNS upstreams for AdGuard, and the Awesome-O console (enrollment, the device’s web certificate, support) |
| TCP 80 (HTTP) | Debian software updates, and the trusted timestamps for audit evidence |
| UDP 53 (DNS) | Name lookups |
| UDP 123 (NTP) | Time from the public NTP pool (pool.ntp.org). Audit evidence depends on correct time |
| Port | What for |
|---|---|
| UDP 60 to 62 | The support tunnel (WireGuard), only while a support session is open |
| TCP 1515 | The support chat, only while a session is open |
| TCP 8883 | The support session’s messaging, only while a session is open |
You can keep these closed and open them only when you need support.
| Port | What for |
|---|---|
| TCP 25 or TCP 465 | Email notifications, if you set up a mail server for them |
| UDP 853 and TCP 22, TCP 514 | Also allowed by the device: encrypted DNS over QUIC, SSH from the device’s terminal, and syslog to another server. None is needed by default |
The Defend-O-Tron does not need any inbound ports opened on your firewall from the internet. It works with outbound connections only.
To change which ports the device itself allows out, see the Lists tab on Detection → Firewall (TCP ports out, UDP ports out).
If your firewall allows outbound traffic only to listed destinations, allow these by name.
Awesome-O servers:
| Name | What for | Ports |
|---|---|---|
support.awesome-o.cloud, console.awesome-o.cloud |
The Awesome-O console: enrollment, the device’s web certificate, and starting a support session | TCP 443 |
firmware.awesome-o.cloud |
Firmware updates | TCP 443 |
secure.support.awesome-o.cloud |
The support tunnel and chat, during a support session | UDP 60 to 62, TCP 1515, TCP 8883 |
Other services. Many of these run on content delivery networks whose addresses change, so allow them by name or by port, not by IP address:
| Name | What for | Ports |
|---|---|---|
deb.debian.org, security.debian.org |
Debian software updates | TCP 80 |
api.crowdsec.net and other crowdsec.net servers |
The CrowdSec community, and its parsers and scenarios | TCP 443 |
www.openinfosecfoundation.org, rules.emergingthreats.net, ti.stamus-networks.io, sslbl.abuse.ch |
Suricata rule updates | TCP 443 |
api.seeip.org |
Detecting your public address, if the Awesome-O console cannot | TCP 443 |
registry-1.docker.io, auth.docker.io, production.cloudflare.docker.com, registry.gitlab.com |
Container images | TCP 443 |
dns10.quad9.net, dns.cloudflare.com |
AdGuard’s encrypted DNS upstreams (you can change them in AdGuard) | TCP 443 |
adguardteam.github.io |
AdGuard’s filter lists | TCP 443 |
freetsa.org |
Trusted timestamps for audit evidence | TCP 80 |
pool.ntp.org |
Time | UDP 123 |
The device keeps its clock right with NTP (chrony). It corrects the clock as soon as it reaches a time server, so the clock does not have to be right when you first power it on. Correct time matters for two reasons:
The web interface works in any current browser:
JavaScript must be on. The layout adjusts to a phone or tablet for quick checks. Longer work is easier on a computer.
Power loss can damage the device’s stored data. Connect the Defend-O-Tron to an uninterruptible power supply (UPS) before you power it up. Never unplug it or switch it off at the wall: use Restart or Shut down on the web interface’s Overview page.
The device uses little power. Connected to a UPS with battery power and surge protection, it keeps defending your network through a power cut. To size the UPS, use the hardware makers’ figures:
| Model | Power input | Maximum draw |
|---|---|---|
| V100 | USB-C Power Delivery (5, 9 or 12 V). Use a charger of 10 W or more | Not published by the maker |
| V200 | 12 V DC from the included 60 W adapter | 45 W |
These are the makers’ figures, not our measurements.