piCopilot is 100% feedback driven. If you like piCopilot and wish to contribute, simply fork and PR; or raise an issue.

Certain aspects of piCopilot may not be legal in every Country or locality. Ensure that you check the rules and regulations for where you will be operating prior to use. The operator is fully and wholly responsible for any legal and/or civil issues that may arise from their usage of piCopilot.

The Wireless and Bluetooth monitoring capabilities of piCopilot should bring pause to anyone. piCopilot is not special in this regard, nor is it alone. There are many tools which do the same thing and sometimes more so than even the idrop module; freely available by way of entities like Google and Github. The very power one has when wielding a tool like piCopilot is immense. Sharing of the code for the world to read comes with it a unique responsibility.

The steps below are meant for the average consumer in 2021. The point is to drive home the details in a way that someone who has not used piCopilot or studied how things like Wireless and Bluetooth work, "gets it".

1. Keep Wireless and Bluetooth off when not in use, seriously. Yes, really.

Your device is noisy because it is always looking for the next best thing. By turning off Wireless and Bluetooth when not in use you will reduce the unique signatures that can be associated with a common device in 2021 that has the ability to leverage Wireless or Bluetooth. Tracking of those signatures is already in use by various advertising companies and potentially, Governmental agencies around the world. Why make yourself a bigger target just for the sake of convenience?

2. Work from home took on a whole new meaning.

For about $35 worth of gear the world around you changes into 0s, 1s and patterns. No longer does one have to wait until working hours are over to see a new ESSID on the off-chance an employee brought their laptop home from work. The Internet as we have it in 2021 proved one thing, baked-in needs to be the new bolt-on. Did you know a Bank moved in next door? How about a Law firm? That dentist too. piCopilot surely does.

3. Keep your list of "Remembered Networks" empty or at a minimum. Your device can be fooled into giving out details of where it has tried to, or successfully connected to a Network Name (ESSID). Statistics can paint quite the vivid picture if you know what you seek.

Advertising the ESSID of your great aunt Sally is not something to be desired, please excuse. Keep Sally's business to Sally.

4. Know just how far your home network reaches.

Don't know? Take your phone out, pick a random direction and keep walking; all the while looking for your home wireless. When you cannot see it anymore, chalk out your 360, you have reached your bubble's end.

Reduce your power output if able. Take a moment and login to that router of yours. Go through the settings and see if there is a way to reduce the power output of the radio transmitter inside of it. While maximum effect seems nice, it just may give Johnny across the way access to more than you bargained for.

Protect the very knowledge of your bubbles and change them up at random when you can.

Friends don't let friends keep ESSIDs for extended times.

5. Realize that there is no anonymity with Wireless, Bluetooth or most any of the common protocols the average person knows in 2021.

The very backbone of how it works would snap in half if you tried to truly make yourself invisible to others. Who would they talk to if not you? Using Wireless or Bluetooth tells anyone within roughly 100 yards of your position, "I am here".

6. Build a piCopilot and learn just how all of this works.

Anyone can code. Anyone in 2021 should know the basics of how these common everyday protocols work. Even if they'll never see it again, nor hear of it again; at least the seed was planted and maybe they'll remember. The possibilities for modules like idrop and the like are endless and yet very well common; you just didn't know it.

7. Press the communities like Motorola, Apple, ABC, Google, etc; press them that your security and privacy matter. The current model has none of that and it should rather be widespread and far-flung. If your phone doesn't have a way to randomize your MAC, you should be asking why.

Out of the United States Ninth Circuit just such a thing happened; somewhat. Joffe -v- Google. Also known as 11-17483. Thirty and five pages. Brilliant, masterful and far-reaching by all rights. Eight years and going strong, yet how many of you are just finding out now for the first time?

11-17483 is the precedence. What will you do with it?

• piCopilot
  • The ecosystem
• piCopilot-idrop
  • Intrusion Detection Reaction Observation Platform
• piCopilot-scripts
  • Useful scripts for piCopilot usage across the ecosystem
• piCopilot-unmanned
  • Pi powered Copilot for Unmanned Systems
• piCopilot-wifi
  • WiFi meta-package for piCopilot

• ecosystem
  • Any objects in memory, files, folders or system processes which make up how piCopilot operates
• kBlue
  • The underlying framework for Ubertooth and PostgreSQL interaction
• kSnarf
  • The underlying framework for 802.11 sniffing and PostgreSQL interaction
• pipeline network
  • The IPv4 network between the user and the ecosystem
  • Built on an 802.11 model
  • Can be 802.3 based with minor modifications
  • Responsible for all interactions with piCopilot
    • 3000 - Grafana
    • 8000 - piCopilot-unmanned control panel
    • 8001 - kSnarf and kBlue control panel
    • 8765 - Motioneye
    • 9001 - Supervisor
    • 9090 - idrop visuals

piCopilot expects a secured network. It is not recommended to connect the pipeline network to any network where untrusted users are present or have the ability to sniff traffic. "Pick one thing and do it well".

1. Create the piCopilot image for the Raspberry Pi

• Refer to notes in RELEASE
• Minimum 8GB SD card required
• Burn the image
• Boot the Raspberry Pi

2. When piCopilot first boots it will be running in hostapd mode.

• Set your wifi NIC to 192.168.10.10/24
• Connect to the wifi ESSID called myPi
• The password is piCopilotAP

3. Verify piCopilot-idrop is running and setup external USB NIC for 802.11

