From: Donny MATEO (donny.mateo@sg.ca-indosuez.com)
Date: Tue Dec 10 2002 - 23:51:23 GMT-3
erm...
OK so you make a neighbor relationship using the neighbor command and issue the passive interface on
that interface. But the question is what is the point of building a neighbor relationship when you
don't want to receive any update from that neighbor ?
Use the unicast to change the nature of RIP broadcast to a unicast when sending routing update. Use
the passive interface when you don't want to learn any routing update receive from a particular
interface.
Check out the following debug ouput on the first line the destination of "Sending v1 update to
x.x.x.x"
Before neighbor command (neigh 150.100.12.1)
2w1d: RIP: sending v1 update to 255.255.255.255 via Serial0 (150.100.12.1)
2w1d: RIP: build update entries
2w1d: subnet 150.100.1.0 metric 1
2w1d: subnet 150.100.2.0 metric 2
2w1d: subnet 150.100.3.0 metric 11
2w1d: subnet 150.100.12.0 metric 1
2w1d: subnet 150.100.23.0 metric 2
After neighbor command (neigh 150.100.12.2)
2w1d: RIP: sending v1 update to 150.100.12.2 via Serial0 (150.100.12.1)
2w1d: RIP: build update entries
2w1d: subnet 150.100.1.0 metric 1
2w1d: subnet 150.100.2.0 metric 2
2w1d: subnet 150.100.3.0 metric 11
2w1d: subnet 150.100.12.0 metric 1
2w1d: subnet 150.100.23.0 metric 2
Donny
"Larson, Chris"
<CLarson@usaid.go To: "'Tran Tien Phong'" <PhongTT2@FPT.COM.VN>, Ram Shummoogum
v> <rshummoo@ca.ibm.com>, eward15@juno.com
Sent by: cc: ccielab@groupstudy.com
nobody@groupstudy Subject: RE: eigrp neighbor command
.com
10-12-2002 22:27
Please respond to
"Larson, Chris"
I believe that if you use the passive interface command (this will stop the
braodcast announcements) and issue the neighbor command (this will do
unicast updates) that it will prevent multicasts and only do unicast
updates. I have not been in the lab for a while now, but I think that is the
way to do it. for both RIP (Ver 1 and 2) and EIGRP.
> -----Original Message-----
> From: Tran Tien Phong [SMTP:PhongTT2@FPT.COM.VN]
> Sent: Monday, December 09, 2002 11:54 PM
> To: Ram Shummoogum; eward15@juno.com
> Cc: ccielab@groupstudy.com
> Subject: RE: eigrp neighbor command
>
> For RIP, although you configure neighbor command, RIP updates still sent
> to multicast address 224.0.0.9. You need to define an access-list to
> prevent this
>
> -----Original Message-----
> From: Ram Shummoogum [mailto:rshummoo@ca.ibm.com]
> Sent: Tue 12/10/2002 8:21 AM
> To: eward15@juno.com
> Cc: ccielab@groupstudy.com
> Subject: Re:eigrp neighbor command
>
>
>
> This is true for RIP but I am not sure about EIGRP. I know for a
> fact that
> in EIGRP the passive-interface will prevent the formation of
> neighbors.
>
> Rgds,
> RAM
>
>
>
> eward15@juno.com@groupstudy.com on 12/09/2002 07:52:52 PM
>
> Please respond to eward15@juno.com
>
> Sent by: nobody@groupstudy.com
>
>
> To: ccielab@groupstudy.com
> cc:
> Subject: Re:eigrp neighbor command
>
>
> I believe the neighbor command is used to send routing annoucements
> as
> unicast packets instead of multicast or broadcast cast packets. For
> instance, there may be 5 routers on a segment but only two of them
> are
> using the same routing protocol. Instead of needlessly sending
> updates to
> the other routers, you could use a passive-interface to block the
> broadcasts/multicasts on the interface and instead send a directed
> unicast.
> Someone please correct me if I am wrong.
>
> Eugene Ward
>
>
>
>
> ________________________________________________________________
> Sign Up for Juno Platinum Internet Access Today
> Only $9.95 per month!
> Visit www.juno.com
> .
> .
> .
.
This message is for information purposes only and its content
should not be construed as an offer, or solicitation of an offer,
to buy or sell any banking or financial instruments or services
and no representation or warranty is given in respect of its
accuracy, completeness or fairness. The material is subject
to change without notice. You should take your own independent
tax, legal and other professional advice in respect of the content
of this message. This message may contain confidential or
legally privileged material and may not be copied, redistributed
or published (in whole or in part) without our prior written consent.
This email may have been intercepted, partially destroyed,
arrive late, incomplete or contain viruses and no liability is
accepted by any member of the Credit Agricole Indosuez group
as a result. If you are not the intended recipient of this message,
please immediately notify the sender and delete this message
from your computer.
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:43 GMT-3