The Noddos client monitors network traffic in the home- or enterprise network, identifies IOT and other devices and dynamically applies device-specific ACLs to the traffic of the identified devices. Its goal is to identify and stop rogue traffic from devices that have been breached, for example when a device is being used in a DDOS attack. The ACLs are downloaded from the cloud and are generated based on traffic stats uploaded anonymously by the Noddos client. You can install the Noddos client on Linux-based (DIY) routers and firewalls and on Home Gateways running firmware from the Lede project.

Noddos runs as a daemon to listen to DHCP, DNS, mDNS/DNS-SD, UPnP/SSDP and WS-Discovery traffic and to monitor traffic flows on the home or enterprise network. It reads DHCP and DNS data by sniffing those packets using AF_PACKET_RING. If incoming SSDP data has a 'Location' header then Noddos will call the URL contained in the header to collect additional device information. Using the Linux Netfilter functionality, Noddos tracks network flows in real time using either /proc/net/nf_conntrack if available or otherwise using the Linux NFCT API. Noddos reads a file with Device Profiles that specifies the matching conditions and traffic filtering rules. Periodically, Noddos matches discovered devices with the device profile database to identify known devices. Noddos can be configured to upload traffic statistics for identified devices and device attributes for devices it has not yet been able to identify. The Noddos configuration file specifies a.o. whether traffic and device statistics should be uploaded anonymously.

The Noddos process should be started at boot time. The Noddos package for routers running firmware of the Lede project includes an init.d/procd script that launches Noddos. The process runs as a daemon and needs to run as root so it can update firewall rules. Depending on traffic patterns and the processor architecture, typically the client consumes about 10MB of DRAM. The CPU usage for the process is all but negligible at 1-2%.

The 'getnoddosdeviceprofiles' script is used to securely download the list of Device Profiles over HTTPS from the Noddos web site, check the digital signature of the file using a Noddos certificate and makes the downloaded file available to the Noddos client. It needs access to the public cert for the key that was used to sign the file. That public key is included in the software distribution of Noddos. Th getnoddosdeviceprofiles script should be called at least once per day from cron.

• Install instructions for routers running firmware from Project Lede.
• Sorry, there are no packages yet for Ubuntu / Fedora / CentOS / Gentoo. For now, just compile it from source using the instructions provided below.

Compilation instructions are available for Home Gateways and regular Linux systems.

• Compile with Project LEDE SDK
• Compile and install for Linux systems

• Configuring Noddos through the noddos.yml file

The following command line options are supported by the Noddos client:

• -n, --no-daemon: Don't run as daemon and send log messages to STDERR in addition to syslog
• -c, --config-file: Location of configuration file, default /etc/noddos/noddos.conf
• -d, --debug: Enable extensive logging, save uploaded data to /tmp
• -h, --help: Print command line options

Noddos handles the following signals

• SIGTERM: Writes DeviceMatches.json file and exits.
• SIGHUP: Reloads noddos.conf and DeviceProfiles.json.
• SIGUSR1: Runs matching alogrithm and writes DeviceDump.json file.
• SIGUSR2: Runs matching algorithm and uploads (if not disabled) device info and traffic stats to the cloud.