• Ports 8001 and 9001 should now be in use
• Plug in USB NIC
• Open a browser and proceed to http:https://192.168.10.254:8001/
• Select NIC prep
• The system will shutdown

For SD card preservation, dphys-swapfile is disabled. It is preferable to offload any swapping to a USB:

1. Become root:

sudo -s
# The password is ~~> notraspberry

2. Plug a USB thumb-drive of ideally at least 4GB in size into the Raspberry Pi and then do:

parted -s /dev/sda mklabel msdos
parted -s /dev/sda mkpart primary 0% 50%
parted -s /dev/sda mkpart primary 51% 100%
mkswap /dev/sda1
mkfs.ext4 /dev/sda2 -m 0

3. Setup /etc/fstab for mounts:

mkdir -p /mnt/usb_storage
echo '/dev/sda1 swap swap defaults 0 0' >> /etc/fstab
echo '/dev/sda2 /mnt/usb_storage ext4 noauto,nofail,x-systemd.automount,x-systemd.idle-timeout=2,x-systemd.device-timeout=2' >> /etc/fstab

4. Turn on swap and storage:

swapon /dev/sda1
mount /dev/sda2

5. You may now plug in an Ubertooth (Optional)

Setup Grafana and visualize your findings

sudo -s
# The password is ~~> notraspberry
systemctl enable grafana-server
systemctl start grafana-server

• Proceed to http:https://192.168.10.254:3000/login
• Login with admin:admin
• Change the default Grafana password if wanted
• Connect grafana to the postgresql database
  • Settings
  • Data Sources
  • Add Data Source
    • PostgreSQL
      • Host --> localhost:5432
      • Database --> idrop
      • User --> root
      • Password --> idrop
      • SSL Mode --> disable
• A sample dashboard for idrop is waiting on you

Benchmark on Raspberry Pi 3 Model B+ as determined by blRip.py w/ no print:

$ python3 blRip.py
Total time: 24.86375856399536
Packets processed: 19235
Packets per second: 773.6159418734769

With the limited horsepower of a Raspberry Pi, any shortcuts we can take are vital to keeping up with the live data flow. By ignoring MAC Addresses that are known and unwanted for monitoring we can cut down on the chaff in the database. To invoke this feature place a file named /opt/piCopilot-idrop/ignore.lst. This file should consist of MAC addresses separated by a newline. For now the only checking done on this is a character count. The case of the string does not matter. MAC addresses should be in colon format, i.e.:

aa:bb:cc:dd:ee:ff

The picopilot-unmanned package has been pre-installed as part of the 20200824 release. In an effort to make the best of both idrop and the unmanned platform in a single image, the decision was made to have the controller running -- but none of the unmanned core services turned on. The following files are of interest to anyone who wants to have the core services turned on at boot:

• /etc/supervisor/conf.d/gsPrep.conf
• /etc/supervisor/conf.d/motionPrep.conf
• /etc/supervisor/telemetry_Service.conf

piCopilot has been tested and verified with the Pixhawk IMU. The unmanned package works seemlessly with either QGroundControl or Mission Planner. For further information on both Ground Control Systems, please refer to their respective websites:

• http:https://qgroundcontrol.com/
• https://ardupilot.org/planner/

• piCopilot wants to be on a 192.168.10.254/24
• Modify /etc/wpa_supplicant/wpa_supplicant.conf accordingly
• Remove the # in /etc/network/interfaces.d/wlan0
• Give /etc/resolv.conf a nameserver

• New image releases can be sporadic
• Interim updates are maintained by the DEBs folder
• Let us determine what versions came with our image:

dpkg --list | grep picopilot

• If the numbers above are lower than the files in DEBs, you have an available upgrade.
• It is recommended to purge piCopilot from the system prior to any upgrade.
• Perform a reboot, ensure there are no .deb files within the current directory and then do:

apt-get purge -y picopilot*

• Once complete verify that /opt now contains only 2 folders; pigpio and vc.

git clone https://github.com/stryngs/piCopilot.git
cd piCopilot/DEBs
dpkg -i *.deb

• Prep the database
  • Database schema changes may occur during upgrades and without warning
  • Backup the data if it matters
  • DROP tables is our friend:

  psql idrop
  DROP TABLE IF EXISTS blue;
  DROP TABLE IF EXISTS dhcp;
  DROP TABLE IF EXISTS main;
  DROP TABLE IF EXISTS probes;
  DROP TABLE IF EXISTS uniques;
  \q
  

• For the page on /, the idrop Service gets confused by the presence of kBlue and how sh.sysMode is used. When enabling kBlue and returning to the main menu, the idrop Service will now read as kBlue. This will be worked out in later releases. To force it proper, cycle the idrop service off and then back on. It will correct by virtue of sh.sysMode flipping through the original idrop logic.
• kBlue makes use of the Ubertooth by way of ubertooth-btle and reading from a pre-recorded stream. The streams default to 20 seconds per stream in real-time. As kBlue currently does not rip stdout for ubertooth-btle, there is no time association just yet. Every packet within a given burst of packets on a given bluesPipe will have the timestamp until a workaround is found.

• Further kSnarf and kBlue method integrations.
• OUI integrations for kBlue module.
• A confirmation for nicPREP or timeSYNC prior to firing.
  • The current workaround is to erase piCopilot browser tab history after firing nicPREP or timeSYNC. This will ensure you do not accidently re-fire it during operational use.

For help with any of the steps or to inquire how piCopilot can support your integration needs for unmanned systems, please contact us via email:

support [at] configitnow.com