We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 606 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)


367 New Members signed up the last 30 days!


100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!


Forum Replies

  1. Hi Rob,

    There’s a big difference between the two. An EIGRP router that is configured as a stub does not receive queries when one of its neighbors loses a network.

    Passive-interface is about sending hello packets on an interface. Normally when you use the network command to advertise something then it does two things:

    1. It advertises all networks that fall within the range of your network commmand on all active interfaces.
    2. It sends hello packets on all active interfaces that have networks that fall within the range of your network command.

    When you enable passive-interface, it will stop sending the hello packets. This is useful on interfaces that connect to end-devices like phones, workstations, servers, etc. You probably don’t want to send EIGRP hello’s in their direction…there are no EIGRP routers there.

    Hope this helps!


  2. Hi John,

    That’s interesting, I just tried it on a 1841 with IOS 15 and it does the same thing. When I configure EIGRP redistributed then that’s the only thing that shows up in the config. On a 3725 running 12.4T it does add connected and summary automatically as well.


  3. Hello Rene,
    I have got some confusion here. I am going to use the below topology to ask my questions.

    1. In this topology, let’s say Stub is not configured. If I shutdown the loopback 0 on R2, who would send out Query? Is it only R1 or only R2 or both routers?

    2. Here If R1 is configured as Stub and Loopback 0 gets shutdown on R2, R2 will not send any Query to R1. However, R1 will send Query to R2. Is it correct?

    Thanks a lot.


  4. Hello Azm

    R2 will query R1 to find an alternate route to R1 will not query any routers because it is not connected to any. Queries will not be sent back to the original router from which it was received, so R1 will not “re-query” R2. R1 will only send queries IF one of its connected networks go down.

    If R1 is configured as a Stub and loopback 0 goes down, R2 will NOT send a query to R1 since it “knows” that because it is a stub, it cannot possibly have an alternate route to Again, R1 will not send a query to R2 unless one of its connected networks go down. If that happens, then yes, R1 will send a query to R2.

    I hope this has been helpful!


  5. Hello Hussein

    There are several specialised cases where the receive-only option is useful. Some of these include:

    1. When applying it to a dual homed stub router with more than one connection to the same EIGRP AS. In a Dual-homed scenario “receive-only” would prevent the stub router from becoming a transit router incase of link failure in your core and still have redundancy from the stubs perspective.
    2. When using a route server connected to an eBGP network
    3. When using DMVPN spokes.

    I hope this has been helpful!


15 more replies! Ask a question or join the discussion by visiting our Community Forum