cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
459
Views
0
Helpful
5
Replies

Routing issue

OneTwoMany
Level 1
Level 1

I cannot ping from the 192.168.10/24 network to the 10.10.16.0/20 network, What am I doing wrong?

Current configuration : 843 bytes

!

version 12.2

service timestamps debug datetime msec

service timestamps log datetime msec

!

hostname hostname

!

enable secret xxxx

!

ip subnet-zero

!

!

no ip domain lookup

!

!

!

!

voice call carrier capacity active

!

!

!

!

!

!

!

!

!

mta receive maximum-recipients 0

!

!

!

!

interface Ethernet0/0

description In

ip address 192.168.1.254 255.255.255.0

no ip route-cache

no ip mroute-cache

half-duplex

!

interface Ethernet0/1

description Out

ip address 10.10.16.2 255.255.240.0

no ip route-cache

no ip mroute-cache

half-duplex

!

!

mta receive maximum-recipients 0

!

!

!

!

interface Ethernet0/0

description In

ip address 192.168.1.254 255.255.255.0

no ip route-cache

no ip mroute-cache

half-duplex

!

interface Ethernet0/1

description Out

ip address 10.10.16.2 255.255.240.0

no ip route-cache

no ip mroute-cache

half-duplex

!

ip default-gateway 10.10.16.1

ip classless

no ip http server

!

!

!

call rsvp-sync

!

!

mgcp profile default

!

dial-peer cor custom

!

!

!

!

!

line con 0

line aux 0

line vty 0 4

password #$&%^&

login

!

!

end

5 Replies 5

Hello,

are both your interfaces up/up ?

Regards,

GP

Thank you for responding.

Yes both are up. If I telnet into the router from the 192 network I can telnet to the firewall 10.10.16.1, however I cannot telnet to the firewall from the 192 network.

I think there are two possibilities to consider:

It might be a default gateway problem on the PC. The PC can telnet to the router because it is on the local subnet. But the PC may have a problem getting to the 10.10.16 network because it is remtoe and the PC default gateway may not be correct. How is the PC default gateway configured?

It might be that the firewall does not have a route to the 192 network. The firewall can talk to the router because they are on a common subnet (10.10.16) but does not have a route to the 192 network.

HTH

Rick

HTH

Rick

The gateway on all the PCs is the internal router interface 192.168.1.254.

If I attempt to ping the inside interface of the firewall does it need to have a route back or will it send the ICMP response back to the outside interface of the router?

It needs to have a route back. The respnse is routed independently. It has no idea which way the request came in.

Kevin Dorrell

Luxembourg