[Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 482
  • Last Modified:

What do i need on this PIX to allow telnet traffic inbound?


I just set up my home network - i have a cisco pix 506E that's connected (via a static IP) to a cable modem.  Internally, all my clients connect to the PIX, which is providing DHCP, etc.
Internal network is /24.

PIX internal address is
PIX external address is, for argument's sake,

Two things i want to be able to do:  

1) I need to allow FTP traffic inbound to a certain IP address (  Over time, i'm going to need to allow certain other traffic types to different internal IPs (for instance I may need web traffic on port 80 to go to, etc).

I put the following commands in the PIX, but for some reason the computer i was on suddenly lost internet connection (bizarre, but from another computer on another internet connection i was able to access the FTP server!).  The commands were:

static (inside,outside) netmask 0 0
conduit permit tcp host eq ftp-data any
conduit permit tcp host eq ftp any

2) I need to be able to ping the PIX from outside, and be able to ping outside IPs from inside the network.  I haven't tested pinging the PIX from outside the network, but i do know that i'm unable to ping outside addresses from inside the network.

Thanks everyone for your help in advance! Much appreciated!
I'm including the PIX config...

: Saved
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 56afLgSQrgMIa4xm encrypted
passwd 56afLgSQrgMIuOxm encrypted
hostname hostname
domain-name domain.local
clock timezone CST -6
clock summer-time CDT recurring
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
access-list inside_access_in permit ip any any
pager lines 24
logging timestamp
logging buffered informational
logging history warnings
logging queue 1024
logging device-id hostname
mtu outside 1500
mtu inside 1500
ip address outside
ip address inside
ip audit info action alarm
ip audit attack action alarm
no pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0 0
access-group inside_access_in in interface inside
rip inside passive version 2
route outside 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
http server enable
http inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet inside
telnet timeout 60
ssh outside
ssh timeout 5
console timeout 0
dhcpd address inside
dhcpd dns
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd enable inside
terminal width 80
: end

Open in new window

  • 5
  • 3
1 Solution
Mystical_IceAuthor Commented:
Just noticed i posted this to the Voice over IP section by mistake.

Moderator - if you could, please delete this question from that zone - it belongs in the other two zones i selected - "network routers" and "networking hardware firewalls"

Thanks - and sorry
You need to do port statics and not the one-one that you attempted.
>static (inside,outside) netmask 0 0

static (inside,outside) tcp interface ftp ftp netmask
static (inside,outside) tcp interface ftp-data ftp-data netmask
static (inside,outside) tcp interface www www netmask

Yes, use the keyword "interface" in the configuration for both statics and access list.

Then, create an access-list instead of conduits:
access-list outside_access_in permit icmp any any
access-list outside_access_in permit tcp any interface outside eq ftp
access-list outside_access_in permit tcp any interface outside eq ftp-data
access-list outside_access_in permit tcp any interface outside eq www

then apply the access-list
 access-group outside_access_in in interface outside

Mystical_IceAuthor Commented:
Much appreciated - that did the trick.
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Mystical_IceAuthor Commented:
One thing - still not able to ping OUT though...i can't ping google.com, can't ping,, etc.
try a conduit
conduit permit icmp any any
Mystical_IceAuthor Commented:
still no go :(
And this entry is in the acl?
access-list outside_access_in permit icmp any any

May sound counter-intuitive, but try this:
 no access-group inside_access_in in interface inside

Mystical_IceAuthor Commented:
actually i take it back; when i tested it last i was on a different connection - d'oh...

working great.

curious though, why would removing that access-group from the inside interface have fixed it?

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now