08-16-2011 01:59 AM - edited 03-11-2019 02:12 PM
Hello,
I try to setup a ASA5510, but without success.
Actually, I have Cisco1800(192.168.96.1/21) from my ISP connected to a cisco 3825 (via port with IP 192.168.96.2) all is working good.
Now I want to insert a asa firewall between ISP router and 3825.
For that, I tried a more simple config :
ISProuter (192.168.96.1/21) ---- ASA outside port(192.168.96.2/255.255.255.248) ASA INSIDE port (192.168.100.1/255.255.255.0) --- a pc with IP 192.168.100.2, netsmask 255.255.255.0, gateway 192.168.100.1
From my ASA, I can ping 192.168.96.1. but a "ping INSIDE 192.168.96.1" fail
from py pc, can ping 192.168.100.1, but not 192.168.96.1
What is missing ?
Thx
Here, my ASA config :
ASA Version 7.0(8)
!
hostname ciscoasa
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
dns-guard
!
interface Ethernet0/0
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet0/1
nameif OUTSIDE
security-level 100
ip address 192.168.96.2 255.255.255.248
!
interface Ethernet0/2
nameif INSIDE
security-level 100
ip address 192.168.100.1 255.255.255.0
!
interface Management0/0
nameif management
security-level 100
ip address 192.168.1.1 255.255.255.0
management-only
!
ftp mode passive
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
access-list OUTSIDE_access_in extended permit ip any any
access-list OUTSIDE_access_in extended permit icmp any any
access-list INSIDE_access_out extended permit ip any any
access-list INSIDE_access_out extended permit icmp any any
access-list OUTSIDE_access_out extended permit ip any any
access-list OUTSIDE_access_out extended permit icmp any any
access-list INSIDE_access_in extended permit ip any any
access-list INSIDE_access_in extended permit icmp any any
pager lines 24
logging asdm informational
mtu OUTSIDE 1500
mtu INSIDE 1500
mtu management 1500
asdm image disk0:/asdm-508.bin
no asdm history enable
arp timeout 14400
access-group OUTSIDE_access_in in interface OUTSIDE
access-group OUTSIDE_access_out out interface OUTSIDE
access-group INSIDE_access_in in interface INSIDE
access-group INSIDE_access_out out interface INSIDE
route OUTSIDE 0.0.0.0 0.0.0.0 192.168.96.1 1
route INSIDE 192.168.99.0 255.255.255.0 192.168.96.18 1
route INSIDE 192.168.103.0 255.255.255.0 192.168.96.18 1
route INSIDE 192.168.102.0 255.255.255.0 192.168.96.18 1
route INSIDE 192.168.101.0 255.255.255.0 192.168.96.18 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
timeout mgcp-pat 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
http server enable
http 192.168.100.65 255.255.255.255 OUTSIDE
http 192.168.1.0 255.255.255.0 management
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh 192.168.100.65 255.255.255.255 OUTSIDE
ssh timeout 5
console timeout 0
dhcpd address 192.168.1.2-192.168.1.254 management
dhcpd lease 3600
dhcpd ping_timeout 50
dhcpd enable management
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map global_policy
class inspection_default
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
!
service-policy global_policy global
08-16-2011 03:01 AM
Hi,
You are missing the following nats:
nat (inside) 1 0.0.0.0 0.0.0.0
global (outside) 1 interface
Try it and ler me know.
-Varun
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide