Elvis Wiki - User contributions [en]

Bettercap

2020-02-15T20:00:32Z

Dsloan: updated playbulb candle

== Summary ==

This documentation is about bettercap, more specifically the functionality related to Bluetooth. The bettercap tool is described on it’s website as "the Swiss Army knife for WiFi, Bluetooth Low Energy, wireless HID hijacking and Ethernet networks reconnaissance and MITM attacks".<ref>https://www.bettercap.org/</ref> In this Wiki entry, bettercap installed on a Raspberry Pi Model 4 B and tested on a Bluetooth Low Energy tea light - MiPow Playbulb Candle.

== Requirements ==

* Raspberry Pi Model 4 B
* Operating system: Raspbian Buster
* Packages: build-essential, libpcap-dev, libusb-1.0-0-dev, libnetﬁlter-queue-dev
* BLE device (MiPow Playbulb Candle)

== Installation ==

=== Step 1 ===

Install the prerequisites

sudo apt install golang git build-essential libpcap-dev libusb -1.0-0-dev libnetfilter-queue-dev

=== Step 2 ===

Install bettercap

go get github.com/bettercap/bettercap
cd go/src/github.com/bettercap/bettercap
make build
sudo make install

=== Step 3 ===

Run bettercap

sudo bettercap

== Practical Demonstration ==

The following shows the output after starting bettercap. Note the subnet and the IP address of the Raspberry Pi are shown.

[[File:sudo_bettercap.png]]

After bettercap is running, a list of available commands and modules can be displayed using the command

help

[[File:bettercap_help.png]]

Enter the module name to gain further help

help ble.recon

[[File:bettercap_help_ble.recon.png]]

Turn on ble.recon and list the available BLE devices

ble.recon on
ble.show

[[File:bettercap_ble_recon_on_show.png]]

Various information is available from these commands such as the RSSI, the MAC address (BD_ADDR), the vendor, the ﬂags that show which version of Bluetooth is supported, whether it is possible to connect to the device and time discovered. The Playbulb Candle has been discovered and from the output it possible to see that it only supports BLE as BR/EDR is not supported.

To list the services and characteristics of the a device use the command

ble.enum MAC

In this case for the Playbulb Candle

ble.enum DC:48:4B:0F:AC:E6

[[File:bettercap_ble_enum.png]]

Attempts to change the values of characteristics can be made with

ble.write MAC UUID HEX_DATA

Results can be seen in the following screenshot.

[[File:bettercap_ble_write.png]]

To end BLE scanning using bettercap, use the command

ble.recon off

== Used Hardware ==

[[Raspberry Pi 3 Model B+]]
[[Raspberry Pi 3, Model B+, WLAN, BT]]
[[Raspberry Pi® 3 Model B, 1GB LPDDR2 RAM]]
MiPow Playbulb Candle

== Courses ==

* [[Vertiefendes Wahlfachprojekt]] (2019, 2020)
* [[Bachelorarbeit 1]] (2019, 2020)

== References ==

* https://www.bettercap.org/
* https://www.bettercap.org/installation/
[[References]]

[[Category:Documentation]]

Bettercap

2020-02-15T19:57:21Z

Dsloan: finished practical steps

== Summary ==

This documentation is about bettercap, more specifically the functionality related to Bluetooth. The bettercap tool is described on it’s website as "the Swiss Army knife for WiFi, Bluetooth Low Energy, wireless HID hijacking and Ethernet networks reconnaissance and MITM attacks".<ref>https://www.bettercap.org/</ref> In this Wiki entry, bettercap installed on a Raspberry Pi Model 4 B and tested on a Bluetooth Low Energy tea light.

== Requirements ==

* Raspberry Pi Model 4 B
* Operating system: Raspbian Buster
* Packages: build-essential, libpcap-dev, libusb-1.0-0-dev, libnetﬁlter-queue-dev
* BLE device

== Installation ==

=== Step 1 ===

Install the prerequisites

sudo apt install golang git build-essential libpcap-dev libusb -1.0-0-dev libnetfilter-queue-dev

=== Step 2 ===

Install bettercap

go get github.com/bettercap/bettercap
cd go/src/github.com/bettercap/bettercap
make build
sudo make install

=== Step 3 ===

Run bettercap

sudo bettercap

== Practical Demonstration ==

The following shows the output after starting bettercap. Note the subnet and the IP address of the Raspberry Pi are shown.

[[File:sudo_bettercap.png]]

After bettercap is running, a list of available commands and modules can be displayed using the command

help

[[File:bettercap_help.png]]

Enter the module name to gain further help

help ble.recon

[[File:bettercap_help_ble.recon.png]]

Turn on ble.recon and list the available BLE devices

ble.recon on
ble.show

