Tom's Hardware > Forum > General Networking > Firewall > [cisco PIX 515e] problem ping from inside to outside

[cisco PIX 515e] problem ping from inside to outside

Forum General Networking : Firewall - [cisco PIX 515e] problem ping from inside to outside

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Ask the community Add a reply
Word :    Username :           
 
gondek   05-04-2006 at 04:01:28 PM

Hi everybody,

I have to configure a cisco PIX 515e

There are three interfaces

-Outside
-Inside
-DMZ (not yet configured)

For the moment, I just want to be able to ping internet IP from the hosts of my Inside interface.

Here is my configuration!!! What is it missing???

interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 dmz security50
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
fixup protocol dns maximum-length 512
.
.
fixup protocol tftp 69
names
access-list ping_acl permit icmp any any
pager lines 24
ip address outside xx.xxx.xx.2 255.255.255.224
ip address inside 192.168.1.1 255.255.255.0
ip address dmz 192.168.3.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
nat (inside) 1 192.168.1.0 255.255.255.0 0 0
static (inside,outside) 192.168.1.0 xx.xxx.xx.0 netmask 255.255.255.224 0 0
access-group ping_acl in interface inside
route outside 0.0.0.0 0.0.0.0 xx.xxx.xx.1 1




THANK YOU FOR YOUR HELP!!!

Add a reply
Sponsored Links
Register or log in to remove.
folken   05-23-2006 at 01:34:00 AM
- 0 +

shouldn't this line:
access-list ping_acl permit icmp any any

be:
access-list allow_ping permit icmp any any

Maybe it is different in the newer PIX os versions but I seem to recall it being allow_ping instead of ping_acl.

Reply to folken
pacman99   05-24-2006 at 02:37:16 PM
- 0 +

You need to have an access-list on the outside interface that allows the ICMP replies to come back into your network:

You can use the same..

access-group ping_acl in interface outside

Reply to pacman99
keshav   06-01-2006 at 10:01:43 AM
- 0 +

I see that you have not given global command.

This is needed for the inside traffic to be routed in internet.

add it and let me know how it goes.

Reply to keshav
keshav   06-01-2006 at 11:23:23 AM
- 0 +

global (outside) 1 interface

Reply to keshav
Jojes   06-05-2006 at 02:15:47 PM
- 0 +

Hi,

It is quite simple.

Steps are like this.

(1) Just create an access-list for permitting the IP to go outside.

(2) Next step is you need to enable ICMP echo-reply Inbound in your outside interface.

In your configuration, it would be :-

# access-list ping_acl permit ip any any
#access-group ping_acl in interface outside

It will work..

or if you want to enable ping for a single computer, you can replace the first command with

# access-list ping_acl permit ip 192.168.1.77 255.255.255.255 any

where 192.168.1.77 is the ip of the computer.


Also in your configuration

remove the line

# static (inside,outside) 192.168.1.0 xx.xxx.xx.0 netmask 255.255.255.224 0 0

and add

#global(outside) 1 interface

where all you internal hosts uses the outside interface address to access the external internet. This is the right way for that configuration.


Regards,

Jojes

Reply to Jojes
agarriz   06-16-2006 at 03:34:45 AM
- 0 +

I HAVE A SIMILAR PROBLEM WITH THE PIX I want to do ping to an Internet address on the eth of dmz or inside but not with himself .To help me?

What is wrong??

