Gre Tunnel

Topology

Objectives

Create Gre tunnel between Router A and Router c. We are creating tunnel to internal communication between two LAN segments without, advertising LAN IP in internet domain.

Steps:

  • Your end to end network should be reachable i.e the interface/node from where you are creating tunnel should reachable to destination interface/node. Here Router A ,B & C is configured and running eigrp under internet domain , we have advertised loopback on Router A &C under eigrp.
  • Ping 2.2.2.2 from Router A and 1.1.1.1 from Router C.

Continue reading

Posted in MPLS | Tagged | Comments Off on Gre Tunnel

MPLS lsp path broken

Topology:

Objective: To test the broken LSP failover using LDP protocol.

All router in the topology are running under OSPF area 0.LDP has been enabled between them. Currently LDP synced and LDP neighbor ship has been established between all routers.

Continue reading

Posted in MPLS | Tagged | Comments Off on MPLS lsp path broken

MPLS Vpn Working Principle

Topology:

Objective:

Configure MPLS L3VPN and understand it’s working. Currently PE1 & PE2 running iBGP under AS 100.PE1, P1, P2 & PE2 running OSPF as IGP. MPLS backbone running LDP for label distribution, LDP neighbor ship has been established among PE1, P1,P2 and PE2.CE1/CE11 using default routing towards PE1/PE2 respectively.

MPLS VPN used two control plane protocols: LDP and MP-BGP to accomplish MPLS VPN communication.

LDP used for signaling and responsible for distributing label among LSR, however LDP rely on IGP for choosing the best path.MPLS unicast ip forwarding is purely based on IGP and LDP.

Continue reading

Posted in MPLS | Tagged | Comments Off on MPLS Vpn Working Principle

Multicast Overview

Posted in Blog | Comments Off on Multicast Overview

BGP Weight Attribute

Topology


Objectives
Use BGP attribute to influence the route selection in BGP. Currently Router R1/R1 running iBGP .Between R1-R3 & R2-R4 ebgp is used. Within ISP we have used Full iBGP mesh ( of course we could have used RR).Connect the network as shown in topology.

Continue reading

Posted in Routing Protocols | Comments Off on BGP Weight Attribute

BGP Initialization

Topology

Objectives

Objective is to understand how bgp initialize when you enable interfaces and bgp parameters. We will check it by sniffing tool Wireshark to know what happening behind the scene.  Wireshark will be enabled on f0/0 on R2.

Continue reading

Posted in Routing Protocols | Tagged | Comments Off on BGP Initialization

BGP Over GRE

Topology

Objective:
To implement BGP over GRE , the topology shown above. In topology R1 & R3 running BGP 100 whereas R2 running only IGP.R1-R4 & R3-R5 running ebgp and advertising prefix 4.4.4.4 and 5.5.5.5 respectively.
R1-R2-R3 running ospf under area 0.
Bgp over GRE can be configured in scenario where end to end BGP is not running or where we want to bypass non bgp peer to peering with BGP peer.

Continue reading

Posted in Routing Protocols | Tagged | Comments Off on BGP Over GRE

Type of ether Frame

Today we will see the different Ethernet frame types and there header size.

1)Ethernet encapsulation 802.3

2)Ethernet encapsulation 802.1q Frame

3)Ethernet encapsulation 802.1ad

4)Ethernet encapsulation 802.1ah

Continue reading

Posted in Packet_Inspection | Comments Off on Type of ether Frame

Types Of VPN in Networking

Types Of VPN in Networking

We are having different techlogy when it comes to secure the private network over internet for securely sharing your data in public domain.The figure above depicts the types of VPN services that we can use as per our requirement.We will see each VPN and their features with configuration ahead.

 

Posted in MPLS | Leave a comment

IPv4 Header Format

IPv4 Packet

The header fields are discussed below:

  • Version (always set to the value 4 in the current version of IP)
  • IP Header Length (number of 32 -bit words forming the header, usually five)
  • Type of Service (ToS), now known as Differentiated Services Code Point (DSCP) (usually set to 0, but may indicate particular Quality of Service needs from the network, the DSCP defines the way routers should queue packets while they are waiting to be forwarded).
  • Total Length: Length of entire IP Packet (including IP header and IP Payload).
  • Identification ( 16-bit number which together with the source address uniquely identifies this packet – used during reassembly of fragmented datagrams)
  • Flags (a sequence of three flags (one of the 4 bits is unused) used to control whether routers are allowed to fragment a packet (i.e. the Don’t Fragment, DF, flag), and to indicate the parts of a packet to the receiver)
  • Fragmentation Offset (a byte count from the start of the original sent packet, set by any router which performs IP router fragmentation)
  • Time To Live (Number of hops /links which the packet may be routed over, decremented by most routers – used to prevent accidental routing loops)
  • Protocol (Service Access Point (SAP) which indicates the type of transport packet being carried (e.g. 1 = ICMP; 2= IGMP; 6 = TCP; 17= UDP).
  • Header Checksum (A 1’s complement checksum inserted by the sender and updated whenever the packet header is modified by a router – Used to detect processing errors introduced into the packet inside a router or bridge where the packet is not protected by a link layer cyclic redundancy check. Packets with an invalid checksum are discarded by all nodes in an IP network)
  • Source Address (the IP address of the original sender of the packet)
  • Destination Address (the IP address of the final destination of the packet)
  • This is optional field, which is used if the value of IHL is greater than 5. These options may contain values for options such as Security, Record Route, Time Stamp, etc.
  • Padding is basically used to make sure that the IP packet header has a length that is a multiple of 32 bits. It is needed because of the varying length of the options field in the IP header

IPV4 header is flexible in size and can vary from 20 bytes to 60 bytes. Usually it is 20 bytes in length.

Te Internet Protocol (IP) is defined in RFC 791. The RFC specifies the format of the IP header. In the header there is the IHL (Internet Header Length) field which is 4 bits long and specifies the header length in 32 bit words. The IHL field can hold values from 0 (Binary 0000) to 15 (Binary 1111).

So the longest Internet Header (IP header) size can be 15*32 Bits = 480 Bits = 60 Bytes. This is why the header has a maximum size of 60 Bytes.

The shortest header size is 20 bytes, where the IHL field has the value 5 (0101). This is because all the required fields in the header need 20 Bytes of space. So while in theory you could set the IHL to a value < 5 this would always be an incorrect value and thus an invalid packet header.

Total field in IPv4 is 13 and you can remember these by using the phrase as below.

VIT TIF FTP HSDO

V I T T I F F T P H S D O
ver IHL TOS TL Indentifier Flag Fragment TTL Protocol Checksum SIP DIP Option
Posted in Packet_Inspection | 2 Comments