Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/devprabal/cnlabassignment1-solutions
https://github.com/devprabal/cnlabassignment1-solutions
Last synced: 3 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/devprabal/cnlabassignment1-solutions
- Owner: devprabal
- Created: 2018-08-19T10:24:51.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2018-08-19T19:22:21.000Z (over 6 years ago)
- Last Synced: 2023-10-20T19:18:29.192Z (over 1 year ago)
- Size: 343 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
>**Instructions**
>
> This markdown file is prepared using [Online Markdown Editor](https://dillinger.io/). It requires certain files to display images within it. It is therefore advised to view this markdown here on github repo or clone the entire repo to your local machine.
>
> The source codes and related csv/spreadsheet files which were used in the making of this assignment are included in a seperate repo. It is recommended to have a view on this [repo](https://github.com/devprabal/CNLabAssignment1-source).
>
> The answers are provided below.
## Q1
### information about 5 hosts selected
| | www.facebook.com | ligben.io | https://distrotest.net/ | www.gmail.com | www.github.com |
| --- | --- | --- | --- | --- | --- |
| 0 | edge-star-mini-shv-01-frt3.facebook.com | no-reverse-dns-configured.com | 77-64-170-23.dynamic.primacom.net | fra15s17-in-f5.1e100.net | lb-192-30-253-113-iad.github.com |
### host1 stats
| | time of day | rtt avg |
| --- | --- | --- |
| 0 | 16 | 97.56775 |
| 1 | 23 | 85.71065 |
| 2 | 0 | 85.69140 |
#### host1 packet loss > 0% stats
none
### host2 stats
| | time of day | rtt avg |
| --- | --- | --- |
| 0 | 16 | 478.12775 |
| 1 | 23 | 475.36325 |
| 2 | 0 | 59.20005 |
#### host2 packet loss > 0% stats
| | name | IP address | % packet loss | rtt min | rtt avg | rtt max | rtt mdev | time of day | packet_size |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 0 | no-reverse-dns-configured.com | 81.171.22.7 | 60% | 644.095 | 673.385 | 701.591 | 24.476 | 16 | 64 |
| 4 | no-reverse-dns-configured.com | 81.171.22.7 | 40% | 605.473 | 677.117 | 806.046 | 71.284 | 16 | 64 |
| 5 | no-reverse-dns-configured.com | 81.171.22.7 | 30% | 545.013 | 637.961 | 746.901 | 60.038 | 16 | 64 |
| 6 | no-reverse-dns-configured.com | 207.244.67.218 | 10% | 518.437 | 608.082 | 692.761 | 60.912 | 16 | 64 |
| 10 | no-reverse-dns-configured.com | 207.244.67.218 | 10% | 549.187 | 590.188 | 642.977 | 29.260 | 16 | 64 |
| 13 | no-reverse-dns-configured.com | 64.32.8.68 | 60% | 70.726 | 70.760 | 70.797 | 0.025 | 16 | 64 |
| 14 | no-reverse-dns-configured.com | 207.244.67.218 | 30% | 711.798 | 816.819 | 1002.714 | 88.342 | 16 | 64 |
| 16 | no-reverse-dns-configured.com | 64.32.8.68 | 50% | 70.683 | 70.769 | 70.814 | 0.295 | 16 | 64 |
### host3 stats
| | time of day | rtt avg |
| --- | --- | --- |
| 0 | 16 | 130.02690 |
| 1 | 23 | 131.12605 |
| 2 | 0 | 130.91160 |
#### host3 packet loss > 0% stats
none
### host4 stats
| | time of day | rtt avg |
| --- | --- | --- |
| 0 | 16 | 60.43605 |
| 1 | 23 | 53.49640 |
| 2 | 0 | 32.09665 |
#### host4 packet loss > 0% stats
none
### host5 stats
| | time of day | rtt avg |
| --- | --- | --- |
| 0 | 16 | 597.88420 |
| 1 | 23 | 32.00675 |
| 2 | 0 | 31.17940 |
#### host5 packet loss > 0% stats
| | name | IP address | % packet loss | rtt min | rtt avg | rtt max | rtt mdev | time of day | packet_size |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 1 | lb-192-30-253-113-iad.github.com | 192.30.253.113 | 10% | 543.271 | 596.078 | 646.322 | 37.860 | 16 | 64 |
| 5 | lb-192-30-253-113-iad.github.com | 192.30.253.113 | 10% | 515.742 | 563.243 | 611.480 | 29.173 | 16 | 64 |
| 10 | lb-192-30-253-113-iad.github.com | 192.30.253.113 | 10% | 545.990 | 626.497 | 688.748 | 40.341 | 16 | 64 |
**Four Causes of Packet Loss**
1. Link Congestion
Your data must travel through multiple devices and links during its trip across your network. If one of these links is at full capacity when your data arrives, then it must wait its turn before being sent across the wire (this is known as queuing).
2. Device (Router/Switch/Firewall/etc.) Performance
If your bandwidth is adequate, you can still face an issue if your router/switch/firewall is not able to keep up with the traffic.The traffic is reaching the device, but the device's CPU or memory is maxed out and not able to handle extra traffic.
3. Software issues (bugs) on a network device
You must upgrade the software on the affected device(s).
4. Faulty Hardware or Cabling
The faulty hardware must be replaced, or the fault link must be repaired.
### geographical distance affects avg rtt
There is a positive correlation between distance and RTT. There are a number of reasons for this. For example, an increased hop count. The packets have to go through more routers, at each router there may be a delay, therefore more routers, the longer the RTT.
As can be seen from the stats that the server of host2 (libgen.io) is farther than the rest.
### time of day affects avg rtt
### change in packet size affects avg rtt
| | name | IP address | % packet loss | rtt min | rtt avg | rtt max | rtt mdev | time of day | packet_size |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 0 | lb-192-30-253-113-iad.github.com | 192.30.253.113 | 0% | 31.115 | 31.203 | 31.249 | 0.226 | 1 | 64 |
| 1 | lb-192-30-253-113-iad.github.com | 192.30.253.113 | 0% | 30.915 | 31.516 | 31.696 | 0.317 | 1 | 128 |
| 2 | lb-192-30-253-113-iad.github.com | 192.30.253.113 | 0% | 32.287 | 32.405 | 32.591 | 0.231 | 1 | 256 |
| 3 | lb-192-30-253-113-iad.github.com | 192.30.253.113 | 0% | 33.686 | 33.775 | 33.886 | 0.239 | 1 | 512 |
| 4 | lb-192-30-253-113-iad.github.com | 192.30.253.113 | 0% | 36.792 | 36.897 | 37.199 | 0.140 | 1 | 1024 |
| | packet_size | rtt avg |
| --- | --- | --- |
| 0 | 64 | 31.203 |
| 1 | 128 | 31.516 |
| 2 | 256 | 32.405 |
| 3 | 512 | 33.775 |
| 4 | 1024 | 36.897 |
_________________
## Q2
```
ifconfig - configure a network interface
ifconfig [interface]
ifconfig interface [aftype] options | address ...
```
Ifconfig is used to configure the kernel-resident network interfaces. It is used at boot time to set up interfaces as necessary. After that, it is usually only needed when debugging or when system tuning is needed. If no arguments are given, ifconfig displays the status of the currently active interfaces. If a single interface argument is given, it displays the status of the given interface only; if a single -a argument is given, it displays the status of all interfaces, even those that are down.
_________________
## Q3
Netstat command displays various network related information such as network connections, routing tables, interface statistics, masquerade connections, multicast memberships etc.,
This program is mostly obsolete. Replacement for netstat is ss. Replacement for netstat -r is ip route. Replacement for netstat -i is ip -s link. Replacement for netstat -g is ip maddr.
Netstat prints information about the Linux networking subsystem. The type of information printed is controlled by the first argument, as follows:
(none)
By default, netstat displays a list of open sockets. If you don't specify
any address families, then the active sockets of all configured address
families will be printed.
--route, -r
Display the kernel routing tables. See the description in route(8) for
details. netstat -r and route -e produce the same output.
--groups, -g
Display multicast group membership information for IPv4 and IPv6.
--interfaces, -i
Display a table of all network interfaces.
--masquerade, -M
Display a list of masqueraded connections.
--statistics, -s
Display summary statistics for each protocol.
`netstat -tn`
Local address : It is the IP address of the local computer (your device) and the port number being used. This address is assigned to you by your router DHCP servers.
Foreign address : It is the IP address and port number of the remote computer to which the socket is connected.
`netstat -r : To get the kernel routing information.`
`netstat -i : To get the list of network interfaces.`
**loopback** `lo`
The loopback device is a special, virtual network interface that your computer uses to communicate with itself. It is used mainly for diagnostics and troubleshooting, and to connect to servers running on the local machine.
The loopback interface does not represent any actual hardware, but exists so applications running on your computer can always connect to servers on the same machine.
For example, if you run a web server, you have all your web documents and could examine them file by file. You may be able to load the files in your browser too.
_________________
## Q4
### information about hosts
| | registered domain | IP |
| --- | --- | --- |
| 0 | github.com | 192.30.253.113 |
| 1 | 1e100.net | 216.239.36.5 |
| 2 | primacom.net | 77.64.170.23 |
| 3 | NaN | 207.244.67.218 |
| 4 | facebook.com | 31.13.92.36 |
### hop counts for each host in each time slot
| | Input | Registered Domain | Time of day | Hop count |
| --- | --- | --- | --- | --- |
| 0 | 192.30.253.113 | github.com | 19 | 10 |
| 10 | 192.30.253.113 | github.com | 22 | 10 |
| 20 | 192.30.253.113 | github.com | 23 | 10 |
| 30 | 216.239.36.5 | 1e100.net | 19 | 5 |
| 35 | 216.239.36.5 | 1e100.net | 22 | 5 |
| 40 | 216.239.36.5 | 1e100.net | 23 | 5 |
| 45 | 77.64.170.23 | primacom.net | 19 | 20 |
| 65 | 77.64.170.23 | primacom.net | 22 | 20 |
| 85 | 77.64.170.23 | primacom.net | 23 | 20 |
| 105 | 207.244.67.218 | NaN | 19 | 10 |
| 115 | 207.244.67.218 | NaN | 22 | 10 |
| 125 | 207.244.67.218 | NaN | 23 | 10 |
| 135 | 31.13.92.36 | facebook.com | 19 | 13 |
| 148 | 31.13.92.36 | facebook.com | 22 | 13 |
| 161 | 31.13.92.36 | facebook.com | 23 | 13 |
Time of day is in 24 hours. [19 means 7:00 pm] (with least count of 60 minutes)
### common hops between two routes
| | Input | Registered Domain | Host name |
| --- | --- | --- | --- |
| 49 | 77.64.170.23 | primacom.net | 100ge5-1.core2.ash1.he.net |
| 138 | 31.13.92.36 | facebook.com | 100ge5-1.core2.ash1.he.net |
| 48 | 77.64.170.23 | primacom.net | 100ge8-1.core1.ash1.he.net |
| 137 | 31.13.92.36 | facebook.com | 100ge8-1.core1.ash1.he.net |
| 47 | 77.64.170.23 | primacom.net | 100ge8-1.core1.atl1.he.net |
| 136 | 31.13.92.36 | facebook.com | 100ge8-1.core1.atl1.he.net |
| 50 | 77.64.170.23 | primacom.net | 100ge8-1.core1.nyc5.he.net |
| 139 | 31.13.92.36 | facebook.com | 100ge8-1.core1.nyc5.he.net |
| 46 | 77.64.170.23 | primacom.net | v509.core1.dal1.he.net |
| 135 | 31.13.92.36 | facebook.com | v509.core1.dal1.he.net |
| 1 | 192.30.253.113 | github.com | vb2000d1.rar3.dallas-tx.us.xo.net |
| 106 | 207.244.67.218 | NaN | vb2000d1.rar3.dallas-tx.us.xo.net |
_________________
## Q5
**ARP** _Address Resolution Protocol_ is a communication protocol used for discovering physical address associated with given network address. Typically, ARP is a network layer to data link layer mapping process, which is used to discover MAC address for given Internet Protocol Address.
In order to send the data to destination, having IP address is necessary but not sufficient; we also need the physical address of the destination machine. ARP is used to get the physical address (MAC address) of destination machine.
ARP is used to find the media access control address of a network neighbour for a given IPv4 Address.
`arp` manipulates or displays the kernel's IPv4 network neighbour cache. It can add entries to the table, delete one or display the current content.
Entries in the ARP table can be static; created by manual configuration or dynamic; created automatically by the normal operation of the protocol. Static entries remain in the table forever and are not timed out.
The default timeout timer for is 4 hours for Cisco devices, this means that a dynamic ARP entry will remain for 4 hours in the cache table before the router attempt to refresh the entry. If the entry is no longer needed it will be removed.