From: Atif Awan (atifawan@xxxxxxxxxxx)
Date: Mon Sep 25 2000 - 06:38:12 GMT-3
but normally RIP does not advertise the directly connected network. I have
seen it advertise the directly connected network only in case of a neighbor
statement being configured ..
Regards
Atif Awan
>From: Kristian Bjoernskov <krbj-ccie@novo.dk>
>To: Atif Awan <atifawan@hotmail.com>
>CC: ccielab@groupstudy.com
>Subject: Re: RIP details
>Date: Mon, 25 Sep 2000 11:12:05 +0200 (CEST)
>
>On Sat, 23 Sep 2000, Atif Awan wrote:
>
> >
> > When i configure RIP for sending unicast updates it also advertises a
>route
> > for the subnet on the interface on which it is sending the updates. For
> > example, suppose my serial 0 interface has an ip address 0f 10.3.0.2/24
>rip
> > is configured to unicast the updates to 10.3.0.1 using the neighbor
>command.
> > When i see the output of the command debug ip rip it displays:
> >
> > RIP: sending v1 update to 10.3.0.1 via Serial0 (10.3.0.2)
> > subnet 10.3.0.0, metric 1
> >
> > in addition to other routes.
> >
> > Can someone please explain why the router needs to advertise the
>directly
> > connected subnet in its updates.
>
>Well, maybe it doesn't! It is however required by RFC1158 #2 to advitice
>the entire route table which include directly connected networks.
>
>If your network was not a Serial but maybe an ethernet or tokenring, more
>than one IP subnet could appear on each physical net. If not all hosts
>without default gw (ie running routed) and all routers is aware of all
>nets, the router(s) will need to route between different subnet on the
>same physical net.
>
>
>Most kind regards,
>Kristian Bjoernskov, <mailto:krbj@novo.dk>
>Novo Nordisk IT, Network - internet.
>Phone: +45 4442 3299. Fax: +45 4442 6061
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:01 GMT-3