Friday, December 6, 2019

TCP/IP Networking Technical Operations

Question: Describe about the TCP/IP Networking for Technical Operations. Answer: 1: Repeater: this is mainly for handling the operations at the level of the physical layer. It is able to generate the signals completely with the same network pattern. For this, it is mainly that the signal is found to be corrupt or weak and so they are completely found to be corrupted along with handling amplification of the signals with the management of the regeneration of the original strength. (Hassan et al., 2003). Switch: This is based on the points which is based on the linkage to handle the MAC address with the proper connections to the system. There have been signal transmission of the data with the proper networking performance which is based on handling the operations depending on the full-duplex mode. The patterns of the transmission are based on the switches which are operative and the transmission is based on handling the connection of 200 to 300 Mbps. Routers: these are for the handling of the logical information addressing with the networking header for the packets with the IP address. The routers are able to handle the larger network with the ability to handle the same protocols with the focus on the broadcasting flow and the routing software setup. (Marchette, 2001). Router is expensive than the switch. It is mainly due to the setup of the connections which are of the multiple devices for the LAN systems. The IP address is able to handle the security of the device along with handling the data sending to the particular destination. With this, there has been no firewall to be found in the switches or no bandwidth. The switches are more complex and expensive than the repeaters. This is mainly due to the repeaters are mainly to handle the transmission in the range of a larger distance. Where there is a patter setup of the transmission which is on a longer distance. This is mainly to handle the transmission of the data with the collision of the data. (Tozer, 2004). 2: a. number of address with 256*128=32768 suffix length log 2128=7 For the 128 address, /25 mask. 255.255.255.128 is for group 1. 150.80.0.0/25 for subnet 1 150.80.0.128/25 for subnet 2 to 150.80.0.255/25 150.80.1.0/25..150.80.1.128/25 for subnet 3 and so on..subnet 100 For 200th subnet 150.80.99.128/25 till 150.80.99.255/25 The complete address is 256*128=32768 used=200*128=25600 reserved 7168 56 are to be assigned. next address 150.80.100.0 400 size with 16 address ----mask is /28 mask or 255.255.255.240 address 512*16=8192 Suffix Length 4log 216=4 subnet 1 as 150.80.128.0/28 Subnet 2 as 150.80.128.16/28 Subnet 16 as 150.80.100.240/28 Subnet 400[400/16=25] as 150.80.152.240/28 to 150.80.152.255/28 Unused 150.80.153.0 to 150.82.159.255 used 400*16=6400 address Reserved 1792 112 can be assigned. Next address ------150.80.160.0 2000 households, /30 mask or 255.255.255.252 address is 2048*4=8192 Suffix length is 2log 24=2 and the prefix length is 32-2=30 subnet 1 as 150.80.160.0/30 Subnet 2 as 150.80.160.4/30 Subnet 16 as 150.80.160.252/64 Subnet 1984 as 150.80.160.252/30 31*64=1984 Subnet 2000 as 150.80.191.60/30 Next address 150.80.191.64 Used 2000*4=8000 reserved 192 These can be for 48 households. Remaining 16384 3: R1 ----- N1 connect to A N2 connect to B N3 connect to C and E. R2 ----- N3 connect to E and C N4 connect to D N5 connect to E N6 connect to F. Hence, R1 is more complex than R2. There are N1, N2, N3, N4, N5, and N6 network. 4: The distance vector routing is based on handling the smaller networking system which will be based on handling the scale up with the higher levels of the CPU and the utilisation. There have been hop counters for the determination of the path which is appropriate to the handling of the source and the destination. (Martin et al., 1994). The working is based on the connection to the different updates and the periodic matters, with the end-to-end visibility approach for the information to be carried to the different prone areas. With the link state routing, the technology has been able to work on the operations which are able to configure the system approach and the maintenance. The patterns are mainly to handle the NLSP where there is a need to calculate the best and the short path for the handling of the packet system. (Gamma, 1995). There has been implementation set for the methods which are mainly to control and effectively handle the time period which will be able to multicast the system as well as the updates to the other neighbours. (Stalling, 1998). 5: ICMP is based on the handling of the data where there is a need to work on the gateways with the buffering patterns to handle the directions. (Perkins et al., 1995). As per the IP address, there is not a proper reliability on the controlled feedback of the system. This is based on handling the setup along with properly planning and controlling the different procedures for the reliability. This is directed to handle the patterns where the ICMP is mainly for the non-forwarding of the messages. (Vasilakos et al., 2016). The capacity for the networking patterns will be through the forwarding of the datagrams which will be able to handle the sending of the traffic system as per the basis of the router. Through this, it is easy to handle and work on the different patterns which includes the TTL messages along with the expiration details. (Shang et al., 2016). References Hassan, M., Jain, R. (2003).High performance TCP/IP networking(Vol. 29). Prentice Hall. Marchette, D. J. (2001). TCP/IP Networking. InComputer Intrusion Detection and Network Monitoring(pp. 3-42). Springer New York. Tozer, E. P. J. (2004). TCP/IP Networking.Broadcast Engineer's Reference Book, 61. Martin, J., Leben, J. (1994).TCP/IP networking: architecture, administration, and programming. Prentice-Hall, Inc.. Gamma, E. (1995).Design patterns: elements of reusable object-oriented software. Pearson Education India. Stallings, W. (1998). High speed networks.TCP/IP and ATM Design Principles, Upper SaddleRiver, NJ, Prenti c eHall, In c. Perkins, C. E., Jagannadh, T. (1995, July). DHCP for mobile networking with TCP/IP. InComputers and Communications, 1995. Proceedings., IEEE Symposium on(pp. 255-261). IEEE. Vasilakos, A. V., Zhang, Y., Spyropoulos, T. (Eds.). (2016).Delay tolerant networks: Protocols and applications. CRC press. Shang, W., Yu, Y., Droms, R., Zhang, L. (2016).Challenges in IoT Networking via TCP/IP Architecture. NDN Project, Tech. Rep. NDN-0038.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.