cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
832
Views
5
Helpful
4
Replies

I cannot ping to next router, even with ip route

hfakoor222
Spotlight
Spotlight

Cannot ping to ISP 64.100.0.1

from PC1 

I can ping to 64.100.0.2 R1 router directly connected to ISP

 

 

My ip route 0.0.0.0 0.0.0.0 64.100.0.1 does not seem to do the trick

 

Any ideas?

 

2.png

 

 

 

 

 

R1 Configuration (output abridged)



R1(config)#ip route 0.0.0.0 0.0.0.0 64.100.0.1
R1(config)#exit








R1#shsh running config


hostname R1
!
boot-start-marker
boot-end-marker

ip cef
!
!
!
!
no ip domain lookup
ip host Externalv4 209.165.200.226
ip host ISPv4 64.100.0.1
ip host PC-Av4 192.168.1.10
ip host R1v4 64.100.0.2
ip host S1v4 192.168.1.2
ipv6 unicast-routing
ipv6 host Externalv6 2001:DB8:ACAD:200::226
ipv6 host ISPv6 2001:DB8:ACAD::1
ipv6 host PC-Av6 2001:DB8:ACAD:1::10
ipv6 host R1v6 2001:DB8:ACAD::2
ipv6 host S1v6 2001:DB8:ACAD:1::2

!
ip tcp synwait-time 5
!
!
!
!
interface FastEthernet0/0
ip address 64.100.0.2 255.255.255.248
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
ipv6 address FE80::2 link-local
ipv6 address 2001:DB8:ACAD::2/64
!
interface Serial0/0
no ip address
shutdown
clock rate 2000000
!
interface FastEthernet0/1
ip address 192.168.1.1 255.255.255.0
duplex auto
speed auto
ipv6 address FE80::1 link-local
ipv6 address 2001:DB8:ACAD:1::1/64
!



ip route 0.0.0.0 0.0.0.0 64.100.0.1

ip nat inside source list 1 interface FastEthernet0/0 overload
!
access-list 1 permit 192.168.1.0 0.0.0.255

ipv6 route ::/0 2001:DB8:ACAD::1
!

Pic2.png

 

 

Seems to be able to ping ipv6 address from PC but not ip address

 

 

 

 

Pic2.png

 

Pic1.png

 

 

 

I can also ping the FastEthernet face of ISP IPV6 address (faces to external router)

Pic2.png

 

 

 

I am thinking it may have someting to do with the nat translations in the running-config

 

 

Any ideas on to fix this issue?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1 Accepted Solution

Accepted Solutions

Hello,

 

If you put in the EIGRP network for the 192.168.1.x network and it worked then it may just need a route back to that network which you can do statically. 

 

On the ISP router you could add the static route of:

 

ip route 192.168.1.0 255.255.255.0 64.100.0.2

 

If that doesn't work can you do a

show ip route

on the ISP router

View solution in original post

4 Replies 4

hfakoor222
Spotlight
Spotlight

I put in EIGRP route for 192.168.1.x network and it works fine, I am really hoping for suggestions on an static ip route 

Hello,

 

If you put in the EIGRP network for the 192.168.1.x network and it worked then it may just need a route back to that network which you can do statically. 

 

On the ISP router you could add the static route of:

 

ip route 192.168.1.0 255.255.255.0 64.100.0.2

 

If that doesn't work can you do a

show ip route

on the ISP router

I didn't think about a static route from ISP being able to work the other way around, I will keep this in mind for future reference,

 

Thank You

Hello,

 

post the full running configurations (sh run) of all three devices (the routers and the switch as well). On R1, there is no

ip nat outside

configured on any interface ?