[[File:bettercap_ble_recon_on_show.png]]

Various information is available from these commands such as the RSSI, the MAC address (BD_ADDR), the vendor, the ﬂags that show which version of Bluetooth is supported, whether it is possible to connect to the device and time discovered. The Playbulb Candle has been discovered and from the output it possible to see that it only supports BLE as BR/EDR is not supported.

To list the services and characteristics of the a device use the command

ble.enum MAC

In this case for the Playbulb Candle

ble.enum DC:48:4B:0F:AC:E6

[[File:bettercap_ble_enum.png]]

Attempts to change the values of characteristics can be made with

ble.write MAC UUID HEX_DATA

Results can be seen in the following screenshot.

[[File:bettercap_ble_write.png]]

To end BLE scanning using bettercap, use the command

ble.recon off

== Used Hardware ==

[[Raspberry Pi 3 Model B+]]
[[Raspberry Pi 3, Model B+, WLAN, BT]]
[[Raspberry Pi® 3 Model B, 1GB LPDDR2 RAM]]
MiPow Playbulb Candle

== Courses ==

* [[Vertiefendes Wahlfachprojekt]] (2019, 2020)
* [[Bachelorarbeit 1]] (2019, 2020)

== References ==

* https://www.bettercap.org/
* https://www.bettercap.org/installation/
[[References]]

[[Category:Documentation]]

Bettercap

2020-02-15T19:54:08Z

Dsloan: added further screenshots

== Summary ==

This documentation is about bettercap, more specifically the functionality related to Bluetooth. The bettercap tool is described on it’s website as "the Swiss Army knife for WiFi, Bluetooth Low Energy, wireless HID hijacking and Ethernet networks reconnaissance and MITM attacks".<ref>https://www.bettercap.org/</ref> In this Wiki entry, bettercap installed on a Raspberry Pi Model 4 B and tested on a Bluetooth Low Energy tea light.

== Requirements ==

* Raspberry Pi Model 4 B
* Operating system: Raspbian Buster
* Packages: build-essential, libpcap-dev, libusb-1.0-0-dev, libnetﬁlter-queue-dev
* BLE device

== Installation ==

=== Step 1 ===

Install the prerequisites

sudo apt install golang git build-essential libpcap-dev libusb -1.0-0-dev libnetfilter-queue-dev

=== Step 2 ===

Install bettercap

go get github.com/bettercap/bettercap
cd go/src/github.com/bettercap/bettercap
make build
sudo make install

=== Step 3 ===

Run bettercap

sudo bettercap

== Practical Demonstration ==

The following shows the output after starting bettercap. Note the subnet and the IP address of the Raspberry Pi are shown.

[[File:sudo_bettercap.png]]

After bettercap is running, a list of available commands and modules can be displayed using the command

help

[[File:bettercap_help.png]]

Enter the module name to gain further help

help ble.recon

[[File:bettercap_help_ble.recon.png]]

Turn on ble.recon and list the available BLE devices

ble.recon on
ble.show

[[File:bettercap_ble_recon_on_show.png]]

Various information is available from these commands such as the RSSI, the MAC address (BD_ADDR), the vendor, the ﬂags that show which version of Bluetooth is supported, whether it is possible to connect to the device and time discovered. The Playbulb Candle has been discovered and from the output it possible to see that it only supports BLE as BR/EDR is not supported.

To list the services and characteristics of the a device use the command

ble.enum MAC

In this case for the Playbulb Candle

ble.enum DC:48:4B:0F:AC:E6

[[File:bettercap_ble_enum.png]]

Attempts to change the values of characteristics can be made with

== Used Hardware ==

[[Raspberry Pi 3 Model B+]]
[[Raspberry Pi 3, Model B+, WLAN, BT]]
[[Raspberry Pi® 3 Model B, 1GB LPDDR2 RAM]]
MiPow Playbulb Candle

== Courses ==

* [[Vertiefendes Wahlfachprojekt]] (2019, 2020)
* [[Bachelorarbeit 1]] (2019, 2020)

== References ==

* https://www.bettercap.org/
* https://www.bettercap.org/installation/
[[References]]

[[Category:Documentation]]

File:Bettercap ble write.png

2020-02-15T19:50:51Z

Dsloan: Shows output of attempting to write commands with bettercap

== Summary ==
Shows output of attempting to write commands with bettercap

File:Bettercap ble enum.png

2020-02-15T19:48:14Z

Dsloan: Shows the output of bettercap ble.enum on the playbulb candle

== Summary ==
Shows the output of bettercap ble.enum on the playbulb candle

File:Bettercap ble recon on show.png

2020-02-15T19:41:46Z

Dsloan: Shows the output when starting ble.recon and listing the ble devices.

