Size: 1152
Comment:
|
Size: 1377
Comment: adding details to protocol
|
Deletions are marked like this. | Additions are marked like this. |
Line 18: | Line 18: |
* Note presence/absence of splash and any self-identification thereon * Note local network |
* 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. |
Line 22: | Line 22: |
* Keep an eye on kismet to/from to see if you see more new BSSIDs and check them out as well |
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.
- 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
- Keep an eye on kismet to/from to see if you see more new BSSIDs and check them out as well
Volunteers
RussellSenior (also leader of this AmazinglyFunEvent)
<add-your-name-and-area-of-interest-here>