This document discusses the Internet Control Message Protocol (ICMP). It begins by listing the chapter objectives and explaining ICMP's position in the TCP/IP protocol suite. It then describes ICMP's message formats, types including error reporting and query, and the ICMP checksum. The document also explains how tools like ping and traceroute use ICMP to debug networks and examine routes. It provides examples of using these tools and interpreting their output.
This document provides information about the Internet Control Message Protocol (ICMP), including:
- ICMP messages are divided into error-reporting messages and query messages. Error messages report problems encountered by routers or hosts, while query messages obtain specific information.
- ICMP is used to diagnose some network problems through query message types including echo request/reply, timestamp request/reply, address-mask request/reply, and router solicitation/advertisement.
- Tools like ping and traceroute use ICMP messages to test network connectivity and debug routing issues. Ping sends echo requests to test reachability, while traceroute identifies the routers along the path between two hosts.
This document provides an overview of the Internet Control Message Protocol (ICMP). It discusses the different types of ICMP messages including error reporting messages like Destination Unreachable and query messages like Echo Request and Reply. It describes the ICMP message format, checksum calculation, and how debugging tools like ping and traceroute use ICMP to troubleshoot network connectivity issues. Specific examples are provided to demonstrate how to use these tools and interpret their output.
This document provides an overview of the Internet Control Message Protocol (ICMP). It discusses ICMP message formats, types of error and query messages, checksum calculation, and debugging tools like ping and traceroute that use ICMP. The key points are that ICMP is used to report errors in IP packets and request information from other nodes, contains error messages for issues like unreachable destinations and time exceeded, and query messages for functions like echo requests and replies. Debugging tools like ping use ICMP echo requests/replies to test connectivity while traceroute uses ICMP responses to map the route between nodes.
The document summarizes Internet Control Message Protocol (ICMP) which is used to report errors and provide diagnostic functions for IP. It describes various ICMP message types including error messages like destination unreachable and time exceeded to report packet delivery problems. It also covers query messages like echo request/reply for reachability testing, and timestamp and mask messages for functions like clock synchronization between hosts. Checksums are used to validate ICMP packets.
Et3003 sem2-1314-8 network layers v (icmpv4)Tutun Juhana
This document discusses the Internet Control Message Protocol version 4 (ICMPv4). It describes ICMPv4's role in reporting errors, providing diagnostic messages like echo requests and replies, and debugging tools like ping and traceroute. ICMPv4 messages include the original datagram header and data to provide context. They are used for tasks like determining reachability, round-trip times, and synchronizing clocks between systems.
This document discusses the Internet Control Message Protocol version 4 (ICMPv4). ICMPv4 is used for error reporting and diagnosing network problems. It uses type and code fields to identify error and query messages. Error messages include Destination Unreachable, Source Quench, Time Exceeded, and Parameter Problem. Query messages include Echo Request/Reply for pinging hosts, and Timestamp Request/Reply for synchronizing clocks and measuring round-trip times. Debugging tools like ping and traceroute utilize ICMPv4 messages to diagnose network connectivity and trace packet routes.
(Icmp) internet control message protocol version 4Gouasmia Zakaria
Internet Control Message Protocol est l’un des protocoles fondamentaux constituant la suite des protocoles Internet. Il est utilisé pour véhiculer des messages de contrôle et d’erreur pour cette suite de protocoles, par exemple lorsqu’un service ou un hôte est inaccessible.
The Internet Control Message Protocol (ICMP) is used to report issues with the delivery of IP packets. It allows devices on the network to check connectivity and diagnose routing problems. ICMP messages are transmitted as IP packets and used by ping and traceroute utilities. It supports functions like announcing network errors, congestion, and assisting troubleshooting. While providing important feedback, ICMP redirect messages can potentially direct traffic to unauthorized systems if not restricted to trusted sources.
This document provides information about the Internet Control Message Protocol (ICMP), including:
- ICMP messages are divided into error-reporting messages and query messages. Error messages report problems encountered by routers or hosts, while query messages obtain specific information.
- ICMP is used to diagnose some network problems through query message types including echo request/reply, timestamp request/reply, address-mask request/reply, and router solicitation/advertisement.
- Tools like ping and traceroute use ICMP messages to test network connectivity and debug routing issues. Ping sends echo requests to test reachability, while traceroute identifies the routers along the path between two hosts.
This document provides an overview of the Internet Control Message Protocol (ICMP). It discusses the different types of ICMP messages including error reporting messages like Destination Unreachable and query messages like Echo Request and Reply. It describes the ICMP message format, checksum calculation, and how debugging tools like ping and traceroute use ICMP to troubleshoot network connectivity issues. Specific examples are provided to demonstrate how to use these tools and interpret their output.
This document provides an overview of the Internet Control Message Protocol (ICMP). It discusses ICMP message formats, types of error and query messages, checksum calculation, and debugging tools like ping and traceroute that use ICMP. The key points are that ICMP is used to report errors in IP packets and request information from other nodes, contains error messages for issues like unreachable destinations and time exceeded, and query messages for functions like echo requests and replies. Debugging tools like ping use ICMP echo requests/replies to test connectivity while traceroute uses ICMP responses to map the route between nodes.
The document summarizes Internet Control Message Protocol (ICMP) which is used to report errors and provide diagnostic functions for IP. It describes various ICMP message types including error messages like destination unreachable and time exceeded to report packet delivery problems. It also covers query messages like echo request/reply for reachability testing, and timestamp and mask messages for functions like clock synchronization between hosts. Checksums are used to validate ICMP packets.
Et3003 sem2-1314-8 network layers v (icmpv4)Tutun Juhana
This document discusses the Internet Control Message Protocol version 4 (ICMPv4). It describes ICMPv4's role in reporting errors, providing diagnostic messages like echo requests and replies, and debugging tools like ping and traceroute. ICMPv4 messages include the original datagram header and data to provide context. They are used for tasks like determining reachability, round-trip times, and synchronizing clocks between systems.
This document discusses the Internet Control Message Protocol version 4 (ICMPv4). ICMPv4 is used for error reporting and diagnosing network problems. It uses type and code fields to identify error and query messages. Error messages include Destination Unreachable, Source Quench, Time Exceeded, and Parameter Problem. Query messages include Echo Request/Reply for pinging hosts, and Timestamp Request/Reply for synchronizing clocks and measuring round-trip times. Debugging tools like ping and traceroute utilize ICMPv4 messages to diagnose network connectivity and trace packet routes.
(Icmp) internet control message protocol version 4Gouasmia Zakaria
Internet Control Message Protocol est l’un des protocoles fondamentaux constituant la suite des protocoles Internet. Il est utilisé pour véhiculer des messages de contrôle et d’erreur pour cette suite de protocoles, par exemple lorsqu’un service ou un hôte est inaccessible.
The Internet Control Message Protocol (ICMP) is used to report issues with the delivery of IP packets. It allows devices on the network to check connectivity and diagnose routing problems. ICMP messages are transmitted as IP packets and used by ping and traceroute utilities. It supports functions like announcing network errors, congestion, and assisting troubleshooting. While providing important feedback, ICMP redirect messages can potentially direct traffic to unauthorized systems if not restricted to trusted sources.
The document discusses the Internet Group Management Protocol (IGMP). It describes IGMP's purpose of managing multicast group membership, its three message types (query, membership report, leave report), and how hosts join and leave groups through the exchange of these messages. It also covers how IGMP packets are encapsulated in IP and link layer frames and provides examples of converting multicast IP addresses to Ethernet multicast addresses.
The document summarizes key concepts related to network layer addressing, error reporting, and multicasting from Chapter 21. It includes:
1) Address mapping allows mapping between logical and physical addresses either statically or dynamically using protocols like ARP.
2) ICMP handles error reporting and network queries that IP lacks. It includes error messages and query messages.
3) IGMP manages group membership and multicast addressing and routing. It allows hosts to join multicast groups.
The document summarizes key concepts related to network layer addressing, error reporting, and multicasting from Chapter 21. It includes:
1) Address mapping allows mapping between logical and physical addresses either statically or dynamically using protocols like ARP.
2) ICMP compensates for IP's lack of error reporting and host/management queries through error messages and query messages.
3) IGMP manages multicast group membership and communication on local networks through group management and messages.
4) ICMPv6 is modified from ICMPv4 for IPv6 with updated error reporting and query messages.
ICMP provides error and control messages at the Internet layer. It is used to send error messages indicating problems with datagram transmission, such as when a datagram's time to live expires or its destination is unreachable, and control messages for router discovery, timestamp requests, and redirecting traffic to better routes. Without ICMP, connectivity and routing issues would be more difficult to troubleshoot and detect.
IGMP (Internet Group Management Protocol) allows multicast routers to track group memberships across multicast networks. It has three message types - query, membership report, and leave report. Upon receiving a query, hosts send membership reports to the router to join or leave groups. The router uses these reports to maintain a list of members for each multicast group on that network segment. IGMP messages are encapsulated in IP datagrams and Ethernet frames for transmission.
The document provides instructions on troubleshooting basic connectivity issues using tools like ping and traceroute. It describes how ping is used to test reachability between devices and can return round-trip time statistics. Traceroute is used to identify where packets are being dropped by showing each hop to the destination. The document also provides details on using Cisco's debug ip packet command to examine packets passing through a router for troubleshooting.
The document discusses the Internet Control Message Protocol (ICMP) which is used to report errors in IP packets and for network debugging tools. ICMP provides error messages, query messages, and is used by tools like ping and traceroute. It describes the different types of ICMP messages including error messages like destination unreachable and source quench, query messages like echo request/reply, and deprecated messages. It also explains how ICMP messages are encapsulated in IP packets and how the checksum is calculated for ICMP headers.
This document discusses the User Datagram Protocol (UDP) which provides a connectionless mode of communication between applications on hosts in an IP network. It describes the format of UDP packets, how UDP checksums are calculated, and UDP's operation including encapsulation, queuing, and demultiplexing. Examples are provided to illustrate how a UDP control block table and queues are used to handle incoming and outgoing UDP packets. The document also discusses when UDP is an appropriate protocol to use compared to TCP.
This document discusses the User Datagram Protocol (UDP) which provides connectionless and unreliable data transmission between applications. It covers UDP packet formats, checksum calculation, operation including encapsulation and multiplexing, appropriate uses of UDP, and the modules involved in a UDP implementation including control blocks, input/output queues, and tables. Examples are provided to illustrate how UDP handles packet reception and association with processes.
This document discusses ICMPv4 (Internet Control Message Protocol version 4). It describes ICMPv4's role in error reporting and querying, including error messages like Destination Unreachable and query tools like Ping and Traceroute. ICMPv4 messages have a header and variable data. The protocol is used to supplement deficiencies in the IP protocol for notification and querying between hosts.
The document discusses several Internet protocols:
- IP prepares packets for transmission across the Internet and provides unreliable packet delivery. IPv6 was created to address issues with IPv4 like exhaustion of addresses.
- ARP resolves IP addresses to hardware addresses on local networks and maintains address mappings in caches.
- ICMP provides error reporting and network monitoring functions to support IP.
- TCP provides reliable data transmission and UDP provides simple transmission of datagrams.
1.1.2 - Concept of Network and TCP_IP Model (2).pptxVINAYTANWAR18
This document provides an overview of network concepts and the TCP/IP model. It describes the key components of TCP/IP including the TCP and IP protocols and how they work together. The TCP/IP model layers are compared to the OSI model layers. Details are given on TCP and IP packet headers including fields like ports, sequence numbers, flags, and checksums. Common applications that use TCP and UDP are also listed.
The Internet Control Message Protocol (ICMP) is an integral part of the TCP/IP protocol suite that sends error and control messages. Unlike error messages, control messages are not the result of lost packets or transmission errors. ICMP uses multiple types of control messages that are encapsulated in IP datagrams. Some examples of ICMP messages include destination unreachable, echo request, echo reply, packet too big, parameter problem, path MTU discovery, redirect message, source quench, and time exceeded.
UDP is a transport layer protocol that provides an unreliable datagram service. It is positioned directly above IP in the TCP/IP protocol stack. UDP packets contain a header with source and destination port numbers as well as length fields, but do not establish connections, provide sequencing, or guarantee delivery like TCP. Well-known ports are assigned to common UDP applications like DNS, time synchronization, and trivial file transfer.
HS1011 Data Communication and Networks 13 August 2015 HS101.docxadampcarr67227
HS1011 Data Communication and Networks 13 August 2015
HS1011 Data Communication and Networks 13 August 2015
HOLMES
INSTITUTE
FACULTY OF HIGHER
EDUCATION
HS1011 Data Communication and Networks
Tutorial/Lab Activity Week 06 Network Models, Standards and Protocols
Hands-On Project 1: Identifying the TCP/IP Layers in a Frame
Objective: Capture packets and view the TCP/IP layers in the frame
Required Tools/Equipment: Your classroom computer with Wireshark installed
Description: In this project, you capture some frames generated by your Web browser and examine the captured frames to identify the TCP/IP layers.
1. Start Wireshark (Use “Wireshark manual” to learn “how to use wireshark to capture data”) and click Capture Options. In the Capture Filter text box, type tcp port http(see Figure 1), and then click Start.
Figure 1: Selecting filtering options
2. Start a Web browser, and open holmes website (http://www.holmes.edu.au/), exit the browser.
3. In Wireshark, click the Stop the running live capture toolbar icon to stop the capture. Scroll up to the first packet summary line, if necessary.
4. Click a packet summary in the top pane with HTTP in the protocol field and an Info line beginning with GET. In the middle pane are summaries of each protocol header (see Figure 5-6). You can ignore the first line starting with Frame X (with X representing the frame number), as it gives information about the frame, such as the time it arrived, its length, protocols in the frame, and so forth.
Figure 2: Summary of protocol headers in Wireshark
5. Click to expand the line beginning with Ethernet II. Examine the information in this header (discussed in more detail in the following sections). Write which layer of the TCP/IP model the Ethernet II header represents, and then click again to collapse this header:
_______________________________________________________________________________
6. Click to expand the line beginning with Internet Protocol. Examine the information in this header (discussed in more detail in the following sections). Write which layer of the TCP/IP model the Internet Protocol header represents, and then click again to collapse this header:
_______________________________________________________________________________
7. Click to expand the line beginning with Transmission Control Protocol. Examine the information in this header (discussed in more detail in the following sections). Write which layer of the TCP/IP model the Transmission Control Protocol header represents, and then click again to collapse this header:
_______________________________________________________________________________
8. Click to expand the line beginning with Hypertext Transfer Protocol, and examine the information. This data portion of the frame is what a Web server actually sees and responds to. In this case, the HTTP command is GET, which means HTTP is requesting a page (or part of a page) from the Web server. Write .
IPv4 uses a datagram format with a header and data. The header contains information for routing and delivery and is 20-60 bytes. It includes fields for the version, length, identification, fragmentation, protocol, and source/destination addresses. Datagrams can be fragmented into smaller pieces if their size exceeds the MTU of a network. Fragments are reassembled at the destination using the identification field. The time to live field limits the number of hops a packet can make to prevent endless routing.
The document discusses packet forwarding and the IP header. It provides information on how routers forward packets based on routing tables to their intended destinations. The IP header contains fields like the version, identification, flags, fragment offset, time to live, protocol, and source and destination addresses that are used to deliver packets to the correct destination. Packet forwarding simply implies forwarding incoming packets to their intended destination by routers in the network.
This document discusses and compares three transport layer protocols: UDP, TCP, and SCTP. It provides details on the services, features, header formats, and operation of each protocol. UDP is a connectionless and unreliable protocol that uses a simple 8-byte header with fields for source/destination ports and length. TCP is connection-oriented and reliable, using sequence numbers and acknowledgments to ensure delivery. It establishes connections for data transfer and teardown. SCTP combines features of UDP and TCP, with support for multiple streams, multihoming, and reliability.
Redefining brain tumor segmentation: a cutting-edge convolutional neural netw...IJECEIAES
Medical image analysis has witnessed significant advancements with deep learning techniques. In the domain of brain tumor segmentation, the ability to
precisely delineate tumor boundaries from magnetic resonance imaging (MRI)
scans holds profound implications for diagnosis. This study presents an ensemble convolutional neural network (CNN) with transfer learning, integrating
the state-of-the-art Deeplabv3+ architecture with the ResNet18 backbone. The
model is rigorously trained and evaluated, exhibiting remarkable performance
metrics, including an impressive global accuracy of 99.286%, a high-class accuracy of 82.191%, a mean intersection over union (IoU) of 79.900%, a weighted
IoU of 98.620%, and a Boundary F1 (BF) score of 83.303%. Notably, a detailed comparative analysis with existing methods showcases the superiority of
our proposed model. These findings underscore the model’s competence in precise brain tumor localization, underscoring its potential to revolutionize medical
image analysis and enhance healthcare outcomes. This research paves the way
for future exploration and optimization of advanced CNN models in medical
imaging, emphasizing addressing false positives and resource efficiency.
The document discusses the Internet Group Management Protocol (IGMP). It describes IGMP's purpose of managing multicast group membership, its three message types (query, membership report, leave report), and how hosts join and leave groups through the exchange of these messages. It also covers how IGMP packets are encapsulated in IP and link layer frames and provides examples of converting multicast IP addresses to Ethernet multicast addresses.
The document summarizes key concepts related to network layer addressing, error reporting, and multicasting from Chapter 21. It includes:
1) Address mapping allows mapping between logical and physical addresses either statically or dynamically using protocols like ARP.
2) ICMP handles error reporting and network queries that IP lacks. It includes error messages and query messages.
3) IGMP manages group membership and multicast addressing and routing. It allows hosts to join multicast groups.
The document summarizes key concepts related to network layer addressing, error reporting, and multicasting from Chapter 21. It includes:
1) Address mapping allows mapping between logical and physical addresses either statically or dynamically using protocols like ARP.
2) ICMP compensates for IP's lack of error reporting and host/management queries through error messages and query messages.
3) IGMP manages multicast group membership and communication on local networks through group management and messages.
4) ICMPv6 is modified from ICMPv4 for IPv6 with updated error reporting and query messages.
ICMP provides error and control messages at the Internet layer. It is used to send error messages indicating problems with datagram transmission, such as when a datagram's time to live expires or its destination is unreachable, and control messages for router discovery, timestamp requests, and redirecting traffic to better routes. Without ICMP, connectivity and routing issues would be more difficult to troubleshoot and detect.
IGMP (Internet Group Management Protocol) allows multicast routers to track group memberships across multicast networks. It has three message types - query, membership report, and leave report. Upon receiving a query, hosts send membership reports to the router to join or leave groups. The router uses these reports to maintain a list of members for each multicast group on that network segment. IGMP messages are encapsulated in IP datagrams and Ethernet frames for transmission.
The document provides instructions on troubleshooting basic connectivity issues using tools like ping and traceroute. It describes how ping is used to test reachability between devices and can return round-trip time statistics. Traceroute is used to identify where packets are being dropped by showing each hop to the destination. The document also provides details on using Cisco's debug ip packet command to examine packets passing through a router for troubleshooting.
The document discusses the Internet Control Message Protocol (ICMP) which is used to report errors in IP packets and for network debugging tools. ICMP provides error messages, query messages, and is used by tools like ping and traceroute. It describes the different types of ICMP messages including error messages like destination unreachable and source quench, query messages like echo request/reply, and deprecated messages. It also explains how ICMP messages are encapsulated in IP packets and how the checksum is calculated for ICMP headers.
This document discusses the User Datagram Protocol (UDP) which provides a connectionless mode of communication between applications on hosts in an IP network. It describes the format of UDP packets, how UDP checksums are calculated, and UDP's operation including encapsulation, queuing, and demultiplexing. Examples are provided to illustrate how a UDP control block table and queues are used to handle incoming and outgoing UDP packets. The document also discusses when UDP is an appropriate protocol to use compared to TCP.
This document discusses the User Datagram Protocol (UDP) which provides connectionless and unreliable data transmission between applications. It covers UDP packet formats, checksum calculation, operation including encapsulation and multiplexing, appropriate uses of UDP, and the modules involved in a UDP implementation including control blocks, input/output queues, and tables. Examples are provided to illustrate how UDP handles packet reception and association with processes.
This document discusses ICMPv4 (Internet Control Message Protocol version 4). It describes ICMPv4's role in error reporting and querying, including error messages like Destination Unreachable and query tools like Ping and Traceroute. ICMPv4 messages have a header and variable data. The protocol is used to supplement deficiencies in the IP protocol for notification and querying between hosts.
The document discusses several Internet protocols:
- IP prepares packets for transmission across the Internet and provides unreliable packet delivery. IPv6 was created to address issues with IPv4 like exhaustion of addresses.
- ARP resolves IP addresses to hardware addresses on local networks and maintains address mappings in caches.
- ICMP provides error reporting and network monitoring functions to support IP.
- TCP provides reliable data transmission and UDP provides simple transmission of datagrams.
1.1.2 - Concept of Network and TCP_IP Model (2).pptxVINAYTANWAR18
This document provides an overview of network concepts and the TCP/IP model. It describes the key components of TCP/IP including the TCP and IP protocols and how they work together. The TCP/IP model layers are compared to the OSI model layers. Details are given on TCP and IP packet headers including fields like ports, sequence numbers, flags, and checksums. Common applications that use TCP and UDP are also listed.
The Internet Control Message Protocol (ICMP) is an integral part of the TCP/IP protocol suite that sends error and control messages. Unlike error messages, control messages are not the result of lost packets or transmission errors. ICMP uses multiple types of control messages that are encapsulated in IP datagrams. Some examples of ICMP messages include destination unreachable, echo request, echo reply, packet too big, parameter problem, path MTU discovery, redirect message, source quench, and time exceeded.
UDP is a transport layer protocol that provides an unreliable datagram service. It is positioned directly above IP in the TCP/IP protocol stack. UDP packets contain a header with source and destination port numbers as well as length fields, but do not establish connections, provide sequencing, or guarantee delivery like TCP. Well-known ports are assigned to common UDP applications like DNS, time synchronization, and trivial file transfer.
HS1011 Data Communication and Networks 13 August 2015 HS101.docxadampcarr67227
HS1011 Data Communication and Networks 13 August 2015
HS1011 Data Communication and Networks 13 August 2015
HOLMES
INSTITUTE
FACULTY OF HIGHER
EDUCATION
HS1011 Data Communication and Networks
Tutorial/Lab Activity Week 06 Network Models, Standards and Protocols
Hands-On Project 1: Identifying the TCP/IP Layers in a Frame
Objective: Capture packets and view the TCP/IP layers in the frame
Required Tools/Equipment: Your classroom computer with Wireshark installed
Description: In this project, you capture some frames generated by your Web browser and examine the captured frames to identify the TCP/IP layers.
1. Start Wireshark (Use “Wireshark manual” to learn “how to use wireshark to capture data”) and click Capture Options. In the Capture Filter text box, type tcp port http(see Figure 1), and then click Start.
Figure 1: Selecting filtering options
2. Start a Web browser, and open holmes website (http://www.holmes.edu.au/), exit the browser.
3. In Wireshark, click the Stop the running live capture toolbar icon to stop the capture. Scroll up to the first packet summary line, if necessary.
4. Click a packet summary in the top pane with HTTP in the protocol field and an Info line beginning with GET. In the middle pane are summaries of each protocol header (see Figure 5-6). You can ignore the first line starting with Frame X (with X representing the frame number), as it gives information about the frame, such as the time it arrived, its length, protocols in the frame, and so forth.
Figure 2: Summary of protocol headers in Wireshark
5. Click to expand the line beginning with Ethernet II. Examine the information in this header (discussed in more detail in the following sections). Write which layer of the TCP/IP model the Ethernet II header represents, and then click again to collapse this header:
_______________________________________________________________________________
6. Click to expand the line beginning with Internet Protocol. Examine the information in this header (discussed in more detail in the following sections). Write which layer of the TCP/IP model the Internet Protocol header represents, and then click again to collapse this header:
_______________________________________________________________________________
7. Click to expand the line beginning with Transmission Control Protocol. Examine the information in this header (discussed in more detail in the following sections). Write which layer of the TCP/IP model the Transmission Control Protocol header represents, and then click again to collapse this header:
_______________________________________________________________________________
8. Click to expand the line beginning with Hypertext Transfer Protocol, and examine the information. This data portion of the frame is what a Web server actually sees and responds to. In this case, the HTTP command is GET, which means HTTP is requesting a page (or part of a page) from the Web server. Write .
IPv4 uses a datagram format with a header and data. The header contains information for routing and delivery and is 20-60 bytes. It includes fields for the version, length, identification, fragmentation, protocol, and source/destination addresses. Datagrams can be fragmented into smaller pieces if their size exceeds the MTU of a network. Fragments are reassembled at the destination using the identification field. The time to live field limits the number of hops a packet can make to prevent endless routing.
The document discusses packet forwarding and the IP header. It provides information on how routers forward packets based on routing tables to their intended destinations. The IP header contains fields like the version, identification, flags, fragment offset, time to live, protocol, and source and destination addresses that are used to deliver packets to the correct destination. Packet forwarding simply implies forwarding incoming packets to their intended destination by routers in the network.
This document discusses and compares three transport layer protocols: UDP, TCP, and SCTP. It provides details on the services, features, header formats, and operation of each protocol. UDP is a connectionless and unreliable protocol that uses a simple 8-byte header with fields for source/destination ports and length. TCP is connection-oriented and reliable, using sequence numbers and acknowledgments to ensure delivery. It establishes connections for data transfer and teardown. SCTP combines features of UDP and TCP, with support for multiple streams, multihoming, and reliability.
Redefining brain tumor segmentation: a cutting-edge convolutional neural netw...IJECEIAES
Medical image analysis has witnessed significant advancements with deep learning techniques. In the domain of brain tumor segmentation, the ability to
precisely delineate tumor boundaries from magnetic resonance imaging (MRI)
scans holds profound implications for diagnosis. This study presents an ensemble convolutional neural network (CNN) with transfer learning, integrating
the state-of-the-art Deeplabv3+ architecture with the ResNet18 backbone. The
model is rigorously trained and evaluated, exhibiting remarkable performance
metrics, including an impressive global accuracy of 99.286%, a high-class accuracy of 82.191%, a mean intersection over union (IoU) of 79.900%, a weighted
IoU of 98.620%, and a Boundary F1 (BF) score of 83.303%. Notably, a detailed comparative analysis with existing methods showcases the superiority of
our proposed model. These findings underscore the model’s competence in precise brain tumor localization, underscoring its potential to revolutionize medical
image analysis and enhance healthcare outcomes. This research paves the way
for future exploration and optimization of advanced CNN models in medical
imaging, emphasizing addressing false positives and resource efficiency.
Literature Review Basics and Understanding Reference Management.pptxDr Ramhari Poudyal
Three-day training on academic research focuses on analytical tools at United Technical College, supported by the University Grant Commission, Nepal. 24-26 May 2024
Optimizing Gradle Builds - Gradle DPE Tour Berlin 2024Sinan KOZAK
Sinan from the Delivery Hero mobile infrastructure engineering team shares a deep dive into performance acceleration with Gradle build cache optimizations. Sinan shares their journey into solving complex build-cache problems that affect Gradle builds. By understanding the challenges and solutions found in our journey, we aim to demonstrate the possibilities for faster builds. The case study reveals how overlapping outputs and cache misconfigurations led to significant increases in build times, especially as the project scaled up with numerous modules using Paparazzi tests. The journey from diagnosing to defeating cache issues offers invaluable lessons on maintaining cache integrity without sacrificing functionality.
Presentation of IEEE Slovenia CIS (Computational Intelligence Society) Chapte...University of Maribor
Slides from talk presenting:
Aleš Zamuda: Presentation of IEEE Slovenia CIS (Computational Intelligence Society) Chapter and Networking.
Presentation at IcETRAN 2024 session:
"Inter-Society Networking Panel GRSS/MTT-S/CIS
Panel Session: Promoting Connection and Cooperation"
IEEE Slovenia GRSS
IEEE Serbia and Montenegro MTT-S
IEEE Slovenia CIS
11TH INTERNATIONAL CONFERENCE ON ELECTRICAL, ELECTRONIC AND COMPUTING ENGINEERING
3-6 June 2024, Niš, Serbia
Advanced control scheme of doubly fed induction generator for wind turbine us...IJECEIAES
This paper describes a speed control device for generating electrical energy on an electricity network based on the doubly fed induction generator (DFIG) used for wind power conversion systems. At first, a double-fed induction generator model was constructed. A control law is formulated to govern the flow of energy between the stator of a DFIG and the energy network using three types of controllers: proportional integral (PI), sliding mode controller (SMC) and second order sliding mode controller (SOSMC). Their different results in terms of power reference tracking, reaction to unexpected speed fluctuations, sensitivity to perturbations, and resilience against machine parameter alterations are compared. MATLAB/Simulink was used to conduct the simulations for the preceding study. Multiple simulations have shown very satisfying results, and the investigations demonstrate the efficacy and power-enhancing capabilities of the suggested control system.
Harnessing WebAssembly for Real-time Stateless Streaming PipelinesChristina Lin
Traditionally, dealing with real-time data pipelines has involved significant overhead, even for straightforward tasks like data transformation or masking. However, in this talk, we’ll venture into the dynamic realm of WebAssembly (WASM) and discover how it can revolutionize the creation of stateless streaming pipelines within a Kafka (Redpanda) broker. These pipelines are adept at managing low-latency, high-data-volume scenarios.
Electric vehicle and photovoltaic advanced roles in enhancing the financial p...IJECEIAES
Climate change's impact on the planet forced the United Nations and governments to promote green energies and electric transportation. The deployments of photovoltaic (PV) and electric vehicle (EV) systems gained stronger momentum due to their numerous advantages over fossil fuel types. The advantages go beyond sustainability to reach financial support and stability. The work in this paper introduces the hybrid system between PV and EV to support industrial and commercial plants. This paper covers the theoretical framework of the proposed hybrid system including the required equation to complete the cost analysis when PV and EV are present. In addition, the proposed design diagram which sets the priorities and requirements of the system is presented. The proposed approach allows setup to advance their power stability, especially during power outages. The presented information supports researchers and plant owners to complete the necessary analysis while promoting the deployment of clean energy. The result of a case study that represents a dairy milk farmer supports the theoretical works and highlights its advanced benefits to existing plants. The short return on investment of the proposed approach supports the paper's novelty approach for the sustainable electrical system. In addition, the proposed system allows for an isolated power setup without the need for a transmission line which enhances the safety of the electrical network
Understanding Inductive Bias in Machine LearningSUTEJAS
This presentation explores the concept of inductive bias in machine learning. It explains how algorithms come with built-in assumptions and preferences that guide the learning process. You'll learn about the different types of inductive bias and how they can impact the performance and generalizability of machine learning models.
The presentation also covers the positive and negative aspects of inductive bias, along with strategies for mitigating potential drawbacks. We'll explore examples of how bias manifests in algorithms like neural networks and decision trees.
By understanding inductive bias, you can gain valuable insights into how machine learning models work and make informed decisions when building and deploying them.
1. TCP/IP Protocol Suite 1
Chapter 9
Upon completion you will be able to:
Internet Control Message
Protocol
• Be familiar with the ICMP message format
• Know the types of error reporting messages
• Know the types of query messages
• Be able to calculate the ICMP checksum
• Know how to use the ping and traceroute commands
• Understand the modules and interactions of an ICMP package
Objectives
4. TCP/IP Protocol Suite 4
9.1 TYPES OF MESSAGES
ICMP messages are divided into error-reporting messages and query
messages. The error-reporting messages report problems that a router or
a host (destination) may encounter. The query messages get specific
information from a router or another host.
7. TCP/IP Protocol Suite 7
9.2 MESSAGE FORMAT
An ICMP message has an 8-byte header and a variable-size data section.
Although the general format of the header is different for each message
type, the first 4 bytes are common to all.
9. TCP/IP Protocol Suite 9
9.3 ERROR REPORTING
IP, as an unreliable protocol, is not concerned with error checking and
error control. ICMP was designed, in part, to compensate for this
shortcoming. ICMP does not correct errors, it simply reports them.
The topics discussed in this section include:
Destination Unreachable
Source Quench
Time Exceeded
Parameter Problem
Redirection
10. TCP/IP Protocol Suite 10
ICMP always reports error messages
to the original source.
Note:
12. TCP/IP Protocol Suite 12
The following are important points about ICMP
error messages:
❏ No ICMP error message will be generated in response
to a datagram carrying an ICMP error message.
❏ No ICMP error message will be generated for a
fragmented datagram that is not the first fragment.
❏ No ICMP error message will be generated for a
datagram having a multicast address.
❏ No ICMP error message will be generated for a
datagram having a special address such as 127.0.0.0 or
0.0.0.0.
Note:
15. TCP/IP Protocol Suite 15
Destination-unreachable messages
with codes 2 or 3 can be created only
by the destination host.
Other destination-unreachable
messages can be created only by
routers.
Note:
16. TCP/IP Protocol Suite 16
A router cannot detect all problems
that prevent the delivery of a packet.
Note:
17. TCP/IP Protocol Suite 17
There is no flow-control mechanism in
the IP protocol.
Note:
19. TCP/IP Protocol Suite 19
A source-quench message informs the
source that a datagram has been
discarded due to congestion in a router
or the destination host.
The source must slow down the
sending of datagrams until the
congestion is relieved.
Note:
20. TCP/IP Protocol Suite 20
One source-quench message is sent for
each datagram that is discarded due to
congestion.
Note:
21. TCP/IP Protocol Suite 21
Whenever a router decrements a
datagram with a time-to-live value to
zero, it discards the datagram and
sends a time-exceeded message to the
original source.
Note:
22. TCP/IP Protocol Suite 22
When the final destination does not
receive all of the fragments in a set
time, it discards the received fragments
and sends a time-exceeded message to
the original source.
Note:
23. TCP/IP Protocol Suite 23
In a time-exceeded message, code 0 is
used only by routers to show that the
value of the time-to-live field is zero.
Code 1 is used only by the destination
host to show that not all of the
fragments have arrived within a set
time.
Note:
28. TCP/IP Protocol Suite 28
A host usually starts with a small
routing table that is gradually
augmented and updated. One of the
tools to accomplish this is the
redirection message.
Note:
30. TCP/IP Protocol Suite 30
A redirection message is sent from a
router to a host on the same local
network.
Note:
31. TCP/IP Protocol Suite 31
9.4 QUERY
ICMP can also diagnose some network problems through the query
messages, a group of four different pairs of messages. In this type of
ICMP message, a node sends a message that is answered in a specific
format by the destination node.
The topics discussed in this section include:
Echo Request and Reply
Timestamp Request and Reply
Address-Mask Request and Reply
Router Solicitation and Advertisement
33. TCP/IP Protocol Suite 33
An echo-request message can be sent
by a host or router. An echo-reply
message is sent by the host or router
which receives an echo-request
message.
Note:
34. TCP/IP Protocol Suite 34
Echo-request and echo-reply messages
can be used by network managers to
check the operation of the IP protocol.
Note:
35. TCP/IP Protocol Suite 35
Echo-request and echo-reply messages
can test the reachability of a host. This
is usually done by invoking the ping
command.
Note:
37. TCP/IP Protocol Suite 37
Figure 9.15 Timestamp-request and timestamp-reply message format
38. TCP/IP Protocol Suite 38
Timestamp-request and timestamp-
reply messages can be used to
calculate the round-trip time between
a source and a destination machine
even if their clocks are not
synchronized.
Note:
39. TCP/IP Protocol Suite 39
The timestamp-request and timestamp-
reply messages can be used to
synchronize two clocks in two
machines if the exact one-way time
duration is known.
Note:
43. TCP/IP Protocol Suite 43
9.5 CHECKSUM
In ICMP the checksum is calculated over the entire message (header
and data).
The topics discussed in this section include:
Checksum Calculation
Checksum Testing
44. TCP/IP Protocol Suite 44
Figure 9.19 shows an example of checksum calculation for a
simple echo-request message (see Figure 9.14). We randomly
chose the identifier to be 1 and the sequence number to be 9.
The message is divided into 16-bit (2-byte) words. The words
are added together and the sum is complemented. Now the
sender can put this value in the checksum field.
Example 1
See Next Slide
46. TCP/IP Protocol Suite 46
9.6 DEBUGGING TOOLS
We introduce two tools that use ICMP for debugging: ping and
traceroute.
The topics discussed in this section include:
Ping
Traceroute
47. TCP/IP Protocol Suite 47
We use the ping program to test the server fhda.edu. The result
is shown below:
Example 2
See Next Slide
$ ping fhda.edu
PING fhda.edu (153.18.8.1) 56 (84) bytes of data.
64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=0 ttl=62 time=1.91 ms
64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=1 ttl=62 time=2.04 ms
64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=2 ttl=62 time=1.90 ms
64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=3 ttl=62 time=1.97 ms
64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=4 ttl=62 time=1.93 ms
48. TCP/IP Protocol Suite 48
Example 2 (Continued)
64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=5 ttl=62 time=2.00 ms
64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=6 ttl=62 time=1.94 ms
64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=7 ttl=62 time=1.94 ms
64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=8 ttl=62 time=1.97 ms
64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=9 ttl=62 time=1.89 ms
64 bytes from tiptoe.fhda.edu (153.18.8.1): icmp_seq=10 ttl=62 time=1.98 ms
--- fhda.edu ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 10103ms
rtt min/avg/max = 1.899/1.955/2.041 ms
49. TCP/IP Protocol Suite 49
For the this example, we want to know if the adelphia.net mail
server is alive and running. The result is shown below:
Example 3
$ ping mail.adelphia.net
PING mail.adelphia.net (68.168.78.100) 56(84) bytes of data.
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=0 ttl=48 time=85.4 ms
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=1 ttl=48 time=84.6 ms
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=2 ttl=48 time=84.9 ms
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=3 ttl=48 time=84.3 ms
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=4 ttl=48 time=84.5 ms
See Next Slide
50. TCP/IP Protocol Suite 50
Example 3 (Continued)
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=5 ttl=48 time=84.7 ms
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=6 ttl=48 time=84.6 ms
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=7 ttl=48 time=84.7 ms
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=8 ttl=48 time=84.4 ms
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=9 ttl=48 time=84.2 ms
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=10 ttl=48 time=84.9 ms
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=11 ttl=48 time=84.6 ms
64 bytes from mail.adelphia.net (68.168.78.100): icmp_seq=12 ttl=48 time=84.5 ms
--- mail.adelphia.net ping statistics ---
14 packets transmitted, 13 received, 7% packet loss, time 13129ms
rtt min/avg/max/mdev = 84.207/84.694/85.469
52. TCP/IP Protocol Suite 52
We use the traceroute program to find the route from the
computer voyager.deanza.edu to the server fhda.edu. The
following shows the result:
Example 4
See Next Slide
$ traceroute fhda.edu
traceroute to fhda.edu (153.18.8.1), 30 hops max, 38 byte packets
1 Dcore.fhda.edu (153.18.31.254) 0.995 ms 0.899 ms 0.878 ms
2 Dbackup.fhda.edu (153.18.251.4) 1.039 ms 1.064 ms 1.083 ms
3 tiptoe.fhda.edu (153.18.8.1) 1.797 ms 1.642 ms 1.757 ms
53. TCP/IP Protocol Suite 53
The un-numbered line after the command shows that the destination is
153.18.8.1. The TTL value is 30 hops. The packet contains 38 bytes: 20
bytes of IP header, 8 bytes of UDP header, and 10 bytes of application data.
The application data is used by traceroute to keep track of the packets.
Example 4 (Continued)
The first line shows the first router visited. The router is named
Dcore.fhda.edu with IP address 153.18.31.254. The first round trip time was
0.995 milliseconds, the second was 0.899 milliseconds, and the third was
0.878 milliseconds.
The second line shows the second router visited. The router is named
Dbackup.fhda.edu with IP address 153.18.251.4. The three round trip times
are also shown.
The third line shows the destination host. We know that this is the
destination host because there are no more lines. The destination host is the
server fhda.edu, but it is named tiptoe. fhda.edu with the IP address
153.18.8.1. The three round trip times are also shown.
54. TCP/IP Protocol Suite 54
In this example, we trace a longer route, the route to
xerox.com
Example 5
$ traceroute xerox.com
traceroute to xerox.com (13.1.64.93), 30 hops max, 38 byte packets
1 Dcore.fhda.edu (153.18.31.254) 0.622 ms 0.891 ms 0.875 ms
2 Ddmz.fhda.edu (153.18.251.40) 2.132 ms 2.266 ms 2.094 ms
...
18 alpha.Xerox.COM (13.1.64.93) 11.172 ms 11.048 ms 10.922 ms
Here there are 17 hops between source and destination. Note that some
round trip times look unusual. It could be that a router is too busy to
process the packet immediately.
55. TCP/IP Protocol Suite 55
An interesting point is that a host can send a traceroute packet
to itself. This can be done by specifying the host as the
destination. The packet goes to the loopback address as we
expect.
Example 6
$ traceroute voyager.deanza.edu
traceroute to voyager.deanza.edu (127.0.0.1), 30 hops max, 38 byte packets
1 voyager (127.0.0.1) 0.178 ms 0.086 ms 0.055 ms
56. TCP/IP Protocol Suite 56
Finally, we use the traceroute program to find the route
between fhda.edu and mhhe.com (McGraw-Hill server). We
notice that we cannot find the whole route. When traceroute
does not receive a response within 5 seconds, it prints an
asterisk to signify a problem, and then tries the next hop..
Example 7
$ traceroute mhhe.com
traceroute to mhhe.com (198.45.24.104), 30 hops max, 38 byte packets
1 Dcore.fhda.edu (153.18.31.254) 1.025 ms 0.892 ms 0.880 ms
2 Ddmz.fhda.edu (153.18.251.40) 2.141 ms 2.159 ms 2.103 ms
3 Cinic.fhda.edu (153.18.253.126) 2.159 ms 2.050 ms 1.992 ms
...
16 * * *
17 * * *
...............
57. TCP/IP Protocol Suite 57
9.7 ICMP PACKAGE
To give an idea of how ICMP can handle the sending and receiving of
ICMP messages, we present our version of an ICMP package made of
two modules: an input module and an output module.
The topics discussed in this section include:
Input Module
Output Module