rip on one interface

[gavin han]

I've multiple svis in 10.1.0.0/16 subnet on the switch but i only want to run rip on SVI that has 10.10.0.0/24 subnet. how to accomplish it? run unicast rip since we can't define classless mask for rip?

[John Blakley]

You should run passive-interface default and then advertise out of the only interface you want:

router rip

passive-interface default

version 2

network 10.0.0.0

no passive-interface <interface number/svi>
no auto-summary

If you don't want any of the other networks advertised, you'll need to create a distribution list to filter those out to the device that you're neighboring to. You can also leave all interfaces passive and then use the neighbor command if you'd rather not multicast.

HTH,

John

[gavin han]

you're answer isn't right.

this is how i've it configured. passive interface works differently in RIP compare to EIGRP, OSPF. passive-interface in RIP won't send routing update to neighbor but it will still learn routing updates from them those neighbors.

following command still enables RIP on all interface that belongs to 10.0.0.0/8. All i want is to enable rip only on 10.10.0.0/24 SVI.

router rip

passive-interface default

version 2

network 10.0.0.0
no auto-summary

[John Blakley]

I guess you didn't read my answer completely. Neighbor statements "bust through" so-to-speak passive interface commands. For example:

R5 is connected to R6:

R5 (has a loopback of 1.1.1.0/24):

R5(config)#do sh run | s router rip
router rip
 version 2
 passive-interface default
 network 1.0.0.0
 network 10.0.0.0
 no auto-summary

R5(config-router)#do sh ip rip data
1.0.0.0/8    auto-summary
1.1.1.0/24    directly connected, Loopback1
10.0.0.0/8    auto-summary
10.125.100.0/24    directly connected, FastEthernet0/1

No routes from R6...

R6 (has a loopback of 6.6.6.0/24):

R6(config-router)#do sh run | s router rip
router rip
 version 2
 passive-interface default
 network 6.0.0.0
 network 10.0.0.0
 no auto-summary

R6(config-router)#do sh ip rip data
6.0.0.0/8    auto-summary
6.6.6.0/24    directly connected, Loopback1
10.0.0.0/8    auto-summary
10.125.100.0/24    directly connected, Vlan1

No routes from R5...I'll add the neighbor command on both sides, but leave them with passive interfaces:

R5:

R5(config-router)#do sh run | s router rip
router rip
 version 2
 passive-interface default
 network 1.0.0.0
 network 10.0.0.0
 neighbor 10.125.100.5
 no auto-summary

R5(config-router)#do sh ip rip data
1.0.0.0/8    auto-summary
1.1.1.0/24    directly connected, Loopback1
6.0.0.0/8    auto-summary
6.6.6.0/24
    [1] via 10.125.100.5, 00:00:31, FastEthernet0/1
10.0.0.0/8    auto-summary
10.125.100.0/24    directly connected, FastEthernet0/1

I have my route from R6 (with passive-interface default enabled).

R6:

R6(config-router)#do sh run | s router rip
router rip
 version 2
 passive-interface default
 network 6.0.0.0
 network 10.0.0.0
 neighbor 10.125.100.2
 no auto-summary

R6(config-router)#do sh ip rip data
1.0.0.0/8    auto-summary
1.1.1.0/24
    [1] via 10.125.100.2, 00:00:13, Vlan1
6.0.0.0/8    auto-summary
6.6.6.0/24    directly connected, Loopback1
10.0.0.0/8    auto-summary
10.125.100.0/24    directly connected, Vlan1

I have my route from R5 (with passive-interface default enabled).

On R6:

R6(config-router)#do sh ip route 1.1.1.0
Routing entry for 1.1.1.0/24
  Known via "rip", distance 120, metric 1
  Redistributing via rip
  Last update from 10.125.100.2 on Vlan1, 00:00:11 ago
  Routing Descriptor Blocks:
  * 10.125.100.2, from 10.125.100.2, 00:00:11 ago, via Vlan1
      Route metric is 1, traffic share count is 1

 Routing for Networks:
    6.0.0.0
    10.0.0.0
  Passive Interface(s):
    FastEthernet0/0
    FastEthernet0/1
    FastEthernet1/0
    FastEthernet1/1
    FastEthernet1/2
    FastEthernet1/3
    FastEthernet1/4
    FastEthernet1/5
  Passive Interface(s):
    FastEthernet1/6
    FastEthernet1/7
    FastEthernet1/8
    FastEthernet1/9
    FastEthernet1/10
    FastEthernet1/11
    FastEthernet1/12
    FastEthernet1/13
    FastEthernet1/14
    FastEthernet1/15
    Vlan1
    Vlan10
    Loopback1
    VoIP-Null0

So, no, my answer wasn't incorrect. If I were to rely on multicasting, then no it wouldn't have worked which is why I said that you could leave it to default and then use the neighbor command.

Also, doing the neighbor statement does seem to alleviate the issue with the advertisement out of other SVIs because they're in a passive state:

Before adding neighbor statement:

*Mar  1 02:28:04.695: RIP: sending v2 flash update to 224.0.0.9 via FastEthernet0/1 (10.20.1.1)
*Mar  1 02:28:04.695: RIP: build flash update entries - suppressing null update
*Mar  1 02:28:04.699: RIP: sending v2 flash update to 224.0.0.9 via FastEthernet0/0 (10.125.100.67)
*Mar  1 02:28:04.699: RIP: build flash update entries
*Mar  1 02:28:04.699:   10.125.56.0/24 via 0.0.0.0, metric 2, tag 0
*Mar  1 02:28:04.699: RIP: sending v2 flash update to 224.0.0.9 via Loopback1 (5.5.5.5)
*Mar  1 02:28:04.703: RIP: build flash update entries
*Mar  1 02:28:04.703:   10.125.56.0/24 via 0.0.0.0, metric 2, tag 0

After adding it:

R5(config-router)#
*Mar  1 02:29:53.115: RIP: received v2 update from 10.20.1.2 on FastEthernet0/1
*Mar  1 02:29:53.119:      10.125.56.0/24 via 0.0.0.0 in 1 hops
R5(config-router)#
*Mar  1 02:30:03.311: RIP: sending v2 update to 10.125.100.5 via FastEthernet0/0 (10.125.100.67)
*Mar  1 02:30:03.311: RIP: build update entries
*Mar  1 02:30:03.311:   5.5.5.0/24 via 0.0.0.0, metric 1, tag 0
*Mar  1 02:30:03.315:   10.20.1.0/24 via 0.0.0.0, metric 1, tag 0
*Mar  1 02:30:03.315:   10.125.56.0/24 via 0.0.0.0, metric 2, tag 0

It doesn't stop the receipt of another rip advertisement, but it does seem to stop the sending of updates out of the other interfaces except the one the neighbor is on.

HTH,

John

[gavin han]

what if you've following?

router rip
 version 2
 passive-interface default
 neighbor 10.125.100.2
 no auto-summary

if vlan for nei is 10.125.100.0/24 than i only want to see 10.125.100.0/24 + routes learned from 10.125.100.2 neighbor.

[John Blakley]

You would filter with distribution lists. Create an acl matching on what you want to see and allow, then apply that to a distribution list inbound.

[gavin han]

distribution lists won't work. i don't want to see any "connected" routes that's there in the routing table you pasted.