Differences between revisions 5 and 8 (spanning 3 versions)
Revision 5 as of 2006-09-15 14:53:22
Size: 1611
Comment: added more protocol detail
Revision 8 as of 2006-09-16 15:23:34
Size: 1600
Editor: c-24-22-73-65
Comment:
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:''' Sometime Soon, To Be Determined [[BR]]
Line 5: Line 4:
Line 8: Line 8:
Line 21: Line 22:
   * 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 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.
Line 26: Line 27:
'''Volunteers'''
Line 27: Line 29:


'''Volunteers'''
Line 32: Line 31:
 * <add-your-name-and-area-of-interest-here>  * MichaelWeinberg
 * SethShikora
Line 35: Line 35:
[CategoryMeetingNotes]  [CategoryMeetingNotes]

Location: All Around the Portland AreaBR Date and Time: Sometime Soon, To Be Determined BR

Agenda

  • 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
    • 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

Volunteers


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