PIXIT# sh conf
: Saved
: Written by enable_15 at 22:10:06.994 UTC Thu Jun 15 2006
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 dmz security4
enable password XXXXXXXXX encrypted
passwd XXXXXXXX encrypted
hostname PIXIT
domain-name mydomain.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
name 0.0.0.0 lan
access-list inside_access_in permit ip interface inside interface dmz
access-list inside_access_in permit icmp interface inside interface dmz
access-list inside_access_in permit udp interface inside interface dmz
access-list inside_access_in permit tcp interface inside interface dmz
access-list dmz_access_in permit tcp interface dmz interface inside
access-list dmz_access_in permit udp interface dmz interface inside
access-list dmz_access_in permit icmp interface dmz interface inside
access-list dmz_access_in permit ip interface dmz interface inside
access-list ping_acl permit ip any any
access-list ping_acl permit icmp any any
access-list allow_ping permit icmp any any
pager lines 24
logging on
logging standby
icmp permit any outside
icmp permit any inside
icmp permit any dmz
mtu outside 1500
mtu inside 1500
mtu dmz 1500
ip address outside IPINTERNET 255.255.255.224
ip address inside 10.4.1.4 255.255.0.0
ip address dmz 192.168.1.11 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 10.5.0.0 255.255.0.0 inside
pdm location 10.0.0.0 255.255.0.0 inside
pdm location 192.168.0.0 255.255.0.0 inside
pdm history enable
arp timeout 14400
global (outside) 10 interface
global (dmz) 5 interface
static (inside,dmz) 10.0.0.0 10.0.0.0 netmask 255.255.0.0 0 0
static (inside,outside) 10.0.0.0 10.0.0.0 netmask 255.255.0.0 0 0
access-group ping_acl in interface outside
access-group inside_access_in in interface inside
access-group dmz_access_in in interface dmz
rip outside default version 1
rip inside default version 1
rip dmz default version 1
route outside lan lan 200.49.11.193 1
route inside 10.5.0.0 255.255.0.0 10.4.1.3 1
route inside 192.168.0.0 255.255.0.0 10.4.1.4 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
aaa authentication enable console LOCAL
aaa authentication serial console LOCAL
aaa authentication telnet console LOCAL
http server enable
http 10.4.0.0 255.255.0.0 inside
http 192.168.1.0 255.255.255.0 dmz
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet 10.4.0.0 255.255.0.0 inside
telnet 192.168.1.0 255.255.255.0 dmz
telnet timeout 5
ssh timeout 5
console timeout 0
username leon password XXXXXXX encrypted privilege 15
username polo password XXXXXXXXX encrypted privilege 15
terminal width 80
Cryptochecksum:4b08d8a59341c000a19b69cdc73e9fb8

Reply to agarriz
Jojes   06-20-2006 at 04:19:49 PM
- 0 +

Simple..

In you access list " ping_acl" , just permit icmp echo-reply.

the command will be like this :-


access-list ping_acl permit icmp any any echo-reply

it shud work

Regards,

Jojes

Reply to Jojes
agarriz   06-20-2006 at 11:25:36 PM
- 0 +

PIXTPS(config)# access-list ping_acl permit icmp any any echo-reply
PIXTPS(config)# write mem
Building configuration...
Cryptochecksum: bb3fd072 43a74908 55efe67c 19df1a77
[OK]
PIXTPS(config)# ping inside 192.168.1.5
192.168.1.5 NO response received -- 1000ms
192.168.1.5 NO response received -- 1000ms
192.168.1.5 NO response received -- 1000ms
PIXTPS(config)# ping inside 192.168.1.5
192.168.1.5 NO response received -- 1000ms
192.168.1.5 NO response received -- 1000ms
192.168.1.5 NO response received -- 1000ms
PIXTPS(config)#

:((( don't work

Reply to agarriz
Jojes   06-21-2006 at 01:58:27 PM
- 0 +

Oh.. you want to ping your local internal address only.

For this you need to enable Network Address Translation (NAT) for the respective address,, whether it is inside or DMZ interfaces mentioning different NAT ID.

Reply to Jojes
agarriz   06-21-2006 at 11:31:03 PM
- 0 +

to say to me like doing it?

thanks

Reply to agarriz
Bujji   11-22-2006 at 05:10:29 PM
- 0 +

Quote :

You need to have an access-list on the outside interface that allows the ICMP replies to come back into your network:

You can use the same..

access-group ping_acl in interface outside



I have to configure a pix 515E. I know nuts about it can anyone help me out with the configuration commands and how to deny the access to internet or outside interfece for a range of ip address in the internal network

Reply to Bujji
zillah   01-04-2007 at 06:53:16 PM
- 0 +

Quote :


static (inside,outside) 192.168.1.0 xx.xxx.xx.0 netmask 255.255.255.224 0 0


Since the 192.168.1.0 is your internal ip address, the format of the static mapping like this :
static (inside,outside) xx.xxx.xx.0 192.168.1.0 netmask 255.255.255.224 0 0

Reply to zillah
bukepards   12-28-2008 at 09:27:24 AM
- 0 +

I'm studying...

Reply to bukepards
Ask the community Add a reply
Tom's Hardware > Forum > General Networking > Firewall > [cisco PIX 515e] problem ping from inside to outside
Go to:

There are 1164 identified and unidentified users. To see the list of identified users, Click here.

Forum map
Bestofmedia Forum ©
2000-2009 Bestofmedia Group
Page generated in 0.426 seconds
Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them