Differences between revisions 12 and 15 (spanning 3 versions)
Revision 12 as of 2006-09-21 01:59:03
Size: 2025
Comment: added some details on protocol, maybe Caleb can clarify
Revision 15 as of 2006-09-25 00:22:06
Size: 2211
Comment: add link to data from trial run
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
'''Location:''' All Around the Portland Area[[BR]] '''Date and Time:''' Sometime Soon, To Be Determined [[BR]] '''Location:''' All Around the Portland Area[[BR]] '''Date and Time:''' September 30th, Time and Place TBD [[BR]]
Line 35: Line 35:
 * CalebPhillips  * CalebPhillips (area of interest: desperate and unreasonable desire for organization)
Line 38: Line 38:

 * [http://www.personaltelco.net/~caleb/kismet/2006-09-20/ Data from Trial Run on 2006-09-20]

Location: All Around the Portland AreaBR Date and Time: September 30th, Time and Place TBD BR


  • Visit, test and collect information at locations identified as once active Personal Telco nodes.

Protocol (tentative)

  • Train in Protocol
  • In teams of 2 or 3, dispatch to each identified location. Identified locations are found here: PersonalTelcoBssids. Each location will have a sheet of paper with a map.

  • One laptop running Kismet or equivalent network stumbler, with GPS if possible.
    • Keep an eye on kismet to/from to see if you see more new PTP BSSIDs and check them out as well
      • CalebPhillips figured out a good way to do this: in kismet, sort by SSID, scroll to the www.personaltelco.net section and look for ! which indicates new packets. beware that some nodes leave off the www part of the SSID.

    • Drive around a few neighboring blocks to collect relative signal strength data, which will help in triangulating network location
    • At the end of the day, upload stumbling data to wigle (or give to Russell to do so).
  • Another laptop available to connect to the node
  • At each location,
    • Discover AP presence/absence
    • For each PersonalTelco-related AP present:

      • AP SSID
      • AP BSSID
      • Connect
      • Note presence/absence of splash and any self-identification thereon. If captive portal indicates usage over time (N authentications since date X), note that as well.
      • Note local network: DHCP server IP, assigned IP.
      • Identify the upstream IP using http://www.whatsmyip.org or equivalent

      • If possible, identify the lat/long or address of the AP



NodeAudit2006 (last edited 2007-11-23 18:01:04 by localhost)