The book is right, I can't give you a correct answer without the specific details of your lab, anyway if you use passive-interface in R2's interface which is connected to R1 then it won't work as the book stated. If I am right on that, you can use passive-interface in not EIGRP neighbor facing interfaces, Loopbacks for instance, then you can check that these routes will be still advertised to the neighbors.
Lo0 10.1.1.1/24-----(R1)---s0/0 220.127.116.11/24-------------------------s0/0 18.104.22.168/24---(R2)
network 10.1.10 0.0.0.255
network 10.1.10.0 0.0.0.255
network 22.214.171.124 0.0.0.255
This will advertise to R2 all the routes....
this will prevent EIGRP neighborship and won't work...
El mensaje fue editado por: carlos hoslet, fixing my typo, sorry ;)
Passive interface only has to do with actual PACKETS sent or not. Nothing to do with an actual routing object (route).
Check to be sure that your connected routes are in "show ip eigrp topology" (the RIB) first.
Also, check to be sure that the interface you are making passive is NOT the one that you are a neighbor present on. If so, it will go away (you're killing the Hello's).
De nada, Héctor:
As Scott pointed out the passive-interface implies no Hellos or EIGRP packets out of the interface, this fact prevents the flow of EIGRP info between neighbors and adjacency indeed, in the other hand the network statement puts that network into the EIGRP process so they can be advertised to the neighbors normally...
Now you got it!
I use the passive-interface command for LAN facing interfaces. So for example, if I have a 2800 router that has 192.168.1.1/24 bound to the ethernet interface and a serial interface of 10.0.0.1/30 for the serial interface and my lan interface is facing just a layer 2 network, then why advertise eigrp hellos to the lan? Seems to be a waste of bandwidth and a possible security problem... assuming you have not authenticated your route advertising.
One other option (that is better IMHO) is to use "passive-interface default". That will turn off the advertisements on ALL interfaces. It will force you to think about where you DO want to form neighbors over (and protect things a little from unplanned neighbors). You'll need to do "no passive-interface (intf)" wherever you want to form peers.
Cisco says that
· Use of the passive-interface command in EIGRP suppresses the exchange of hello packets between two routers, which results in the loss of their neighbor relationship
· This stops not only routing updates from being advertised, but it also suppresses incoming routing updates.
The router is still advertising the networks which are configured under "network" command but with no neighborship. (as the Hellos are supressed). check this link:
When an EIGRP−enabled interface is made passive, no EIGRP packets are sent out to that interface, and since
EIGRP uses hello packets to form adjacencies with neighbors, no adjacencies will be formed.
Unlike RIP or IGRP (where updates are received but not sent), when thepassive−interface
command is used with EIGRP, routing updates are neither received nor sent because no neighbor relationship