and hosts. The type
of each link (wired or wireless, bluetooth, wifi, 3G or 4G)
should be evident from the picture (e.g.,
through solid or dotted line etc).
Explain each line in the output.
First IP address on campus : 172.16.42.10 (wired).
I traced www.york.cuny.edu (198.61.16.7) on this IP address over a maximum hops
of 30.
1 < 1ms < 1ms < 1ms 172.16.42.10
2 < 1ms < 1ms < 1ms 192.168.42.101
3 < 1ms < 1ms < 1ms 198.61.16.7
- Trace Complete -
3 < 1ms < 1ms < 1ms 198.61.16.7
- Trace Complete -
I traced www.york.cuny.edu (198.61.16.7) on this IP address over a maximum hops
of 30.
1 1ms < 1ms 1ms 172.20.0.1
2 5ms 1ms 1ms 172.16.20.1
3 3ms 1ms 2ms 198.61.16.7
- Trace Complete -
Looking at both of the IP addresses, they both took 3 hops to reach the destination. If
you take a look at the first one, the time intervals between data sent and received is less
than 1ms. This is due to the connection being wired to the campus network. The second
IP address on the other hand, was a wireless connection. Therefore, you can see that the
time intervals between data sent and received between each hop is more than the first IP
address. This is because there wasn’t a direct connection to the network, it was wireless
and had more distance to travel to retrieve the information.
3. Use traceroute to any dotcom website hosted in your home country. This might not work
from campus because traceroute is blocked by the firewall so try at home. Then copy all IP
addresses in the trace and do a web search "where is <IP address>". Note and write or draw
the geographic route your query took.
The dotcom website I decided to trace was: www.cricbuzz.com
IP Address Location
192.***.*.* United States, New York, Flushing
10.49.32.1 Private Network
208.59.246.2 United States, Kansas
207.172.15.85 United States, Kansas
198.32.160.27 United States, Kansas
192.***.*.* United States, New York, Flushing
10.49.32.1 Private Network
208.59.246.2 United States, Kansas
207.172.15.85 United States, Kansas
198.32.160.27 United States, Kansas
173.192.18.132 United States, Texas, Dallas
173.192.18.136 United States, Texas, Dallas173.192.18.211 United States, Texas, Dallas
66.228.118.214 United States, Texas, Dallas
208.43.207.2 United States, Texas, Dallas
4. #include <sys/socket.h> // Core BSD socket functions and data structures.
#include <netinet/in.h> // AF_INET and AF_INET6 address families and their corresponding
protocol families PF_INET and P_INET6.
#include <arpa/inet.h> // Functions for manipulating numeric IP addresses.
#include <netdb.h> // Name Resolution.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.