Žilinská univerzita > Fakulta riadenia a informatiky > Katedra informačných sietí

Routing, RIP, OSPF

Parsing OSPF packets using tcpdump

Sometimes we need to capture and parse OSPF packets for next analysis and we have a comand line only, in my case on linux server with dynamips. We should use tcpdump tool for this purpose, of course, several ways are available.

Capturing OSPF packets on the fly

tcpdump -i eth0 ip[9] == 89

where OSPF ip protocol number is 89, and the protocol field is the 9th octet on the ip header.

Another way is:

tcpdump -i eth0 proto ospf

Writing captured packets to a file

Configuration of the RIPv2 authentication

In this article I will configure, debug and shows the process of RIPv2 authentication.


Authentication methods

  1. Plain text
  2. MD5


Note 1: When using plain text authentication mode, make sure that the following parameters are matching on neighboring routers for successful authentication.

  • Key-string

  • Authentication mode

Possible bugs/limitations encountered in Cisco's RIP implementation

  1. Default route origination not working reliably.
  2. Automatic summarization turned on causes major networks to be propagated throughout the RIP domain with a metric of 1.
  3. Using RIPv2 on NBMA hub-and-spoke topology causes the hub router to rewrite the next hop field in the RIPv2 update to the IP address of the spoke router advertising the originalupdate, thereby creating reachability issues
Syndicate content