02/19

• Figured out that the ethernet MAC address is different from the WiFi MAC address :O
• Re-registered both comovos (Sam and Sandy) with their WiFi MAC addresses on the CMU-DEVICE network
• Now both comovos have private IP addresses on the CMU network and while laptop is logged into CMU-SECURE wifi, we are able to ping the private IP addresses (meaning that the MAC addresses are now correct and the devices are active on the network)
• However, we are still unable to ssh into the Pis with both:
  • ssh pi@comovosam.wifi.local.cmu.edu
  • ssh pi@172.26.231.148
• Neither works and we don’t know why because the hostnames definitely match the IP addresses (i.e. doing nslookup 172.26.231.148 gives comovosam.wifi.local.cmu.edu
• comovosam’s hostname changed on Pi also with sudo raspi-config to comovosam (used to be comovo1)
• comovosandy has been registered but not yet tested
• Both probably have the same issue though..
• Getting a public IP involves talking to the CMU Help Center (IT?) and may not be worth it/required.
• It should be possible to ssh within CMU network with the private IP (or not…)
• Joe (TA) told us that connecting the Pi to CMU-SECURE would give it a public IP and then we can ssh (we are trying this now)
• Also using online threads that have potential solutions.
• Had class discussion on ch 1-3 reading assignment

UPDATE from 02/19 Meeting 2 at 213 conceptual OH:  It worked woohoo!  We did nothing different.  We are able to ssh into Sam both through pi@172.26.213.148 and also pi@comovosam.wifi.local.cmu.edu.  Will make this work for Sandy on Friday.  In theory this should work since we registered it today.

No idea why it worked in the evening and not in the morning.  We think it might be because it took time to “actually” register (but then ping worked before… so unsure).