Daily Report 4/18/19

Today in class I spent some time finishing my one-pager for people to read and getting a copy printed and ready to go. I also helped Daniel pick out some parts for both a super over the top system and a more moderate reasonable one. He wants this computer so he has some processing power when he goes off to college.


Weekly Report 12/8/18

This week our class time was mainly taken up by the video me and my group decided to embark on producing. If you want to see the day-by-day of the filming, look at my other weblogs. The long and the short of it though is we shot it at school, and I edited the thing at home. Overall I think it went very well. Link to video:


Daily Report 12/7/18

Today in class I showed some other people the video me and my group made, and then followed that by watching a few other peoples videos. This was a short class day, so there wasn't really any time to do anything meaningful. But watching Morgan and Ethans videos was pretty fun and interesting.


Wireless lab

1. WAN setup: login via wifi, set the WAN address (see below for definitions of WAN)

2. LAN setup: Connect WAN port to ethernet, login via elab network, check speed at

3. Wireless options
2.4 gHz has 11 channels, 20-40 mHz wide
5.8 gHz has many more, 20/40/80/160 mHz wide, two sets of channels ~30, ~150

Types of network:
a=5.8 gHz
b, g=2.4 gHz, b goes 11 mb/s, g goes 54 mb/s
n=is a combination of a and g, 150mb/s
ac=is the latest one, max speed is around 867 mb/s, fat channels

Check your wireless status with option-fan on macs
Look for:
channel #
channel width

4. Access control
MAC address
hidden network

5. NAT/DHCP, port forwarding
If a client on the LAN uses your router as a gateway, you can forward traffic from the WAN to that machine specifically, like a web server.
This is based on ports (like doors):
80 = web
8000, 8080, other web ones
548=apple file sharing

Next steps:
DD-WRT on linksys routers
ubnt wireless networks


Wireless stuff

Access point basics:
WAN=Wide Area Network, the outside world (a circle on the airport base stations)
LAN=Local Area Network (e.g. the inside)
Your access point will act as a router, connecting these two networks.
On the outside, your router will have a specific address, like 10.14.251.x
On the inside, it will create a set of addresses, in our case, 192.168.1.x
Computers on the inside (wired to the three ports, or wireless to your network) will get 192.168.1.x addresses, and see the router as their "gateway"
The DNS setting will be set on the outside, telling the access point who to ask for directory services (like a phone book)

Router setup:
Set the IP address to the address given on the board for your access point/router
The gateway will be
The DNS will be the same, or You can also list (google)
The netmask on the outside (WAN) will be, giving us 254x254 address possibilities.

Task one:
Connect to your access point by wireless network, leaving the password the same.
Configure the WAN address, plug the WAN side into the elab network, check to see if your router is working.
Check your new wireless IP address, it should be something like 192.168.1.x.
Browse to some place on the outside, like
Check with or

Task two:
Make your network hidden
See "wireless options"

Task three:
Block some person from using your access point as a router based on MAC address
See Network setup, "access control"

Task three:
Setup inbound port mapping, using port 80 to some address specified.
Look for Network Settings, the lower box, add the address of the machine on the inside and the port (80 for web)
Browse from the elab side of the network to your access point WAN address, see if you get the web server on the inside. This is useful for games.

IP masquerading
routers vs. gateways
apache web server startup
dhcp vs. static addresses
ports: 80
html basics: index.html is the default page on web servers
(later: much more on servers, ports, html and net neutrality)

Ports: computer "doors"
portscan: what doors are available
Port 80: default web server port
test on your network with and your 10.14.8.x address
try with the 80 and without

use IPNM to test yours, and others
test is this? how could you find out? try dns

router setup:
Airport extreme defaults to DHCP (dynamic host configuration protocol)
how is this different from static? why is it useful? where would I find it?
two sides to every gateway/router: the WAN side (wide area network=outside) and the LAN side (inside)
We will setup your routers to pass traffic from the HPA LAN (our WAN) to your private LAN (192.168.1.x). This means only YOUR computer, not the shared switch on your desktop. Why?
How will you know it is working?

See previous weblog for router setup notes, as well as the wiki here:

"DHCP wired" location, wireless disabled, can you browse the web?
Look at the settings the router gave you...
Your mind is probably constructing network diagrams, try writing these down. It's what I use to fall asleep at times...
Try now with a static address (static and DHCP can co-exist, but you can only have one DHCP server on the LAN)
Try either a 192.168.1.x address (your crossover network setting)
You will have to make sure the router is giving out addresses on the 192.168.1.x network.
NAT and Port forwarding (also known as inbound port mapping).

