Telnet access to PIX

[jdl508]

This will seem like an easy one I guess.
I am finding out that telnet is a little harder to setup on the pix rather than a router. After reading the docs it seems like you need to set up ipsec on the int you want to tlnet into. so far my config is
telnet 192.168.1.0 255.255.255.0 outside

this should allow me to telnet in from any address on the 192.168.1.0 network right? wrong I'm missing something. my config is as follows

PIX Version 6.1(1)
nameif ethernet0 outside security0
nameif ethernet1 dmz1 security99
nameif ethernet2 dmz2 security50
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 1720
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
names
pager lines 24
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto
mtu outside 1500
mtu dmz1 1500
mtu dmz2 1500
ip address outside 192.168.1.x 255.255.255.0
ip address dmz1 10.1.1.x 255.255.255.0
ip address dmz2 10.2.2.x 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
conduit permit icmp any any
route outside 0.0.0.0 0.0.0.0 192.168.1.x 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h323 0:05:00 si
p 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
no sysopt route dnat
telnet 192.168.1.0 255.255.255.0 outside
telnet 10.1.1.0 255.255.255.0 dmz1
telnet 10.2.2.0 255.255.255.0 dmz2
telnet timeout 5
ssh timeout 5
terminal width 80
Cryptochecksum:8ec2ce22ef7ca1b9e89b954ca5b556f2
: end

thanks for the help
jon

 

[yizhar]

HI.

Yes, adding telnet access not from inside isn't easy.

Option 1:
Use SSH instead. Much easier to setup.


Option 2 (not recommended unless you must or you have configured vpn client for other purposes):

Configure a VPN client access to the pix.
Configure an access-list to encript traffic to the pix own interface that is facing your client (the outside address in most cases, the dmz address in your case).
Permit telnet to the ip local pool of the vpn clients.

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[jdl508]

Thanks Yizhar! After reading your reply I'm prob going to try and get ssh up and running, I don't like the idea of needing a client but I guess it's definitely more secure. I also talked with cisco on the phone and they said there was NO way to telnet into the outside int which is what I wanted to do from the router. thanks again
jon

 

[yizhar]

HI.

Another option is to telnet to a specific host in the "inside", and use it as a telnet proxy.

However this is not recommended for obvious security reasons.

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[RishMaster]

Yizhar,

What would be the command lines to do option two? In a non-dmz setup.

 

[PeterS]

Allowing a person whose only access is to the outside interface of the PIX (i.e. potentially the entire Internet!) to telnet into the firewall seems unwise. IP spoofing is too easy, and passwords often can be lost, stolen, or guessed.
I recognize the convenience, but you shouldn't need to change the configuration very often.

 

[jdl508]

I just wanted to intitally turn on telnet because the pix is in a rack and I dont have a laptop to console into it however now that I see how difficult it is I took the pix out of the rack until the config's are complete and working

thanks
jon