== Summary ==
Shows the output when starting ble.recon and listing the ble devices.

Bettercap

2020-02-15T19:39:16Z

Dsloan: Added screenshots

File:Bettercap help ble.recon.png

2020-02-15T19:38:25Z

Dsloan: Shows the output from bettercap help ble.recon

== Summary ==
Shows the output from bettercap help ble.recon

File:Bettercap help.png

2020-02-15T19:37:03Z

Dsloan: Shows the output of the help command when using bettercap

== Summary ==
Shows the output of the help command when using bettercap

File:Sudo bettercap.png

2020-02-15T19:27:10Z

Dsloan: Output from the command sudo bettercap.

== Summary ==
Output from the command sudo bettercap.

Bettercap

2020-02-15T19:20:14Z

Dsloan: /* Description */

== Summary ==

This documentation is about bettercap, more specifically the functionality related to Bluetooth.

== Requirements ==

* Raspberry Pi Model 4 B
* Operating system: Raspbian Buster
* Packages: build-essential, libpcap-dev, libusb-1.0-0-dev, libnetﬁlter-queue-dev

== Installation ==

=== Step 1 ===

Install the prerequisites

sudo apt install golang git build-essential libpcap-dev libusb -1.0-0-dev libnetfilter-queue-dev

=== Step 2 ===

Install bettercap

go get github.com/bettercap/bettercap
cd go/src/github.com/bettercap/bettercap
make build
sudo make install

=== Step 3 ===

Run bettercap

sudo bettercap

== Used Hardware ==

[[Raspberry Pi 3 Model B+]]
[[Raspberry Pi 3, Model B+, WLAN, BT]]
[[Raspberry Pi® 3 Model B, 1GB LPDDR2 RAM]]

== Courses ==

* [[Vertiefendes Wahlfachprojekt]] (2019, 2020)
* [[Bachelorarbeit 1]] (2019, 2020)

== References ==

* https://www.bettercap.org/
* https://www.bettercap.org/installation/

[[Category:Documentation]]

Bettercap

2020-02-15T19:19:02Z

Dsloan: /* Summary */

== Summary ==

This documentation is about bettercap, more specifically the functionality related to Bluetooth.

== Requirements ==

* Raspberry Pi Model 4 B
* Operating system: Raspbian Buster
* Packages: build-essential, libpcap-dev, libusb-1.0-0-dev, libnetﬁlter-queue-dev

== Description ==

=== Step 1 ===

Install the prerequisites

sudo apt install golang git build-essential libpcap-dev libusb -1.0-0-dev libnetfilter-queue-dev

=== Step 2 ===

Install bettercap

go get github.com/bettercap/bettercap
cd go/src/github.com/bettercap/bettercap
make build
sudo make install

=== Step 3 ===

Run bettercap

sudo bettercap

== Used Hardware ==

[[Raspberry Pi 3 Model B+]]
[[Raspberry Pi 3, Model B+, WLAN, BT]]
[[Raspberry Pi® 3 Model B, 1GB LPDDR2 RAM]]

== Courses ==

* [[Vertiefendes Wahlfachprojekt]] (2019, 2020)
* [[Bachelorarbeit 1]] (2019, 2020)

== References ==

* https://www.bettercap.org/
* https://www.bettercap.org/installation/

[[Category:Documentation]]

Bettercap

2020-02-15T19:18:17Z

Dsloan: Basic structure and installation

== Summary ==

This documentation is about bettercap. More specifically dfgd 7899

== Requirements ==

* Raspberry Pi Model 4 B
* Operating system: Raspbian Buster
* Packages: build-essential, libpcap-dev, libusb-1.0-0-dev, libnetﬁlter-queue-dev

== Description ==

=== Step 1 ===

Install the prerequisites

sudo apt install golang git build-essential libpcap-dev libusb -1.0-0-dev libnetfilter-queue-dev

=== Step 2 ===

Install bettercap

go get github.com/bettercap/bettercap
cd go/src/github.com/bettercap/bettercap
make build
sudo make install

=== Step 3 ===

Run bettercap

sudo bettercap

== Used Hardware ==

[[Raspberry Pi 3 Model B+]]
[[Raspberry Pi 3, Model B+, WLAN, BT]]
[[Raspberry Pi® 3 Model B, 1GB LPDDR2 RAM]]

== Courses ==

* [[Vertiefendes Wahlfachprojekt]] (2019, 2020)
* [[Bachelorarbeit 1]] (2019, 2020)

== References ==

* https://www.bettercap.org/
* https://www.bettercap.org/installation/

[[Category:Documentation]]

Botnets

2020-01-31T16:27:05Z

Dsloan:

== Summary ==

