cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1202
Views
1
Helpful
5
Replies

Static default route doesn't work properly!

Dragos Burcut
Level 1
Level 1

Hi! I have configured in Cisco Packet Tracer a network composed of three LANs, each LAN being composed of a laptop and a switch, and that LAN connects to a router. Thus, in the network, along with the three routers of the LANs, a fourth router is connected, through which the Internet is accessed. The Internet connection is made using a

default static route (ip route 0.0.0.0 0.0.0.0 89.125.0.1)

Within the network, I used the

RIPv2

protocol for routing. But in that network I cannot connect from any terminal device (laptop) to the Internet (

ping 5.5.5.5

 doesn't work, Request timed out.). What could be the problem? I specify that the rest of the network connections are working fine! I have attached a picture of the computer network to the post.

1 Accepted Solution

Accepted Solutions

M02@rt37
VIP
VIP

Hello @Dragos Burcut 

On R4, add interface loopback 0 with

ip address 5.5.5.5/32

Also always on R4, on router RIP instance add

redistribute connected

command.

M02rt37_1-1694874495939.png

 

After, that you will be able to

ping 5.5.5.5

from PCs:

M02rt37_0-1694874471112.png

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

View solution in original post

5 Replies 5

M02@rt37
VIP
VIP

Hello @Dragos Burcut 

On R4, add interface loopback 0 with

ip address 5.5.5.5/32

Also always on R4, on router RIP instance add

redistribute connected

command.

M02rt37_1-1694874495939.png

 

After, that you will be able to

ping 5.5.5.5

from PCs:

M02rt37_0-1694874471112.png

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

Thank you very much for your help! I did everything you suggested and it worked perfectly!

You're very welcome @Dragos Burcut 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

Having a host actually at

5.5.5.5

to ping is a requirement, so that's well done by adding a loopback interface on R4 with that address, as suggested.

However, unclear why you also need to add 

redistribute connected

 command on R4.  I don't believe it's needed, and just a moment ago, opened the PT file, added the loopback interface with an IP of

5.5.5.5

and was able to ping that IP from laptop1.

JosephWDoherty_0-1694891259272.png

 


@Joseph W. Doherty wrote:

However, unclear why you also need to add 

redistribute connected

 command on R4.  I don't believe it's needed, and just a moment ago, opened the PT file, added the loopback interface with an IP of

5.5.5.5

and was able to ping that IP from laptop1.


BTW, the reason I believed the 

redistribute connected

 command isn't needed, or functionally appears not needed, on R4, is because the

default route

leads to R4 and R4 has all the RIP routes.

If you weren't using a

default route, then 5.5.5.5

would need to be inserted into the RIP topology.

The suggested 

redistribute connected

 command would do that, but so would the RIP network

5.0.0.0

Which to use?  Unsure about

RIPv2

but some routing protocols make a distinction between networks added via a network statement and those added via a

redistribution

statement, which may impact which would be better to use.

Also, the 

redistribute connected

 command picks up all the connected interfaces, in fact, in this instance, with it, it overlaps with the network

89.0.0.0

but (possibly? [true in PT]) without the that network statement, R4 will not share RIP with its RIP router (R3) neighbor.

Also BTW, since you are using the RIP 

default-information originate

 on R3, and have a

default static route

defined there, you don't need the

default static routes

on R1 and R2.