EIGRP Passive Interface

When you use the EIGRP network command, two things will happen:

  • All interfaces that have a network that falls within the range of your network command will be advertised in EIGRP.
  • EIGRP hello packets will be sent on these interfaces.

Sometimes however you might want to advertise a network in EIGRP but you don’t want to send hello packets everywhere. Take a look at the topology below for an example:

EIGRP Passive Interface Demo Topology

Above we have two routers, R1 and R2. On the left side there’s the /24 network with a switch and some computers. R1 wants to advertise this network to R2 but since there are no other EIGRP routers in the /24 network, it’s pointless to send EIGRP hello packets on the FastEthernet 0/1 interface.

It’s also a security risk, when someone connects a router in the /24 network (or starts a virtual router on their computer) they will be able to become EIGRP neighbors with R1.

To prevent this from happening, we will use the passive-interface command. This will ensure that the network is advertised in EIGRP but it will disable hello packets on the interface.

Another trick to advertise something in EIGRP without sending hello packets on the interface is using the “redistribute” command.

Let me show you how to configure this.


Here’s the EIGRP configuration of R1 and R2:

R1(config)#router eigrp 12
R2(config)#router eigrp 12

As a result, R2 will learn network /24:

R2#show ip route eigrp 
D [90/307200] via, 00:00:59, FastEthernet0/0

The problem however is that R1 is sending hello packets towards our computers. You can verify this by enabling a debug:

R1#debug eigrp packets hello
EIGRP Packets debugging is on

EIGRP: Sending HELLO on FastEthernet0/0
  AS 12, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

EIGRP: Sending HELLO on FastEthernet0/1
  AS 12, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0

Above you can see that the hello packets are going in both directions.

EIGRP Sending Hello Packets

Let’s use the passive interface command to disable the hello packets towards the switch:

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 791 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

1632 Sign Ups in the last 30 days

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

Forum Replies

  1. Hi Rene,
    Very Good Explanation!


  2. Hi Rene,

    If we are connected different clients with a L3 Switch , we can used this command (Passive Interface) to stop hello packet to clients.

    My question is , if make Passive Interface Defaults on all interface (directly connected to other router) should Adjacency will be there or will be stop ?

    Thanks …


    Adil Khan

  3. Hi Adil,

    The adjacency will be killed. If you use passive-interface on all interfaces then you need to use no passive-interface for the interfaces that require an EIGRP neighbor adjacency.


  4. Great and easy to understand lesson. I would only make one request on this for something to be added.
    in my lab of this lesson everything went smoothly. Only thing I had some hiccups on that I had to search was the following.

    I knew how to setup from the lesson the default command for passive interface. However, for some reason I was thinking “incorrectly” that I needed to setup the no passive-interface command under the interfaces… I tried a few times but it was not working for obvious reasons as that was the wrong place. Its small thing and I quickly d

    ... Continue reading in our forum

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