RIP Irregularities: Authentication, Updates: Uni-cast vs Multicast vs Broadcast
RIP (IPv4 versions) is a bit obsolete, I know, and very few production environments will use it as a "routing protocol of choice", but it´s also quite simple and there is simply no excuse for a Network Engineer to not know it in smallest details, let´s say - just in case.
If you need details about the protocol itself, look it up on Wikipedia, or even better - the RFCs:
RIPv1
RIPv2
Here I will only talk about the non-standard RIP behaviors.
RIPv2 weird behavior 1: Authentication
RIP Version 2 supports clear text and MD5 Authentication. The key-chain needs to be defined, and applied to the physical interface using the command:
(config-if)#ip rip authentication mode md5
(config-if)#ip rip authentication key-chain CISQUEROS_CHAIN
IMPORTANT!!!
The passwords and the key numbers MUST be the same on all the routers.
In case the key numbers are different:
- Router with the HIGHER key number will receive ALL the routes
- Router with the LOWER key number will IGNORE (reject) the received all routes received from the other router
RIPv2 weird behavior 2: Updates
By default Version 1 uses Broadcast to send it´s updates. Version 2 uses Multicast, with the destination address 224.0.0.9.
There is a way to "force" the routing updates to only one of the neighbours. To achieve this you need to:
- Manualy define the neighbour using the "network" command
- Define the interface towards the defined neighbour as PASSIVE, to prevent the Multicast Updates that are sent by default (If the interface is not defined as passive, both UNICAST and MULTICAST Updates will be sent)
There is also a way to force Broadcast Updates (ip 255.255.255.255 instead of default multicast destination 224.0.0.9) in Version 2 of RIP, and it´s achieved using the Interface Command:
(config-if)#ip rip v2-broadcast
RIPv2 weird behavior 3: Inject a Default Route into RIP
Another RIP-specific feature is injecting the default route using the "ip default-network" command. This is done in the Global Configuration mode:
(config)#ip default-network 4.0.0.0
Dont forget to advertise the network into RIP protocol:
(config-router)#network 4.0.0.0
Subscribe to:
Post Comments (Atom)
Most Popular Posts
-
Before we start, lets once again make sure we fully understand what Bridge Domain is. The bridge domain can be compared to a giant distribut...
-
Ever since Cisco bought Insieme and created Cisco ACI, and VMware bought Nicira and created NSX, I've been intensively deep-diving and b...
-
[In collaboration with the guest blogger, Marc Espinosa ] Let's start with the messaging protocols, MQTT and CoAP, and consider which ...
-
By know you should know the following facts about ACI: Cisco Nexus 9k Switches make the ACI Fabric, which is the Control and the Data pla...
-
Get ready to have your mind blown. One of the easiest procedures I've encountered. You just need to follow these 3 steps, to migrate the...
-
The VM-Series firewall for VMware NSX is jointly developed by Palo Alto Networks and VMware. NetX APIs are used to integrate the Palo Alto N...
-
Google has made their Cloud Platform (GCP) so that you can host your application any way your business requires. When we talk about the ...
-
First time we “unpack” ACI, we will find a certain number of potential Spine and potential Leaf switches, and hopefully 3 (or 5) APIC Contro...
-
Narbik Topology for web-iou Disclaimer: I DON’T OWN NOR HAVE AN ACCESS TO THE TOPOLOGY, INITIAL CONFIGS, IOU/IOL BINARIES OR ANY OTHER ...
-
Before I get into the Python for NX-OS, let me explain a few concepts that I've seen Network Engineers have been struggling with. Dev...
No comments:
Post a Comment