This Wiki entry deals with the topic botnets. It introduces the reader to the key terminology before discussing the various types of botnets, including architecture and infection methods. The explosion in recent years of IoT devices that lack the security standards of devices such as laptops and smartphones has created a new pool of potential hosts for botnets and exacerbated the problem of botnets. Criminals will always look to exploit new technology for illegal financial gains and more must be done on a global level to combat the threat of botnets. Countermeasures and prevention methods will be discussed.

== What is a Botnet ==

A botnet is a network of compromised machines under the control of an attacker.<ref>Ben Stock, Jan Göbel, Markus Engelberth, Felix C Freiling, and Thorsten Holz. Walowdac-analysis of a peer-to-peer botnet. In 2009 European Conference on Computer Network Defense, pages 13–20. IEEE, 2009.</ref>

===Types of Botnets===

There are two types of botnet architecture - centralised and decentralised.<ref>Himanshi Dhayal and Jitender Kumar. Botnet and p2p botnet detection strategies: A review. In 2018 International Conference on Communication and Signal Processing (ICCSP), pages 1077–1082. IEEE, 2018.</ref> Centralised botnets have a client-server architecture. They usually communicate via IRC protocol.<ref name="Botnet survey"> Pedram Amini, Muhammad Amin Araghizadeh, and Reza Azmi. A survey on botnet: Classiﬁcation, detection and defense. In 2015 International Electronics Symposium (IES), pages 233–238. IEEE, 2015.</ref> Decentralised botnets have a peer-to-peer(P2P)or unstructured architecture. To create a botnet, machines or IoT devices ﬁrst need to be infected to allow for remote control. This is done without the consent of the owners. Infection can be done by a special Trojan virus that can breach the security of users’ computers.<ref>Kapersky. https://usa.kaspersky.com/resource-center/threats/botnet-attacks What is a botnet?, 2020. Last accessed Thursday 2nd January, 2020.</ref> The botnet is then controlled a person called the Botmaster.<ref name="Botnet survey" /> Infection mechanisms can include web downloads, email attachments as well as automatic bots that scan for vulnerabilities to exploit.<ref name="Botnet survey" /> Infection can also come in form of an infected USB stick or an insider attack.

====Centralised====

In the centralised model, each bot acts only a client receiving instructions from a server. There is a central point that forwards the control messages to the bots.<ref name="BCJ" >Michael Bailey, Evan Cooke, Farnam Jahanian, Yunjing Xu, and Manish Karir. A survey of botnet technology and defenses. In 2009 Cybersecurity Applications & Technology Conference for Homeland Security, pages 299–304. IEEE, 2009.</ref>

====Peer-to-Peer====

In the P2P model, each bot or node acts as both client and server. This means it can both send and receive commands. A P2P botnet is much harder to disrupt as the P2P communication system is much harder to disrupt.<ref name="BCJ" /> Stopping one bot does not lead to stopping the whole botnet. Control commands can be sent from the command and control centre and are then propagated throughout the botnet via the bots themselves.

====Unstructured====

The unstructured model is a sub-type of P2p model where "no single bot would know about any more than one other bot".<ref name="BCJ" /> The bot or controller would send a message and it would get randomly passed on to the next bot.<ref name="BCJ" /> This makes it very hard to detect the bots and it may not even be possible to detect all the bots.<ref name="BCJ" /> The drawback for the attacker is that there is no guarantee of delivery and the latency is very high.<ref name="BCJ" />

===Components===

Every botnet needs bots. These are the machines or IoT devices that are infected by an attacker and make up the network. IoT devices include light bulbs, fridges, sensors and health equipment. The bots are controlled by a command and control server which is in turn controlled by the Botmaster.

===Purpose===

Botnets can be used for various purposes including DDOS attacks, stealing info from the infected machine (bot), bitcoin mining, spam, phishing, identity theft and keylogging.<ref name="Botnet survey" /> A Distributed Denial of Service (DDoS) attack is an attempt to make an online service unavailable by overwhelming it with traﬃc from multiple sources.<ref>Arbor Networks Google Ideas. https://www.digitalattackmap.com/understanding-ddos/ What is a ddos attack?, 2013. Last accessed Tuesday 7th January, 2020.</ref> According to <ref name="Gon12">Max Goncharov. Russian underground 101. Trend Micro incorporated research paper, page 51, 2012.</ref>, a DDoS service can be hired for as little as $10 per hour, $30-70 per day, $150 per week or $1,200 per month. A list of uses for botnets from <ref name="Gon12" /> is as follows:
* Attack ISPs, sometimes resulting in denial-of-service to legitimate traffic
* Send spam email
* Launch DDoS attacks and bring down websites and APIs
* Perform click fraud
* Solve weak CAPTCHA challenges on websites in order to imitate human behaviour during logins
* Steal credit card information
* Hold companies to ransom with threats of DDoS attacks
The aim is to make money out of the victims or increase the size of the botnet to in turn make more money.

