Skip to main content

Ping and Trace

    Packets travel through a network by “hopping” from your computer, to your internet service provider, and then on through various other hops until the destination is reached. When looking at the data from the ping command I noticed the Google ping had the quickest response time average at 49ms. The Baidu website had and average response time of 149ms while the Spiegel website had and average response time of 295ms. These numbers are consistent with how I thought they would turn out because the Google website is closer to my home location than the other websites. I was surprised to see that between all three websites there was no packet loss. I would have thought that with the connections to the other websites being so far apart that I would have lost at least a small amount of packet data. 

    After running the “trace route” command the data showed that each website had taken the same number of hops to complete a successful trace. Each website also had a request time out at some point. I did notice that the number of hops and the step at which a request timed out were inconsistent. On a Google trace I typically had a timeout on hop six and ten, but I ran the command a few times and would sometimes find those hops and miss others. Utilizing the traceroute command can be very beneficial when troubleshooting issues with internet connections. If you are unable to connect to a certain website you can run the command and tell where along the way you are losing connection. This command can also tell you whether there is an issue with your internet service provider or not. One reason a ping request might time out is if the host website is down. Another reason may be that the computer trying to send the ping request is not connected to the internet. It should be noted that the traceroute command does not like to be ran through a VPN. I have tried on several attempts to gain a successful trace but failed each time until I shut the VPN off.



Comments

Popular posts from this blog

Peering Points and the Network Application Interface

According to Gibb (2019), “Peering is a method that allows two networks to connect and exchange traffic directly without having to pay a third party to carry traffic across the Internet.” Utilizing a peering point allows users to send a receive data directly to one another without the need to route through other computer networks. Doing so allows for a quicker, more efficient, and safer form of communication.  Researching the total number of active Internet Exchange Points (IXP) proved difficult as it was hard to pinpoint an accurate number. However, according to Rosas (2021), “as of January 2021, of the 630 registered IXPs, 229 are in Europe, 126 in North America, 140 in Asia-Pacific, 96 in Latin America and the Caribbean (LAC), and 39 in Africa.” These numbers are constantly changing as new IXPs are added, and some are removed.  Finding a definitive number of Internet Service Providers (ISP) globally was also difficult to accomplish. Most sources seem to point to the Nations Encyclop

VLAN Aggregation for Efficient IP Address Allocation

The project I chose to summarize on the Internet Engineering Task Force (IETF) website was RFC: 3069, VLAN Aggregation for Efficient IP Address Allocation. Within this project, the authors point out how inefficiently a Virtual Local Area Network (VLAN) allocates IP addresses along with their proposed solutions. I have also attached a diagram showing how the network would look pertaining to this project. Currently, an IP subnet would be made for each existing customer by understanding how many hosts they currently need and may need in the future. Based on that total number, the IP subnet and gateway address would change according to how many hosts the customer requested. For example, if a customer has indicated that they need ten hosts, and they only use five, the additional five that are not in use cannot be used by another customer. An illustration of this is shown below. The proposed solution to this problem is to allocate IP addresses under the same IP subnet and gateway address uti

Access Lists and Capabilities

To implement an access matrix, we must first understand what it is. An access matrix is a protection model within an operating system consisting of objects and domains. The access matrix determines which processes interact with objects within the domain. Objects within the domain can consist of both hardware and software. The lists below show the advantages and disadvantages of access lists associated with objects, and capabilities with domains.  Access lists associated with objects Advantages  Corresponds directly to the user’s needs.  Easy revocation and review of access.  Disadvantages  Difficult to determine access rights for a domain.  Takes time to search the domain for access rights.  Capabilities with domains Advantages  Useful for localizing information for a process.  Secured against unauthorized access.  Disadvantages  Inefficient at the revocation of capabilities.  Does not correspond directly to the user’s needs.  Even though each implementation has its own strengths and w