====== Botnets ======
Botnets allow the player to create fake traffic to a producer to meet demands that are otherwise difficult to manage. 

The concept of a botnet is as follows. 
  - User traffic is analyzed by a device on your network.
  - User traffic is converted into fake packets by a device on your network.
  - Fake packets are used by Bots to send traffic to a producer from a device on your network. 
  - Producer sees these packets and assumes they are all legit increasing your earnings and their happiness. 

==== In Practice ====
  - A device using WireRat inspects packets and creates inspect-user-packets.
  - A device using UBBT requests inspect-user-packets from the server to the WireRat via udp/6343.
  - A device using UBBT converts inspect-user-packets into support-bots.
  - A device running Bots made by botconf uses support-bots to create fake traffic to Producers.

==== Devices with WireRat ====
^ Device Name    ^ 
| [[wiki:tower_networking_inc:devices:utilities:eth_tapper|Eth Tapper]]         |
| [[wiki:tower_networking_inc:devices:firewalls:firewatch_es4a|FireWatch ES4A]] | 
| [[wiki:tower_networking_inc:devices:firewalls:firewatch_cp4e|FireWatch CP4E]] | 
| [[wiki:tower_networking_inc:devices:firewalls:bastion_5e|Bastion 5E]]         | 

==== Programs ====
^ Program Name       ^ CPU Cost ^ Memory Cost ^ Storage Cost ^ Usage                                   ^
| [[wiki:tower_networking_inc:programs:firmware:wirerat|Firmware - WireRat]] | 2        | 2           | 1            | Producer - Creates inspect-user-packets |
| [[wiki:tower_networking_inc:programs:converter:ubbt|Program - UBBT]] | 4        | 4           | 6            | Converter - Converts inspect-user-packets to support-bots |
| [[wiki:tower_networking_inc:programs:converter:bot|Program - Bots]]     | 1        | 1           | 1            | Converter - Converts support-bots into fake traffic |

One Instance of WireRat can produce an unlimited number of inspect-user-packets based on the traffic flowing through it. This is based on a 1 to 1 ratio of 1 User Request to 1 inspect-user-packets. The only limiting factor is the amount of users running through the device and the amount of memory on the device. The ratio is 1 Total Memory to 4 Inspect-User-Packets. IE 6 Total Memory = 24 Inspect-User-Packets.

One Instance of UBBT can support up to a maximum of TWO bots. You will need additional instances in order to run more bots.
 
==== Routines ====
You will need to understand the following routines in order to successfully setup a botnet. 
^ Routine ^ Usage                                                          ^
| [[wiki:tower_networking_inc:concepts:routines:botconf|Routine - botconf]]  | Creation of bot configurations. Review of bot configurations.  |
| [[wiki:tower_networking_inc:concepts:routines:program|Routine - program]] | Starting the bot programs after creation                      |
| [[wiki:tower_networking_inc:concepts:routines:route|Routine - route]]   | Creation of udp/6343 routes on routers if needed               |

Botnet Routines Syntax
^ Purpose                   ^ Syntax                                                         ^
| Create bot configurations | botconf create visitor to <color #ed1c24>@ProducerAddress</color> on <color #ed1c24>@BotHostAddress</color> |
| Show bot Configurations   | botconf show on <color #ed1c24>@BotHostAddress</color> |

==== Targets ====
The target you select is entirely up to you. You mainly want to target producers that are not getting enough traffic to meet SLAs or Producers that will pay large amounts of money based on how much traffic you send them.

==== Setting It All Up ====
There are multiple ways to set this up and it is entirely based on your preferences and architecture.

  * Directly Attached WireRat
    - This relies on a piece of hardware running WireRat directly attached to the server running UBBT
      - Setup a piece of hardware running WireRat with traffic flowing through it.
      - Connect the device directly to a server running UBBT.
      - Create two bots per UBBT instance running on the server. 

  * Remotely Attached WireRat
    - This relies on a piece of hardware running WireRat atteched to one or many servers using a route on udp/6343.
      - Setup a piece of hardware running WireRat with traffic flowing through it.
      - Setup a route from your server network to your WireRat device with udp/6343.
      - Create two bots per UBBT instance running on the server.

[[wiki:tower_networking_inc:main|Back to Home]]