===Prevention===

<ref name="Pol18">William T Polk. A report to the president on enhancing the resilience of the internet and communications ecosystem against botnets and other automated, distributed threats. Technical report, NIST, 2018.</ref> gives a comprehensive list of actions necessary to protect and prevent botnets. These include:
* Ingress and egress filtering
* Legacy devices that cannot be secured should be located, removed and replaced these with secure devices
* Devices should be kept up to date
* DDoS mitigation services that are on and oﬀ premise should deployed – Cloudflare, Project Shield (Google), AWS Shield, Microsoft Azure
* Enterprise traffic should be monitored
* Market incentives that align with security practice

Further actions from <ref name="Pol18" /> are:
* Using industry-led inclusive processes, establish internationally applicable IoT capability baselines supporting lifecycle security for home and industrial applications founded on voluntary, industry-driven international standards
* Internet service providers should expand current information sharing to achieve timelier and eﬀective sharing of actionable threat information both domestically and globally
* Home IT and IoT products should be easy to understand and simple to use securely

====Countermeasures====

Six countermeasures, as described in <ref>Christian Czosseck, Gabriel Klein, and Felix Leder. On the arms race around botnets - setting up and taking down botnets. In 2011 3rd International Conference on Cyber Conflict, pages 1–14. IEEE, 2011.</ref>, are:
* Command and Control Server Takedown
Command and control server takedown is only possible when the server location is known. Even if the location is known, it still may not be possible to stop the server due to backups, issues coordinating with law enforcement and geographical constraints.
* DNS-based Countermeasures
DNS-based countermeasures only work if the command and control infrastructure of the botnet is based on DNS. It requires the de-registration of the domains used by the botnet. It only affects the newly connected hosts and not the already connected computers.
* Response DDoS
For this countermeasure to work, the command and control endpoints need to be known. A DDoS response will only keep the botnet offline as long as the DDoS response lasts. DDoS attacks are illegal in most countries which means that this countermeasure should not be considered.
* Hack-Back
If a command and control server can be found then it would be possible to disable the botnet via hacking. A vulnerability must be found and compromised in the infrastructure and this countermeasure requires a team of specialised penetration team. The ethics of hacking a compromised machine are a little murky. It is possible that third-party data is obtained as a result of hacking
* Infiltration/Manipulation
Identifies and exploits weaknesses in the command and control protocol and/or architecture.
* BGP Blackholing
BGP Blackholing (also known as sinkholing) is the redirecting of botnet-related traffic. Redirected traffic can be discarded or analysed to gain insight into the botnet.

==Conclusion==

In conclusion, botnets will continue to pose a threat to enterprises and home users until global standards can be reached to better secure devices, especially IoT devices. Whilst having an infected IoT device or computer might not be recognisable to the average user as the device will continue to function normally, albeit at a slightly reduced capacity, outages to DNS servers and for example a loss of access to services such as Netflix will or when sensitive data such as a credit card or banking details are stolen from an infected machine. There needs to be globally concerted action to improve standards to make sure the onus does not lie on the consumer. Criminals will always look to exploit weaknesses to make financial gains and to disrupt services. It should not be made easy for them by offering unsecured IoT devices on a platter to be infected.

== Courses ==

* [[Ausgewählte Kapitel der IT-Security SE]] (2019, 2020)

== References ==

<references />

[[Category:Documentation]]

Botnets

2020-01-31T16:14:14Z

Dsloan: added countermeasures

== Summary ==

This Wiki entry deals with the topic botnets. It introduces the reader to the key terminology before discussing the various types of botnets, including architecture and infection methods. The explosion in recent years of IoT devices that lack the security standards of devices such as laptops and smartphones has created a new pool of potential hosts for botnets and exacerbated the problem of botnets. Criminals will always look to exploit new technology for illegal financial gains and more must be done on a global level to combat the threat of botnets. Countermeasures and prevention methods will be discussed.

== What is a Botnet ==

A botnet is a network of compromised machines under the control of an attacker.<ref>Ben Stock, Jan Göbel, Markus Engelberth, Felix C Freiling, and Thorsten Holz. Walowdac-analysis of a peer-to-peer botnet. In 2009 European Conference on Computer Network Defense, pages 13–20. IEEE, 2009.</ref>

===Types of Botnets===

