Skip to main content

EIGRP Adjacency


When your neighbor's router is on fire, your internet is not at stake! Wish the same were true in the EIGRP universe as well (unless you have a well designed redundant network, which unfortunately is not very often the case!)





EIGRP works if and only if your router establishes an 'amicable' EIGRP neighborship with the adjacent EIGRP router. Well, this is not an issue in most cases. Of importance, here, is how do you quantify the 'amicability' of the EIGRP adjacency.





Let's inspect various fields in the "show ip eigrp neighbor" output





show ip eigrp neighbor




Autonomous System (AS) number - Here, visible as "Process 100" - EIGRP uses the concept of autonomous systems. An autonomous system is simply a group of EIGRP-enabled routers that should become EIGRP neighbors and exchange routes.





Address: IP address of the EIGRP neighbor





Interface: Which interface is this EIGRP adjacency is formed upon





Hold timer: Hold down timer is the number of seconds EIGRP router would wait to learn a hello packet from its neighbor till the time it decides that the neighbor is no longer 'alive'





Uptime: The total time this particular neighbor has been UP and stable





SRTT: Smooth Round Trip Time - The time it takes to send an EIGRP packet and receive an acknowledgment from the neighbor





RTO: Retransmission Time Out - This is the time that the router would wait before retransmitting a packet from the retransmission queue to a neighbor





Q Cnt – the number of EIGRP packets (Update, Query or Reply) in the queue that are awaiting transmission. Should be 0





Seq Num – the sequence number of the last EIGRP packet which can be update, query, or reply packet that was received from the EIGRP neighbor





End result: The Uptime, SRTT, RTO, Q Cnt can be used to determine the 'amicability' of two EIGRP routers forming adjacency. High uptime, low SRTT and RTO and zero 'Q cnt' should indicate that the EIGRP adjacency is stable.


Labels:

Comments

Post a Comment

Popular posts from this blog

MITRE ATT&CK - Kerberos Vulnerabilities and Security

From the previous post, the summary of Kerberos authentication process is as below: For the initial authentication, the user’s client machine sends a request to the KDC  Authentication Service (AS) . The request includes details like the user’s username, and the date and time. All information except the username is encrypted using the hash of the user’s password. The KDC AS uses the username to look up its copy of the user’s password hash and uses it to decrypt the rest of the request. If the decryption is successful, that means the client used the correct password hash and the user has successfully authenticated. Once the user is authenticated, the KDC AS sends the user’s client a  ticket granting ticket   (TGT) . The TGT includes a unique session key and a timestamp that specifies how long that session is valid (normally 8 or 10 hours). Importantly, before sending the TGT, the KDC encrypts it using the password hash for a special account, the  KRBTGT account. ...
4 comments
Read more

Checkpoint - Exporting Objects in CSV format

Be it a Network Operations Manager, Security Architect or a Security Auditor, the people up the hierarchy always harangue the Security Engineers to compile the list of firewall objects or rules or policies or the traffic statistics and so on.. This can turn out to be quite hectic especially if there are no built in features to systematically provide the output in a "layman-readable" format. Come, Checkpoint's "Object Explorer..."  which not only provides the output in the "layman-readable" format, but also provides in-built filtering mechanisms, thereby ensuring that the Security Engineer doesn't have to rely on Google for building his scarce Microsoft Excel data filtering skills. The following screenshots will show how easy it is, with Checkpoint R80.10 to generate the firewall configuration inventory. On the SmartConsole Unified Portal, navigate to Menu >> Open Object Explorer... Select the Categories you wish to see in your output: Click o...
Post a Comment
Read more

MITRE ATT&CK - Understanding Kerberos (for Golden Ticket Attack)

Kerberos = Network Authentication Protocol used by AD environments Provides authentication by issuing tickets to authenticate users and allow them access to the services Tickets are distibuted by KDC (Key Distribution Center), which is typically a Domain Controller (DC) During initial authentication, a TGT (Ticket Granting Ticket) is a ticket asigned to a user by KDC. TGT is later used to authenticate the user to the KDC in order to request a service ticket from TGS (Ticket Granting Service). Service tickets are granted for authentication against services. List of steps / negotiations for Kerberos authentication (of the user with the service): The user requests  (AS-REQ)  a TGT from the KDC and the KDC verifies and validates the credentials and user information. This request if often done automatically at login. After authenticating the user, the KDC sends an encrypted TGT back to the requester  (AS-REP) . The user presents the TGT to the DC and requests a TGS  (TGS-...
Post a Comment
Read more