Skip to main content

Authentication with different Routing Protocols

 Routing Protocol Authentication

Authentication is crucial in routing protocols to ensure the integrity and authenticity of routing updates. Most protocols support different types of authentication mechanisms like plain text, MD5, and more advanced cryptographic methods such as HMAC-SHA-256.

EIGRP Authentication

  • EIGRP Authentication: EIGRP supports both MD5 (in classic mode) and HMAC-SHA-256 (in named mode). Authentication ensures that packets exchanged between EIGRP neighbors are verified using pre-shared keys.
    • Technical Tip: Use HMAC-SHA-256 in named mode as it is stronger than MD5.

Example configuration for MD5 in classic mode:

key chain EIGRP-R2-R4

 key 1

  key-string CCIE

!

interface eth0/2

 ip authentication mode eigrp 1 md5

 ip authentication key-chain eigrp 1 EIGRP-R2-R4

Example for HMAC-SHA-256 in named mode:

router eigrp ONE

 address-family ipv4 unicast autonomous-system 1

  af-interface Ethernet0/2

   authentication mode hmac-sha-256 CCIE

  • Technical Tip: For passwords containing special characters, escape sequences might be necessary. For example, entering "C?IE" requires pressing Esc and q before entering the ? character.

OSPF Authentication

OSPF supports three types of authentication:

  • Type 0: No authentication.
  • Type 1: Plain text authentication.
  • Type 2: MD5-based authentication.
  • Cryptographic Authentication: Newer OSPF implementations support SHA-based authentication, such as HMAC-SHA-256.

OSPF MD5 authentication example:

interface GigabitEthernet0/1

 ip ospf authentication message-digest

 ip ospf message-digest-key 1 md5 OSPF-KEY

Cryptographic authentication example (SHA-256):

key chain OSPF

 key 1

  key-string CCIE

  cryptographic-algorithm hmac-sha-256

interface GigabitEthernet0/1

 ip ospf authentication key-chain OSPF

  • Key Rollover: In MD5-based OSPF, multiple keys can be configured, and routers go through a key rollover process where the last key added is used to sign packets, while received packets are authenticated with the key ID in the packet.
  • Virtual Links: If OSPF authentication is enabled in Area 0, it must also be enabled on virtual links since they are considered part of Area 0. Virtual links use demand circuits, suppressing hello messages to avoid keeping the link up unless there is a topology change.
  • Technical Tip: Be cautious with key numbering in OSPF. The newest key is not determined by the numeric value but by the order in which it was added.

 

Comments

Popular posts from this blog

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.

AS Path Prepending: Controlling Inbound Traffic in BGP

AS Path Prepending is a BGP feature used to make a specific path appear less preferred by artificially lengthening the AS path. This is done by adding your AS number multiple times to the AS path. It is a common method to influence inbound traffic from external networks. Longer AS Path = Less preferred route . Example Scenario : You have two ISPs: ISP1 (through CE1) and ISP2 (through CE2). You want inbound traffic from the internet to prefer ISP1 over ISP2. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP2): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE2 (AS Path Prepending to Make ISP2 Less Preferred) : Create a route map to prepend your AS path multiple times for CE2: route-map PREPEND_AS permit 10 set as-path prepend 65001 65001 65001 Apply this route map to the neighbor in the BGP configuration for CE2: router bgp 65001 neighbor 10.0.2.1 remote-as 65002 neighbor 10.0.2.1 ro...

Authoritative DNS Servers Delegation and Internal DNS Explained

DNS (Domain Name System) plays a critical role in how users and systems find resources on the internet or within internal networks. Whether it's managing an internal domain in an enterprise or delegating parts of a domain for traffic distribution, DNS setups vary widely depending on needs. In this blog post, we’ll break down the different types of DNS setups, including authoritative DNS servers, DNS delegation, and how internal DNS functions within organizations. 1. Authoritative DNS Server An Authoritative DNS server is the final source of truth for a specific domain. When someone queries a domain (e.g., example.com ), the authoritative DNS server for that domain holds the DNS records (A records, CNAME, MX, etc.) and responds with the corresponding IP address. Key Points: Who can host it? Authoritative DNS servers are often hosted by domain registrars (e.g., GoDaddy, Namecheap) or cloud DNS providers (e.g., AWS Route 53, Cloudflare). However, organizations can also host their ...