This document discusses load balancing using Per Connection Classifier (PCC) in MikroTik RouterOS. It begins with an introduction and example use case. It then explains that PCC divides incoming data into streams and uses routing rules to distribute traffic across multiple internet connections. Specifically, it uses hashing on packet header fields to sort traffic into streams, and then packet marking and routing tables to ensure each stream follows the designated path out the specified interface. Finally, it stresses the importance of understanding how the various components of the PCC solution work together.
MPLS enables packets to be forwarded based on labels rather than IP addresses. PE routers add labels to incoming packets and remove labels from outgoing packets. P routers swap or pop labels to forward packets. MPLS with L3 VPN allows private networks in different locations to communicate securely over a shared infrastructure by associating routes with virtual routing instances (VRFs) and advertising them using BGP. An example configuration shows VRF and BGP configuration, along with commands to view MPLS label bindings and packet forwarding information.
This document provides information about load balancing techniques in networking. It discusses several types of load balancing including sub-packet load balancing using MLPPP, per-packet load balancing using bonding, per-connection load balancing using nth, per-address-pair load balancing using ECMP and PCC, custom load balancing using policy routing, and bandwidth-based load balancing using MPLS traffic engineering tunnels. It also provides examples and instructions for configuring various load balancing options in MikroTik RouterOS.
“MPLS is that it’s a technique, not a service.”
The fundamental concept behind MPLS is that of labeling packets. In a traditional routed IP network,
each router makes an independent forwarding decision for each packet based solely on the packet’s
network-layer header. Thus, every time a packet arrives at a router, the router has to “think through”
where to send the packet next.
MPLS VPN provides a way to extend private network connectivity over a shared public infrastructure in a secure manner. It utilizes MPLS to create virtual point-to-point connections between customer sites. There are two main types of MPLS VPNs - Layer 3 VPNs which use extensions to BGP to exchange routing information between customer edge routers and provider edge routers, and Layer 2 VPNs which extend customer layer 2 networks across the MPLS backbone by encapsulating layer 2 frames with labels.
MPLS is a forwarding scheme that uses fixed-length labels to simplify packet forwarding. It allows explicit routing and fast restoration from failures. MPLS headers carry labels that are used by routers to forward packets based on forwarding equivalence classes. This enables traffic management and quality of service routing. Local protection techniques like bypass tunnels and label stacking allow MPLS to provide fast restoration by pre-establishing backup label switched paths.
The document provides an overview of MPLS (Multi-Protocol Label Switching) concepts and components. It discusses how MPLS separates routing from forwarding by using labels to forward packets based on the label rather than the IP address. It describes MPLS components like edge label switching routers (ELSR or PE), label switching routers (LSR or P), and the label distribution protocol (LDP). It also provides examples of MPLS forwarding and MPLS VPN operation.
- MPLS stands for Multi-Protocol Label Switching and was originally introduced to improve router forwarding speeds and meet bandwidth management requirements in IP networks.
- MPLS uses labels to forward packets based on their destination rather than long IP addresses. Label Edge Routers assign labels and interface with external networks, while Label Switch Routers in the core switch packets based on their labels.
- MPLS establishes Label Switched Paths between ingress and egress routers to efficiently route packets through the network based on forwarding tables that map incoming to outgoing labels. This allows traffic engineering and quality of service control.
Tutorial about MPLS Implementation with Cisco Router, this first of two chapter discuss about What is MPLS, Network Design, P, PE, and CE Router Description, Case Study of IP MPLS Implementation, IP and OSPF Routing Configuration
MPLS enables packets to be forwarded based on labels rather than IP addresses. PE routers add labels to incoming packets and remove labels from outgoing packets. P routers swap or pop labels to forward packets. MPLS with L3 VPN allows private networks in different locations to communicate securely over a shared infrastructure by associating routes with virtual routing instances (VRFs) and advertising them using BGP. An example configuration shows VRF and BGP configuration, along with commands to view MPLS label bindings and packet forwarding information.
This document provides information about load balancing techniques in networking. It discusses several types of load balancing including sub-packet load balancing using MLPPP, per-packet load balancing using bonding, per-connection load balancing using nth, per-address-pair load balancing using ECMP and PCC, custom load balancing using policy routing, and bandwidth-based load balancing using MPLS traffic engineering tunnels. It also provides examples and instructions for configuring various load balancing options in MikroTik RouterOS.
“MPLS is that it’s a technique, not a service.”
The fundamental concept behind MPLS is that of labeling packets. In a traditional routed IP network,
each router makes an independent forwarding decision for each packet based solely on the packet’s
network-layer header. Thus, every time a packet arrives at a router, the router has to “think through”
where to send the packet next.
MPLS VPN provides a way to extend private network connectivity over a shared public infrastructure in a secure manner. It utilizes MPLS to create virtual point-to-point connections between customer sites. There are two main types of MPLS VPNs - Layer 3 VPNs which use extensions to BGP to exchange routing information between customer edge routers and provider edge routers, and Layer 2 VPNs which extend customer layer 2 networks across the MPLS backbone by encapsulating layer 2 frames with labels.
MPLS is a forwarding scheme that uses fixed-length labels to simplify packet forwarding. It allows explicit routing and fast restoration from failures. MPLS headers carry labels that are used by routers to forward packets based on forwarding equivalence classes. This enables traffic management and quality of service routing. Local protection techniques like bypass tunnels and label stacking allow MPLS to provide fast restoration by pre-establishing backup label switched paths.
The document provides an overview of MPLS (Multi-Protocol Label Switching) concepts and components. It discusses how MPLS separates routing from forwarding by using labels to forward packets based on the label rather than the IP address. It describes MPLS components like edge label switching routers (ELSR or PE), label switching routers (LSR or P), and the label distribution protocol (LDP). It also provides examples of MPLS forwarding and MPLS VPN operation.
- MPLS stands for Multi-Protocol Label Switching and was originally introduced to improve router forwarding speeds and meet bandwidth management requirements in IP networks.
- MPLS uses labels to forward packets based on their destination rather than long IP addresses. Label Edge Routers assign labels and interface with external networks, while Label Switch Routers in the core switch packets based on their labels.
- MPLS establishes Label Switched Paths between ingress and egress routers to efficiently route packets through the network based on forwarding tables that map incoming to outgoing labels. This allows traffic engineering and quality of service control.
Tutorial about MPLS Implementation with Cisco Router, this first of two chapter discuss about What is MPLS, Network Design, P, PE, and CE Router Description, Case Study of IP MPLS Implementation, IP and OSPF Routing Configuration
this pdf contain simple method to install one of important MPLS service MPLS L3VPN and explain how mpls distribute labels
use simple routing protocol with customer (static route) to initiate L3VPN
This document discusses MPLS VPN and its three main types: point-to-point VPNs using pseudowires to encapsulate traffic between two sites; layer 2 VPNs called VPLS that provide switched VLAN services across sites; and layer 3 VPNs known as VPRN that utilize VRF tables to segment routing for each customer using BGP. It describes how MPLS VPN works using CE, PE, and P routers to forward labeled packets through the provider network and pop the label at the destination PE to deliver the packet. Finally, it provides additional resources for learning more about MPLS VPN technologies.
Tutorial about MPLS Implementation with Cisco Router, this second of two chapter discuss about MPLS Configuration, LDP Configuration, VPN Services, L2VPN (VLL & VPLS) and L3VPN (VPRN).
it also contain case study and implementation of VLL, VPLS, and VPRN
MPLS (Multi Protocol Label Switching) is a mechanism for data transport that operates on the data link layer below protocols like IP. It is mainly used to forward IP datagrams and Ethernet traffic. MPLS overcomes limitations of traditional IP routing by bringing the intelligence of routing with the performance of switching, and supports VPNs, QoS, and effective bandwidth management. MPLS works by assigning short fixed-length labels to packets, and routers use the labels stored in forwarding tables to make switching decisions instead of long IP addresses.
This document provides an overview of MPLS (Multiprotocol Label Switching) including:
- MPLS uses labels instead of IP addresses to forward packets for benefits like decreased routing overhead and support for non-IP protocols.
- Key MPLS terminology includes label-switched routers that forward packets based on labels, edge routers that impose/remove labels, and label switched paths that define the path through the network.
- The MPLS control plane establishes label switched paths and the data plane uses forwarding based on pre-established labels for faster switching compared to IP routing.
The document provides an overview of Internet Enhanced Service (IES) on Alcatel-Lucent platforms. IES allows customer IP interfaces to participate in the same routing instance as the service network core. Key points include:
- IES provides Internet connectivity through logical IP interfaces with SAP access points.
- Multiple IES services can be created to separate customer IP interfaces.
- Features like QoS policy propagation using BGP (QPPB) and VRRP are supported on IES interfaces.
MPLS is a forwarding mechanism that uses labels instead of IP addresses to forward packets. It allows routers to forward based on simple label lookups rather than complex routing lookups. MPLS has benefits like supporting multiple applications and decreasing forwarding overhead on core routers. It has a control plane that exchanges routing information and labels, and a data plane that forwards packets based on labels. Label Switch Routers implement MPLS forwarding by exchanging labels and forwarding packets based on those labels.
This document discusses techniques for prioritizing traffic types and limiting bandwidth per user on a MikroTik router using RouterOS. It describes using mangle rules to mark traffic, a queue tree in the global-in HTB for initial prioritization and shaping, additional mangle rules to mark by client, and per-connection queues in interface HTBs to apply per-user limits. Address lists are also discussed to help reduce rule counts when applying limits by client.
Multi-Protocol Label Switching has become by far one of the most important Internet technologies of the last 15 years. From humble beginnings back in 1996-97, it is literally the defacto standard in a large majority of service provider networks today. This presentation, delivered to executives at MTNL, Mumbai (a large regional carrier in India), explains the key operational principles behind MPLS, and its significant applications.
The document discusses MPLS VPN configurations. It covers VPN concepts like overlay and peer models, benefits of MPLS VPNs, and how routing information is propagated between provider edge (PE) routers using MP-BGP. Key aspects include using virtual routing and forwarding (VRF) instances to isolate customer routes, extending prefixes with route distinguishers (RDs) to handle overlapping addresses, and exchanging VPN routes between PE routers in the provider network.
RCS Global Limited is a software and IT services company focused on providing quality solutions at reasonable prices in a timely manner. It aims to redefine IT consulting through excellent teamwork, total client satisfaction, and helping clients focus on their core businesses. The company offers various software suites and services including Medi-Suite, Edu-Suite, SAP, .NET, and Ramco. It is part of the RAMA Group established in 1992.
MPLS (Multi-Protocol Label Switching) simplifies packet forwarding by assigning labels to packets and using these labels for forwarding instead of long network addresses. It allows for traffic engineering and quality of service by establishing Label Switched Paths (LSPs) to direct different types of traffic over specific paths. MPLS supports various Layer 2 and Layer 3 protocols and improves network performance and scalability compared to traditional IP routing. It is widely used to implement virtual private networks (VPNs) across shared infrastructures.
This document provides an overview and student guide for the "Implementing Cisco MPLS (MPLS) Version 2.2" course. It introduces basic MPLS concepts including the MPLS architecture, labels, label stacks, and applications such as MPLS VPNs and traffic engineering. It also covers frame-mode MPLS implementation on Cisco IOS platforms, including configuration, monitoring, and troubleshooting tasks. Finally, it discusses MPLS VPN technology in depth, including the MPLS VPN architecture, routing model, and packet forwarding mechanisms.
MPLS stands for Multi-Protocol Label Switching, a framework specified by the IETF to efficiently forward, route, and switch traffic through a network. MPLS works at layer 2.5, using label switching to combine the benefits of circuit switching and packet switching. It allows separation of addressing and traffic through VPNs, improving security, bandwidth utilization, and user experience while reducing network complexity and congestion.
MPLS L3 VPN allows companies to offer Layer 3 VPN services with advantages like scalability, security, and support for duplicate IP addresses and different network topologies. The key components that enable this are VRF tables on PE routers that separate routing information for each customer to avoid duplicate IP issues, and MP-BGP which customizes VPN routing information using a Route Distinguisher, VPN label, and Route Target to support different VPN topologies. MPLS L3 VPN provides services like multi-homed sites for redundancy, hub-and-spoke networks, internet access with security, and extranets for inter-company communication.
MPLS Traffic Engineering provides mechanisms to optimize network traffic flow and efficiently utilize bandwidth. It determines paths based on additional parameters like available resources and constraints. This allows load balancing across unequal paths and routing around failed links or nodes. MPLS TE uses extensions to IGPs to distribute link attributes and tunnel information. Constrained Shortest Path First (CSPF) is used for path computation to find paths meeting constraints like bandwidth and affinities. Tunnels are set up using RSVP-TE and traffic can be forwarded down tunnels using methods like static routes, auto-routing, or policy routing. Fast Re-Route provides local repair of TE tunnels if a link or node fails to minimize traffic loss.
The document discusses Virtual Private Routed Network (VPRN) services. VPRNs use BGP and MPLS to provide Layer 3 VPN connectivity between customer sites. Each VPRN has its own routing table maintained by provider edge (PE) routers. PE routers exchange routes for each VPRN using MP-BGP. Routes include a Route Distinguisher to identify the VPRN. Tunnels using MPLS or GRE carry customer traffic across the provider network to the correct PE router based on the route label. The document outlines requirements, protocols, and features used to implement VPRNs such as route reflectors, route redistribution, and CE connectivity checks.
This document discusses bonding interfaces in Mikrotik routers. It begins with an overview of bonding and its benefits of higher throughput and failover. It then covers the different options for link monitoring and bonding modes, including active-backup, load balancing, and broadcast modes. It provides an example configuration of bonding two Ethernet interfaces together. Finally, it proposes testing the bonded bandwidth and provides references for further reading.
This document provides an overview and agenda for a presentation on VXLAN BGP EVPN technology. It begins with an introduction to VXLAN and EVPN concepts. It then outlines the agenda which includes explaining VXLAN configuration, EVPN configuration, underlay configuration, overlay configuration, and EVPN VXLAN service configuration. It also provides a sample migration from a legacy device configuration to a VXLAN BGP EVPN configuration. Various networking acronyms related to VXLAN and EVPN are defined. Sample vendor supported data center technologies and a VXLAN test topology are shown.
RouterOS v6 will include several new features and improvements, including support for new hardware, an updated Linux kernel, additional CPU architecture support, and a reworked QoS system. It features improved performance on multi-CPU systems, enhanced interface drivers, lifted CPU core limits, and simplified simple queue configuration. New capabilities include wireless advanced channels, SCEP protocol support, and more flexible DHCP options handling.
this pdf contain simple method to install one of important MPLS service MPLS L3VPN and explain how mpls distribute labels
use simple routing protocol with customer (static route) to initiate L3VPN
This document discusses MPLS VPN and its three main types: point-to-point VPNs using pseudowires to encapsulate traffic between two sites; layer 2 VPNs called VPLS that provide switched VLAN services across sites; and layer 3 VPNs known as VPRN that utilize VRF tables to segment routing for each customer using BGP. It describes how MPLS VPN works using CE, PE, and P routers to forward labeled packets through the provider network and pop the label at the destination PE to deliver the packet. Finally, it provides additional resources for learning more about MPLS VPN technologies.
Tutorial about MPLS Implementation with Cisco Router, this second of two chapter discuss about MPLS Configuration, LDP Configuration, VPN Services, L2VPN (VLL & VPLS) and L3VPN (VPRN).
it also contain case study and implementation of VLL, VPLS, and VPRN
MPLS (Multi Protocol Label Switching) is a mechanism for data transport that operates on the data link layer below protocols like IP. It is mainly used to forward IP datagrams and Ethernet traffic. MPLS overcomes limitations of traditional IP routing by bringing the intelligence of routing with the performance of switching, and supports VPNs, QoS, and effective bandwidth management. MPLS works by assigning short fixed-length labels to packets, and routers use the labels stored in forwarding tables to make switching decisions instead of long IP addresses.
This document provides an overview of MPLS (Multiprotocol Label Switching) including:
- MPLS uses labels instead of IP addresses to forward packets for benefits like decreased routing overhead and support for non-IP protocols.
- Key MPLS terminology includes label-switched routers that forward packets based on labels, edge routers that impose/remove labels, and label switched paths that define the path through the network.
- The MPLS control plane establishes label switched paths and the data plane uses forwarding based on pre-established labels for faster switching compared to IP routing.
The document provides an overview of Internet Enhanced Service (IES) on Alcatel-Lucent platforms. IES allows customer IP interfaces to participate in the same routing instance as the service network core. Key points include:
- IES provides Internet connectivity through logical IP interfaces with SAP access points.
- Multiple IES services can be created to separate customer IP interfaces.
- Features like QoS policy propagation using BGP (QPPB) and VRRP are supported on IES interfaces.
MPLS is a forwarding mechanism that uses labels instead of IP addresses to forward packets. It allows routers to forward based on simple label lookups rather than complex routing lookups. MPLS has benefits like supporting multiple applications and decreasing forwarding overhead on core routers. It has a control plane that exchanges routing information and labels, and a data plane that forwards packets based on labels. Label Switch Routers implement MPLS forwarding by exchanging labels and forwarding packets based on those labels.
This document discusses techniques for prioritizing traffic types and limiting bandwidth per user on a MikroTik router using RouterOS. It describes using mangle rules to mark traffic, a queue tree in the global-in HTB for initial prioritization and shaping, additional mangle rules to mark by client, and per-connection queues in interface HTBs to apply per-user limits. Address lists are also discussed to help reduce rule counts when applying limits by client.
Multi-Protocol Label Switching has become by far one of the most important Internet technologies of the last 15 years. From humble beginnings back in 1996-97, it is literally the defacto standard in a large majority of service provider networks today. This presentation, delivered to executives at MTNL, Mumbai (a large regional carrier in India), explains the key operational principles behind MPLS, and its significant applications.
The document discusses MPLS VPN configurations. It covers VPN concepts like overlay and peer models, benefits of MPLS VPNs, and how routing information is propagated between provider edge (PE) routers using MP-BGP. Key aspects include using virtual routing and forwarding (VRF) instances to isolate customer routes, extending prefixes with route distinguishers (RDs) to handle overlapping addresses, and exchanging VPN routes between PE routers in the provider network.
RCS Global Limited is a software and IT services company focused on providing quality solutions at reasonable prices in a timely manner. It aims to redefine IT consulting through excellent teamwork, total client satisfaction, and helping clients focus on their core businesses. The company offers various software suites and services including Medi-Suite, Edu-Suite, SAP, .NET, and Ramco. It is part of the RAMA Group established in 1992.
MPLS (Multi-Protocol Label Switching) simplifies packet forwarding by assigning labels to packets and using these labels for forwarding instead of long network addresses. It allows for traffic engineering and quality of service by establishing Label Switched Paths (LSPs) to direct different types of traffic over specific paths. MPLS supports various Layer 2 and Layer 3 protocols and improves network performance and scalability compared to traditional IP routing. It is widely used to implement virtual private networks (VPNs) across shared infrastructures.
This document provides an overview and student guide for the "Implementing Cisco MPLS (MPLS) Version 2.2" course. It introduces basic MPLS concepts including the MPLS architecture, labels, label stacks, and applications such as MPLS VPNs and traffic engineering. It also covers frame-mode MPLS implementation on Cisco IOS platforms, including configuration, monitoring, and troubleshooting tasks. Finally, it discusses MPLS VPN technology in depth, including the MPLS VPN architecture, routing model, and packet forwarding mechanisms.
MPLS stands for Multi-Protocol Label Switching, a framework specified by the IETF to efficiently forward, route, and switch traffic through a network. MPLS works at layer 2.5, using label switching to combine the benefits of circuit switching and packet switching. It allows separation of addressing and traffic through VPNs, improving security, bandwidth utilization, and user experience while reducing network complexity and congestion.
MPLS L3 VPN allows companies to offer Layer 3 VPN services with advantages like scalability, security, and support for duplicate IP addresses and different network topologies. The key components that enable this are VRF tables on PE routers that separate routing information for each customer to avoid duplicate IP issues, and MP-BGP which customizes VPN routing information using a Route Distinguisher, VPN label, and Route Target to support different VPN topologies. MPLS L3 VPN provides services like multi-homed sites for redundancy, hub-and-spoke networks, internet access with security, and extranets for inter-company communication.
MPLS Traffic Engineering provides mechanisms to optimize network traffic flow and efficiently utilize bandwidth. It determines paths based on additional parameters like available resources and constraints. This allows load balancing across unequal paths and routing around failed links or nodes. MPLS TE uses extensions to IGPs to distribute link attributes and tunnel information. Constrained Shortest Path First (CSPF) is used for path computation to find paths meeting constraints like bandwidth and affinities. Tunnels are set up using RSVP-TE and traffic can be forwarded down tunnels using methods like static routes, auto-routing, or policy routing. Fast Re-Route provides local repair of TE tunnels if a link or node fails to minimize traffic loss.
The document discusses Virtual Private Routed Network (VPRN) services. VPRNs use BGP and MPLS to provide Layer 3 VPN connectivity between customer sites. Each VPRN has its own routing table maintained by provider edge (PE) routers. PE routers exchange routes for each VPRN using MP-BGP. Routes include a Route Distinguisher to identify the VPRN. Tunnels using MPLS or GRE carry customer traffic across the provider network to the correct PE router based on the route label. The document outlines requirements, protocols, and features used to implement VPRNs such as route reflectors, route redistribution, and CE connectivity checks.
This document discusses bonding interfaces in Mikrotik routers. It begins with an overview of bonding and its benefits of higher throughput and failover. It then covers the different options for link monitoring and bonding modes, including active-backup, load balancing, and broadcast modes. It provides an example configuration of bonding two Ethernet interfaces together. Finally, it proposes testing the bonded bandwidth and provides references for further reading.
This document provides an overview and agenda for a presentation on VXLAN BGP EVPN technology. It begins with an introduction to VXLAN and EVPN concepts. It then outlines the agenda which includes explaining VXLAN configuration, EVPN configuration, underlay configuration, overlay configuration, and EVPN VXLAN service configuration. It also provides a sample migration from a legacy device configuration to a VXLAN BGP EVPN configuration. Various networking acronyms related to VXLAN and EVPN are defined. Sample vendor supported data center technologies and a VXLAN test topology are shown.
RouterOS v6 will include several new features and improvements, including support for new hardware, an updated Linux kernel, additional CPU architecture support, and a reworked QoS system. It features improved performance on multi-CPU systems, enhanced interface drivers, lifted CPU core limits, and simplified simple queue configuration. New capabilities include wireless advanced channels, SCEP protocol support, and more flexible DHCP options handling.
Mikrotik router backup and restore processTitas Sarker
This document discusses the Mikrotik router backup and restore process. It begins by explaining what a Mikrotik router is and why regularly backing up the router configuration is important to protect against hardware failures, theft, human errors, and natural disasters. It then outlines the different backup methods, including manual backups in Winbox and automatically scheduled backups using scripts. The document concludes by reviewing the restore process where the backup file is uploaded and the configuration is restored.
Dokumen tersebut membahas tentang DHCP Server pada Mikrotik yang digunakan untuk membantu distribusi IP, gateway, dan DNS secara otomatis ke beberapa komputer. DHCP Server akan memiliki pool IP yang bisa digunakan sebagai alokasi IP otomatis, dan jumlah pool dapat ditentukan sesuai kebutuhan. Mikrotik menyediakan wizard setup otomatis untuk membuat DHCP Server dengan mudah.
Dokumen ini memberikan panduan konfigurasi VLAN pada MikroTik SwitchOS. Terdapat penjelasan tentang pengaturan VLAN mode, VLAN ID, dan forwarding rules pada setiap port dan VLAN. Diberikan contoh topologi VLAN lab dengan 1 router dan 1 switch untuk membagi traffic ke 3 VLAN yang berbeda. Langkah-langkah konfigurasinya meliputi pengaturan port trunk, VLAN tab, dan VLANs tab pada SwitchOS.
This document provides an introduction to cloud computing, including:
- Defining cloud computing as using the internet/network to provide everything as a service, selling services instead of products.
- Describing infrastructure as a service, platform as a service, and software as a service.
- Introducing GLC Learning Center, an organization that provides online training, workshops, and webinars in Indonesia.
- Discussing some pros and cons of cloud computing, such as low costs but also risks of downtime, security, and vendor lock-in.
Limiting bandwidth of specific destination based on address listAchmad Mardiansyah
in this webinar, we are talking about limiting bandwidth of specific destination based on address list on mikrotik router. we also talking about the latest feature of mikrotik that is dynamic address-list. at the end of the session, there was a demo that shows how to configure the mikrotik router
Multicast routing configuration and lab example in MikroTik
video multicast routing 1 router
https://www.youtube.com/watch?v=nqUlUIB93Mg
video multicast routing 2 router over wireless
https://www.youtube.com/watch?v=eYEocGYsGZ4
Konfig VLC sebagai stream server multicast
https://www.youtube.com/watch?v=Z1lthcBSSrM
Konfig VLC sebagai player
https://www.youtube.com/watch?v=s2uTs8NRQpY
in this webinar, we were discussing about an introduction to mikrotik, network management, and the dude.
There are some demos of installing the dude on mikrotik, as well as some the dude features to manage several aspects of network elements.
the recording of this webinar will be uploaded on youtube: https://www.youtube.com/channel/UCI611_IIkQC0rsLWIFIx_yg
In this webinar, we are talking about BGP implementation on mikrotik router. the presentation starts with the fundamental of BGP and then discuss about Basic BGP setting on RouterOS
/International Agency for Research on Cancer(IARC)Claudiu Nemeş
International Agency for Research on Cancer(IARC) has
classified radiofrequency electromagnetic fields as possibly carcinogenic to humans(Group 2B),
based on an increased risk for glioma, a malignant type of brain cancer1
, associated with
wireless phone use.
This document summarizes a study on unionism in the Philippines. It begins by outlining the legal foundations for unionization and self-organization under the Philippine Labor Code. It then reviews literature on the history and development of trade unions globally and locally in response to industrialization and changing economic conditions. Tables show declining union registration and membership in the Philippines in recent decades. The document introduces various forms and roles of trade unions discussed in academic literature and traces the development of trade unionism in the Philippines in the post-WWII period.
Southwest Memorial Hospital in Cortez, Colorado was recently named one of the top 100 critical access hospitals in the United States. The hospital offers a wide range of medical services to the community including emergency care, surgery, imaging, and various outpatient services. Several new physicians have also joined the hospital's staff. The document also discusses Medicaid expansion and average hospital charges in Colorado.
This document summarizes a dispute between a family and the Building Services Authority (BSA) regarding defective bamboo flooring installed in the family's newly constructed home. The flooring buckled severely, preventing the family from moving in. While the BSA initially found in the family's favor, requiring the floors be replaced, the BSA later reversed its decision without informing the family. The family has spent $30,000 fighting the case so far and repairs are estimated to cost over $100,000. Brisbane's Lord Mayor criticized the BSA for being "bogged down with red tape" and failing to properly handle building disputes.
The document discusses a proposed joint venture between Health Spring, a US-based health insurance company, and St. Luke's Medical Center in the Philippines to establish Health Spring as a medical tourism facilitator. This would allow Health Spring to offer lower-cost medical procedures to its customers in the Philippines while also increasing business and revenues for St. Luke's. Key benefits include lower costs for Health Spring (20-80% savings on procedures), business expansion into medical tourism, and increased revenues and patient volumes for St. Luke's. A 3-year plan and potential risks are also outlined.
- LinkedIn operates a global backbone network to connect its datacenters and points of presence to support services for professional networking.
- The network previously used RSVP-TE tunnels to control traffic flows but faced issues with underutilized links, operational overhead, and tunnel setup failures.
- LinkedIn improved its traffic engineering by implementing a dynamic container LSP approach using multiple member RSVP-TE tunnels. This allows automatic adjustment of tunnels based on traffic thresholds and improves bandwidth utilization while reducing management overhead.
The document discusses different routing methods used in computer networks, including:
- Network-specific routing which treats all hosts on the same network as a single entity in the routing table.
- Host-specific routing which explicitly defines routes to individual host addresses in the routing table.
- Default routing which uses a single default route for all unknown destinations.
It also covers routing protocols like RIP and OSPF, explaining how they establish and maintain routing tables dynamically as the network changes. Distance vector protocols like RIP propagate full routing tables between routers, while link-state protocols like OSPF flood link state information to build independent views of the network topology.
Networking and Internetworking Devices21viveksingh
This document provides information on various networking and internetworking devices. It discusses hubs, which connect multiple networking cables together but do not amplify or filter signals. It covers bridges, which operate at the physical and data link layers to filter traffic between network segments. Routers are described as connecting LANs and WANs by routing packets based on logical addresses using routing tables. Gateways link different network types and protocols by translating between formats. Finally, switches and brouters are introduced, with switches offering intelligence beyond hubs to reduce congestion, and brouters combining routing and bridging capabilities.
This document discusses network protocols, structure, and scope. It defines what a network protocol is and describes some common protocols like Ethernet, Token Ring, FDDI, and ATM. It also discusses different types of network structures including peer-to-peer and client-server models, and various network topologies like bus, star, ring, and mesh. Finally, it covers the scope of different network types including local area networks (LANs), personal area networks (PANs), home area networks (HANs), wide area networks (WANs), campus networks, metropolitan area networks (MANs), virtual private networks (VPNs), backbone networks, and global area networks (GANs).
This document discusses network protocols and structure. It defines what a network protocol is and describes some common protocols like Ethernet, Token Ring, FDDI, and ATM. It also discusses different types of network models and structures including local area networks (LANs), personal area networks (PANs), home area networks (HANs), wide area networks (WANs), campus networks, metropolitan area networks, virtual private networks (VPNs), backbone networks, and global area networks (GANs). Finally, it covers different network topologies like bus, star, mesh, and ring topologies.
This document provides a summary of key concepts related to routing and routing protocols. It discusses routing and how routers forward packets from source to destination using routing tables. Common routing algorithms and protocols like RIP, OSPF, BGP, DVMRP and PIM are explained at a high level. Network concepts like metrics, areas, autonomous systems, and multicast addressing are also covered briefly. The document is intended to provide an overview of routing fundamentals and protocols for a computer networks course.
In part 4 of this BGP webinar series, we cover how to optimize Autonomous System paths, especially in cases of suboptimal international routes. Tips include monitoring layer 3 forwarding alongside BGP, monitoring reverse paths, layering covering prefixes, as well as prepending and MED.
Starting from key concepts, you'll learn how to recognize route leaks and hijacks in the data, alert for these events and proactively mitigate their impact. See the webinar recording at https://www.thousandeyes.com/webinars/detecting-hijacks-and-leaks
This document discusses switching, routing, and flow control in interconnection networks. It covers different switching mechanisms like packet switching and circuit switching. It also discusses routing algorithms and techniques to avoid deadlocks like virtual channels and deadlock-free routing. The key topics are how packets are routed through switches, challenges like tree saturation and deadlocks, and approaches to provide reliable communication while matching the capabilities of the network hardware.
This document provides an overview of communication in distributed systems. It discusses various communication models including remote procedure call, message-oriented middleware, and data streaming. It also covers fundamental communication concepts like protocols, layers in the OSI model, and widely-used protocols at each layer like TCP/IP. The document examines both connection-oriented and connectionless protocols and how communication works at the physical, data link, network, transport, and application layers.
Next-generation networks are becoming more complex and must support global workforces, legacy devices, and integrated voice, video, and data. Cisco's borderless network architecture addresses these challenges through a hierarchical design with core, distribution, and access layers that provide modularity, resiliency, and flexibility. Ethernet switches establish separate collision domains and extend broadcast domains, so network design must minimize broadcasts to prevent congestion.
Module 3 Part B - computer networks module 2 pptanushaj46
The document discusses several key issues in network layer design including store-and-forward packet switching, services provided to the transport layer, implementation of connectionless and connection-oriented services, and comparison of virtual-circuit and datagram networks. It also covers routing algorithms such as shortest path, flooding, distance vector, link state, and hierarchical routing.
Xin Jin
Princeton University
Research Track Part 1
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
A computer network connects two or more computers together to allow sharing of resources and communication between users. Common network types include local area networks (LANs) within a building, metropolitan area networks (MANs) within a city, and wide area networks (WANs) spanning multiple cities or countries. The topology, or layout of connections between devices, can take bus, star, ring or mesh forms. Protocols and layered network architectures like TCP/IP or OSI model provide standards for communication between networked devices.
This document provides an overview of metropolitan area networks (MANs) and wide area networks (WANs). It defines MANs and WANs, describes their key characteristics, and compares MAN technologies like SONET and Ethernet. It also covers WAN basics such as routing algorithms, congestion, and an example of WANs in smartphones. The document seeks to explain the differences between LANs, MANs and WANs and how data is transmitted over each type of network.
Converged network quality issues include lack of bandwidth, end-to-end delay, variation of delay (jitter), and packet loss. These issues are caused by multiple flows competing for limited bandwidth over network devices and links, resulting in increased processing, queuing, and propagation delays as well as dropped packets during congestion. Implementing quality of service features such as priority queuing, traffic shaping, and dropping can help address these issues by classifying and prioritizing important traffic.
This document outlines the course Fundamentals of Computer Networks. It discusses the goals of conveying principles and mechanisms to build scalable computer networks that can grow globally and support diverse applications. The course covers topics like routing, end-to-end protocols, congestion control, wireless networks, and applications through a combination of lectures, practical assignments, and conceptual assignments. It also provides an outline of the first lecture covering requirements, architecture, implementation, and an overview of chapters in the textbook.
This document discusses the key topics for Lab 4 of the CSE-307 Internetworking Essentials course, including network hardware, IP addressing concepts, and configuration of routers using Cisco Packet Tracer. It provides definitions and explanations of communication modes, carrier waves, IP addressing formats, and the functions of switches, routers, and hubs. The lab objectives are to understand these networking components and configure routers with IP addresses using simulation software. Evaluation will include two practical exams before the midterm covering the first four labs.
A routing algorithm determines the best path for data packets to travel between a source and destination on the Internet. This document discusses and compares different routing algorithms used within autonomous systems (ASes) and between ASes. It covers link-state algorithms like OSPF that use flooding to share full topology information, distance-vector algorithms like RIP that share routing tables with neighbors, and BGP which connects different ASes and allows policies to influence path selection.
The document discusses various topics related to the Tungsten Connector including:
- The role of the Connector in routing connections to the appropriate database nodes.
- Best practices for deploying Connectors in different topologies including on application servers, dedicated nodes, or database nodes with load balancing.
- How to perform zero-downtime maintenance on a Tungsten cluster by manually switching the master role between nodes using the cctrl utility.
- How Connectors route connections in a composite cluster with multiple local clusters and how affinity can be set to prefer local reads from a particular cluster.
- That a Connector can provide access to multiple clusters or composite clusters by configuring the dat
MPLS (Multi-Protocol Label Switching) is introduced as a "Layer 2.5" protocol that sits between traditional Layer 2 and Layer 3 networking. It works by assigning labels to packets at ingress routers and using those labels for fast forwarding decisions without additional routing lookups at subsequent routers. This improves performance over traditional IP routing. MPLS also enables traffic engineering through protocols like RSVP-TE that allow reserving bandwidth on specific paths. Other key MPLS concepts covered are label switching, MPLS signaling protocols, label stacking, pseudowires, VPN services, and fast reroute for improved convergence during failures.
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODELijaia
As digital technology becomes more deeply embedded in power systems, protecting the communication
networks of Smart Grids (SG) has emerged as a critical concern. Distributed Network Protocol 3 (DNP3)
represents a multi-tiered application layer protocol extensively utilized in Supervisory Control and Data
Acquisition (SCADA)-based smart grids to facilitate real-time data gathering and control functionalities.
Robust Intrusion Detection Systems (IDS) are necessary for early threat detection and mitigation because
of the interconnection of these networks, which makes them vulnerable to a variety of cyberattacks. To
solve this issue, this paper develops a hybrid Deep Learning (DL) model specifically designed for intrusion
detection in smart grids. The proposed approach is a combination of the Convolutional Neural Network
(CNN) and the Long-Short-Term Memory algorithms (LSTM). We employed a recent intrusion detection
dataset (DNP3), which focuses on unauthorized commands and Denial of Service (DoS) cyberattacks, to
train and test our model. The results of our experiments show that our CNN-LSTM method is much better
at finding smart grid intrusions than other deep learning algorithms used for classification. In addition,
our proposed approach improves accuracy, precision, recall, and F1 score, achieving a high detection
accuracy rate of 99.50%.
Software Engineering and Project Management - Introduction, Modeling Concepts...Prakhyath Rai
Introduction, Modeling Concepts and Class Modeling: What is Object orientation? What is OO development? OO Themes; Evidence for usefulness of OO development; OO modeling history. Modeling
as Design technique: Modeling, abstraction, The Three models. Class Modeling: Object and Class Concept, Link and associations concepts, Generalization and Inheritance, A sample class model, Navigation of class models, and UML diagrams
Building the Analysis Models: Requirement Analysis, Analysis Model Approaches, Data modeling Concepts, Object Oriented Analysis, Scenario-Based Modeling, Flow-Oriented Modeling, class Based Modeling, Creating a Behavioral Model.
Software Engineering and Project Management - Software Testing + Agile Method...Prakhyath Rai
Software Testing: A Strategic Approach to Software Testing, Strategic Issues, Test Strategies for Conventional Software, Test Strategies for Object -Oriented Software, Validation Testing, System Testing, The Art of Debugging.
Agile Methodology: Before Agile – Waterfall, Agile Development.
Optimizing Gradle Builds - Gradle DPE Tour Berlin 2024Sinan KOZAK
Sinan from the Delivery Hero mobile infrastructure engineering team shares a deep dive into performance acceleration with Gradle build cache optimizations. Sinan shares their journey into solving complex build-cache problems that affect Gradle builds. By understanding the challenges and solutions found in our journey, we aim to demonstrate the possibilities for faster builds. The case study reveals how overlapping outputs and cache misconfigurations led to significant increases in build times, especially as the project scaled up with numerous modules using Paparazzi tests. The journey from diagnosing to defeating cache issues offers invaluable lessons on maintaining cache integrity without sacrificing functionality.
VARIABLE FREQUENCY DRIVE. VFDs are widely used in industrial applications for...PIMR BHOPAL
Variable frequency drive .A Variable Frequency Drive (VFD) is an electronic device used to control the speed and torque of an electric motor by varying the frequency and voltage of its power supply. VFDs are widely used in industrial applications for motor control, providing significant energy savings and precise motor operation.
AI for Legal Research with applications, toolsmahaffeycheryld
AI applications in legal research include rapid document analysis, case law review, and statute interpretation. AI-powered tools can sift through vast legal databases to find relevant precedents and citations, enhancing research accuracy and speed. They assist in legal writing by drafting and proofreading documents. Predictive analytics help foresee case outcomes based on historical data, aiding in strategic decision-making. AI also automates routine tasks like contract review and due diligence, freeing up lawyers to focus on complex legal issues. These applications make legal research more efficient, cost-effective, and accessible.
Build the Next Generation of Apps with the Einstein 1 Platform.
Rejoignez Philippe Ozil pour une session de workshops qui vous guidera à travers les détails de la plateforme Einstein 1, l'importance des données pour la création d'applications d'intelligence artificielle et les différents outils et technologies que Salesforce propose pour vous apporter tous les bénéfices de l'IA.
Advanced control scheme of doubly fed induction generator for wind turbine us...IJECEIAES
This paper describes a speed control device for generating electrical energy on an electricity network based on the doubly fed induction generator (DFIG) used for wind power conversion systems. At first, a double-fed induction generator model was constructed. A control law is formulated to govern the flow of energy between the stator of a DFIG and the energy network using three types of controllers: proportional integral (PI), sliding mode controller (SMC) and second order sliding mode controller (SOSMC). Their different results in terms of power reference tracking, reaction to unexpected speed fluctuations, sensitivity to perturbations, and resilience against machine parameter alterations are compared. MATLAB/Simulink was used to conduct the simulations for the preceding study. Multiple simulations have shown very satisfying results, and the investigations demonstrate the efficacy and power-enhancing capabilities of the suggested control system.
Introduction- e - waste – definition - sources of e-waste– hazardous substances in e-waste - effects of e-waste on environment and human health- need for e-waste management– e-waste handling rules - waste minimization techniques for managing e-waste – recycling of e-waste - disposal treatment methods of e- waste – mechanism of extraction of precious metal from leaching solution-global Scenario of E-waste – E-waste in India- case studies.
Use PyCharm for remote debugging of WSL on a Windo cf5c162d672e4e58b4dde5d797...shadow0702a
This document serves as a comprehensive step-by-step guide on how to effectively use PyCharm for remote debugging of the Windows Subsystem for Linux (WSL) on a local Windows machine. It meticulously outlines several critical steps in the process, starting with the crucial task of enabling permissions, followed by the installation and configuration of WSL.
The guide then proceeds to explain how to set up the SSH service within the WSL environment, an integral part of the process. Alongside this, it also provides detailed instructions on how to modify the inbound rules of the Windows firewall to facilitate the process, ensuring that there are no connectivity issues that could potentially hinder the debugging process.
The document further emphasizes on the importance of checking the connection between the Windows and WSL environments, providing instructions on how to ensure that the connection is optimal and ready for remote debugging.
It also offers an in-depth guide on how to configure the WSL interpreter and files within the PyCharm environment. This is essential for ensuring that the debugging process is set up correctly and that the program can be run effectively within the WSL terminal.
Additionally, the document provides guidance on how to set up breakpoints for debugging, a fundamental aspect of the debugging process which allows the developer to stop the execution of their code at certain points and inspect their program at those stages.
Finally, the document concludes by providing a link to a reference blog. This blog offers additional information and guidance on configuring the remote Python interpreter in PyCharm, providing the reader with a well-rounded understanding of the process.
Gas agency management system project report.pdfKamal Acharya
The project entitled "Gas Agency" is done to make the manual process easier by making it a computerized system for billing and maintaining stock. The Gas Agencies get the order request through phone calls or by personal from their customers and deliver the gas cylinders to their address based on their demand and previous delivery date. This process is made computerized and the customer's name, address and stock details are stored in a database. Based on this the billing for a customer is made simple and easier, since a customer order for gas can be accepted only after completing a certain period from the previous delivery. This can be calculated and billed easily through this. There are two types of delivery like domestic purpose use delivery and commercial purpose use delivery. The bill rate and capacity differs for both. This can be easily maintained and charged accordingly.
2. About Me
• Steve Discher, from College Station,Texas, USA
• Class of ’87 Texas A&M University
• Using MikroTik since early 2004 when I started my first WISP
•Author of the book “RouterOS by Example”
• MikroTik Certified Trainer and teach RouterOS classes,
MyWISPTraining.com
• Operate a wireless distribution company, ISPSupplies.com
3. 1. What is load balancing
and
why would I want it?
6. Typical Scenario Requiring Load Balancing
Problem: No high capacity circuits available, DSL only
Distribution: Fiber, Copper,Wireless, etc.
Hotel, Apartments, etc.
8. 1. What is load balancing and why would I
want it?
9. 1. What is load balancing and why would I
want it?
• Process to utilize multiple internet connections in such a
manner as to proportionately distribute internet traffic across
all the connections.
10. 1. What is load balancing and why would I
want it?
• Process to utilize multiple internet connections in such a
manner as to proportionately distribute internet traffic across
all the connections.
• Distribution may be symmetrical or asymmetrical depending
on circuit availability.
11. 1. What is load balancing and why would I
want it?
• Process to utilize multiple internet connections in such a
manner as to proportionately distribute internet traffic across
all the connections.
• Distribution may be symmetrical or asymmetrical depending
on circuit availability.
• Useful when the downstream bandwidth requirement to a
single routing device exceeds the capabilities of a single
internet circuit.
13. Load Balancing in General
• First, the type of load balancing we are discussing today should
not be confused with any type of bonding protocol or sub-packet
based load balancing.
Options Available
14. Load Balancing in General
• First, the type of load balancing we are discussing today should
not be confused with any type of bonding protocol or sub-packet
based load balancing.
• Bonding, MLPP, etc. require that the protocol be recognized on
both the subscriber and provider ends. Not available with
commodity internet connections.
Options Available
15. Load Balancing in General
• First, the type of load balancing we are discussing today should
not be confused with any type of bonding protocol or sub-packet
based load balancing.
• Bonding, MLPP, etc. require that the protocol be recognized on
both the subscriber and provider ends. Not available with
commodity internet connections.
• Can’t simply bridge two DSL or Cable modem connections,
doesn’t work.
Options Available
16. Load Balancing in General
• First, the type of load balancing we are discussing today should
not be confused with any type of bonding protocol or sub-packet
based load balancing.
• Bonding, MLPP, etc. require that the protocol be recognized on
both the subscriber and provider ends. Not available with
commodity internet connections.
• Can’t simply bridge two DSL or Cable modem connections,
doesn’t work.
•There are several methods to provide load balancing in
RouterOS.
Options Available
19. • ECMP - Equal Cost Multi-Path Routing
Options Available
Load Balancing Options With RouterOS:
20. • ECMP - Equal Cost Multi-Path Routing
• Per-address pair load balancing
Options Available
Load Balancing Options With RouterOS:
21. • ECMP - Equal Cost Multi-Path Routing
• Per-address pair load balancing
• Doesn’t work well for certain protocols, connections break when routing
table flushes every ten minutes to prevent DOS attacks
Options Available
Load Balancing Options With RouterOS:
22. • ECMP - Equal Cost Multi-Path Routing
• Per-address pair load balancing
• Doesn’t work well for certain protocols, connections break when routing
table flushes every ten minutes to prevent DOS attacks
• Nth Load Balancing - Per connection load balancing, with the addition
of persistent connections
Options Available
Load Balancing Options With RouterOS:
23. • ECMP - Equal Cost Multi-Path Routing
• Per-address pair load balancing
• Doesn’t work well for certain protocols, connections break when routing
table flushes every ten minutes to prevent DOS attacks
• Nth Load Balancing - Per connection load balancing, with the addition
of persistent connections
• Hybrid / Custom Setups - Solutions based on one or more methods
above with the addition of scripts or policy routing to make the solution
more intelligent.
Options Available
Load Balancing Options With RouterOS:
24. • ECMP - Equal Cost Multi-Path Routing
• Per-address pair load balancing
• Doesn’t work well for certain protocols, connections break when routing
table flushes every ten minutes to prevent DOS attacks
• Nth Load Balancing - Per connection load balancing, with the addition
of persistent connections
• Hybrid / Custom Setups - Solutions based on one or more methods
above with the addition of scripts or policy routing to make the solution
more intelligent.
• Bandwidth based load balancing - MPLS,Traffic Engineering, etc.
Options Available
Load Balancing Options With RouterOS:
25. • ECMP - Equal Cost Multi-Path Routing
• Per-address pair load balancing
• Doesn’t work well for certain protocols, connections break when routing
table flushes every ten minutes to prevent DOS attacks
• Nth Load Balancing - Per connection load balancing, with the addition
of persistent connections
• Hybrid / Custom Setups - Solutions based on one or more methods
above with the addition of scripts or policy routing to make the solution
more intelligent.
• Bandwidth based load balancing - MPLS,Traffic Engineering, etc.
• PCC - Per Connection Classifier
Options Available
Load Balancing Options With RouterOS:
26. • ECMP - Equal Cost Multi-Path Routing
• Per-address pair load balancing
• Doesn’t work well for certain protocols, connections break when routing
table flushes every ten minutes to prevent DOS attacks
• Nth Load Balancing - Per connection load balancing, with the addition
of persistent connections
• Hybrid / Custom Setups - Solutions based on one or more methods
above with the addition of scripts or policy routing to make the solution
more intelligent.
• Bandwidth based load balancing - MPLS,Traffic Engineering, etc.
• PCC - Per Connection Classifier
• Simple, effective, scalable, no nasty side effects
Options Available
Load Balancing Options With RouterOS:
27. • ECMP - Equal Cost Multi-Path Routing
• Per-address pair load balancing
• Doesn’t work well for certain protocols, connections break when routing
table flushes every ten minutes to prevent DOS attacks
• Nth Load Balancing - Per connection load balancing, with the addition
of persistent connections
• Hybrid / Custom Setups - Solutions based on one or more methods
above with the addition of scripts or policy routing to make the solution
more intelligent.
• Bandwidth based load balancing - MPLS,Traffic Engineering, etc.
• PCC - Per Connection Classifier
• Simple, effective, scalable, no nasty side effects
• Per-address pair load balancing method
Options Available
Load Balancing Options With RouterOS:
29. 2. How does it work?
• PCC divides the incoming data into streams and then uses
routing rules to sort the traffic evenly (or not) across multiple
WAN connections.
30. 2. How does it work?
• PCC divides the incoming data into streams and then uses
routing rules to sort the traffic evenly (or not) across multiple
WAN connections.
•This is done by:
31. 2. How does it work?
• PCC divides the incoming data into streams and then uses
routing rules to sort the traffic evenly (or not) across multiple
WAN connections.
•This is done by:
1. Using a hashing algorithm to first sort the traffic based on
source address, source port, destination address, destination
port or various combinations thereof.
32. 2. How does it work?
• PCC divides the incoming data into streams and then uses
routing rules to sort the traffic evenly (or not) across multiple
WAN connections.
•This is done by:
1. Using a hashing algorithm to first sort the traffic based on
source address, source port, destination address, destination
port or various combinations thereof.
2. Using packet marking and routing marks and several
routing tables to ensure traffic follows a specified route out
the specified WAN interface.
33. 2. How does it work?
• PCC divides the incoming data into streams and then uses
routing rules to sort the traffic evenly (or not) across multiple
WAN connections.
•This is done by:
1. Using a hashing algorithm to first sort the traffic based on
source address, source port, destination address, destination
port or various combinations thereof.
2. Using packet marking and routing marks and several
routing tables to ensure traffic follows a specified route out
the specified WAN interface.
35. Understand the Solution
• MikroTik RouterOS is extremely powerful and configurable,
so this can be a double edged sword, several possible
solutions to the same problem
36. Understand the Solution
• MikroTik RouterOS is extremely powerful and configurable,
so this can be a double edged sword, several possible
solutions to the same problem
• Each has multiple moving pieces
37. Understand the Solution
• MikroTik RouterOS is extremely powerful and configurable,
so this can be a double edged sword, several possible
solutions to the same problem
• Each has multiple moving pieces
• Greatest success with any solution by understanding the
pieces and what they do.
39. Understanding the PCC Load Balancing Solution
1. Packet - The container for our data, header and payload.
Terms...
40. Understanding the PCC Load Balancing Solution
1. Packet - The container for our data, header and payload.
2. Connections - “Conduit” through which host to host
communication occurs, based on Src/Dst addresses and ports
Terms...
41. Understanding the PCC Load Balancing Solution
1. Packet - The container for our data, header and payload.
2. Connections - “Conduit” through which host to host
communication occurs, based on Src/Dst addresses and ports
3.Mangle Facility - Firewall function within RouterOS that
allows you to create a mark which is then associated with packets
that can be identified later by other functions like firewall rules or
routing tables.
Terms...
43. Understanding the PCC Load Balancing Solution
4. PCC - Per Connection Classifier, function contained with the
“Mangle Facility” to sort traffic into streams
44. Understanding the PCC Load Balancing Solution
4. PCC - Per Connection Classifier, function contained with the
“Mangle Facility” to sort traffic into streams
5. Routing Table - Route rules, the rules the router uses to
determine what to do with a packet. By comparing the destination
address in the packet to the list of routes, the router decides
which interface to send the packet out. By adding a routing mark
with mangle, we can have multiple routing tables!
45. Understanding the PCC Load Balancing Solution
A packet is like a letter & envelope.
The front is the header and the letter inside the envelope is the
payload.
Source Address
& Port
Destination Address
& Port
1.What is a packet?
46. Understanding the PCC Load Balancing Solution
IPv4 Header
Source Address
(sender)
Destination Address
(receiver)
Port Port
Protocol
48. 3.What is the mangle facility?
Understanding the PCC Load Balancing Solution
If - Then: Identify and then
perform some action.
49. 4.What is PCC?
Per Connection Classifier is a mangle option that sorts
data into streams that can be marked for identification later.
Understanding the PCC Load Balancing Solution
(s)
Unsorted In Sorting Sorted Streams
50. Where is it found?
Understanding the PCC Load Balancing Solution
1
2
3
51. How does PCC work?
Understanding the PCC Load Balancing Solution
•"PCC takes selected fields from IP header, and with the help of a hashing
algorithm converts selected fields into 32-bit value.
•This value then is divided by a Denominator and the Remainder then is
compared to a specified Remainder, if equal then packet will be captured.
•You can choose from src-address, dst-address, src-port, dst-port (or various
combinations) from the header to use in this operation."
52. PCC uses a hashing algorithm.
Understanding the PCC Load Balancing Solution
•A hashing algorithm is a mathematical function that takes
an input and returns an output.
•The output will always be the same for a specified input.
• Example of a simple hash:
Input x 100 = hash value
53. PCC uses modular arithmetic (clock arithmetic).
Understanding the PCC Load Balancing Solution
• Numerators, Denominators and Remainders are parts of modular arithmetic.
• It is represented by a % sign and it is spoken as “mod”.
•To work modular math, think of it as "how many are left over (Remainder) after
you've subtracted the second value (Denominator) from the first (Numerator) as
many times as possible without going negative?"
• Here are some examples of modular math:
Numerator =3 Denominator = 3
3 % 3 = 0 because 3 - 3 = 0 left over
or
4 % 3 = 1 because 4 - 3 = 1 left over
5 % 3 = 2 because 5 - 3 = 2 left over
6 % 3 = 0, because 6 - 3 = 3, subtract 3 again = 0 left over
54. Example: 2 WAN Connections
Understanding the PCC Load Balancing Solution
•The first line means "produce the output of the hash function
given the packet's source IP address, divide it by 2 and if the
remainder is 0, perform the action of marking the connection as
WAN1".
•The second line means "produce the output of the hash function
given the packet's source IP address, divide it by 2 and if the
remainder is 1, perform the action of marking the connection as
WAN2".
Denominator Remainder
Modular math helps us understand how to create the PCC rules!
2 PCC Rules Required
55. How to set PCC, Remember:
Understanding the PCC Load Balancing Solution
2 WAN connections:
2 / 0 First WAN
2 / 1 Second WAN
3 WAN connections:
3 / 0 First WAN
3 / 1 Second WAN
3 / 2 Third WAN and so on...
56. 5.What is a routing table?
Understanding the PCC Load Balancing Solution
Routes determine which
interface a packet is sent
out.
They also tell the router
which upstream or
downstream router will take
the packet to it’s next hop
until it reaches its final
destination.
57. Details of a route, key pieces are destination and gateway.
Understanding the PCC Load Balancing Solution
58. Multiple routing tables with route marks
Understanding the PCC Load Balancing Solution
May have multiple
routes to same
destination network,
different gateways in
different routing tables!
59. Multiple routing tables with route marks
Understanding the PCC Load Balancing Solution
May have multiple
routes to same
destination network,
different gateways in
different routing tables!
60. Multiple routing tables with route marks
Understanding the PCC Load Balancing Solution
May have multiple
routes to same
destination network,
different gateways in
different routing tables!
61. Multiple routing tables with route marks
Understanding the PCC Load Balancing Solution
May have multiple
routes to same
destination network,
different gateways in
different routing tables!
63. Understanding the PCC Load Balancing Solution
1. Packet - Container for IP data
Review:
64. Understanding the PCC Load Balancing Solution
1. Packet - Container for IP data
2. Connections - Bi-directional conduit for communication
between two hosts
Review:
65. Understanding the PCC Load Balancing Solution
1. Packet - Container for IP data
2. Connections - Bi-directional conduit for communication
between two hosts
3. Mangle Facility - Manipulates packets by adding marks
Review:
66. Understanding the PCC Load Balancing Solution
1. Packet - Container for IP data
2. Connections - Bi-directional conduit for communication
between two hosts
3. Mangle Facility - Manipulates packets by adding marks
4. PCC - Divides data into streams (based on marks)
Review:
67. Understanding the PCC Load Balancing Solution
1. Packet - Container for IP data
2. Connections - Bi-directional conduit for communication
between two hosts
3. Mangle Facility - Manipulates packets by adding marks
4. PCC - Divides data into streams (based on marks)
5. Routing Table - List of route rules to direct packets and we
can have multiple tables based on routing marks
Review:
68. 3. Ok, I want it but how do I set it up?
Hotel, Apartments, etc.
69. 3. Ok, I want it but how do I set it up?
Scenario: One router, many clients, three DSL connections
Hotel, Apartments, etc.
71. Step by Step Configuration
1. Set up the basic portion of the network (MTCNA,Wiki, etc):
• Private IP address on LAN interface
• DHCP Server on LAN interface
• DNS server
• Static IP for WAN or DHCP client on WAN
• Firewall if required
72. Step by Step Configuration
1. Set up the basic portion of the network (MTCNA,Wiki, etc):
• Private IP address on LAN interface
• DHCP Server on LAN interface
• DNS server
• Static IP for WAN or DHCP client on WAN
• Firewall if required
2.Create load balancing part of the configuration:
• Mangle rules
• Routing tables
73. Step by Step Configuration
1. Set up the basic portion of the network (MTCNA,Wiki, etc):
• Private IP address on LAN interface
• DHCP Server on LAN interface
• DNS server
• Static IP for WAN or DHCP client on WAN
• Firewall if required
2.Create load balancing part of the configuration:
• Mangle rules
• Routing tables
75. Step by Step Configuration
IP Addresses
DHCP Client - WAN
Masquerade Rules
DNS Client & Caching
1.Set up the basic portion of the network (MTCNA,Wiki, etc):
76. Step by Step Configuration
2.Create load balancing part of the configuration:
• Create various mangle rules to mark connections
• Create mangle rules to associate routing marks with packets
based on their connection mark.
• Create routes to send traffic out the WAN connections in a
predetermined manner.
77. Step by Step Configuration
Step 1: Create some accept rules.
We have to manually force local traffic to connected
networks to stay in the main routing table.
• Background - Any subnet for which the router has an IP
address configured is called a connected network, meaning
packets to that network are sent out an interface and can reach
their destination without using another router to get there.
78. Step by Step Configuration
Connected network example
The problem using mangles here is it will
force traffic to follow alternate routing tables
(not main)
Traffic to these connected networks would
go out the WAN interfaces and not reach
their intended destinations.
Step 1 continued...
79. Step by Step Configuration
Step 1 continued...
Solution:
•The “accept” action causes the packet to leave the mangle chain, thereby
not marking it and allowing that traffic to use the main routing table.
80. Step by Step Configuration
• One rule for each connected network, in this example these are
our WAN networks
Step 1 continued...
81. Step by Step Configuration
/ip firewall mangle
add action=accept chain=prerouting disabled=no dst-address=172.17.0.0/24
add action=accept chain=prerouting disabled=no dst-address=172.18.0.0/24
add action=accept chain=prerouting disabled=no dst-address=172.19.0.0/24
Step 1 Completed
Completed accept
mangle rules
Create one rule for
each connected
network (WAN’s)
82. Step by Step Configuration
Create the PCC mangles:
•We will use optimal mangle method of marking connections first
and then packets because it is the most efficient way to mark
traffic, uses least resources.
•First identify traffic and mark the connection.
•Second, look for that connection mark and mark the routes.
Step 2: Create Mangle rules that will sort the traffic into
streams.
86. Step by Step Configuration
Step 2 Continued...
Several choices here, both
addresses is the safest option,
best balance of performance
and reliability.
87. Step by Step Configuration
Step 2 Continued...
Several choices here, both
addresses is the safest option,
best balance of performance
and reliability.
88. Step by Step Configuration
Step 2 Continued...
Several choices here, both
addresses is the safest option,
best balance of performance
and reliability.
The mangle chain prerouting will be
capturing all traffic, even traffic that is
going to the router itself. To avoid this
we will use dst-address-type=!local.
89. Step by Step Configuration
Step 2 Continued...
Several choices here, both
addresses is the safest option,
best balance of performance
and reliability.
The mangle chain prerouting will be
capturing all traffic, even traffic that is
going to the router itself. To avoid this
we will use dst-address-type=!local.
90. Step by Step Configuration
Step 2 Continued...
“In Interface” is where
the clients are, the LAN
interface.
Several choices here, both
addresses is the safest option,
best balance of performance
and reliability.
The mangle chain prerouting will be
capturing all traffic, even traffic that is
going to the router itself. To avoid this
we will use dst-address-type=!local.
91. Step by Step Configuration
Create one PCC mangle
rule for each WAN
connection
ip firewall mangle
add action=mark-connection chain=prerouting connection-mark=no-mark disabled=no dst-address-type=!local
in-interface=ether5 new-connection-mark=WAN1 passthrough=yes per-connection-classifier=both-addresses:3/0
add action=mark-connection chain=prerouting connection-mark=no-mark disabled=no dst-address-type=!local
in-interface=ether5 new-connection-mark=WAN2 passthrough=yes per-connection-classifier=both-addresses:3/1
add action=mark-connection chain=prerouting connection-mark=no-mark disabled=no dst-address-type=!local
in-interface=ether5 new-connection-mark=WAN3 passthrough=yes per-connection-classifier=both-addresses:3/2
Step 2 Completed
Completed PCC Mangle
Rules
92. Step by Step Configuration
Step 3: Create the mangles to add the routing marks to the packets based on
the connection mark in the PREROUTING CHAIN:
93. Step by Step Configuration
Step 3: Create the mangles to add the routing marks to the packets based on
the connection mark in the PREROUTING CHAIN:
94. Step by Step Configuration
Step 3: Create the mangles to add the routing marks to the packets based on
the connection mark in the PREROUTING CHAIN:
95. Step by Step Configuration
Step 3: Create the mangles to add the routing marks to the packets based on
the connection mark in the PREROUTING CHAIN:
This is where we mark
routing for the bulk of
our traffic
96. Step by Step Configuration
Step 3 Continued for OUTPUT CHAIN...
97. Step by Step Configuration
Step 3 Continued for OUTPUT CHAIN...
98. Step by Step Configuration
Step 3 Continued for OUTPUT CHAIN...
99. Step by Step Configuration
Step 3 Continued for OUTPUT CHAIN...
This rule ensures traffic
from the router itself
returns through the
proper interface
100. Step by Step Configuration
Step 3 Completed
Completed route
marking rules
/ip firewall mangle
add action=mark-routing chain=prerouting connection-mark=WAN1 disabled=no in-interface=ether5
new-routing-mark=ether1-mark passthrough=yes
add action=mark-routing chain=prerouting connection-mark=WAN2 disabled=no in-interface=ether5
new-routing-mark=ether2-mark passthrough=yes
add action=mark-routing chain=prerouting connection-mark=WAN3 disabled=no in-interface=ether5
new-routing-mark=ether3-mark passthrough=yes
add action=mark-routing chain=output connection-mark=WAN1 disabled=no new-routing-mark=ether1-mark passthrough=yes
add action=mark-routing chain=output connection-mark=WAN3 disabled=no new-routing-mark=ether3-mark passthrough=yes
add action=mark-routing chain=output connection-mark=WAN2 disabled=no new-routing-mark=ether2-mark passthrough=yes
Create one rule for for
each WAN connection,
in prerouting chain and
same in output chain
101. Step by Step Configuration
Step 4: Identify which WAN interface the traffic came in and
mark the connections appropriately.
102. Step by Step Configuration
Step 4: Identify which WAN interface the traffic came in and
mark the connections appropriately.
103. Step by Step Configuration
Step 4: Identify which WAN interface the traffic came in and
mark the connections appropriately.
104. Step by Step Configuration
Step 4 Completed
Completed WAN
connection marking
rules
/ip firewall mangle
add action=mark-connection chain=prerouting connection-mark=no-mark disabled=no
in-interface=ether1 new-connection-mark=WAN1 passthrough=yes
add action=mark-connection chain=prerouting connection-mark=no-mark disabled=no
in-interface=ether3 new-connection-mark=WAN3 passthrough=yes
add action=mark-connection chain=prerouting connection-mark=no-mark disabled=no
in-interface=ether2 new-connection-mark=WAN2 passthrough=yes
Create one rule for
each WAN connection
105. Step by Step Configuration
Final result: Connections should be marked, route marks added to
packets based on connection mark.
Always check the
connection table to
ensure mangles are
working for connections
106. Step by Step Configuration
Mangles are done, we now create the routes:
107. Step by Step Configuration
•We will need one default route for each routing mark,
corresponding to each of the WAN connections.
Mangles are done, we now create the routes:
108. Step by Step Configuration
•We will need one default route for each routing mark,
corresponding to each of the WAN connections.
•We will also need one unmarked default route corresponding to
each of the WAN connections.
Mangles are done, we now create the routes:
109. Step by Step Configuration
Step 5: Create the unmarked default routes.
110. Step by Step Configuration
Step 5: Create the unmarked default routes.
111. Step by Step Configuration
Step 5: Create the unmarked default routes.
112. Step by Step Configuration
Step 5: Create the unmarked default routes.
113. Step by Step Configuration
Step 5: Create the unmarked default routes.
Provides failover -
ensures traffic always
has a default route
because if there is no
active marked route to
match a packet, it
follows the main routing
table!
114. Step by Step Configuration
Step 5: Create the unmarked default routes.
Provides failover -
ensures traffic always
has a default route
because if there is no
active marked route to
match a packet, it
follows the main routing
table!
Considering using
distance to prefer one
default over another.
115. Step by Step Configuration
Step 6: Create the marked default routes.
116. Step by Step Configuration
Step 6: Create the marked default routes.
117. Step by Step Configuration
Step 6: Create the marked default routes.
118. Step by Step Configuration
Step 6: Create the marked default routes.
119. Step by Step Configuration
Step 6: Create the marked default routes.
Use “check-gateway” to
ensure gateway is alive.
Only need to use
“check-gateway” on
marked routes because
any routes with that
gateway become
inactive if it fails thereby
affecting marked routes
too.
120. Step by Step Configuration
Final result - Routing table
One marked default for
each WAN connection,
and one unmarked
default route for each
WAN connection
Completed routing
table
121. Step by Step Configuration
Final result!
Actual screen shots from a load balance configuration in
production with 2 WAN connections.
122. Common Problems
I use DHCP for my WAN addressing, how can I get the marked
routes created properly?
/system script
add name=ConfigureDHCPRoutes policy=
ftp,reboot,read,write,policy,test,winbox,password,sniff,sensitive,api source=":local cli
entcounterr
n:local routecounterr
n:local duplicatecounterr
n:local routeupdated "no"r
n:foreach clientcounter in=[/ip dhcp-client find] do={r
n:local routingmarkname ([/ip dhcp-client get $clientcounter interface] . "-mark")r
n:local newroutinggateway [ip dhcp-client get $clientcounter gateway]r
n:foreach routecounter in=[/ip route find where routing-mark=$routingmarkname] do={r
n :local routinggateway [/ip route get [find routing-mark=$routingmarkname] gateway]
r
nt:if ([:len $newroutinggateway] > 0) do={r
nt :if ($"routinggateway" != $"newroutinggateway") do={ r
nt /ip route set $routecounter gateway=$newroutinggateway r
ntt:set routeupdated "yes"r
nt }r
nt}r
n } r
n :if ([:len $newroutinggateway] > 0) do={r
n :if ($routeupdated = "no") do={r
n /ip route add routing-mark=$routingmarkname gateway=$newroutinggateway dst-add
ress=0.0.0.0/0r
n }r
n }r
n}r
n"
Script by Andrew Cox
124. Common Problems
PCC doesn’t seem to work properly with HotSpot or IP
Webproxy
• It is possible to make it work but the rules get very detailed and
complicated.
Solution: Use two routers, one for load balancing, one for HotSpot
or IP Webproxy.
Solution: Use metarouter with host router doing main routing
functions, virtual router doing the load balancing.
125. Common Problems
DNS resolves from some clients, not others
• If you are using two different ISP’s and their respective name
servers, possibly some clients are accessing ISP1’s DNS server
through ISP2’s connection and ISP1 is blocking DNS requests from
outside their IP space.
Solution: Consider OpenDNS, destination NAT with redirect to
DNS cache, etc.
126. Common Problems
Strange http issues, some images load, other don’t, problems with
some secure sites
Solution:Try using “both addresses” or “source address “ for PCC
classifier. While “both addresses and ports” gives the greatest
chance for randomization and better possibility for even
distribution, it can create these types of issues.
127. Common Problems
I can only get asymmetrical connections, one DSL and one cable
modem.
Solution:You can “weight” one interface higher and force more traffic
through it by repeating the connection marking PCC rule more than once
for that connection.
Example for added weight to WAN3.
/ip firewall mangle
add action=mark-connection chain=prerouting connection-mark=no-mark disabled=
no dst-address-type=!local in-interface=ether5 new-connection-mark=WAN1
passthrough=yes per-connection-classifier=both-addresses:3/0
add action=mark-connection chain=prerouting connection-mark=no-mark disabled=
no dst-address-type=!local in-interface=ether5 new-connection-mark=WAN2
passthrough=yes per-connection-classifier=both-addresses:3/1
add action=mark-connection chain=prerouting connection-mark=no-mark disabled=
no dst-address-type=!local in-interface=ether5 new-connection-mark=WAN3
passthrough=yes per-connection-classifier=both-addresses:3/2
add action=mark-connection chain=prerouting connection-mark=no-mark disabled=
no dst-address-type=!local in-interface=ether5 new-connection-mark=WAN3
passthrough=yes per-connection-classifier=both-addresses:3/3
128. Thank You!
• MyWISPTraining.com
• LearnMikroTik.com
• ISPSupplies.com
•“RouterOS by Example” available for
many distributors or Amazon.com, iTunes