Locating hosts by TULIP (Trilateration Utility as long as Locating IP hosts) Purpose Goals Uses of Locating Hosts How to get the location

Locating hosts by TULIP (Trilateration Utility as long as Locating IP hosts) Purpose Goals Uses of Locating Hosts How to get the location www.phwiki.com

Locating hosts by TULIP (Trilateration Utility as long as Locating IP hosts) Purpose Goals Uses of Locating Hosts How to get the location

DiGiovanna, James, Film Critic has reference to this Academic Journal, PHwiki organized this Journal Locating hosts by TULIP (Trilateration Utility as long as Locating IP hosts) Prepared by: Les CottrellSLAC, Faran JavedNIIT, Shahryar KhanNIIT,Umar KalimNIIT Internet2 fall members meeting San Diego, October 2007 http://www.slac.stan as long as d.edu/grp/scs/net/talk07/i2mmfall07.ppt Purpose Geo locate a host given its name or address Uses ping (RTT) measurements from l in addition to marks l in addition to marks at known locations worldwide RTT roughly proportional to distance in many cases Distance (km) = alpha RTT (ms) Velocity light in fibre ~ 0.6c or 1ms as long as 100km. Use min RTT to reduce effect of queueing Using distance from RTT, triangulate to get lat/long Goals Plat as long as m agnostic (Java & Perl (CGI)) Open, non-proprietary (cf. Traceware, Edgescape) Minimize security concerns Include developing regions Sustainable robust service Minimize manual ef as long as t (keep databases current) Provide an API to enable other applications We also wanted to verify the locations of the hosts in the PingER database.

American InterContinental University - Atlanta US www.phwiki.com

This Particular University is Related to this Particular Journal

Uses of Locating Hosts Choose content to send (e.g. language, local store) Security: pin-point suspicious hosts Where to get replicated service (e.g. Grid) In as long as mation as long as maps (e.g. visualroute) Efficiency of routing For Digital Divide & world-wide collaborations How to get the location Database (e.g. DNS, whois, Geo IP tools) Hard to keep up, may require subscription, maybe inaccurate, out-of-date or incomplete Traceroute in addition to heuristics on names (Visual traceroute) RTTs (e.g. Octant from Cornell, Constraint based Geolocation from Belgium/Boston U) Neither are active any more (student projects pointing the way) They are complementary Each has own strengths in addition to weaknesses Could/should be used together to validate each other in addition to make corrections. Simple Methodology (1) Client loads (Java Webstart), runs Java applet gets target from user Client requests Reflector to get pings to target Reflector requests L in addition to marks to ping target, Reflector L in addition to marks Client Target Ping target (web server running CGI script)

Simple Methodology (2) Client analyses data, Reflector send RTTs back to Client L in addition to marks send results back to Reflector Reflector L in addition to marks Client Target Ping target (web server running CGI script) visualizes in addition to provides to user L in addition to marks Want good geographical coverage as long as world. Need to be reliable, answer No connection, timeouts, 100%loss (24 excellent PlanetLabs) Respond quickly Not satellite connection Not a proxy PlanetLab ~ 150 l in addition to marks Mainly in N. America in addition to Europe SLAC/PingER reverse traceroute servers ~ 60, but more diverse, see www.slac.stan as long as d.edu/comp/net/wan-mon/traceroute-srv.html Security (lots of concerns) Can be used as long as DoS attacks against a target Looks like a potential scan of the target vs many hosts Target ICMP replies to a large number of hosts CGI scripts (Perl) needs to be well vetted as long as holes Ability to discover & then blackhole abusers Only one TULIP client per host L in addition to marks in addition to reflector both limit the number of running requests Centralized logging of all requests in addition to results, plus analysis Look as long as anomalies Also discovers what l in addition to marks are failing, who is requesting Possible privacy problems if locate a person’s host accurately (could add fuzz)

Problems Geostationary satellite connections 24Kmiles => RTT >370ms, heavily used in C. Asia in addition to Africa IP name refers to multiple hosts (e.g. Google, Akamai, root name servers) in many locations Hosts move, have proxies etc. Indirect routing so RTT !~ distance E. Asia vs. Australia seen from US Security concerns Duration as long as measurements (50 seconds to complete, results start arriving earlier) Optimizing of parallel requests from reflector, timeouts, tiering, remove poor l in addition to marks Optimizing alpha in distance (km) = alpha RTT (ms). Optimizing the choice of tier 0 l in addition to marks, reliable & at edges, want very few, yet few false positives or mistakes N. America: SLAC/CA, BNL/NY, AMPATH/FL, TRIUMF/CA(Vancouver), Winnipeg/CA, Houston, Saint Louis, Chicago Europe: CERN/CH, ICTP/IT, DL/UK Demo of early version www.slac.stan as long as d.edu/comp/net/wan-mon/tulip 2 sets of l in addition to marks: PlanetLabs & SLAC/PingER type Enter host name or address & Locate Site Raw results in Ping Results window Visualize results in map Evaluation of early version Use ~600 PingER hosts with “known” lat/long Hosts in over 130 countries Also validates PingER data 50% accurate to within 200 km, 70% within 1000km Ouch, not very successful, worse with RTT Need l in addition to marks close to targets

Improvements Add more l in addition to marks as long as better coverage: PlanetLab & more SLAC l in addition to mark deployment (especially in developing world) Underst in addition to outliers, correct PingER dB Outliers: Multi-homed, e.g. yahoo, root servers, Move: e.g. supercomp Not at site of ASN: e.g. 134.79 SLAC host in Arizona Indirect routing: SFO-LA-SEA-VIC Alpha = 48.54 RTT/Dist (km/ms) Look at Alpha Set alpha to right value to get correct distance from RTT in addition to look at distributions Done as long as major US to N. America & major Europe to Europe sites In progress Have stable version 1 www.slac.stan as long as d.edu/comp/net/wan-mon/tulip/ Adding: More l in addition to mark, filter out non-working instances Integrate PlanetLabs & other l in addition to mark databases Improved map visualization in addition to zoom Optimizing timing parameters (parallel streams, timeouts, l in addition to mark choices, alpha ) Faster l in addition to mark response GeoIP Tool estimates http://www.geoiptool.com/ Tiering Redo evaluation, compare with other methods

Tiering Want to reduce the traffic hitting a target First find region target is in (tier 0 search) Use few best l in addition to marks in region Highly responsive, at edges of region Determine most likely region (N. America, Europe, the rest) Then if client wants more detail use all l in addition to marks in region to pin-point target Take 1/10 time as long as tier 0s vs all as long as N. America More in as long as mation/Questions Acknowledgements: PlanetLab, SLAC reverse tracroute servers hosted in Africa, E. Asia, Latin America, Middle East, Russia, S. Asia TULIP Home Page: http://www.slac.stan as long as d.edu/comp/net/wan-mon/tulip/ PingER (driving reason as long as tool) www-iepm.slac.stan as long as d.edu/pinger, TULIP 1st Prize at All Asia Softec 2007 http://www.niit.edu.pk/press/pages/releases/tulip.php

DiGiovanna, James Tucson Weekly Film Critic www.phwiki.com

DiGiovanna, James Film Critic

DiGiovanna, James is from United States and they belong to Tucson Weekly and they are from  Tucson, United States got related to this Particular Journal. and DiGiovanna, James deal with the subjects like Motion Pictures

Journal Ratings by American InterContinental University – Atlanta

This Particular Journal got reviewed and rated by American InterContinental University – Atlanta and short form of this particular Institution is US and gave this Journal an Excellent Rating.