RIP question (Im doing my ccna)

Say that i have 3 routers all connected via direct serial links, running
RIP (version 1). Each of the serial interfaces can be pinged remotely
and locally. None of the ethernet interfaces can be pinged remotely, but
can be locally. Does this mean that rip is not advertising the networks
properly?

Advertisements

In article <>, Martin <1@1.1> wrote:
> Say that i have 3 routers all connected via direct serial links, running
> RIP (version 1). Each of the serial interfaces can be pinged remotely
> and locally. None of the ethernet interfaces can be pinged remotely, but
> can be locally. Does this mean that rip is not advertising the networks
> properly?

Sounds like it. If they're using RIPv1, maybe the LANs are all subnets
of the same classful network -- RIPv1 can't deal with non-contiguous
networks like this.

Advertisements

So should I double check the network advertisement statements and clear
the rip routing tables on each router to force each router to re-learn
all networks again and try my connectivity tests again?

Barry Margolin wrote:
> In article <>, Martin <1@1.1> wrote:
>
>
>>Say that i have 3 routers all connected via direct serial links, running
>>RIP (version 1). Each of the serial interfaces can be pinged remotely
>>and locally. None of the ethernet interfaces can be pinged remotely, but
>>can be locally. Does this mean that rip is not advertising the networks
>>properly?
>
>
> Sounds like it. If they're using RIPv1, maybe the LANs are all subnets
> of the same classful network -- RIPv1 can't deal with non-contiguous
> networks like this.
>

In article <40891c58$>, 1@1.1 says...
> So should I double check the network advertisement statements and clear
> the rip routing tables on each router to force each router to re-learn
> all networks again and try my connectivity tests again?
>
>

If you have a non-contigouos networks with RIP1, re-learning will not
help. Can you please, specify your addressing here?

Ivan Ostres <> wrote in message news:<c6b7d8$aasrv$-berlin.de>...
> In article <40891c58$>, 1@1.1 says...
> > So should I double check the network advertisement statements and clear
> > the rip routing tables on each router to force each router to re-learn
> > all networks again and try my connectivity tests again?
> >
> >
>
> If you have a non-contigouos networks with RIP1, re-learning will not
> help. Can you please, specify your addressing here?

Please check your RUNNING configuration and make sure that you add your
Ethernet prot's network. So each router you will have all connected
networks addresses under --router rip-- line, in your RUNNING configuration.
I think this will help you to solve your problem.

In article <>, 1@1.1 says...
> Say that i have 3 routers all connected via direct serial links, running
> RIP (version 1). Each of the serial interfaces can be pinged remotely
> and locally. None of the ethernet interfaces can be pinged remotely, but
> can be locally. Does this mean that rip is not advertising the networks
> properly?
>
> I will probably have some questions about ospf and eigrp soon.

This is better suited for alt.certification.cisco.

Common RIP mistakes

1) Using VLSM with RIPv1.
2) Not enabling RIP on the Ethernet interfaces (missing 'network ....'
statement)
3) Forgetting about split horizon on various serial interfaces.
4) ACL in place that prevents routing updates.

--

hsb

"Somehow I imagined this experience would be more rewarding" Calvin
*************** USE ROT13 TO SEE MY EMAIL ADDRESS ****************
********************************************************************
Due to the volume of email that I receive, I may not not be able to
reply to emails sent to my account. Please post a followup instead.
********************************************************************

Hansang Bae wrote:
> In article <>, 1@1.1 says...
>
>>Say that i have 3 routers all connected via direct serial links, running
>>RIP (version 1). Each of the serial interfaces can be pinged remotely
>>and locally. None of the ethernet interfaces can be pinged remotely, but
>>can be locally. Does this mean that rip is not advertising the networks
>>properly?
>>
>>I will probably have some questions about ospf and eigrp soon.
>
>
>
> This is better suited for alt.certification.cisco.
>
> Common RIP mistakes
>
> 1) Using VLSM with RIPv1.
> 2) Not enabling RIP on the Ethernet interfaces (missing 'network ....'
> statement)
> 3) Forgetting about split horizon on various serial interfaces.
> 4) ACL in place that prevents routing updates.
>

Share This Page

Welcome to Velocity Reviews!

Welcome to the Velocity Reviews, the place to come for the latest tech news and reviews.

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. You'll be able to chat with other enthusiasts and get tech help from other members.
Sign up now!