The Advanced part of RIP Protocol
Previously, I wrote a blog about the primary application of RIP, but now I summarize other aspects of RIP, such as security authentication, default routing, unicast updates of RIP, etc., but they should not be used much in actual engineering projects. It's more about command deployment.
one。 RIP certification
Text mode:
Md5 mode:
Lab Topology:
Deployment:
R1:
R1 (config) # key chain PL
R1 (config-keychain) # key 1
R1 (config-keychain-key) # key-string cisco
R1 (config-keychain-key) # int f0bin0
R1 (config-if) # ip rip authentication mode?
Md5 Keyed message digest
Text Clear text authentication
R1 (config-if) # ip rip authentication key-chain PL
R2:
R2 (config) # key chain PL / / defines the keychain name, which can be inconsistent
R2 (config-keychain) # key 1 / / define key sequence number
R2 (config-keychain-key) # key-string cisco / / define key password
R2 (config-keychain-key) # int f0and0
R2 (config-if) # ip rip authentication mode?
Md5 Keyed message digest-> password plaintext
Text Clear text authentication-> password md5 encryption
R2 (config-if) # ip rip authentication key-chain PL
Show command: show key chain
Show run | s key
II. Default route of RIP
Easy to configure-simple command, just one command
Dynamic adaptation to network topology
Command deployment:
R2 (config) # router rip
R2 (config-router) # default-information originate
-dynamic default routes, usually deployed on edge egress routes
Default route for Renewable RIP-> Murray.
III. Passive interface of RIP
Deployment:
Method ①:
R1 (config) # router rip
R1 (config-router) # passive-interface f0swap 0 / / Router execution
Or
R1 (config-router) # passive-interface vlan 10 Universe 20 Accord 30... / / generally executed on the aggregation layer switch
-optimize packets that the other party does not need
Method ②:
R1 (config) # router rip
R1 (config-router) # passive-interface default / / set all interfaces as passive
R1 (config-router) # no passive-interface f0swap 0 / / enable an interface
General deployment environment:
① is deployed on aggregation layer switches because the access layer switches do not need protocol packets and only recognize mac.
② is deployed on edge router
IV. RIP unicast updates
Deployment:
R1 (config) # router rip
R1 (config-router) # version 2
R1 (config-router) # no auto-summary
R1 (config-router) # network x.0.0.0 / / send out Multicast packet 224.0.0.9
R1 (config-router) # neighbor 12.1.1.2 / / Unicast specifies neighbors and uses unicast packets to interact with neighbors
R1 (config-router) # passive-interface f0swap 0 / / passive interface feature can only suppress multicast, broadcast packets, not unicast packets.
R2 also needs to be deployed.
Note: RIP traffic optimization = passive interface + unicast update
5. Offset list of RIP
Definition: offset-list (increase only, not decrease), used to modify the measure
Deployment:
① matches routes through ACL
Access-list 1 permit 2.2.2.2
② calls ACL through offset list
Router rip
Offset-list 1 in 5 f0amp 0 / / routes coming in from interface f0pic0 increase the hop count by 5
Offset-list 1 out 12 f0amp 0 / / routes out of interface f0max 0 increased by 5
Offset-list 0 out 12 f0amp 0 / / increase all routes out of interface f0max 0 by 5
With regard to the choice of direction:
Where did you learn the route? write in the direction. For example, R1 learns routing from R2, that is, R2 routes to R1, so to increase the hop count of R2 in R1, use in. Whoever receives it will in.
