Advanced Routing. Routing is the process of forwarding packets from one network to the destination address in another network. ... Each route is known as a routing entry
IGMP (Internet Group Management Protocol) allows hosts to dynamically join multicast groups and routers to manage delivery of multicast data packets. IGMP version 1 uses query and report messages between routers and hosts to discover which hosts belong to which multicast groups on local networks. Version 2 and 3 added new message types and formats to more efficiently manage group membership and enhance security.
This white paper provides an overview of IGMP and how it can support IPTV networks. IGMP is the protocol used to control multicast traffic delivery and allows clients to join and leave multicast groups, representing TV channels. When intermediate network devices are introduced, techniques like IGMP snooping, proxy routing, and query/report suppression are used to optimize multicast traffic delivery and IGMP message processing. These techniques aim to reduce bandwidth consumption and speed up channel change times.
Multicast is a communication protocol that allows a single sender to transmit data to multiple receivers simultaneously. It works by addressing data to a group of destination computers, reducing network load compared to unicast which requires separate transmissions to each receiver. The document outlines the history of multicast, how it works including reverse path forwarding using pruning and grafting, the IGMP protocol used by end systems to signal group membership, challenges in implementing multicast security, and applications such as audio/video broadcasting and software distribution where it provides benefits over unicast.
IP Multicast allows one-to-many and many-to-many communication through multicast addressing and routing protocols. It identifies multicast groups with class D IP addresses and uses IGMP for hosts to join and leave groups, while multicast routing protocols like PIM-SM and PIM-DM establish distribution trees. PIM-SM uses a shared tree by default rooted at a rendezvous point, while PIM-DM uses source-based trees and assumes dense receiver distribution initially pruned by leaves.
Marvin Hoffmann presented on multicasting for the next generation internet. He began with introducing himself and explaining why he chose this topic, which has always interested him. The presentation covered what multicasting is, the benefits of using it, how it works under both IPv4 and IPv6 including necessary protocols, and some challenges with multicasting. In the conclusion, Hoffmann restated that multicasting over the internet without a multicast backbone is still an interesting topic and thanked the audience for their attention, inviting any questions.
This document discusses the Internet Group Management Protocol (IGMP), which allows hosts to report their multicast group memberships to neighboring multicast routers. It describes the different versions of IGMP, including IGMPv1, IGMPv2, and IGMPv3. It also covers IGMP messages like membership queries, reports, and leaves. IGMP snooping is defined as a switch feature that optimizes multicast traffic delivery by only forwarding traffic to ports with interested receivers. Multicast Listener Discovery (MLD) serves a similar purpose for IPv6 as IGMP does for IPv4.
IP multicasting allows for efficient one-to-many and many-to-many communication on the internet. It uses multicast groups and protocols like IGMP for group management and PIM for multicast routing. PIM supports both source-based trees using flood-and-prune and core-based trees with a rendezvous point to deliver multicast data.
IP multicast is a method of sending Internet Protocol (IP) datagrams to a group of interested receivers in a single transmission. It is often employed for streaming media applications on the Internet and private networks.(wikipedia)
IGMP (Internet Group Management Protocol) allows hosts to dynamically join multicast groups and routers to manage delivery of multicast data packets. IGMP version 1 uses query and report messages between routers and hosts to discover which hosts belong to which multicast groups on local networks. Version 2 and 3 added new message types and formats to more efficiently manage group membership and enhance security.
This white paper provides an overview of IGMP and how it can support IPTV networks. IGMP is the protocol used to control multicast traffic delivery and allows clients to join and leave multicast groups, representing TV channels. When intermediate network devices are introduced, techniques like IGMP snooping, proxy routing, and query/report suppression are used to optimize multicast traffic delivery and IGMP message processing. These techniques aim to reduce bandwidth consumption and speed up channel change times.
Multicast is a communication protocol that allows a single sender to transmit data to multiple receivers simultaneously. It works by addressing data to a group of destination computers, reducing network load compared to unicast which requires separate transmissions to each receiver. The document outlines the history of multicast, how it works including reverse path forwarding using pruning and grafting, the IGMP protocol used by end systems to signal group membership, challenges in implementing multicast security, and applications such as audio/video broadcasting and software distribution where it provides benefits over unicast.
IP Multicast allows one-to-many and many-to-many communication through multicast addressing and routing protocols. It identifies multicast groups with class D IP addresses and uses IGMP for hosts to join and leave groups, while multicast routing protocols like PIM-SM and PIM-DM establish distribution trees. PIM-SM uses a shared tree by default rooted at a rendezvous point, while PIM-DM uses source-based trees and assumes dense receiver distribution initially pruned by leaves.
Marvin Hoffmann presented on multicasting for the next generation internet. He began with introducing himself and explaining why he chose this topic, which has always interested him. The presentation covered what multicasting is, the benefits of using it, how it works under both IPv4 and IPv6 including necessary protocols, and some challenges with multicasting. In the conclusion, Hoffmann restated that multicasting over the internet without a multicast backbone is still an interesting topic and thanked the audience for their attention, inviting any questions.
This document discusses the Internet Group Management Protocol (IGMP), which allows hosts to report their multicast group memberships to neighboring multicast routers. It describes the different versions of IGMP, including IGMPv1, IGMPv2, and IGMPv3. It also covers IGMP messages like membership queries, reports, and leaves. IGMP snooping is defined as a switch feature that optimizes multicast traffic delivery by only forwarding traffic to ports with interested receivers. Multicast Listener Discovery (MLD) serves a similar purpose for IPv6 as IGMP does for IPv4.
IP multicasting allows for efficient one-to-many and many-to-many communication on the internet. It uses multicast groups and protocols like IGMP for group management and PIM for multicast routing. PIM supports both source-based trees using flood-and-prune and core-based trees with a rendezvous point to deliver multicast data.
IP multicast is a method of sending Internet Protocol (IP) datagrams to a group of interested receivers in a single transmission. It is often employed for streaming media applications on the Internet and private networks.(wikipedia)
Multicasting allows data to be sent from one source to multiple receivers simultaneously. It provides an efficient way to disseminate information to many recipients. The document discusses IP multicast addressing, the IGMP protocol for joining and leaving multicast groups, multicast routing protocols like DVMRP and PIM, and methods for constructing multicast distribution trees like source-based and shared trees. Multicasting is important for applications like streaming media and teleconferencing that require one-to-many or many-to-many communication.
Basics of multicasting and its implementation on ethernet networksReliance Comm
Multicasting allows data to be sent from one source to multiple receivers simultaneously. It provides an efficient way to disseminate information to many recipients. The document discusses IP multicast addressing, the IGMP protocol for joining and leaving multicast groups, multicast routing protocols like DVMRP and PIM, and methods for constructing multicast distribution trees like source-based and shared trees. Multicasting is important for applications like streaming media and teleconferencing that require one-to-many or many-to-many communication.
This document discusses multicasting and multicast routing protocols. It defines unicast, multicast, and broadcast messages and describes applications of multicasting like accessing distributed databases and teleconferencing. It also explains different multicast routing protocols including MOSPF, DVMRP, CBT, and PIM, covering concepts like shortest path trees, flooding, and pruning. Finally, it describes MBONE which connects isolated multicast routers using tunneling.
This document discusses routing and multicast protocols at the MAC, routing, and application layers. It describes key modules like transmission, receiving, and neighbor list handling at the MAC layer. At the routing layer, it discusses unicast and multicast routing tables, forwarding, tree construction, and session maintenance. The application layer handles data transmission, multicast session initiation and termination, and route repair. It also compares source tree and shared tree approaches, and soft state and hard state maintenance mechanisms.
This document discusses MAC multicast and IGMP snooping. It provides information on:
1) MAC multicast uses the lower 23 bits of the IP multicast address mapped to the Ethernet address. IGMP snooping allows switches to learn which ports need to forward specific multicast traffic based on IGMP membership reports.
2) IGMP snooping works by intercepting IGMP messages between hosts and routers. When a switch receives a membership report, it adds the receiving port to the multicast group entry. Ports are removed if no reports are heard within a timeout.
3) The snooping process allows switches to build a MAC multicast filtering table per VLAN. Multicast traffic is then only forwarded
This document discusses multicasting and provides examples of how it can be used. Multicasting allows a server to send data to multiple clients simultaneously without using excessive bandwidth. It describes how multicasting works using UDP and IGMP, and provides examples of chat and picture sharing applications that can benefit from multicasting. The key aspects of multicasting covered are unicast, broadcast, and multicast addressing; the IGMP protocol; multicast routing; and application models for multicasting.
Implementation of multicast communication in internet
Individual hosts are configured as members of different multicast groups
One particular user may a member of many multicast groups
For a one multicast can be few members/nodes
IP Multicast group is identified by Class D address (224.0.0.0 – 239.255.255.255)
Every IP datagram send to a multicast group is transferred to all members of group
Multicast IP allows transmission of data to a group of destinations simultaneously. It provides more efficient use of network resources than unicast. The key challenges of multicast include defining group addresses, replicating packets in routers/switches, and managing group membership and traffic distribution without knowledge of all members. IGMP allows hosts to join/leave multicast groups and routers to maintain knowledge of groups with local members to direct traffic only to necessary links.
Unicast involves sending data from one computer to another, with one sender and one receiver. Multicast sends data to a group of devices that have joined the multicast group, with one sender but multiple potential receivers. Broadcast sends data from one computer that is then forwarded to all connected devices, with one sender and all devices receiving the broadcast traffic.
MLD is the IPv6 equivalent of IGMPv2 for IPv4. It uses ICMPv6 messages to enable routers to discover the set of multicast addresses for which there are listening nodes on each attached interface. MLD messages include Multicast Listener Query to query for listeners, Multicast Listener Report for listeners to report interest, and Multicast Listener Done for listeners to inform routers they are no longer listening.
Anycast is a new address type in IPv6 that refers to one among many interfaces with the same address. It is used to identify sets of routers or servers. Anycast addresses are allocated from unicast space and packets sent to an anycast address are routed to the nearest interface. Multicast addresses use a class D range in IPv4 from 224.0.0.0 to 239.255.255.255 and have a specific format in IPv6 to identify multicast groups and allow delivery of packets to many destinations.
- Anycast is a new type of address in IPv6 that allows an address to be assigned to multiple interfaces but packets are only routed to the nearest interface, unlike multicast which routes to all interfaces. It can be used to identify sets of routers.
- Multicast allows delivery of packets to many destinations like interactive conferencing and dissemination of content. In IPv4 it uses class D addresses and in IPv6 it uses addresses with prefix FF.
- IPv6 nodes are assigned multicast addresses that correspond to solicited node addresses used for neighbor discovery and all nodes/routers addresses for different address scopes.
1. Routing is the process of forwarding packets between source and destination networks through routing devices. Routing protocols are used for topology and path discovery.
2. Routers maintain routing tables containing paths to known destinations and routing information like metrics, next hops, and ages. Administrative distances define route preferences.
3. The Internet uses interior gateway protocols (IGPs) within autonomous systems (ASes) and exterior gateway protocols (EGPs) between ASes. Common IGPs include RIP, OSPF, IS-IS. BGP is a prominent EGP.
Modes of communication for group messaging include multicast, broadcast, anycast and unicast. Groups are dynamic with processes able to join or leave. Design issues involve whether groups are open or closed, peer-to-peer or hierarchical, and how membership is managed. Hardware and software approaches exist to implement group communication mechanisms like multicast, with hardware multicast using network addresses and software using multiple unicasts. Reliability and ordering of multicast messages must also be considered.
This document discusses IPv6 for IP Telephony. It provides background on IPv6 and describes its core protocols including IPv6, ICMPv6, MLD, and ND. It also covers IPv6 addressing and routing, including IPv6 address autoconfiguration, IPv6 routing, and IPv6 addressing structures like unicast and multicast addresses. Finally, it discusses the benefits of using IPv6 for IP Telephony, highlighting features like its large address space, efficient addressing and routing, and support for quality of service.
This document describes a Wireshark lab to analyze the IP protocol by capturing packets from an execution of the traceroute program using different packet sizes. Key points:
1. The student is instructed to run traceroute with packet sizes of 56 bytes, 2000 bytes, and 3500 bytes to generate an IP packet trace with and without fragmentation.
2. Questions are provided to analyze fields in IP packet headers like the TTL, identification, and fragmentation flags to understand how the IP protocol functions.
3. Analyzing the traceroute replies reveals the routers between the source and destination while pattern in identification fields show unique datagram identification. Fragmentation is observed when packet size exceeds the MTU.
Anycast is a new address type in IPv6 that refers to one among many interfaces with the same address. It is used to identify sets of routers or servers. Anycast addresses are allocated from unicast space and packets sent to an anycast address are routed to the nearest interface. Multicast addresses use a class D range in IPv4 from 224.0.0.0 to 239.255.255.255 and have a specific format in IPv6 to identify multicast groups and are mapped to Ethernet addresses for multicast transmission.
Here are the steps to examine routes using PathPing and TraceRt:
1. Open a command prompt as Administrator.
2. To examine the route using PathPing, type:
pathping www.microsoft.com
3. Examine the output and note the routers used to reach the destination.
4. To get a quicker response, use TraceRt:
tracert www.microsoft.com
5. Note the routers displayed in the output. TraceRt and PathPing may display different results due to timing.
Examining routes will help understand the network path and identify any issues that could impact connectivity. You can then use this information for configuring static routes if needed.
Design and Implementation of Dynamic Routing in Wireless NetworksSatish Reddy
This document summarizes a student's research on designing and implementing dynamic routing in wireless networks. It discusses several dynamic routing algorithms including SPRA, ECMP, AODV, and proposes a new algorithm called DDRA. DDRA aims to improve security and throughput by routing consecutive packets along different paths instead of the same path. Evaluation shows DDRA has less path similarity, higher throughput, and is less vulnerable to attacks like eavesdropping compared to other algorithms. The document also covers related topics like routing methods, protocols, and a security-enhanced routing table design.
Zdalna komunikacja sieciowa - zagadnienia sieciowe Agnieszka Kuba
This document discusses remote communication and networking concepts. It covers transmission modes, Ethernet basics, the TCP/IP model including layers, IP addressing and subnets, network devices like routers and firewalls, protocols like TCP, UDP, DNS, DHCP, and VPN technology. Mobile networks including 2G, 3G, 4G and LTE standards are also summarized along with examples of mobile remote access solutions.
This document discusses IP multicasting and provides an overview of key concepts. It covers IP class D addressing for multicasting, the IGMP protocol for hosts to join and leave multicast groups, and different strategies for multicasting across routers including broadcast, multiple unicast, and distribution trees. It also discusses practical applications of multicasting and various multicast routing protocols like DVMRP, MOSPF, and PIM.
Multicast IP addresses range from 224.0.0.0 to 239.255.255.255. The document discusses well-known multicast addresses, calculating multicast MAC addresses from IP addresses, and protocols for managing multicast traffic distribution including IGMP, CGMP, IGMP snooping, and RGMP. IGMP is used by hosts to join and leave multicast groups and by routers to manage multicast traffic forwarding. Version 2 is the default and includes features like group-specific queries and shorter leave latency. CGMP and IGMP snooping allow switches to optimize multicast forwarding.
Multicasting allows data to be sent from one source to multiple receivers simultaneously. It provides an efficient way to disseminate information to many recipients. The document discusses IP multicast addressing, the IGMP protocol for joining and leaving multicast groups, multicast routing protocols like DVMRP and PIM, and methods for constructing multicast distribution trees like source-based and shared trees. Multicasting is important for applications like streaming media and teleconferencing that require one-to-many or many-to-many communication.
Basics of multicasting and its implementation on ethernet networksReliance Comm
Multicasting allows data to be sent from one source to multiple receivers simultaneously. It provides an efficient way to disseminate information to many recipients. The document discusses IP multicast addressing, the IGMP protocol for joining and leaving multicast groups, multicast routing protocols like DVMRP and PIM, and methods for constructing multicast distribution trees like source-based and shared trees. Multicasting is important for applications like streaming media and teleconferencing that require one-to-many or many-to-many communication.
This document discusses multicasting and multicast routing protocols. It defines unicast, multicast, and broadcast messages and describes applications of multicasting like accessing distributed databases and teleconferencing. It also explains different multicast routing protocols including MOSPF, DVMRP, CBT, and PIM, covering concepts like shortest path trees, flooding, and pruning. Finally, it describes MBONE which connects isolated multicast routers using tunneling.
This document discusses routing and multicast protocols at the MAC, routing, and application layers. It describes key modules like transmission, receiving, and neighbor list handling at the MAC layer. At the routing layer, it discusses unicast and multicast routing tables, forwarding, tree construction, and session maintenance. The application layer handles data transmission, multicast session initiation and termination, and route repair. It also compares source tree and shared tree approaches, and soft state and hard state maintenance mechanisms.
This document discusses MAC multicast and IGMP snooping. It provides information on:
1) MAC multicast uses the lower 23 bits of the IP multicast address mapped to the Ethernet address. IGMP snooping allows switches to learn which ports need to forward specific multicast traffic based on IGMP membership reports.
2) IGMP snooping works by intercepting IGMP messages between hosts and routers. When a switch receives a membership report, it adds the receiving port to the multicast group entry. Ports are removed if no reports are heard within a timeout.
3) The snooping process allows switches to build a MAC multicast filtering table per VLAN. Multicast traffic is then only forwarded
This document discusses multicasting and provides examples of how it can be used. Multicasting allows a server to send data to multiple clients simultaneously without using excessive bandwidth. It describes how multicasting works using UDP and IGMP, and provides examples of chat and picture sharing applications that can benefit from multicasting. The key aspects of multicasting covered are unicast, broadcast, and multicast addressing; the IGMP protocol; multicast routing; and application models for multicasting.
Implementation of multicast communication in internet
Individual hosts are configured as members of different multicast groups
One particular user may a member of many multicast groups
For a one multicast can be few members/nodes
IP Multicast group is identified by Class D address (224.0.0.0 – 239.255.255.255)
Every IP datagram send to a multicast group is transferred to all members of group
Multicast IP allows transmission of data to a group of destinations simultaneously. It provides more efficient use of network resources than unicast. The key challenges of multicast include defining group addresses, replicating packets in routers/switches, and managing group membership and traffic distribution without knowledge of all members. IGMP allows hosts to join/leave multicast groups and routers to maintain knowledge of groups with local members to direct traffic only to necessary links.
Unicast involves sending data from one computer to another, with one sender and one receiver. Multicast sends data to a group of devices that have joined the multicast group, with one sender but multiple potential receivers. Broadcast sends data from one computer that is then forwarded to all connected devices, with one sender and all devices receiving the broadcast traffic.
MLD is the IPv6 equivalent of IGMPv2 for IPv4. It uses ICMPv6 messages to enable routers to discover the set of multicast addresses for which there are listening nodes on each attached interface. MLD messages include Multicast Listener Query to query for listeners, Multicast Listener Report for listeners to report interest, and Multicast Listener Done for listeners to inform routers they are no longer listening.
Anycast is a new address type in IPv6 that refers to one among many interfaces with the same address. It is used to identify sets of routers or servers. Anycast addresses are allocated from unicast space and packets sent to an anycast address are routed to the nearest interface. Multicast addresses use a class D range in IPv4 from 224.0.0.0 to 239.255.255.255 and have a specific format in IPv6 to identify multicast groups and allow delivery of packets to many destinations.
- Anycast is a new type of address in IPv6 that allows an address to be assigned to multiple interfaces but packets are only routed to the nearest interface, unlike multicast which routes to all interfaces. It can be used to identify sets of routers.
- Multicast allows delivery of packets to many destinations like interactive conferencing and dissemination of content. In IPv4 it uses class D addresses and in IPv6 it uses addresses with prefix FF.
- IPv6 nodes are assigned multicast addresses that correspond to solicited node addresses used for neighbor discovery and all nodes/routers addresses for different address scopes.
1. Routing is the process of forwarding packets between source and destination networks through routing devices. Routing protocols are used for topology and path discovery.
2. Routers maintain routing tables containing paths to known destinations and routing information like metrics, next hops, and ages. Administrative distances define route preferences.
3. The Internet uses interior gateway protocols (IGPs) within autonomous systems (ASes) and exterior gateway protocols (EGPs) between ASes. Common IGPs include RIP, OSPF, IS-IS. BGP is a prominent EGP.
Modes of communication for group messaging include multicast, broadcast, anycast and unicast. Groups are dynamic with processes able to join or leave. Design issues involve whether groups are open or closed, peer-to-peer or hierarchical, and how membership is managed. Hardware and software approaches exist to implement group communication mechanisms like multicast, with hardware multicast using network addresses and software using multiple unicasts. Reliability and ordering of multicast messages must also be considered.
This document discusses IPv6 for IP Telephony. It provides background on IPv6 and describes its core protocols including IPv6, ICMPv6, MLD, and ND. It also covers IPv6 addressing and routing, including IPv6 address autoconfiguration, IPv6 routing, and IPv6 addressing structures like unicast and multicast addresses. Finally, it discusses the benefits of using IPv6 for IP Telephony, highlighting features like its large address space, efficient addressing and routing, and support for quality of service.
This document describes a Wireshark lab to analyze the IP protocol by capturing packets from an execution of the traceroute program using different packet sizes. Key points:
1. The student is instructed to run traceroute with packet sizes of 56 bytes, 2000 bytes, and 3500 bytes to generate an IP packet trace with and without fragmentation.
2. Questions are provided to analyze fields in IP packet headers like the TTL, identification, and fragmentation flags to understand how the IP protocol functions.
3. Analyzing the traceroute replies reveals the routers between the source and destination while pattern in identification fields show unique datagram identification. Fragmentation is observed when packet size exceeds the MTU.
Anycast is a new address type in IPv6 that refers to one among many interfaces with the same address. It is used to identify sets of routers or servers. Anycast addresses are allocated from unicast space and packets sent to an anycast address are routed to the nearest interface. Multicast addresses use a class D range in IPv4 from 224.0.0.0 to 239.255.255.255 and have a specific format in IPv6 to identify multicast groups and are mapped to Ethernet addresses for multicast transmission.
Here are the steps to examine routes using PathPing and TraceRt:
1. Open a command prompt as Administrator.
2. To examine the route using PathPing, type:
pathping www.microsoft.com
3. Examine the output and note the routers used to reach the destination.
4. To get a quicker response, use TraceRt:
tracert www.microsoft.com
5. Note the routers displayed in the output. TraceRt and PathPing may display different results due to timing.
Examining routes will help understand the network path and identify any issues that could impact connectivity. You can then use this information for configuring static routes if needed.
Design and Implementation of Dynamic Routing in Wireless NetworksSatish Reddy
This document summarizes a student's research on designing and implementing dynamic routing in wireless networks. It discusses several dynamic routing algorithms including SPRA, ECMP, AODV, and proposes a new algorithm called DDRA. DDRA aims to improve security and throughput by routing consecutive packets along different paths instead of the same path. Evaluation shows DDRA has less path similarity, higher throughput, and is less vulnerable to attacks like eavesdropping compared to other algorithms. The document also covers related topics like routing methods, protocols, and a security-enhanced routing table design.
Zdalna komunikacja sieciowa - zagadnienia sieciowe Agnieszka Kuba
This document discusses remote communication and networking concepts. It covers transmission modes, Ethernet basics, the TCP/IP model including layers, IP addressing and subnets, network devices like routers and firewalls, protocols like TCP, UDP, DNS, DHCP, and VPN technology. Mobile networks including 2G, 3G, 4G and LTE standards are also summarized along with examples of mobile remote access solutions.
This document discusses IP multicasting and provides an overview of key concepts. It covers IP class D addressing for multicasting, the IGMP protocol for hosts to join and leave multicast groups, and different strategies for multicasting across routers including broadcast, multiple unicast, and distribution trees. It also discusses practical applications of multicasting and various multicast routing protocols like DVMRP, MOSPF, and PIM.
Multicast IP addresses range from 224.0.0.0 to 239.255.255.255. The document discusses well-known multicast addresses, calculating multicast MAC addresses from IP addresses, and protocols for managing multicast traffic distribution including IGMP, CGMP, IGMP snooping, and RGMP. IGMP is used by hosts to join and leave multicast groups and by routers to manage multicast traffic forwarding. Version 2 is the default and includes features like group-specific queries and shorter leave latency. CGMP and IGMP snooping allow switches to optimize multicast forwarding.
Solving QoS multicast routing problem using aco algorithm Abdullaziz Tagawy
In IP multicasting messages are sent from the source node to all destination nodes. In order to meet QoS requirements an optimizing algorithm is needed. We propose an Ant Colony Optimization algorithm to do so. Ants release a chemical called pheromone while searching for food. They are capable of finding shortest path to their target. This can give an effective optimal solution to our Multicast Routing Problem.
One to many; Source is unicast address, but the destination is a group address (Class D)
When a router receives a packet, it may forward it through several of its ports
Router may discard the packet if it is not in the multicast path.
Flooding: A router forwards a packet out of all its port except the one from which the packet came. Flooding provides broadcasting, but it also creates loops. A router will receive the same packet over and over from different ports. Several copies of the same packet are circulated, creating traffic jams.
The document outlines the key components of IP multicasting including multicast addressing, groups, routing protocols, and properties of routing protocols. It discusses Internet Group Management Protocol (IGMP) and its role in allowing hosts to join and leave multicast groups. The document also explains the differences between opt-in and opt-out routing protocols, source-based and shared trees, and dense and sparse modes such as PIM-Dense Mode and PIM-Sparse Mode.
This document discusses implementing a multicast communication system using an existing data network to provide free TV channels. It describes how a company can set up such a system to offer IP television services, saving money compared to proprietary TV systems. The document outlines the advantages of multicast communication like reduced bandwidth usage compared to unicast. It also discusses challenges like lack of reliability and potential security issues. It provides an overview of the IGMP and PIM routing protocols that enable multicast routing and how they work with unicast routing.
Implementing multicast communication system making use of an existing data ne...iosrjce
This document discusses implementing a multicast communication system using an existing data network to offer free TV channels. It describes how a company can use multicast routing protocols like PIM and IGMP to efficiently stream video to multiple devices. The key advantages of multicast are reducing bandwidth usage and server load compared to unicast. It also discusses challenges like lack of reliability and potential security issues. The document provides an overview of PIM sparse and dense modes and how to configure a prototype multicast network with load balancing and failover between multiple rendezvous points for high availability.
RIP is a distance-vector routing protocol that uses hop count as its routing metric. It operates at the OSI application layer and uses port 520. The maximum number of hops in a RIP route is 15. There are three versions of RIP with RIP v2 being classless and supporting authentication. RIP timers include the update, invalid, hold down, and flush timers. OSPF is a link-state routing protocol that uses the SPF/Dijkstra algorithm to calculate the shortest path. It has five message types including hello, database description, link-state request, link-state update, and link-state acknowledgement messages.
Exterior Routing Protocols And Multi casting Chapter 16daniel ayalew
This document discusses exterior routing protocols and multicasting. It begins by explaining the limitations of distance-vector and link-state routing protocols for exterior routing between autonomous systems. It then describes path vector routing and the Border Gateway Protocol (BGP) which allows routers in different autonomous systems to exchange routing information. The document provides details on BGP neighbor acquisition, reachability, and network reachability procedures. It also discusses multicast addressing, protocols like IGMP for host group management, and multicast routing protocols like PIM that establish distribution trees independent of unicast routing.
IGMP (Internet Group Management Protocol) allows hosts to join and leave multicast groups, enabling efficient delivery of data from a sender to multiple receivers. It works between hosts and multicast routers to inform when a host wants to join or leave a multicast transmission. This avoids overloading the network by allowing data to be sent to all interested receivers simultaneously rather than requiring separate data streams to each device. Stanford University first specified IGMP in 1989 to manage dynamic groups for IP multicast transmissions.
IGMP (Internet Group Management Protocol) is used to manage multicast group membership on local networks. It allows multicast routers to keep track of which hosts on the network are interested in receiving packets for different multicast groups. IGMP uses query messages from routers to discover group members, and membership report and leave report messages from hosts in response. It employs mechanisms like sending reports twice and delayed responses to ensure routers accurately maintain lists of groups with interested members.
This document discusses different types of routing in computer networks: unicast, broadcast, and multicast. It focuses on multicast routing and describes several multicast routing protocols, including distance vector multicast routing protocol (DVMRP) which uses flooding, reverse path forwarding (RPF), reverse path broadcasting (RPB), and reverse path multicasting (RPM). It also discusses protocol independent multicast (PIM) which has two modes: dense mode PIM uses source-based trees while sparse mode PIM uses group-shared trees with a rendezvous point.
Introduction to the Network Layer: Network layer services, packet switching, network layer performance, IPv4 addressing, forwarding of IP packets, Internet Protocol, ICMPv4, Mobile IP Unicast Routing: Introduction, routing algorithms, unicast routing protocols. Next generation IP: IPv6 addressing, IPv6 protocol, ICMPv6 protocol, transition from IPv4 to IPv6. Introduction to the Transport Layer: Introduction, Transport layer protocols (Simple protocol, Stop-and-wait protocol, Go-Back-n protocol, Selective repeat protocol, Bidirectional protocols), Transport layer services, User datagram protocol, Transmission control protocol
NP - Unit 4 - Routing - RIP, OSPF and Internet Multicastinghamsa nandhini
Routing protocols like RIP and OSPF automate the distribution of routing information between routers. RIP is a distance-vector protocol that uses hop counts as its metric. It faces problems like slow convergence after failures. OSPF is a link-state protocol that uses shortest path first algorithm for routing. It provides faster convergence. IP multicast uses a special address range and delivery mechanisms to efficiently deliver data from one source to multiple receivers in a group.
This document discusses various concepts in multicast routing including unicasting, multicasting, source-based trees, group-shared trees, and multicast routing protocols. It provides examples and diagrams to illustrate key differences between unicast and multicast routing as well as different approaches to multicast routing such as reverse path forwarding, reverse path broadcasting, and core-based trees. Common multicast routing protocols including MOSPF, PIM, and CBT are also introduced along with the concept of tunneling to connect isolated multicast networks.
Group communication allows a process to send a single message to multiple recipients through multicast operations. It provides features like fault tolerance through replicated services, where client requests are multicast to all servers performing the same operation. While multicast has no guarantees about delivery or ordering, it enables applications like discovery of servers in spontaneous networks or propagation of event notifications. IP multicast implements group communication by allowing a sender to transmit a single packet to a multicast group specified by a class D address. Membership in multicast groups is dynamic and packets may be lost or arrive out of order.
Group communication allows a process to send a single message to multiple recipients through multicast operations. It provides features like fault tolerance through replicated services, where client requests are multicast to all servers performing the same operation. IP multicast builds on the internet protocol to transmit a single packet to a multicast group specified by a class D address. It has reliability issues since messages may be lost between multicast routers or if a router fails, and ordering is not guaranteed as packets over the internet may arrive out of order.
This document discusses unicasting and multicasting in computer networks. It provides details on:
- The key differences between unicasting (one-to-one communication) and multicasting (one-to-many communication), including how routers handle forwarding for each.
- Common applications that use multicasting like audio/video distribution, file sharing, and conferencing.
- Approaches to multicast routing including source-based trees, group-shared trees, and protocols like PIM, CBT, and MBONE tunneling to connect isolated multicast networks.
- Mechanisms used in multicast routing protocols like RPF, pruning/grafting, and IGMP to discover multicast group members
Similar to NetSim Technology Library- Advanced Routing (20)
The document provides information about simulating Vehicular Adhoc Networks (VANETS) using NetSim and SUMO. It discusses:
1. Key features of the NetSim VANET module including support for IEEE 802.11p, DSRC/WAVE protocols, routing protocols, RF propagation modeling, and interfacing with SUMO.
2. The steps to create a VANET scenario in NetSim including importing a SUMO configuration file, setting node/link/application properties, enabling traces, and running the simulation.
3. Details about the IEEE 802.11p protocol stack implementation in NetSim and how it works.
4. How to create custom road
NetSim Technology Library - Software defined networksVishal Sharma
Software Defined Networking (SDN) module is featured from NetSim v11 onwards. This
module features an SDN controller which can be used to control packet forwarding of all Layer
3 devices in the Network.
NetSim Technology Library- Military radio-tdma-and-dtdmaVishal Sharma
This document describes the features and usage of NetSim's military radio module, which supports TDMA and DTDMA protocols. It discusses how to set up a simulation scenario in NetSim, configure node and environment properties, run the simulation, and view results. Key features covered include node join/leave functionality, DTDMA packet size limits, and using the DTDMA slot planner to allocate slots to nodes in a predefined pattern. Example simulations demonstrate TDMA slot allocation and analyzing results, as well as DTDMA packet size analysis and round robin slot allocation.
NetSim MANETs component can be interfaced with
Component 6 (IOT) module to run 802.15.4 in MAC/PHY
Component 9 (VANETs) module to run IEEE 1609 WAVE in MAC/PHY
Military Radio Add on to run TDMA/DTDMA in MAC/PHY
NetSim Long Term Evolution (LTE) Networks library includes LTE/LTE-A networks, LTE
Femto Cell, LTE D2D and LTE VANET. The LTE libraray allows you to connect, if required,
with Internetwork devices such as Routers, Switches etc running Ethernet, Wireless LAN, IP
Routing, TCP / UDP.
This document provides instructions for simulating legacy networks like Pure Aloha and Slotted Aloha using NetSim. It describes how to create a scenario by adding wireless nodes and adhoc links. It also explains how to set node, link, and application properties, enable packet tracing, and run the simulation. Finally, it notes that legacy networks are non-IP based and run standalone, so they cannot be connected to Internetworks. NetSim provides the ability to simulate these older legacy networks that are rarely used today for educational and research purposes only on an unsupported basis.
Internet of Things (IoT) is an ecosystem of connected physical objects that are accessible
through the internet. It is the network of physical objects that can communicate, sense or
interact with their internal states or the external environment.
An internetwork is a collection of two or more computer networks (typically Local Area
Networks or LANs) which are interconnected to form a bigger network. All networks in an
Internetwork have a unique network address. Routers interconnect the networks
A network simulator mimics the behaviour of networks but cannot connect to real networks.
NetSim Emulator enables users to connect NetSim simulator to real hardware and interact
with live applications.
Cognitive Radio Network simulation is available from v7 of NetSim. Cognitive Radio Networks
allows you to connect, if required, with Ethernet, Wireless LAN, IP Routing, TCP / UDP and
allows users to log packet and event traces.
This document provides an overview of simulating cellular networks like GSM and CDMA in NetSim. It describes the simulation GUI for creating scenarios with nodes like BTS, MSC and MS. It also explains how to set node/link properties, enable traces and plots, and run simulations. Two example simulations are presented - one demonstrating GSM handover and the other showing CDMA handover. The document notes that while source code is provided, further development of GSM and CDMA is not expected and they are provided on an unsupported basis only. It also provides a link to the latest FAQs on NetSim's cellular network library.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Choosing The Best AWS Service For Your Website + API.pptx
NetSim Technology Library- Advanced Routing
1. Ver 11.1 1
Advanced Routing
Contents
1 Multicast Routing Protocols ..................................................................................................2
1.1 IGMP..........................................................................................................................................2
1.1.1 Introduction .............................................................................................................2
1.1.2 IGMP Example..........................................................................................................6
1.1.3 Results....................................................................................................................12
1.2 PIM ..........................................................................................................................................16
1.2.1 Introduction ...........................................................................................................16
2 Access Control Lists (ACLs) .................................................................................................. 20
2.1 Introduction.............................................................................................................................20
2.2 ACL Example............................................................................................................................20
3 Virtual LAN (VLAN).............................................................................................................. 24
3.1 Introduction.............................................................................................................................24
3.1.1 When do we need a VLAN?....................................................................................25
3.1.2 Understanding Access and Trunk Links..................................................................26
3.2 Featured Examples..................................................................................................................28
3.2.1 Intra-VLAN..............................................................................................................28
3.2.2 Inter-VLAN..............................................................................................................32
3.2.3 Trunking .................................................................................................................36
4 Public IP Address & NAT (Network Address Translation) ...................................................... 43
4.1 Introduction.............................................................................................................................43
4.1.1 Public Address........................................................................................................43
4.1.2 Private Address ......................................................................................................43
4.1.3 Network address translation (NAT) .......................................................................44
4.2 Featured Examples..................................................................................................................45
5 Reference Documents......................................................................................................... 49
6 Latest FAQs ........................................................................................................................ 49
2. Ver 11.1 2
1 Multicast Routing Protocols
Note: Multicast routing protocols can be configured and run only if licenses for component 3 (advanced
routing) is available
Multicasting is one source sending a packet to multiple destinations. Group formation and
management is an integral part of multicasting.
IP Multicast Group Addressing: A multicast group is identified by its multicast group
address. Multicast packets are delivered to that multicast group address. Unlike unicast
addresses that uniquely identify a single host, multicast IP addresses do not identify a
particular host. To receive the data sent to a multicast address, a host must join the group that
address identifies. The data is sent to the multicast address and received by all the hosts that
have joined the group indicating that they wish to receive traffic sent to that group. The
multicast group address is assigned to a group at the source.
IP Class D Addresses: IP multicast addresses have been assigned to the IPv4 Class D
address space by IANA. The high-order four bits of a Class D address are 1110. Therefore,
host group addresses can be in the range 224.0.0.0 to 239.255.255.255. A multicast address
is chosen at the source (sender) for the receivers in a multicast group.
NetSim supports the following protocols to implement IP multicast routing:
IGMP is used between hosts on a LAN and the routers on that LAN to track the
multicast groups of which hosts are members.
Protocol Independent Multicast (PIM) is used between routers so that they can
track which multicast packets to forward to each other and to their directly connected
LANs.
1.1 IGMP
1.1.1 Introduction
About Multicasting
Multicasting is a data delivery method where one sender sends data to thousands of recipients
across a routed network. Multicasting is controlled-broadcasting; the sender transmits data to
specific recipients only.
3. Ver 11.1 3
With IP multicasting, a host sends packets to a multicast group of hosts anywhere within the
IP network by using a special form of IP address called the IP multicast group address. A
multicast group is made of an arbitrary number of hosts who join a group to receive packets
from the source. To ensure that a host receives data, the host must join the multicast group to
which the sender is sending data.
Note: You can configure and simulate multicast routing protocols such as IGMP and PIM, only if you have
licenses for component 3 (advanced routing).
About IGMP
The Internet Group Management Protocol (IGMP) is a communication protocol that hosts and
adjacent multicast routers on IPv4 networks use, to establish and manage the membership of
hosts and routing devices in multicast groups. Hosts and multicast routers use IGMP as
follows:
The hosts use IGMP to report their multicast group memberships to neighboring
multicast routers.
The multicast routers use IGMP to know the members in multicast groups, for every
physical network the multicast router is connected.
The multicast routers maintain a list of multicast group memberships for every network
to which the multicast routers are connected, and a timer for each membership.
The messages that IGMP uses are encapsulated in IP datagrams, with an IP protocol number
of 2. All IGMP messages are sent with an IP TTL of 1 and contain the IP Router Alert option
in their IP header. All IGMP messages sent between a host and the multicast router use the
following format:
Type: There are three types of IGMP messages that hosts and multicast routers
exchange, when they interact:
1. 0x11: Membership Query
The two sub of Membership Query messages are:
4. Ver 11.1 4
General Query: The multicast router sends a General Query to all hosts to
collect and update multicast group membership information for the hosts on
all networks to which the multicast router is connected.
Group-Specific Query: The multicast router sends Group-Specific Query
to the multicast group from which it received a leave group message, to find
out if other hosts in the group require multicast data.
2. 0x16: Version 2 Membership Report
Version 2 Membership Report is a message that a host sends to all other hosts
in the group or all hosts on the network, in response to a General Query or a
Group-Specific Query message from the multicast router.
3. 0x17: Leave Group (Not available with NetSim)
Hosts use the Leave Group message to tell the multicast router that they intend
to leave the group.
Max Response Time: Maximum Response Time is a random-value delay timer which
a host sets, for the host to send a Version 2 Membership Report to other hosts in the
group, after the host receives a Group-Specific Query message.
Checksum: The Checksum is the 16-bit one's complement of the one's complement
sum of the whole IGMP message (the entire IP payload).
Group Address: The multicast router sets the Group Address to zero when it sends
a General Query and sets to the Group Address to the address of the multicast group
when it sends a Group-Specific Query.
How IGMP Works
If a router has multiple physical interfaces on a single network, IGMP runs only on one of
physical interfaces. Hosts, on the other hand, need to use all interfaces that have
memberships associated with them.
For every network the multicast router is connected to, the multicast router performs one of
the following roles: Querier or Non-Querier. There is normally only one Querier per physical
network.
5. Ver 11.1 5
At startup, all multicast routers start as a Querier on every network to which the multicast
routers are connected. If a multicast router hears a Query message from another multicast
router with a lower IP address, the first multicast router must perform the role of a Non-Querier
on the network which has the multicast router with a lower IP address. If a multicast router
does not hear a Query message from another multicast router for a time duration defined by
the Other Querier Present Interval, the multicast router persists with the role of the Querier.
Now, the multicast router sends one of the two Membership Query messages:
General Query to all hosts to collect and update multicast group membership
information: The multicast router sends the General Query to the all-systems
multicast group (224.0.0.1), with a Group Address field set to 0, and with a Max
Response Time for the Query Response Interval.
When a host receives the General Query, the host sets the delay timers for every group
(excluding the all-systems group) to which the host belongs, on the interface on which
it received the query.
The host sets every timer to a different random value, by using the highest clock
granularity available on the host, and by choosing a value between 0 and the Max
Response Time. The Max Response Time is specified in the General Query packet.
Group-Specific Query to the multicast group from which it received a leave
group message: The multicast router sends the Group-Specific Query to the multicast
group from which it received a leave group message, and with a Max Response Time
for the Query Response Interval. This helps the multicast router to learn if there are
other members on the group and if the group needs multicast data.
When a host receives the Group-Specific Query, the host sets the delay timers for
every group to which the host belongs, on the interface on which it received the query.
The host sets every timer to a different random value by choosing a value between 0
and the Max Response Time. The Max Response Time is specified in the Group-
Specific Query packet.
If the delay timer for a group has started, the host resets the delay time to a random value only
if the requested Max Response Time is less than the time left in the active delay timer.
When a group's delay timer expires, the host multicasts a Version 2 Membership Report to
other hosts in the group, with an IP TTL of 1. If the host receives a Version 2 Membership
6. Ver 11.1 6
Report (version 1 or 2) from another host in the same group, when the host’s timer is active,
the host stops the timer for the group from which it received the report. The host also does
send a report to other hosts, to avoid duplicate reports and conserve the bandwidth on the
network.
When a multicast router receives a Version 2 Membership Report, it does the following:
Adds the multicast group from which it received the Version 2 Membership Report, to
the list of multicast group memberships on the network on which it received the Version
2 Membership Report.
Sets the timer for the membership to the Group Membership Interval.
Refreshes the timer, when the multicast router receives another Version 2 Membership
Report from the same group.
If the multicast router does not receive any Version 2 Membership Reports from a multicast
group before the Group Membership Interval timer expires, the multicast router assumes that
the group has no members and that it need not forward multicast data for that group.
The multicast router may also receive an unsolicited Version 2 Membership Report from a
host when the hosts intends to join a multicast group.
1.1.2 IGMP Example
This example explains how IGMP works to multicast data in interconnected networks.
The network modelled consists of:
A subnet with 4 wired nodes, a multicast router, and a multicast application running
on one of the wired nodes.
IGMP is running on all the wired nodes.
IGMP is running on the multicast router.
Only a few nodes receive multicast traffic.
NetSim uses the following defaults for IGMP simulations:
The multicast destination address is set to 239.12.14.5.
The IGMP protocol starts only after 1 second in to the simulation.
The multicast application starts only after 5 seconds in to the simulation.
Note that NetSim does not support the following in IGMP:
7. Ver 11.1 7
Leave Group message
IGMP v1 compatibility
Open NetSim, Select Examples->Advanced-Routing->IGMP-Configuration as shown below:
The following network diagram illustrates what the NetSim UI displays when you open
the example configuration file for IGMP.
1. See that by default, NetSim has enabled IGMP on the router, as follows:
a. Right-click the router and click Properties.
The Router pop-up window appears.
b. Click NETWORK LAYER in the left area.
8. Ver 11.1 8
c. IGMP_Status drop-down list is set to TRUE.
d. Click OK.
2. See that by default, NetSim has enabled IGMP on a node, as follows:
a. Right-click a wired node (say Wired_Node_2) and click Properties.
The Wirednode pop-up window appears.
b. Click NETWORK LAYER in the left area.
c. IGMP_Status drop-down list is set to TRUE.
The Wirednode pop-up window displays the following parameters you can
configure for IGMP, on the node:
Robustness_variable: The Robustness_variable parameter allows
you tune your subnet to a specific number of lost packets (packet loss)
in the subnet.
Query_Interval(s): The Query_Interval(s) parameter allows you to
specify the interval (in seconds) between two successive General
Queries that a Querier multicast router sends.
Last_Member_Q_Intvl(s): The Last_Member_Q_Intvl(s) parameter
allows you specify the interval (in seconds) between two successive
Group-Specific Query messages that a multicast router sends to hosts.
Unsol_Report_Intvl(s): The Unsol_Report_Intvl(s) parameter allows
you specify the interval (in seconds) between two successive
unsolicited Version 2 Membership Reports that hosts send to the
multicast group.
The following image illustrates the Wirednode pop-up window and the
parameters you can configure for IGMP, on the node.
9. Ver 11.1 9
d. Click OK.
3. (Optional) Do the following to modify the parameters of IGMP.
To modify the value of the Robustness_variable, enter a value in the
Robustness_variable text box.
The default value of the Robustness_variable parameter is 2.
You can enter a value between 2 and 10.
NetSim does not allow you to enter a value that is less than 2. If you enter a
value that is less than 2, NetSim resets the value to 2.
Increase the value of the Robustness_variable to more than 2, if you want to
simulate a subnet that must lose more packets.
By default, IGMP is robust to (Robustness Variable-1) packet losses.
To modify the value of the Query_Interval(s), enter a value in seconds, in the
Query_Interval(s) text box.
The default value of the Query_Interval(s) parameter is 125 seconds.
You can enter a value between 1 and 3600 seconds.
10. Ver 11.1 10
Fine-tune the Query_Interval(s) parameter to control the number of IGMP
messages on the subnet.
To modify the value of the Query_Interval(s), enter a value in seconds, in the
Last_Member_Q_Intvl(s) text box.
The default value of the Last_Member_Q_Intvl(s) parameter is 1 second.
You can enter a value between 1 and 25 seconds.
Fine-tune the Last_Member_Q_Intvl(s) parameter to make your subnet less or
more bursty of IGMP messages.
To modify the value of the Query_Interval(s), enter a value in seconds, in the
Unsolicited_Report_Interval(s) text box.
The default value of the Last_Member_Q_Intvl(s) parameter is 10 seconds.
Fine-tune the Unsolicited_Report_Interval(s) parameter to make your subnet
less or more bursty of IGMP messages.
You can enter a value between 1 and 10,000 seconds.
4. Repeat steps 3 on other nodes to see that NetSim has enabled IGMP and step 4 on
other nodes, if you to modify the IGMP parameters.
5. To configure a multicast application:
a. Click the Application icon located in the toolbar.
The Application pop-up window appears.
b. See that by default, NetSim has set the following properties for the multicast
application:
i. Application_Method = MULTICAST.
ii. Source_ID = 2, which means Wired_Node_2 node is the source of the
application and the multicast traffic.
iii. Destination_Count = 2, which means two nodes will receive multicast
traffic from the multicast application.
11. Ver 11.1 11
iv. Destination_ID = 3, 4, which means, Wired_Node_3 and
Wired_Node_4 nodes must receive multicast traffic from the multicast
application.
v. Set application start time to 30s.
c. (Optional) Modify the properties except (i).
Note: You add more than one destination IDs, by separating two successive
numbers by a “,” (comma). The following image illustrates the properties of the
multicast application.
d. Click OK.
6. See that by default, NetSim has enabled the Packet Trace and Event Trace icons
located in the toolbar.
7. To start and run the simulation:
a. Click the Run icon located in the toolbar.
b. Enter a numerical value in the Simulation Time text box, say 50s.
12. Ver 11.1 12
c. Click OK.
NetSim simulates IGMP for the time set
1.1.3 Results
After NetSim simulates IGMP, a Simulation Results window appears.
You can do the following on this window:
Print the results that NetSim displays in the Simulation Results window.
View the packet trace details in a .CSV file and save the .CSV file to your computer.
View the event trace details in a .CSV file and save the .CSV file to your computer.
Export the results that NetSim displays in the Simulation Results window, in a
spreadsheet.
Close the Simulation Results window and return to your simulation.
NetSim also saves the last instance of your simulation for you to view, analyse, and
download the results.
Interpreting the IGMP Simulation
Before you analyse the packet trace and event trace results, we recommend that you first
interpret how IGMP worked with the parameters you specified. So, you must first view the
simulation.
To view and interpret the simulation:
1. Close the Simulation Results window and return to your simulation.
2. Click the View Animation icon located on the toolbar.
The NetSim Packet Animation window appears.
3. Click the Play icon located on the toolbar.
You will see that the simulation runs IGMP.
The details of the packet traversing in your network appear as table located below the
simulation window.
4. (Optional) To fine-tune the speed of the animation, use the Animation Speed slider
located on the toolbar.
You will see the following happen in the animation:
13. Ver 11.1 13
i. Initially, all nodes (Wired_Node_2, 3, 4 and 5) receive the
IGMP_Memebership_Query message from Router_1.
ii. When a node receives the IGMP_Memebership_Query message, the node
sends the IGMP_V2_Membership_Report to Router_1 indicating that it is
interested to join the multicast group.
You can see that Wired_Node_3 sends the IGMP_V2_Membership_Report
message to Router_1. Wired_Node 2, 4 and 5 also send the
IGMP_V2_Membership_Report message to Router_1.
iii. Router_1 makes an entry for the membership in its routing table.
The following image illustrates IGMP at work.
When NetSim completes the simulation, the Simulation Results window appears.
Analyzing the Packet Trace Results
Now that you have seen the simulation for IGMP, we will analyze the communication between
the nodes and the router.
To view and analyze the packet trace results:
1. On the Simulation Results window, click Open Packet Trace located in the left area.
14. Ver 11.1 14
A .CSV appears.
2. Open the .CSV file and filter the PACKET_ID column by 0 and 1.
You will see the following in the .CSV file.
i. Router_1 broadcasts the IGMP_Memebership_Query message to all the
nodes.
ii. When a node receives the IGMP_Memebership_Query message, the node
sends the IGMP_V2_Membership_Report message to the Router_1.
iii. The IGMP protocol starts to work only after 1 second in to the simulation.
The following image illustrates (i), (ii), and (iii).
iv. The multicast application Wired_Node_2 starts to send multicast traffic to
Wired_Node_3 and Wired_Node_4 only after 5 seconds in to the simulation.
This is because, in NetSim, the multicast application starts after 5 seconds by
default.
v. Wired_Node_2 multicasts Constant Bit Rate (CBR) packets only to
Wired_Node_3 and Wired_Node_4.
The following image illustrates (iv), and (v).
vi. Hosts send the IGMP_V2_Membership_Report to 224.0.0.1 to the multicast
application sends multicast traffic to 239.12.14.5.
The following image illustrates (vi).
15. Ver 11.1 15
IGMP Event Trace Analysis:
Now that you have seen the results of packet trace, we will analyze the event trace for this
IGMP simulation.
To view the event trace results:
1. On the Simulation Results window, click Open Event Trace located in the left area.
A .CSV appears.
2. Open the .CSV file and filter the Event_Type column by NETWORK_OUT and
TIMER_EVENT.
You will see the following sub-events in the Subevent_Type column:
a. IGMP_DelayTimer: This sub-event occurs when a node sets the delay timers
for every group (excluding the all-systems group) to which the node belongs,
on the interface on which it received the query, after the node receives a
General Query from the multicast router.
b. IGMP_GroupMembershipTimer: This sub-event occurs when the multicast
router refreshes the group membership interval timer, every time it receives a
membership report for a multicast group. If this timer expires, the multicast
router removes this group from the list of destinations for multicast traffic.
c. IGMP_SendQuery: This sub-event occurs when the multicast router
periodically (based on Query Interval) sends a Query message on every
network to which the multicast router is connected, to solicit multicast group
membership information.
d. IGMP_SendStartupQuery: This subevent occurs when the multicast router
sends the Startup query count to quickly and reliably determine the multicast
group membership information, at startup.
16. Ver 11.1 16
e. IGMP_UnsolicitedReportTimer: If the initial membership report is lost or
damaged, this timer repeats once or twice after short delays, after every
Unsolicited Report Interval.
f. JOIN_MULTICAST_GROUP: This sub-event occurs when a node sends the
join multicast group message, when the node decides to join a multicast
group on an interface.
In NetSim, a node joins a multicast group only after 5 seconds in to the simulation.
The following image illustrates that hosts join the multicast group after 5 seconds.
1.2 PIM
1.2.1 Introduction
Protocol-Independent Multicast or PIM is a group of multicast routing protocols for Internet
Protocol (IP) networks. PIM distributes data in one-to-many and many-to-many multicast
modes over a LAN, WAN or the Internet. PIM builds Multicast Distribution Tree (MDT) loop-
free trees to enable multicast data distribution over a network.
PIM is termed protocol-independent because PIM does not include its own topology discovery
mechanism; PIM uses routing information available from other routing protocols such as
Enhanced Interior Gateway Routing Protocol (EIGRP), Open Shortest Path First (OSPF), and
static routes.
PIM also does not build its own routing tables. PIM uses the unicast routing table that IGP
creates, to create a loop free MDT and uses the unicast routing table to perform the reverse
path forwarding (RPF). Unlike other routing protocols, PIM does not send and receive routing
updates between routers.
In a PIM-enabled network, a Rendezvous Point (RP) router is the point where other routers in
the PIM protocol’s domain exchange information. All routers in the PIM protocol’s domain must
17. Ver 11.1 17
provide a mapping to the RP router. In a PIM enabled network, only the RP router knows the
active sources for the entire PIM protocol’s domain. The other routers just need to know how
to reach the RP router. This way, the RP router matches the receivers with the sources in the
PIM protocol’s domain.
The RP router is downstream from the source and forms one end of the Shortest Path Tree
(SPT). The RP router is upstream from the receiver and forms one end of the Rendezvous
Point Tree (RPT).
The following figure illustrates a PIM-enabled network with the routers, source node, and the
destination node.
To configure PIM in NetSim:
Create a network as shown below
18. Ver 11.1 18
Set PIM status as TRUE in all routers as shown below:
Set IGMP status as true for all devices.
Configure the PIM properties as per the below screenshot and click on Add.
Then click on Accept
19. Ver 11.1 19
Configure the same PIM properties for all routers in the network
Application Properties:
Set the application properties as per the screenshot below – Multicast application with source
5 and destinations 6, 7, 8, 9, 10
Set IGMP_Status to TRUE in all wired nodes since we are running multicast application
Enable packet Trace and run simulation for 10s. Open Packet trace and filter PACKET_ID to
1. Users can observe there is no formation of loops between source and destinations.
20. Ver 11.1 20
2 Access Control Lists (ACLs)
2.1 Introduction
Access Control Lists or ACLs are filters that routers use to control which routing updates or
packets are permitted or denied in or out of a network. An ACL contains a sequential list of
“permit” or deny statements (rules) that apply to IP packets originating or destined to hosts, IP
addresses and upper-layer IP protocols.
An ACL tells the router what types of packets to: permit or deny. The router using the ACL
does the following when it finds packets inbound to or outbound from a network:
If the router finds packets inbound or outbound categorized against the permit
statements, the router forwards the packets to the next hop in the network.
If the router finds packets inbound or outbound categorized against the deny
statements, the router blocks and drops the packets at the router’s interface. The
packets cannot reach the intended destination host or IP address.
ACLs control traffic in one direction at a time, on an interface. To allow inbound and outbound
traffic from a host, IP address, or for a protocol, you must create two ACLs, one for each
direction, one for inbound and one for outbound traffic.
2.2 ACL Example
This example models a network and simulates an ACL to understand how ACL filters
inbound and outbound traffic at a router’s interface.
The network modelled consists of:
A subnet with 3 wired nodes, a router, and an application running on one of the wired
nodes.
ACLs with both permit and deny rules are defined on the interfaces of the router.
NetSim uses the following default for ACL simulations:
The direction of the ACL is set to both. This means the ACL applies to both inbound
and outbound traffic.
21. Ver 11.1 21
1. Open NetSim, Select Examples->Advanced-routing->ACL-Configuration as shown
below:
The following network diagram illustrates what the NetSim UI displays when you open
the example configuration file for ACL.
2. See that by default, NetSim has enabled ACL on the router, as follows:
a. Right-click the router and click Properties.
The Router pop-up window appears.
22. Ver 11.1 22
b. Click NETWORK LAYER in the left area.
c. ACL_Status drop-down list is set to Enable.
d. Click OK.
3. To see the ACL rules on the router, click Configure ACL.
The ACL Window pop-up window appears.
Set the properties as shown below and click on OK.
4. To start and run the simulation:
a. Click the Run icon located in the toolbar.
b. Enter a numerical value in the Simulation Time text box, say 10.
c. Click OK.
NetSim simulates ACL for the time you asked NetSim to run the simulation.
The throughput for first application is zero, since the ACL blocks traffic flow in Router's 3rd
interface from Wired Node 2 to Wired Node 4
1. Configuring ACL - Via .txt file
Go to system temp path (Using Run command “ %temp%Netsim”)
Open the Router_1_Firewall.txt file and edit the properties manually.
Note: If Device name is changed it has to be updated in both .txt file and GUI
23. Ver 11.1 23
This file is loaded into GUI with text fields and contents
24. Ver 11.1 24
3 Virtual LAN (VLAN)
3.1 Introduction
VLAN is called as virtual local area network, used in Switches and it operates at layer2 and
Layer3. A VLAN, is a group of hosts which communicate as if they were attached to the same
broadcast domain, regardless of their physical location.
For example, all workstations and servers used by a particular workgroup team can be
connected to the same VLAN, regardless of their physical connections to the network or the
fact that they might be intermingled with other teams. VLANs have the same attributes as
physical LANs, but you can group end stations even if they are not physically located on the
same LAN segment.
A VLAN behaves just like a LAN in all respects but with additional flexibility. By using VLAN
technology, it is possible to subdivide a single physical switch into several logical switches.
VLANs are implemented by using the appropriate switch configuration commands to create
the VLANs and assign specific switch interfaces to the desired VLAN.
Switches implement VLANs by adding a VLAN tag to the Ethernet frames as they enter the
switch. The VLAN tag contains the VLAN ID and other information, which is determined by the
interface from which the frame enters the switch. The switch uses VLAN tags to ensure that
each Ethernet frame is confined to the VLAN to which it belongs based on the VLAN ID
contained in the VLAN tag. The VLAN tags are removed as the frames exit the switch on the
way to their destination.
VLAN 20 VLAN 30VLAN10
10
25. Ver 11.1 25
Any port can belong to a VLAN, and unicast, broadcast, and multicast packets are forwarded
and flooded only to end stations in that VLAN. Each VLAN is considered a logical network.
Packets destined for stations that do not belong to the VLAN must be forwarded through a
router. In the below screenshot, the stations in the development department are assigned to
one VLAN, the stations in the marketing department are assigned to another VLAN, and the
stations in the testing department are assigned to another VLAN.
3.1.1 When do we need a VLAN?
You need to consider using VLAN’s in any of the following situations:
You have more than 200 devices on your LAN
You have a lot of broadcast traffic on your LAN
Groups of users need more security are being slowed down by too many broadcasts
Groups of users need to be on the same broadcast domain because they are running
same applications or just make a single switch into multiple virtual switches
3.1.1.1 VLAN ID
VLAN 20
VLAN 30
VLAN 10
26. Ver 11.1 26
VLANs are identified by a VLAN ID (a number between 0 – 4095), with the default VLAN on
any network being VLAN 1. Each port on a switch or router can be assigned to be a member
of a VLAN (i.e., to allow receiving and sending traffic on that VLAN).
For example: On a switch, traffic that is sent to a port that is a member of VLAN2, may be
forwarded to any other VLAN2 port on the switch, and it can also travel across a trunk port
(connections between switches) to another switch and forwarded to all VLAN2 ports on that
switch. Traffic will not be forwarded to ports that are on a different VLAN ID.
3.1.2 Understanding Access and Trunk Links
The links connecting the end devices are called access links. These are the links usually
carrying the Data VLAN information
The link between the switches is called trunk link. It carries packets from all the VLANs.
VLAN 3
VLAN 2VLAN 2
Trunk LinkVLAN 3
Access Link VLAN2 traffic flow
27. Ver 11.1 27
3.1.2.1 Access Link
Access link connection is the connection where switch port is connected with a device that
has a standardized Ethernet NIC. Standard NIC only understand IEEE 802.3 or Ethernet II
frames. Access link connection can only be assigned with single VLAN. That means all
devices connected to this port will be in same broadcast domain.
For example twenty users are connected to a hub, and we connect that hub with an access
link port on switch, then all of these users belong to same VLAN. If we want to keep ten users
in another VLAN, then we need to plug in those ten users to another hub and then connect it
with another access link port on switch.
3.1.2.2 Trunk Link
Trunk link connection is the connection where switch port is connected with a device that is
capable to understand multiple VLANs. Usually trunk link connection is used to connect two
switches. Trunking allows us to send or receive VLAN information across the network. To
support trunking, original Ethernet frame is modified to carry VLAN information.
Trunk Link
Access Link
Access Link Access Link
Access Link
28. Ver 11.1 28
3.2 Featured Examples
3.2.1 Intra-VLAN
Open NetSim, Select Examples->Advanced-routing->VLAN->Intra-VLAN as shown below:
The following network diagram illustrates what the NetSim UI displays when you open the
example configuration file for Intra VLAN.
Trunk LineTrunk Line
29. Ver 11.1 29
Intra-VLAN communication is a mechanism in which hosts in same VLAN can communicate
to each other. Create a network as per the above screenshot. Edit the properties of L2 Switch
1 as per the table below
L2 Switch 1
Interface ID VLAN Status VLAN ID VLAN Port
Type
Interface_1 TRUE 2 Access _Port
Interface_2 TRUE 2 Access _Port
Interface_3 TRUE 3 Access _Port
To configure VLAN settings in L2 switch go to VLAN_Status parameter under INTERFACE_1
(ETHERNET) and set as TRUE.
VLAN 1
VLAN 2
30. Ver 11.1 30
Then click Configure VLAN under VLAN_GUI parameter. The following window will open.
Now set the properties as shown below and after changing the properties click on Add button
to add it in the VLAN table
Similarly change the VLAN properties for Interface ID 2 and click on ADD
31. Ver 11.1 31
To add another VLAN click plus icon, after that add the VLAN properties for Interface ID 3
Set the VLAN ID’s for the L2_Switch Interface_1 as shown below:
32. Ver 11.1 32
Similarly set VLAN_ID as 2 for L2_Switch Interface_2 and VLAN_ID as 3 for L2_Switch
Interface_3
Run simulation for 10 seconds and observe the throughputs.
Throughput (Mbps)
Application 1 0.58
Application 2 0
The throughput for 2nd
application is zero because the source and destination is in different
VLANs, thereby traffic flow or communication between 2 VLANs using Layer2 switch is not
possible. To overcome this problem, an L3 switch is used.
3.2.2 Inter-VLAN
VLANs divide broadcast domains in a LAN environment. Whenever hosts in one VLAN need
to communicate with hosts in another VLAN, the traffic must be routed between them. This is
known as Inter-VLAN routing. This can be possible by using L3 switch.
What is a layer 3 switch?
Layer 3 switch (also known as a multi-layer switch) is a multi-functional device that have the
same functionality like a layer 2 switch, but behaves like a router when necessary. It’s
33. Ver 11.1 33
generally faster than a router due to its hardware based routing functions, but it’s also more
expensive than a normal switch.
Open NetSim, Select Examples->Advanced-routing->VLAN->Inter-VLAN as shown below:
The following network diagram illustrates what the NetSim UI displays when you open the
example configuration file for Inter VLAN.
34. Ver 11.1 34
Create a network as per the above screenshot. Edit all the wired node properties shown
below:
Node
Wired Node
2
Wired Node
3
Wired Node
4
Wired Node
5
Wired Node
6
I/f1_Ethernet I/f1_Ethernet I/f1_Ethernet I/f1_Ethernet I/f1_Ethernet
IP Address 10.0.0.4 10.1.0.4 11.2.0.4 11.3.0.4 11.4.0.4
Default
Gateway
10.0.0.3 10.1.0.3 11.2.0.3 11.3.0.3 11.4.0.3
Edit the L3 Switch 1 properties shown below:
Switch
I/f1_Ethernet I/f2_Ethernet I/f3_Ethernet I/f4_Ethernet I/f5_Ethernet
IP Address IP Address IP Address IP Address IP Address
L3
Switch 1
10.0.0.3 10.1.0.3 11.2.0.3 11.3.0.3 11.4.0.3
L3 Switch 1
Interface ID VLAN Status VLAN ID VLAN Port
Type
Interface_1 TRUE 2 Access _Port
VLAN 2 VLAN 3
35. Ver 11.1 35
Interface_2 TRUE 2 Access _Port
Interface_3 TRUE 3 Access _Port
Interface_4 TRUE 3 Access _Port
Interface_5 TRUE 3 Access _Port
Configure the VLAN properties of L3 Switch 1 as per the below screenshots:
36. Ver 11.1 36
Run simulation for 10 seconds and observe the throughputs.
In this case, application1 is in VLAN2, application2 is in VLAN3 and application 3 is in between
VLAN2 and VLAN3. From the above results, the throughput for application 3 (different VLANs)
is non zero, because of using L3 switch. So, communication between 2 VLANs is possible
using L3 Switch.
3.2.3 Trunking
Open NetSim, Select Examples->Advanced-routing->VLAN->Access-and-Trunk-Links as
shown below:
Throughput (Mbps)
Application 1 0.58
Application 2 0.58
Application 3 0.58
37. Ver 11.1 37
The following network diagram illustrates what the NetSim UI displays when you open the
example configuration file for Inter Access and Trunk links.
Create a network and edit the properties as per the above screenshot. Edit all the wired
node properties shown below:
VLAN 3
VLAN 2
38. Ver 11.1 38
Edit the L3 Switch 1 and L3 Switch 2 properties shown below:
Change subnet mask of all L3 Switch interfaces to 255.255.255.0
Switch I/f1_Ethernet I/f2_Ethernet I/f3_Ethernet
IP Address IP Address IP Address
L3 Switch 1 192.168.1.1 192.168.2.1 192.168.3.1
L3 Switch 2 192.168.3.2 192.168.1.2 192.168.2.2
Node Wired Node
3
Wired Node
4
Wired Node
5
Wired Node
6
I/f1_Ethernet I/f1_Ethernet I/f1_Ethernet I/f1_Ethernet
IP
Address
192.168.1.3 192.168.1.4 192.168.2.3 192.168.2.4
Default
Gateway
192.168.1.1 192.168.1.2 192.168.2.1 192.168.2.2
Subnet
Mask
255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
39. Ver 11.1 39
L3 Switch 1
Interface ID VLAN Status VLAN ID VLAN Port
Type
Interface_1 TRUE 2 Access _Port
Interface_2 TRUE 3 Access _Port
Interface_3 TRUE 1 Trunk _Port
L3 Switch 2
Interface ID VLAN Status VLAN ID VLAN Port
Type
Interface_1 TRUE 1 Trunk _Port
Interface_2 TRUE 2 Access _Port
Interface_3 TRUE 3 Access _Port
40. Ver 11.1 40
Click on Configure VLAN in L3_Switch_1 and set the properties for VLAN 2 as per the
screenshot shown below
Set the properties for VLAN 3 as per the screenshot
41. Ver 11.1 41
After setting the properties of VLAN2 and VLAN3 click on Accept.
Go to L3_Switch_1 properties -> Network_Layer -> Configure Static Route IP
Set the properties in Static Route IP window as per the screenshot below and click on Add.
Click on Accept
Note: Disable TCP in Transport Layer in Wired Node 3 and Wired Node 5
Run simulation for 10 seconds and observe the throughput.
Throughput (Mbps)
Application 1 0.57
Application 2 0.57
42. Ver 11.1 42
The above results conclude that Trunking allows us to send or receive any VLAN information
across the network.
43. Ver 11.1 43
4 Public IP Address & NAT (Network
Address Translation)
4.1 Introduction
4.1.1 Public Address
A public IP address is assigned to every computer that connects to the Internet where
each IP is unique. Hence there cannot exist two computers with the same public IP address
all over the Internet. This addressing scheme makes it possible for the computers to “find each
other” online and exchange information. User has no control over the IP address (public) that
is assigned to the computer. The public IP address is assigned to the computer by the Internet
Service Provider as soon as the computer is connected to the Internet gateway.
4.1.2 Private Address
An IP address is considered private if the IP number falls within one of the IP address ranges
reserved for private networks such as a Local Area Network (LAN). The Internet Assigned
Numbers Authority (IANA) has reserved the following three blocks of the IP address space for
private networks (local networks):
Class Starting IP
address
Ending IP
address
No. of hosts
A 10.0.0.0 10.255.255.255 16,777,216
B 172.16.0.0 172.31.255.255 1,048,576
C 192.168.0.0 192.168.255.255 65,536
Private IP addresses are used for numbering the computers in a private network including
home, school and business LANs in airports and hotels which makes it possible for the
computers in the network to communicate with each other. For example, if a network A
consists of 30 computers each of them can be given an IP starting from 192.168.0.1 to
192.168.0.30.
Devices with private IP addresses cannot connect directly to the Internet. Likewise, computers
outside the local network cannot connect directly to a device with a private IP. It is possible to
44. Ver 11.1 44
interconnect two private networks with the help of a router or a similar device that supports
Network Address Translation.
If the private network is connected to the Internet (through an Internet connection via ISP) then
each computer will have a private IP as well as a public IP. Private IP is used for
communication within the network whereas the public IP is used for communication over the
Internet.
4.1.3 Network address translation (NAT)
NAT (Network Address Translation or Network Address Translator) is the virtualization of
Internet Protocol (IP) addresses. NAT helps to improve security and decrease the number of
IP addresses an organization needs.
A device that is configured with NAT will have at least one interface to the inside network and
one to the outside network. In a typical environment, NAT is configured at the exit device
between a stub domain (inside network) and the backbone. When a packet leaves the domain,
NAT translates the locally significant source address into a globally unique address. When a
packet enters the domain, NAT translates the globally unique destination address into a local
address. If more than one exit point exists, each NAT must have the same translation table.
NAT can be configured to advertise to the outside world only one address for the entire
network. This ability provides additional security by effectively hiding the entire internal
network behind that one address. If NAT cannot allocate an address because it has run out of
addresses, it drops the packet and sends an Internet Control Message Protocol (ICMP) host
unreachable packet to the destination.
45. Ver 11.1 45
NAT is secure since it hides network from the Internet. All communications from internal
private network are handled by the NAT device, which will ensure all the appropriate
translations are performed and provide a flawless connection between internal devices and
the Internet.
In the above figure, a simple network of 4 hosts and one router that connects this network to
the Internet. All hosts in the network have a private Class C IP Address, including the router's
private interface (192.168.0.1), while the public interface that's connected to the Internet has
a real IP Address (203.31.220.134). This is the IP address the Internet sees as all internal IP
addresses are hidden.
4.2 Featured Examples
Open NetSim, Select Examples->Advanced-routing->Public-IP-Addressing-and-NAT as
shown below:
192.168.1(Public IP)192.168.01(Private
IP address)
Network router
(Gateway)
192.168.0.5
192.168.04
192.168.0.3
192.168.0.2
Internet
46. Ver 11.1 46
The following network diagram illustrates what the NetSim UI displays when you open the
example configuration file for NAT.
Internal Private
network
Internet cloud equivalent
Internal Private
network
47. Ver 11.1 47
Wired node Properties:
Wired
Node
IP address Subnet
mask
7 10.0.0.2 255.0.0.0
8 10.0.0.3 255.0.0.0
9 10.0.0.4 255.0.0.0
10 172.16.0.2 255.255.0.0
11 172.16.0.3 255.255.0.0
12 172.16.0.4 255.255.0.0
Router Properties:
Router Interface IP address Subnet mask
Router 1 Interface1_WAN 11.1.1.1 255.0.0.0
Interface2_Ethernet 10.0.0.1 255.0.0.0
Router 2 Interface1_WAN 11.1.1.2 255.0.0.0
Interface2_WAN 12.1.1.1 255.0.0.0
Router 3 Interface1_WAN 12.1.1.2 255.0.0.0
Interface2_WAN 13.1.1.2 255.0.0.0
Router 4 Interface1_WAN 13.1.1.1 255.0.0.0
Interface2_Ethernet 172.16.0.1 255.255.0.0
Configure the application with Source_ID as 7 and Destination_ID as 10
Set start time =50
Inside
I/F
48. Ver 11.1 48
Enable Packet trace and run simulation for 100 seconds.
After simulation open packet trace and filter Packet Id to 1
SOURCE_IP – source node IP (Node)
DESTINATION_IP – gateway IP (Router/ Node)
GATEWAY_IP – IP of the device which is transmitting a packet (Router/ Node)
NEXT_HOP_IP – IP of the next hop (Router/ Node)
Source node 7 (10.0.0.2) wouldn’t know how to route to the destination and hence its default
gateway is Router 1 with interface IP (10.0.0.1). The first line in the above screenshot specifies
49. Ver 11.1 49
packet flow from Source Node 7 to L2 Switch 5 with SOURCE_IP (10.0.0.2),
DESTINATION_IP (10.0.0.1), GATEWAY_IP (10.0.0.2) and NEXT_HOP_IP (10.0.0.1). Since
Switch is Layer2 device there is no change in the IPs in second line. Third line specifies the
packet flow from Router 1 to Router 2 with SOURCE_IP (10.0.0.2), DESTINATION_IP
(13.1.1.1- IP of the router connected to destination. Since OSPF is running, the router is looks
up the route to its destination from routing table), GATEWAY_IP (11.1.1.1) and
NEXT_HOP_IP (11.1.1.2) and so on.
5 Reference Documents
1. IEEE802.1Q for Virtual LAN
2. IETF 7761 for Protocol Independent Multicast – Sparse Mode (PIM-SM)
3. RFC 2236 for Internet Group Management Protocol, Version 2
6 Latest FAQs
Up to date FAQs on NetSim’s Advance Routing library is available at
https://tetcos.freshdesk.com/support/solutions/folders/14000113123