There are two types of botnet architecture - centralised and decentralised.<ref>Himanshi Dhayal and Jitender Kumar. Botnet and p2p botnet detection strategies: A review. In 2018 International Conference on Communication and Signal Processing (ICCSP), pages 1077–1082. IEEE, 2018.</ref> Centralised botnets have a client-server architecture. They usually communicate via IRC protocol.<ref name="Botnet survey"> Pedram Amini, Muhammad Amin Araghizadeh, and Reza Azmi. A survey on botnet: Classiﬁcation, detection and defense. In 2015 International Electronics Symposium (IES), pages 233–238. IEEE, 2015.</ref> Decentralised botnets have a peer-to-peer(P2P)or unstructured architecture. To create a botnet, machines or IoT devices ﬁrst need to be infected to allow for remote control. This is done without the consent of the owners. Infection can be done by a special Trojan virus that can breach the security of users’ computers.<ref>Kapersky. https://usa.kaspersky.com/resource-center/threats/botnet-attacks What is a botnet?, 2020. Last accessed Thursday 2nd January, 2020.</ref> The botnet is then controlled a person called the Botmaster.<ref name="Botnet survey" /> Infection mechanisms can include web downloads, email attachments as well as automatic bots that scan for vulnerabilities to exploit.<ref name="Botnet survey" /> Infection can also come in form of an infected USB stick or an insider attack.

====Centralised====

In the centralised model, each bot acts only a client receiving instructions from a server. There is a central point that forwards the control messages to the bots.<ref name="BCJ" >Michael Bailey, Evan Cooke, Farnam Jahanian, Yunjing Xu, and Manish Karir. A survey of botnet technology and defenses. In 2009 Cybersecurity Applications & Technology Conference for Homeland Security, pages 299–304. IEEE, 2009.</ref>

====Peer-to-Peer====

In the P2P model, each bot or node acts as both client and server. This means it can both send and receive commands. A P2P botnet is much harder to disrupt as the P2P communication system is much harder to disrupt.<ref name="BCJ" /> Stopping one bot does not lead to stopping the whole botnet. Control commands can be sent from the command and control centre and are then propagated throughout the botnet via the bots themselves.

====Unstructured====

The unstructured model is a sub-type of P2p model where "no single bot would know about any more than one other bot".<ref name="BCJ" /> The bot or controller would send a message and it would get randomly passed on to the next bot.<ref name="BCJ" /> This makes it very hard to detect the bots and it may not even be possible to detect all the bots.<ref name="BCJ" /> The drawback for the attacker is that there is no guarantee of delivery and the latency is very high.<ref name="BCJ" />

===Components===

Every botnet needs bots. These are the machines or IoT devices that are infected by an attacker and make up the network. IoT devices include light bulbs, fridges, sensors and health equipment. The bots are controlled by a command and control server which is in turn controlled by the Botmaster.

===Purpose===

Botnets can be used for various purposes including DDOS attacks, stealing info from the infected machine (bot), bitcoin mining, spam, phishing, identity theft and keylogging.<ref name="Botnet survey" /> A Distributed Denial of Service (DDoS) attack is an attempt to make an online service unavailable by overwhelming it with traﬃc from multiple sources.<ref>Arbor Networks Google Ideas. https://www.digitalattackmap.com/understanding-ddos/ What is a ddos attack?, 2013. Last accessed Tuesday 7th January, 2020.</ref> According to <ref name="Gon12">Max Goncharov. Russian underground 101. Trend Micro incorporated research paper, page 51, 2012.</ref>, a DDoS service can be hired for as little as $10 per hour, $30-70 per day, $150 per week or $1,200 per month. A list of uses for botnets from <ref name="Gon12" /> is as follows:
* Attack ISPs, sometimes resulting in denial-of-service to legitimate traffic
* Send spam email
* Launch DDoS attacks and bring down websites and APIs
* Perform click fraud
* Solve weak CAPTCHA challenges on websites in order to imitate human behaviour during logins
* Steal credit card information
* Hold companies to ransom with threats of DDoS attacks
The aim is to make money out of the victims or increase the size of the botnet to in turn make more money.

===Prevention===

<ref name="Pol18">William T Polk. A report to the president on enhancing the resilience of the internet and communications ecosystem against botnets and other automated, distributed threats. Technical report, NIST, 2018.</ref> gives a comprehensive list of actions necessary to protect and prevent botnets. These include:
* Ingress and egress filtering
* Legacy devices that cannot be secured should be located, removed and replaced these with secure devices
* Devices should be kept up to date
* DDoS mitigation services that are on and oﬀ premise should deployed – Cloudflare, Project Shield (Google), AWS Shield, Microsoft Azure
* Enterprise traffic should be monitored
* Market incentives that align with security practice

Further actions from <ref name="Pol18" /> are:
* Using industry-led inclusive processes, establish internationally applicable IoT capability baselines supporting lifecycle security for home and industrial applications founded on voluntary, industry-driven international standards
* Internet service providers should expand current information sharing to achieve timelier and eﬀective sharing of actionable threat information both domestically and globally
* Home IT and IoT products should be easy to understand and simple to use securely

====Countermeasures====

Six countermeasures, as described in <ref>Christian Czosseck, Gabriel Klein, and Felix Leder. On the arms race around botnets - setting up and taking down botnets. In 2011 3rd International Conference on Cyber Conflict, pages 1–14. IEEE, 2011.</ref>, are:
* Command and Control Server Takedown
* DNS-based Countermeasures
* Response DDoS
* Hack-Back
* Infiltration/Manipulation
* BGP Blackholing

== Courses ==

* [[Ausgewählte Kapitel der IT-Security SE]] (2019, 2020)

== References ==

<references />

[[Category:Documentation]]

Botnets

2020-01-31T14:28:01Z

Dsloan:

Botnets

2020-01-31T14:20:31Z

Dsloan: This Wiki entry deals with the topic botnets. It introduces the reader to the key terminology before discussing the various types of botnets, including architecture and infection methods. The explosion in recent years of IoT devices that lack the security

Install ioBroker

2019-07-17T19:05:05Z

Dsloan: /* Step 6 */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian
* See [[Used Hardware]]

In order to complete these steps, you must have followed https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up before.

== Description ==

=== Step 1: System Update ===

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2: Test for existing versions of nodejs and npm ===

Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match.

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3: Uninstall existing node and node.js versions ===

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4: Install node.js for Linux and Raspberry 2/3 ===

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5: Install ioBroker ===

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5: Start ioBroker ===

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6: Launch ioBroker web interface ===

Go to https://localhost:8081

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T19:04:31Z

Dsloan: /* Step 5 */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian
* See [[Used Hardware]]

In order to complete these steps, you must have followed https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up before.

== Description ==

=== Step 1: System Update ===

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2: Test for existing versions of nodejs and npm ===

Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match.

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3: Uninstall existing node and node.js versions ===

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4: Install node.js for Linux and Raspberry 2/3 ===

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5: Install ioBroker ===

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5: Start ioBroker ===

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via https://localhost:8081

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T19:04:17Z

Dsloan: /* Step 5 */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian
* See [[Used Hardware]]

In order to complete these steps, you must have followed https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up before.

== Description ==

=== Step 1: System Update ===

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2: Test for existing versions of nodejs and npm ===

Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match.

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3: Uninstall existing node and node.js versions ===

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4: Install node.js for Linux and Raspberry 2/3 ===

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5: Install ioBroker ===

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5 ===

Start ioBroker

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via https://localhost:8081

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T19:03:58Z

Dsloan: /* Step 4 */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian
* See [[Used Hardware]]

In order to complete these steps, you must have followed https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up before.

== Description ==

=== Step 1: System Update ===

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2: Test for existing versions of nodejs and npm ===

Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match.

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3: Uninstall existing node and node.js versions ===

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4: Install node.js for Linux and Raspberry 2/3 ===

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5 ===

Start ioBroker

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via https://localhost:8081

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T19:03:46Z

Dsloan: /* Step 3 */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian
* See [[Used Hardware]]

In order to complete these steps, you must have followed https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up before.

== Description ==

=== Step 1: System Update ===

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2: Test for existing versions of nodejs and npm ===

Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match.

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3: Uninstall existing node and node.js versions ===

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5 ===

Start ioBroker

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via https://localhost:8081

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T19:03:31Z

Dsloan: /* Step 2 */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian
* See [[Used Hardware]]

In order to complete these steps, you must have followed https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up before.

== Description ==

=== Step 1: System Update ===

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2: Test for existing versions of nodejs and npm ===

Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match.

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5 ===

Start ioBroker

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via https://localhost:8081

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T19:03:12Z

Dsloan: /* Step 1 */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian
* See [[Used Hardware]]

In order to complete these steps, you must have followed https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up before.

== Description ==

=== Step 1: System Update ===

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm.
Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match.

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5 ===

Start ioBroker

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via https://localhost:8081

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T19:00:17Z

Dsloan: /* Requirements */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian
* See [[Used Hardware]]

In order to complete these steps, you must have followed https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm.
Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match.

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5 ===

Start ioBroker

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via https://localhost:8081

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T18:59:51Z

Dsloan: /* Step 6 */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian
* See [[Used Hardware]]

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm.
Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match.

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5 ===

Start ioBroker

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via https://localhost:8081

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T18:54:37Z

Dsloan: /* Requirements */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian
* See [[Used Hardware]]

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm.
Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match.

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5 ===

Start ioBroker

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via [[localhost:8081]]

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T18:52:32Z

