Check the requirements before beginning.
Rebooting the Defend-O-Tron after placing it inline with your firewall and ISP will result in temporary loss of internet connectivity as the protection zone goes offline and is re-initialized.
The Defend-O-Tron will need to be situated in a location close to the ISP equipment and your firewall/router, in order to cable the protected zone which goes from the ISP edge device (i.e. Cable/DSL Modem, ONT/ONU, ISP Router) to your on-site equipment WAN port.
Use this list and checks below to assist in your Defend-O-Tron deployment, simply print the page and follow the steps.
Placing the Defend-O-Tron inline with your ISP and Firewall/Router is the last step after verifying management connectivity.
The initial setup requires you connect and configure the Defend-O-Tron management network and the power adapter.
Each port listed below on the Defend-O-Tron serves a distinct purpose and must be cabled correctly in order to operate.
Ethernet Ports
Power Port
Optional Ports
The management port for the Defend-O-Tron is connected to your network, either directly to the firewall/router OR to a switch that connects to a management network. Either connection must have DHCP enabled. In simple setups the management network could be your default LAN network, it just needs to be a network that is accessible to the LAN side for you to manage and a gateway to the internet for updates. Most manufacturers will denote the LAN side ports with a color or label.
OR VIA Switch
After the management network connection is completed, connect the power module to the USB-C connector.
The management interface currently is configured to be provisioned via DHCP (IPv4 only). There is a fallback static address of 192.168.88.10/24 available if DHCP fails, this will only grant you access to the administration interface to debug the DHCP failure.
We suggest making the DHCP client lease static so the users accessing the DNS server on the Defend-O-Tron have a consistent IP address to query.
Below are optional management configuration scenarios and normally you will not require them, they are list here as a reference for situations or I.T. policies that would require them.
Similar to the serial option, this allows you to connect an HDMI compatible monitor and USB keyboard to perform command line management. You can also just plug in a monitor only and observe the boot process.
The boot screen will also display the management IP address of the Defend-O-Tron.
# X.X.X.X = Management IP
_____ _____ _____ _____ _____ _____ _____ ____ _____ _____ _____
| _ / __/ __/ __/ _ | _ \ / _ \ / / _ / _ / _ \
| | | __| __| __| | | | | | | | \- -| _ | | | | |
|_____\_____\__/ \_____\__|__|_____/ \_____/ |__|\__|\_\_____\__|__/
C R O W D S E C E D I T I O N v1.0
Awesome-O Gadgets (c) 2024
-----------------------------------------------------------------
Web Admin NO DNS: https://X.X.X.X:9090
Web Admin DNS: https://defend-o-tron.protected.lan:9090
DNS: Use management IP [ X.X.X.X ] on your router/DNS proxy
Base Domain: [protected.lan]
DNS Dashboard: https://adguard.protected.lan
Metrics Dashboard: https://dashboard.protected.lan/grafana
-----------------------------------------------------------------
Web console: https://defend-o-tron.protected.lan:9090/ or https://X.X.X.X:9090/
If your management network is on a separate VLAN you can configure the port to accept DHCP on that VLAN by editing the file /etc/network/interfaces.d/mgmt-vlan file and replacing XX with your VLAN ID.
NOTE: This is currently a work in progress and not yet implemented. The preferred method is to use an access port on your switch instead of editing the interfaces file. This is only necessary in VLAN management scenarios.
$~ sudo nano /etc/network/interfaces
# The management network interface
# DHCP by default
# Fallback: 192.168.88.10/24 (via dhclient.conf)
auto mgmt0
iface mgmt0 inet manual
auto vlanXX
iface vlanXX inet dhcp
alias management
vlan-raw-device mgmt0
# MGMT VLAN
NOTE: The interfaces file has the VLAN configuration commented out by default, if you need to edit it you also have to remove the # symbol at the beginning of each line so it appears as above.
Once the interfaces file is saved you need to reconfigure the management interface with the terminal command:
$~ sudo ifreload mgmt0
When in doubt reboot the Defend-O-Tron.
If you have your Defend-O-Tron connected to a VLAN capable switch you can configure the port connecting to management as an ACCESS port (VLAN PVID) instead of having to add the VLAN to the device.
PVID stands for "Port VLAN ID" and is used in VLAN applications and it can be used to set an untagged traffic received by a given port(s) as a member of a specific VLAN. This is usually ubiquitous with Access Port.
Access ports are network switch ports that are configured to carry network traffic for a specific virtual LAN (VLAN) only. These switch ports are connected with devices such as end user devices within a specified VLAN. Consult your device documentation to see specific information about access ports.
Here are some typical switch access port configurations.
NOTE: These are only examples and actual interface and bridge names may be different in your environment, consult your I.T. administrator if you are unsure.
In this example your Defend-O-Tron is connected to port 10 on the switch.
To set port 10 as an Ethernet access port that carries traffic for VLAN XX only:
switch# configure terminal
switch(config)# interface FastEthernet 0/10
switch(config-if)# switchport mode access
switch(config-if)# switchport access vlan XX
In this example your Defend-O-Tron is connected to port ether1 on the switch.
To set port ether1 as an Ethernet access port that carries traffic for VLAN XX only:
/interface bridge
add comment="Master Switch Bridge" name=switch-bridge vlan-filtering=yes
/interface bridge port
add bridge=switch-bridge comment="Defend-O-Tron" interface=ether1 pvid=XX
/interface bridge vlan
add bridge=switch-bridge untagged="ether1" vlan-ids=XX
A detailed guide on Dlink switch setup is here DGS-1510
The Defend-O-Tron comes with in optional serial port to perform basic command line management in situations where technicians need quick access with limited resources. You should be familiar with Linux command line syntax when using this option.
Download and install Minicom for Linux or Putty for Windows.
Use the following serial parameters:
Baud rate: 1500000
Data bit: 8
Parity check: None
Stop bit: 1
Flow control: None
user@host:~# minicom -b 1500000 -D /dev/ttySx (replace x with the TTY port)
The DNS provided by the Defend-O-Tron is Adguard Home, this is an AD blocking DNS with additional safeguard features to help mitigate data privacy leaks. It also allows you to view which sites your users are visiting via logging.
You will require the DNS on the Defend-O-Tron if you wish to access the dashboards and DNS management utilities. Different router manufactures have their own methods to perform this task, contact your I.T. administrator or consult your router documentation for further information.
To configure the Defend-O-Tron as a DNS server for your network you will need to override the default DNS server IP address that your router or management network provides. Typically this is ether the ISP's DNS servers or an upstream provider such as Google or Cloudflare.
If you have deployed an internal DNS server you can set the Defend-O-Tron DNS as an upstream provider or forwarder.
In the Windows server DNS manager, right click on "Conditional Forwarders" and select "New Conditional Forwarder"
Enter protected.lan in the DNS Domain box, and the management IP address of the Defend-O-Tron.
Click OK.
Once you know the management IP address of the device you can test connectivity by browsing to the administration web ui. (See below)
Other ways to check connectivity:
Ping the Defend-O-Tron by FQDN, it should respond as shown with the IP address. Your DNS is working if the request is successfull, if not you'll need to check the DNS configuration.
Windows will sometimes require you to either reboot or flush the DNS cache on your system.
Open the command prompt (cmd.exe) or powershell console (powershell.exe).
In a terminal window on your linux device
~ % ping defend-o-tron.protected.lan -c 5
PING defend-o-tron.protected.lan(defend-o-tron.protected.lan (192.168.10.1)) 56 data bytes
64 bytes from defend-o-tron.protected.lan (192.168.10.1): icmp_seq=1 ttl=64 time=0.115 ms
64 bytes from defend-o-tron.protected.lan (192.168.10.1): icmp_seq=2 ttl=64 time=0.120 ms
64 bytes from defend-o-tron.protected.lan (192.168.10.1): icmp_seq=3 ttl=64 time=0.117 ms
64 bytes from defend-o-tron.protected.lan (192.168.10.1): icmp_seq=4 ttl=64 time=0.114 ms
64 bytes from defend-o-tron.protected.lan (192.168.10.1): icmp_seq=5 ttl=64 time=0.121 ms
--- defend-o-tron.protected.lan ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4088ms
rtt min/avg/max/mdev = 0.114/0.117/0.121/0.002 ms
You will need an adminitrative command prompt to perform this action. Once completed retest the ping.
PS C:\> ipconfig /flushdns
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
The IP address assigned to the Defend-O-Tron is shown on the console only, if you want to see that you'll need to attach an HDMI compatible monitor to the device. Otherwise your DHCP server should contain the management IP address of the Defend-O-Tron with a fully qualified domain name (FQDN) of defend-o-tron.protected.lan. Consult your DHCP documentation in order to lookup client leases.
Browse to the Defend-O-Tron web interface using http://X.X.X.X:9090 where X.X.X.X is the management IP address of the device or if you've setup the DNS, use https://defend-o-tron.protected.lan:9090
It will appear like this here
To place the Defend-O-Tron inline with your ISP and firewall/router first locate the WAN port on your router, this will be the ethernet port that currently connects to the ISP edge device. Most manufacturers will denote the WAN port with a different colored port than the LAN ports.
Here are some typical ISP edge devices you may encounter in your environment. It is important to understand how each one of the devices will supply you an internet connection via ethernet before connecting your Defend-O-Tron.
You may need to reboot your Firewall/Router to obtain or renew it's IP address.
The Defend-O-Tron is ideally secured and away from any unauthorized personnel who could access it. Gaining physical access to any device, not just the Defend-O-Tron can allow bad actors to penetrate or exploit your security equipment.
Keep the following in mind: