title | date | draft | weight | pre |
---|---|---|---|---|
Configuration |
2019-02-25 10:57:57 +0100 |
false |
3 |
<i class='fas fa-cog'></i> |
For the initial configuration, the easiest way is creating a new config.yml
file of the boot
partition of the SD card.
This partition should be easily accessible from your computer regardless of your operating system as it is a simple FAT32.
Once you've written the image file onto the SD card, there're a few steps you'll have to follow in order to configure your new Pwnagotchi properly.
Pwnagotchi displays its UI in English by default, but it can speak several other languages! If you're fine with English, you don't need to do anything special here.
But if you do want to change what language Pwnagotchi displays its status in, you can change main.lang
to one of the supported languages:
- English (default)
- German
- Italian
- French
- Russian
- Dutch
- Greek
- Swedish
- Macedonian
- Irish
- Japanese (can't be displayed with the current font)
- Polish
{{% notice tip %}}
If you want to contribute a new language (or improve an existing translation!), you can check out the Adding a Language doc for more details.
{{% /notice %}}By default, the grid
plugin is only partially enabled. This means that whenever the unit will detect internet connectivity while in MANUAL mode, it will signal its existence to the PwnGrid server by sending ONLY the following enrollment data:
- The cryptographic identity of the unit, generated at first boot and used for authentication.
- The output of the
uname -a
command on the unit used to determine the type of hardware.
If you would like your unit to participate in PwnGrid's community rankings and scoreboards (PwnGrid is like Pokémon Go, but for WiFi!), as well as be a datapoint in regional (country-level) statistics, you can fully opt-in to PwnGrid by enabling your unit to send the PwnGrid API some basic information about the networks it has pwned. None of your unit's captured cryptographic material is sent to the PwnGrid server; ONLY the minimum information to enroll the unit in the PwnGrid database (see above) and calculate how many networks it has "conquered" so far, namely:
- The list of networks that the unit collected handshakes of (consisting of their
BSSID
andESSID
).
In order to fully opt-in to PwnGrid, you must make the following change in your /etc/pwnagotchi/config.yml
file:
main:
plugins:
grid:
enabled: true
report: true # full-opt in
Even if you have decided to fully opted-in to PwnGrid, you can still disable reporting for specific networks—for instance, if you don't want your home network to be in the system:
main:
plugins:
grid:
enabled: true
report: true
exclude:
- MyHomeNetwork # both ESSIDs and BSSIDs are supported
- de:ad:be:ef:de:ad # both ESSIDs and BSSIDs are supported
{{% notice warning %}}
PLEASE NOTE:As we use YAML for the configuration, you should know some YAML rules. Especially when it comes to quotation, some things can go wrong! E.g. if your ESSIDs starts with 0x or @ or contains some other special characters, you should use single quotes, which allows you to use all kinds of characters in your string (you only need to escape the single quote itself).
{{% /notice %}}If instead you prefer to completely opt-out by also disabling signaling:
main:
plugins:
grid:
enabled: false # full opt-out
report: false
{{% notice tip %}}
If you want to use the web UI (instead of an e-ink display attached to your unit's RPi0W) to see your Pwnagotchi's face, check out the User Interface doc for more details on using the web UI.
{{% /notice %}}Set the type of display you want to use via ui.display.type
.
If your display does not work after changing this setting, you might need to completely remove power from the Raspberry Pi and make a clean boot.
Currently supported:
waveshare_2
for the V2 version of Waveshare's ePaper HAT, this is the recommended and officially supported display.waveshare_1
for the V1 legacy version of Waveshare's ePaper HATwaveshare27inch
for 2.7inch e-Paper HATinky
for Pimoroni's Inky pHAT.papirus
for PaPiRus Zero.oledhat
for Waveshare's OLED Hat.
You can configure the refresh interval of the display via ui.fps
. We recommend using a slow refresh rate to avoid shortening the lifetime of your e-ink display. The default value is 0
, which will only refresh when changes are made to the screen.
Your config.yml
file in the boot
partition of the SD card should now look something like the following (with the
right differences if you're using different hardware):
main:
whitelist:
- YourHomeNetworkMaybe
plugins:
grid:
enabled: true
report: true
exclude:
- YourHomeNetworkMaybe
ui:
display:
type: 'inkyphat'
color: 'black'
Congratulations! Your SD card is now ready for the first boot! 👾 🎉
You can also connect to your Pwnagotchi via SSH.
{{% notice warning %}}
PLEASE NOTE: If you cannot connect to your Pwnagotchi no matter what you try, ensure that the micro-USB you are using allows data transfer and doesn't ONLY provide charge. Cheaper quality micro-USB cords often do not support data transfer and will NOT allow you to actually connect to your Pwnagotchi. :'( Use a quality cord!
{{% /notice %}}- Start by connecting the micro-USB cable to the data port of your Pwnagotchi's RPi0W, then connect the other end of that cable to your computer.
- If your Pwnagotchi has already been booted up at least once before: after a few seconds, you will see a new Ethernet interface on your host computer.
- If you have never booted your Pwnagotchi before: it will take a few minutes to boot up &/or become visible or responsive. DO NOT INTERRUPT YOUR PWNAGOTCHI DURING THIS PROCESS. That extra time it takes to boot the first time you turn your Pwnagotchi on? It's because it is generating its RSA keys; if you interrupt this process, the generated keys may be corrupted!
- You'll need to configure it with a static IP address:
- IP:
10.0.0.1
- Netmask:
255.255.255.0
- Gateway:
10.0.0.1
- DNS (if required):
8.8.8.8
(or whatever)
- IP:
- If everything's been configured properly, you will now be able to
ping
either10.0.0.2
orpwnagotchi.local
- If you have already configured the name of your Pwnagotchi,
pwnagotchi.local
won't work. Instead, try your unit's hostname +.local
.
- If you have already configured the name of your Pwnagotchi,
- Congratulations! You should now be able to connect to your unit using SSH:
ssh [email protected] # default password: raspberry
- Works for Release RC5 *
{{% notice warning %}}
DEV NOTE: These are directions for the recommended hardware, a Pi0w - and connecting to it from a Linux based host via a Micro-USB through the data port. This was written while connecting to a Pi0w with a Data Capable MicroUSB to a Macbook Pro late 2012 running Ubuntu 19.04. We can not guarantee these specific directions work on any other OS. Hopefully further write ups will be provided at a later date.
{{% /notice %}}- If you have any wired interfaces on your host PC, you will need to remove them from Network Manager so we can be sure you have everything set correctly, on the correct interface.
- If you are using Wi-Fi on your host computer, you need to be certain that your routers IP address scheme is not in the
10.0.0.1/24
range. If it is, you should turn Wi-Fi off initially to best troubleshoot your connectivity issues, then change the interface IP scheme on your Pi once you canssh
to it. - These settings are only verified to work on, 1. a Pi0w, with a 2. MicroUSB data capable cable, 3. the newest released image found on our Github which at the time of writing is RC5, and 4. a completely vanilla image(plug-in and whitelist configuration is fine, but if you have previously adjusted the UI: from
10.0.0.2
to0.0.0.0
, you need to revert those changes by deleting anything related toUI:
in yourconfig.yml
.)
- First, type
ifconfig
to check and take note of the names of your current interfaces, and what is now recognized as an adapter on your system. Take note of the Mac Addresses that you see in this output. - Starting with a clean slate in your Network Manager (remove all wired interface profiles that you have on your Network Manager,) plug your unpowered Pi0w into your computer through the data port seen in the picture shown above .
- Wait until your Pi boots into Manu mode. Once you see the breakdown that Pwnagotchi does when in MANU mode, type
ifconfig
again on your host machine and look for a new interface that was not there during Step 1. *Take EXTRA note of the new interfaces mac address I will be referencing this mac address on multiple occasions as Step 3.- If you have never booted your Pwnagotchi before: it will take a few minutes to boot up &/or become visible or responsive. DO NOT INTERRUPT YOUR PWNAGOTCHI DURING THIS PROCESS. That extra time it takes to boot the first time you turn your Pwnagotchi on? It's because it is generating its RSA keys; if you interrupt this process, the generated keys may be corrupted!*
- On Network Manager on your PC/Host, (if there are no interfaces automatically added, you can attempt to add a new interface by selecting the mac address noted in Step 3 for the interface profile) select Settings > IPv4 and then change from
automatic
tomanual
, then for your address, you'll need to configure it with a static IP address and then press apply in the top right:- IP:
10.0.0.1
- Netmask:
255.255.255.0
- IP:
- Back in your terminal, type
ifconfig
and look for the interface that you found in Step 3 and that you edited the settings for in Step 4. If you see the following on the second line of the interface that matches the mac address from Step 3, you should now be able to enterping 10.0.0.2
and receive a response from your pi.
inet 10.0.0.1 netmask 255.255.255.0 broadcast 10.0.0.255
- Congratulations! You should now be able to connect to your unit using SSH:
{{% notice tip %}}
TIP: you may need to use the `linux_connection_share.sh` script before your PC will allow you to ssh to your Pi. [Host connection sharing](/configuration/#host-connection-sharing)
{{% /notice %}}{{% notice warning %}}
DEV NOTE: if you have some issues, either you are using the wrong cord, or your Operating System is missing required drivers, or something mostly out of our control. We can't help everyone with their networking, sorry
{{% /notice %}}The default password is raspberry
; you should change it as soon as you log in for the first time by issuing the passwd
command and selecting a new and more complex passphrase.
If you want to login directly without entering a password (recommended and necessary for certain packaged scripts to work, like backup.sh
for instance!), copy your SSH public key to the unit's authorized keys:
ssh-copy-id -i ~/.ssh/id_rsa.pub [email protected]
You can give your new Pwnagotchi unit its own name by changing its hostname. By default, your new Pwnagotchi's name will be Pwnagotchi
.
Open the /etc/pwnagotchi/config.yml
file (either via SSH or by directly editing the SD card's contents from a computer with a card reader) to override the default configuration with your custom values.
Want to be able to update your Pwnagotchi and access things from the internet on it? Sure you do!
- Connect to the Pwnagotchi unit via
usb0
(A.K.A., using the data port). - Run the appropriate connection sharing script to bring the interface up on your end and share internet connectivity from another interface:
OS | Script Location | Link |
---|---|---|
Linux | scripts/linux_connection_share.sh |
link |
Mac OS X | scripts/macos_connection_share.sh |
link |
Windows | scripts/win_connection_share.ps1 |
link |
If you want to upload your handshakes while walking, want to use your smartphone as a display or simply shutdown your pwnagotchi gracefully, you can use the bt-tether
-plugin.
{{% notice warning %}}
PLEASE NOTE:Please note this is reported (on Slack) to work fine with Android, but not on iOS.
{{% /notice %}}Now in pwnagotchi's config.yml
add the following:
main:
plugins:
bt-tether:
enabled: true
mac: 'FF:FF:FF:FF:FF' # you need to put your phones bt-mac here (the same as above, or goto your phones settings > status)
ip: 'xx.xx.xx.44' # this is the static ip of your pwnagotchi
# adjust this to your phones pan-network (run "ifconfig bt-pan" on your phone)
# if you feel lucky, try: 192.168.44.44 (Android) or 172.20.10.44 (iOS)
# 44 is just an example, you can choose between 2-254 (if netmask is 24)
netmask: 24
interval: 1
share_internet: true # this will change the routing and nameserver on your pi
Also don't forget to bind your pwnagotchi to all interfaces:
ui:
display:
video:
address: 0.0.0.0
Your pwnagotchi will indicate the status via a little BT
symbol at the top of the screen.
The status codes are:
- CON Connected: This means the connection to the device has been established
- NF Not found: This means the connection to the device could not be established (probably because it could not be found)
- ERR1 Error 1: This error occures, when the address (ip/netmask) could not be set to the
bnep0
interface - ERR2 Error 2: This error occures, when the
bnep0
interface could not be found
If you want to fix these problems, the first step should be to start pwnagotchi with --debug
and
check the log file (/var/log/pwnagotchi.log
) for related debug messages.
Some users had problems with the auto pairing feature of the plugin (in old versions). If your pwnagotchi should not make an effort to connect to your bluetooth device after a few minutes, there is a chance that this can be fixed by doing the pairing manually. To do this, put your phone in discoverable mode. On your pwnagotchi, run sudo bluetoothctl
and once in the bluetooth-shell, type scan on
. That will scan the environment for nearby bluetooth devices.
Pick the mac of your phone and type pair <mac>
and trust <mac>
. In short time (maybe not immediately)
you will be prompted on the phone to allow connection from your pwnagotchi hostname.
All done configuring your new Pwnagotchi? Time to learn how to take care of your new friend over in Usage!
- Check if
usb0
(or equivalent) device is being controlled by NetworkManager. - You can check this via
nmcli dev status
. - If you are having trouble connecting to your Pi via USB, be sure you are using a microUSB cord that is capable of data transfer