Dsloan: /* Step 2 */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm.
Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match.

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5 ===

Start ioBroker

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via [[localhost:8081]]

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T18:51:46Z

Dsloan: /* Description */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm. (Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match)

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5 ===

Start ioBroker

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via [[localhost:8081]]

[[File:ioBroker_localhost.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

File:IoBroker localhost.png

2019-07-17T18:50:37Z

Dsloan:

Install ioBroker

2019-07-17T18:50:14Z

Dsloan: /* Description */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm. (Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match)

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

=== Step 5 ===

Start ioBroker

Use commands:

sudo systemctl stop iobroker
sudo systemctl start iobroker
sudo systemctl restart iobroker
sudo systemctl status iobroker

=== Step 6 ===

Launch ioBroker web interface via [[localhost:8081]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T18:47:22Z

Dsloan: /* Used Hardware */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm. (Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match)

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

== Used Hardware ==

* [[Raspberry Pi 3, Model B+, WLAN, BT]]
* 32GB (4GB min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T18:46:45Z

Dsloan: /* References */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm. (Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match)

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

== Used Hardware ==

[[Raspberry Pi 3, Model B+, WLAN, BT]]
4GB (min) microSD card

== References ==

* https://www.iobroker.net/
* https://projects.raspberrypi.org/en

[[Category:Documentation]]

Install ioBroker

2019-07-17T18:45:44Z

Dsloan:

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm. (Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match)

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

== Used Hardware ==

[[Raspberry Pi 3, Model B+, WLAN, BT]]
4GB (min) microSD card

== References ==

* https://wikipedia.org
* https://google.com

[[Category:Documentation]]

Install ioBroker

2019-07-17T18:44:33Z

Dsloan: /* Used Hardware */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm. (Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match)

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

== Used Hardware ==

[[Raspberry Pi 3, Model B+, WLAN, BT]]
4GB (min) microSD card

== Courses ==

* [[A course where this documentation was used]] (2017, 2018)
* [[Another one]] (2018)

== References ==

* https://wikipedia.org
* https://google.com

[[Category:Documentation]]

Install ioBroker

2019-07-17T18:39:40Z

Dsloan: /* Used Hardware */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm. (Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match)

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

== Used Hardware ==

Raspberry Pi 3 Model B+
4GB (min) microSD card

== Courses ==

* [[A course where this documentation was used]] (2017, 2018)
* [[Another one]] (2018)

== References ==

* https://wikipedia.org
* https://google.com

[[Category:Documentation]]

Install ioBroker

2019-07-17T18:38:48Z

Dsloan: /* Description */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm. (Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match)

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

[[File:ioBroker_installer.png]]

== Used Hardware ==

[[Device to be used with this documentation]]
[[Maybe another device to be used with this documentation]]

== Courses ==

* [[A course where this documentation was used]] (2017, 2018)
* [[Another one]] (2018)

== References ==

* https://wikipedia.org
* https://google.com

[[Category:Documentation]]

File:IoBroker installer.png

2019-07-17T18:37:58Z

Dsloan:

Install ioBroker

2019-07-17T18:37:07Z

Dsloan: /* Description */

== Summary ==

This documentation describes how to install ioBroker on a Raspberry Pi 3 Model B+

== Requirements ==

* Operating system: Raspbian

In order to complete these steps, you must have followed [[https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up]] before.

== Description ==

=== Step 1 ===

System Update:

In the command line interface enter:

sudo apt-get update && sudo apt-get upgrade

=== Step 2 ===

Test for existing versions of nodejs and npm. (Recommended version for node is 8.x with js-contoller 1.5.7, >6 for npm. Version numbers for node and nodejs must match)

node -v
nodejs -v
npm -v

[[File:Node.png]]

If the commands don’t result in a shown version number, then proceed to Step 4.

=== Step 3 ===

Uninstall existing node and node.js versions

sudo apt-get --purge remove node
sudo apt-get --purge remove nodejs
sudo apt-get autoremove
sudo reboot

=== Step 4 ===

Install node.js for Linux and Raspberry 2/3

curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
sudo apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs
sudo reboot

=== Step 5 ===

Install ioBroker

curl -sL https://iobroker.net/install.sh | bash -

== Used Hardware ==

[[Device to be used with this documentation]]
[[Maybe another device to be used with this documentation]]

== Courses ==

* [[A course where this documentation was used]] (2017, 2018)
* [[Another one]] (2018)

== References ==

* https://wikipedia.org
* https://google.com

[[Category:Documentation]]

Install ioBroker

2019-07-17T18:34:15Z

Dsloan: /* Step 2 */

File:Node.png

2019-07-17T18:33:37Z

Dsloan:

Install ioBroker

2019-07-17T18:32:36Z

Dsloan: This