NAT: your computer uses the router to translate your address into a web request to the server, which then passes the response back to you, Network address translation (NAT)

Port forwarding/inbound port mapping: calls to the outside WAN side of the router are passed to some FIXED address on the LAN.
You have to have a fixed address on the LAN for the router to know who to send the packet to.

Test this on your private network with your apache web server.

Play around with this in the class, looking for others' routers, and your web server
You can also look under Utilities for Activity monitor, it should show folks looking at your web page
If you are really curious, you can go to console and see who exactly is looking at your web pages...
(look into the tail -f command for future reference)

Next steps: port forward 548, 22 and others...what do you see?
How could this be useful at your home/dorm?


Unix stuff

Here is a review of where we are so far:
  • fsck -yf file system check
  • cd change directory
  • ls list
  • pwd print working directory
  • ssh secure shell
  • say say something
  • mkdir make a directory
  • less look into it (also use more)
  • who who you are
  • last who last logged in
  • ctrl-z halt

First thing today, log in to Jody or Kai's machine as victim or herobrine and say a message with your name in it.

Module 2: wild cards, man pages, deleting files
This is how wild cards work:
Instead of typing out herobrine, you could type
just make sure that nothing else matches the h part.
Another example:
These files are in a folder called test:
malcolm mary tom
if you type
rm m*
it will delete mary and malcolm
if you type
rm mal*
it will delete only malcom
if you type
rm *
it will remove everything.
You can also use this to delete certain types of files (jpg, txt, mp4)
rm *.jpg
will remove every jpg file in the folder

Now you try it:
  1. open terminal
  2. navigate to your desktop (remember, it is called Desktop)
  3. create a folder using mkdir called test
  4. navigate into that folder
  5. create three text files using sudo nano, the first will be called malcolm, then mary, then tom
  6. read each one using less or more
  7. take a screenshot of this folder from the gui (graphical user interface), command-3 takes a screen shot, command-4 is a screenshot of only what you select.
  8. copy this screenshot into your weblog, so you can remember how you did this
  9. remove one file at a time using the rm command, take more screenshots
Ok, at this point, you can navigate around, login to remote computers, create and delete text files.
What's next?
Module 3: Internet
Your computer needs 4 things to be able to get onto the internet:
IP address, example
Subnet mask, example
Gateway/router, example
Domain name server (DNS), example

Here's what each one does:
IP address:
All traffic on the internet or local area network (LAN) is in the form of packets of information, like mail envelopes with a letter inside. Each letter you mail has two important things: the address you want it to go to, and the message inside the envelope.
TCP/IP is the format of these, which stands for Transmission control protocol and internet protocol.
The TCP part is the message, and the IP part is the envelope, with an IP address on it.
Check the IP address of your machine:
From the GUI: open system preferences, network
From the terminal: type ifconfig

Subnet mask:
Imagine you want to stay in one of two large 254 room hotels. One has long hallways, and very few floors, the other has many floors, but short hallways.
If you want to sleep, you don't want many people walking down the hall in front of your room. You want many floors with fewer rooms per floors.
This is what subnet masking does on a network. Each of the four segments can hold 254 addresses.
At home, you probably have a network that looks like this:

This means that the last zero can hold up to 254 addresses (from to
HPA has this sort of mask:
which means that
is the elab, which can have 254 x 254 addresses
It makes for a quieter network, also providing some security as others cannot see you easily.

This is the gateway for all of your traffic, usually the access point at your home. The technical difference between these words is that a router routes traffic between two networks of the same type (like ethernet), while a gateway is between different types of networks (like a cable modem or DSL gateway)

Domain name server:
This is the computer on your network or outside that translates names into numbers, like a digital phone book.
Try this in terminal:
  1. when you get the address, write it down
  2. open a browser
  3. go to
  4. now go to the numbers you wrote down.
  5. Try this with another name, either on campus or off
Ping and traceroute:
Imagine you want to find out if a machine is responding (you can block this by using "stealth mode")
In terminal ping one of the IP addresses in your class
ping an address out on the internet
what is the difference?

now try this:

It should give you a trace of the path your connection took.
Try this with other addresses on and off campus.

Say you want to find out the name of something, or the IP address from the name.
try this:
(you will get a funny > sign)
what do you get?
where is this machine?
Try again using as the server

The best use of this is to find out what OTHER people might call a machine.
We have several DNS servers on campus, the main one is at
Others to try:

you can get out by typing
or control-z (halt)



IPNM 2.7:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist SYSTEM "file://localhost/System/Library/DTDs/PropertyList.dtd">
<plist version="0.9">
<string>2f12c691 ef2c1a46 ed36d1c2 1ad56cfd 27f87fcb 605a3d56</string>
<string>Bill Wiecking</string>
<string>This file contains a licensed registration code and is Copyright 2002 by Sustainable Softworks Inc. Unauthorized copying and distribution is expressly prohibited.</string>



Here's what you'll need to include in your project proposal

Proposal Rubric:
Abstract: short summary of what you hope to research
Title: the title of your proposal
Background: any information we'll need to understand your proposal
Purpose: the goal of your project
What will you measure, research or learn?
How will you measure it, what will success look like?:
Tools/resources needed: people, stuff, places to work, local resources, collaboration resources:
What you used/need?
Why is it credible or needed?
How are you going to use it/was it used?
Impact and legacy (HPA, local, global): what legacy will this leave? how will this impact HPA, our community and the world?
Course Timeline:
Meet with mentor in person and/or email, discuss and develop abstract proposal
(most of you have done this already)

Daily/each class (due by 9 PM that night)
Weblog entry: what you did, what worked, what did not, why, next steps

Weekly (due 6 PM each Saturday):
Weekly summary report: what worked, what did not, what you plan next week, what will you need, due at 6 PM every Saturday.

Quarter summary weblog entry, quarter video (2-3 minute summary of progress)

Group presentations
Due dates:
September: proposal abstract due
Q1 final: video and Q1 summary due, wiki complete
Q2 final: video and semester summary due
S1 final: meet with mentor, meet with review team, present to small group on campus
Q3 final: video and Q3 summary due
Q4 final: year summary video due, year summary due online
Year final: meet with mentor, meet with review team, present to larger formal group


2018-2019 project pages

We'd like to hear your ideas for your projects this year, including a secondary backup project.
Below is a list of projects ongoing, let us know if something on this list appeals to you.
We'll formalize the proposal process next week, for now let's just brainstorm.
Mr. Bishop and I will be collaborating on period F of ISR, and Dr. Bill will be hosting you fine folks for period G.
Let us know how we can help, our emails are:

ISR/elab project list
New projects: 2018-2019
Vognet network:
Effective classrooms audit: sound, air quality, lighting
Vog and PV production study
sound study-elab main hall
2018-2019 ideas:
IFTTT automation
homekit automation and integration
xgrid cluster computing simulation
MFI sensor integration-classroom automation
NASA robotics challenge
NASA BASALT collaboration (Mars lava research project)
Campus access systems sensor tags-CAO
EMC-NASA mission VIIa
Elab radio station: collaboration with NASA satellite and deep space systems
Ongoing projects:
Human machine interfaces:
Brain wave headsets (EEG)
what happens where in the brain
psychological studies
brain to machine control
emotiv, neurosky
EKG/EMG analysis
muscles and heart action analysis
backyard brains
relaxation, study effectiveness
Virtual Reality headsets
Oculus rift headset/hand controls
Digital media vizualization
immersive remote viewing
integration of VR and biosignals
Virtual reality
Pix 4d visualization
Drone mapping/visualization 3D/2D
Drone control and navigation
Virtual reality immersion
Keck observatory
Video editing
3D printing
Machine learning/AI
Facial recognition
Data analytics
Computer tech
Wireless networks
RFID tracking
Computer repair/maintenance
Micro/embedded computers
Raspberry Pi
Minecraft educational platform
NASA collaboration
energy, water, environment
EMC control system
NASA habitat
Acoustics analysis
Effective classrooms
Energy Audits
Electric vehicles
Earthquake/Tsunami network analysis
Microgrid analysis
Food miles analysis
Kohala shore research station
seismic studies
whale studies
Radio telescope
FCC licensing
Shortwave listening station
Space weather
Elab radio station KH6HPA
Elab internet radio station
Satellite communications
GMO studies
3d prosthetics
Bio engineered reconstructive devices
3D printing/modeling
Laser cutter
Shop skills
Digital media
digital music creation
Video editing
Sound recording/analysis
Interview skills
Storytelling skills
Podcast project
Website creation, navigation, analytics


ISR notes


  • proposal
  • weblogs-daily/weekly/legacy
  • wiki
  • status Q1
  • preso S1
  • status Q3
  • Final preso S2
  • weblog: 9 points:
  • content, documentation, depth

  • video snapshots Q1/Q2/Q3/Q4
  • elevator speech
  • posters
  • check out: