BusyBear log

BusyBear Log

Link to Project Page

[View Project Page]

Week of 1/28/19 (1)

- 01/28

• Whole Group: Had a group meeting with Profesor Feher and discussed possible implications of our busybear concept. In addition, we researched similar projects and found a variety of sources. (https://www.crc.id.au/tracking-people-via-wifi-even-when-not-connected/ and https://www.raspberrypi.org/forums/viewtopic.php?t=47059) - 1 hour
• Whole Group: Met with David and further went over the specifics of our project including discussing the possibility of either using wifi based or camera-based system. In addition, David provided the link to some working projects that also used Arduino as well as a tutorial (https://picar.readthedocs.io/en/latest/chapters/introduction.html) - 1 hour

-01/29

• Whole Group: Looked more into proof of concepts and specific tutorial on how to track devices using wifi/Bluetooth and found a variety of in-depth albeit confusing sources. (https://makezine.com/projects/build-raspberry-pi-network-scanner/ and https://www.youtube.com/watch?time_continue=1&v=fmhjtzmLrg8 and https://zone13.io/post/wifi-monitoring-using-raspberry-pi/) - 1 hour

-01/30

• Whole Group: Met to try and finalize general goals and project. We worked on our project proposal on our Wiki page. - 2 hours

-01/31

• Allison: Finished up the project proposal by inserting the Gantt Chart into the Wiki page. - 30 minutes

-02/1

• Thomas and Tom: Worked on the nightlight and established a successful prototype. - 30 minutes

LED is off when lights are on

LED is on when the sensor is covered

Goals for Next Week:

1. Demonstrate the Night Light
2. Start working on setting up an environment for the Pi
3. Investigate networking and image collection for the Pi

Week of 02/04/19 (2)

- 02/04

• Whole Group: Had meeting with Professor Feher and TA David to discuss current progress and future goals. Determined that the goals for next week will be:

1. Get Pi going and ready for project
2. Complete Blackjack website
3. Complete any tutorials for Pi
4. Download Stretch and use Etcher
5. Find a file for 3D printing a Pi + Camera case
6. Research networking
7. Consider other locations to test

- 45 minutes

-02/05

• Tom and Allison: Downloaded Python, set up an Amazon Web Services account, and began the Blackjack tutorial. - 1 1/2 hours

-02/06

• Allison: Finished setting up the MySQL workbench by connecting to the Amazon Web Services account. - 30 minutes
• Whole Group: Continued working on the Blackjack tutorial and began working on the SSHing the Raspberry Pi Tutorial. We ran into many roadblocks and had to email Ethan several times. Between waiting for software to download and browsing help forums we spent a lot of time away from our actual objectives. Found a 3D printing design file for a Raspberry Pi Case with Camera Mount. https://www.thingiverse.com/thing:1411080 - 3 hours

-02/08

• Tom: Researched more about the ability of the Pi to monitor devices via WiFi on the tutorials we found. Found commands that returns MAC Addresses, but none belonged to phones or recognizable devices that would be found on a student. Other tutorials necessitate some sort of network adapter or WiFi dongle that are capable of "monitoring mode". -1 hour
• All: Worked on powerpoint presentation -1 hour

Week of 02/11/19 (3)

• Whole Group: Had meeting with Professor Feher and TA David to discuss current progress and future goals. Determined that the goals for next week will be:

1. Continue working on Blackjack tutorial
2. Construct a blinking-LED circuit with the Pi
3. Meet sometime during the week to discuss networking
4. Work through a Pi camera tutorial

- 45 minutes

-02/11

• Whole Group: Spent some time updating the Powerpoint. More bullet point orientated, changed challenges, and added a resource/helpful links slide - 30 minutes
• Thomas: Continued following the blackjack tutorial and ran into many problems especially regarding how to use the command line. Communicated extensively with Ethan to try and resolve problems - 1.5 hour

-02/12

• Tom: Got an LED to blink using the Pi using [Blinking LED] - 30 minutes

LED is off with no input

LED is on when button is pressed

-02/14

• Tom: Altered the LED blink code to work with user input (a button) and uploaded to GIT. Also made a code for the camera to take n number of pictures overtime just to see if I could get the camera working. Also added to GitHub repository - 1 hour
• Whole Group: Met with Ethan to work pass roadblocks in Blackjack. Talked about Blackjack's parts and functions as well as how our project might look like the big picture - 1 hour
• Thomas: Finished up BlackJack and was able to fully run the program on localhost. Then began working on the Lightsail Tutorial and how to migrate our server files to an AWS hosted service. Made progress and purchased a server but encountered problems regarding downloading nodejs to the server as well as using ssh to reconnect to the server after it timed out. -1.5 hour

-02/15

• Whole Group: Had a meeting with Prof. Feher, David, and Ethan to talk about networking. We went over typical protocols, specifically ARP, and how our project fits into the structure of the internet as a whole. Went over possible methods to talk to devices like ping. -1 hour
• Thomas: Made more progress on BlackJack. Recreated many instances to try and solve issues regarding ssh and found a solution on my third attempt. Additionally was able to upload server files and attempted to run them with pm2 but was give an errored message immediately after running. - 1.5 hour

-02/17

• Tom: Explored different techniques for possibly obtaining MAC/IP Addresses and the issues/potentials of each. Refer to resource links on project page for some of the links used. Also used the command line help menus and a lot of experimentation to see what would work.
  • ping: Was able to successfully ping my phone. However, when trying to ping a range, it would get hung up every time it tried to ping an unreachable IP address even with a -w or -W parameter. Additionally, to scan through all possibly endings on the WiFi seems like it would take over a half-hour, but uncertain. [pinging my phone]
  • arp: Used directly from pi w/o any package installations but was only able to get a single address, presumably the router itself? [arp display]
  • arp-scan: Package that provides a more options working from the ARP layer. At first seemed very promising because it returned numerous IP & MAC addresses. However, I could not find my phone listed and it seems fairly hard to discern what devices are even being displayed. [arp-scan display]
  • fping: Another package extension of a normal ping. Allows us to ping a range of addresses quickly and return if the device is reachable or not. Downside is there is no MAC Address and no way to discern what the device is. [fping display 1] [fping display 2]
    • To experiment, I let fping run from 172.27.0.0 to 172.27.255.255, which seems to be the range of all devices connected to a WUSTL network. First of all, it is definitely not local (router dependent), because there is no way there is this many reachable devices in range presumably. Additionally, the fping took 21 minutes. [fping max range]
  • nmap: Another package that has an overwhelming amount of methods and documentation. So far have only found a way to return IP addresses (no MAC addresses), but also provides some description of the device. Was able to find my phone but not sure if nmap works locally or across the network. [nmap display]
    • Did the same as fping, again it's clearly doing a network wide scan. Too long and too many hosts. 7100 hosts after 49 minutes [nmap full scan] -2.5 hours

• Tom: Tried to work through a tutorial with the network adapter. Hit a lot of roadblocks and searched many forums trying to correct errors. Workarounds and other driver installations, GitHub projects, etc. did not work. In the end, I'm fairly confident that we have v3 of the adapter which apparently does not support monitoring mode, only v1 does. We need new network adapters to try this route. - 1.5 hours

• Thomas: Attempted to install and run nodejs/pm2 on a personal computer but wasn't successful due to a lack of continuity between ubuntu command line and mac terminal however working to resolve misunderstanding in order to be able to test that the server file works properly - .5 hours

Week of 2/18/19 (4)

-02/18/19

• Whole Group: Weekly meeting to discuss goals:

1. Finish Blackjack
2. Work on primitive website form
3. Possibly design code for the server

-02/19/19

• Tom: Made a tentative website flowchart and posted on project page. - 30 minutes

[Category:Logs]]