How to access another subnet via inside interface

[teddyteddyteddy]

Hi all, I'm facing a problem that client from tw subnet(192.168.200.0) to us subnet(175.17.1.0) via inside to 2600router

IN some graphical::

TW client(192.168.200.10) -->PIX515(inside,192.168.200.0) -->(e0,192.168.200.1)cisco2600(e1,175.17.1.1)-->US client(175.17.1.10)

I have deploy a very simple config to isolate other affacting factor:

====================================================

PIX Version 7.2(2)
!
hostname PIXHK
domain-name default.domain.invalid
enable password xx encrypted
names
name 192.168.200.0 tw
name 175.17.1.0 us
!
interface Ethernet0
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet1
nameif inside
security-level 100
ip address 192.168.240.4 255.255.255.0
!
passwd xx encrypted
ftp mode passive
dns server-group DefaultDNS
domain-name default.domain.invalid
access-list inside_access_in extended permit icmp tw 255.255.255.0 us 255.255.255.0 echo log debugging
access-list inside_access_in extended permit icmp tw 255.255.255.0 us 255.255.255.0 echo-reply log debugging
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
icmp unreachable rate-limit 1 burst-size 1
icmp permit any inside
asdm image flash:/asdm
no asdm history enable
arp timeout 14400
access-group inside_access_in in interface inside
route inside us 255.255.255.0 192.168.240.1 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout uauth 0:05:00 absolute
http server enable
http tw 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
telnet timeout 5
ssh timeout 5
console timeout 0
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect icmp
inspect icmp error
!
service-policy global_policy global
prompt hostname context
Cryptochecksum:03acb03d7e13cb4cfdf7ff0ac14c25ce
: end
asdm image flash:/asdm
no asdm history enable

=====================================================

Under the above config, tw client(192.168.200.10) ping any host on 175.17.1.0/24 including 175.17.1.1, it outcome the follow error:

Deny inbound icmp src inside:192.168.200.10 dst inside:175.17.1.1 (type 8, code 0)

any idea, thousand thanks!!

 

[NetworkGhost]

Simply not possible my friend. The Pix will no route traffic out the same interface it came on. The other options would be to add a host route on the system that is trying to access the remote network or to poing the .200.x users to use 2600 as the default gateway and ensure the appropriate routes are in place on the 2600.

The 2600 is located off of the inside interface of the Pix right?

Free Firewall/Network/Systems Support-

http://firewalls.ath.cx:8080

 

[teddyteddyteddy]

Thanks NetworkGhost! Actually I have searched in google and finding the PIX cannot routing back via a single interface, but does it possible to add one more interface e2 and for example assign an IP 192.168.240.2 and dedicate it for routing to 175.17.1.0/24 network?? thanks again!

 

[BuckWeet]

I believe (not 100% sure) that PIX can route with 7.x code..

Could someone verify that??

 

[NetworkGhost]

Buckweet, you are correct with 7.2 you can use the intra interface command to allow traffic to flow in and out the same interface.

Here it is:

same-security-traffic permit intra-interface

Keep in mind you apply this at the interface that you want traffic to be rerouted out for and you should also have a ACL allowing this traffic. You will also need a valid route for that network.

Free Firewall/Network/Systems Support-

http://firewalls.ath.cx:8080