[Packet tracer] Router can't ping outside local address, others can :(

[k3n]

I was able to successfully configure a nat overload between 2 networks with different addresses.

This video helped: http://www.youtube.com/watch?v=G2NN3VK9LWk

Unfortunately though, the router with the redundant link, R1, refuses to ping, 64.1.1.6, while the Corp & R2 routers can.

I went as far as to create another duplicate router, making sure that only ospf was configured on it.

Here is my .pkt file (version 5.3.3+ needed) if anyone's interested:
http://rapidshare.com/files/1082872771/4-14-13_nat.pkt

 

[Udgnim]

get this message when trying to download "The download for this file has not been enabled. Only the user who uploaded it, can enable the download option."

have you tried taking a look at what information Simulation mode produces?

 

[k3n]

Thanks for the response. The following link may work: https://mega.co.nz/#!vRYTVCzD!YqPBzWGI9_BGYHJNIw-nKjC8zBMJEl1_ICjLCS4iynA

 

[david_brent]

Can you ping other hosts from R1, e.g. PC-PT?

 

[rasczak]

This is beyond me. marked for later.

could we look at your config file for R1 and Corp?

Which interface is unable to ping?

 

[Danimal1209]

Without looking at the configs:

Makes sure that the T1 links for R1 are addressed properly.
Make sure the routing protocols are properly set up. (the other routers need to be advertising the proper networks)
Setup an ICMP debug on the corp router to see if it is receiving and sending the packets to R2.

 

[Udgnim]

R2 can ping 64.1.1.6 on R3 because R2 has a default route out its s0/2/0 which is directly connected with Corp

Corp is directly connected with R3 on 64.1.1.4 /30, so Corp and R2 can ping 64.1.1.6

R1 has no default route to Corp or route to 64.1.1.4 /30 which is why it can't ping that network

 

[Danimal1209]

If R1 has no default route and it hasn't learned where to send packets destined for 64.1.1.6 then it won't send them.

Since corp is the only way packets will need to go make it the default route.

 

[k3n]

Thanks alot for the response. I went ahead and added network 64.1.1.4 /30 to the OSPF configuration of the Corp & R3 router & it resolved the issue

In real world scenarios, setting a default route would be the better scenario since there are billions of public addresses; making it impracitical to manually configure them for a dynamic protocol.

Also I had to make sure that the access list on Corp router would permit the network to make outside contact

 

[Danimal1209]

In most cases, you just need to advertise networks that are on your network/Autonomous System. Then you have a default route for everything else.

 

[k3n]

Unfortunately though, a ping can't complete when I try to ping from host ".5.2", located directly left of the cloud symbol at the the top, to the server with the address 192.168.30.3.

I looked at it in simulation mode:
The packet is able to reach the server, but once it reaches back the Corp router, of which host .5.2 is directly connected to, it's discarded. It seems it's discarded because the router no longer sees the host's destination as 192.168.5.2, but as 64.1.1.5, due to the initial translation.



Default routes were set on the border routers (Corp & R3).

These are the command I used:
ip nat inside pool Todd 64.1.1.5 64.1.1.5 net 255.255.255.252
ip nat inside source list 1 pool Todd overload

Corp router's access-list:

    permit 64.1.1.4 0.0.0.3 (60 match(es))
    permit 192.168.3.0 0.0.0.255 (20 match(es))
    permit 192.168.1.0 0.0.0.127 (96 match(es))
    permit 192.168.128.0 0.0.0.127
    permit 192.168.5.0 0.0.0.255 (84 match(es))
    permit 192.168.21.0 0.0.0.255 (26 match(es))
    permit 192.168.10.0 0.0.0.255 (8 match(es))

Edit: I configured NAT/PAT on separate network & realized, setting the pool the range to handing more than 1 unique address was a requirement:
I.e: ip nat inside pool Todd 64.1.1.9 64.1.1.14 net 255.255.255.248