-
Notifications
You must be signed in to change notification settings - Fork 0
Canary Services
Project Canary leverages CORE's support for custom services to allow experimenters to load Attacker and Node services onto the hosts in a simulation to emulate the behavior of a DDoS Attack. The number and placement of the Attacker and Node services depends on a predeployment parameter specified by the network_initalizer. Both the Node and Attacker processes are basic bash scripts that are loaded by their corresponding python scripts.
A CORE node running the Attacker process will begin pinging the victim host (10.42.0.12) node at simulation time and will continue to send ping packets to that single node for the duration of the simulation. With several CORE nodes running the Attacker process this creates the impression of a DDoS attack when compared to the noise created by the standard Node processes.
At simulation time a CORE node with the Node process will begin randomly sending one ping packet to a randomly selected node in the network, then chose another node and send another ping packet and so forth. A node with this Node process will continue to do this for the duration of the simulation thus creating network noise. Every CORE node that does not have the Attacker process will have the Node process.