%PIX-4-402106: Rec'd packet not an IPSEC packet.

515 running 7.2 Attempting to ssh to inside interface through a cisco vpnclient connection. I can successfully ssh to inside interface from a machine on the same physical/logical segment.

pix515# sh ssh Timeout: 5 minutes Version allowed: 2

0.0.0.0 0.0.0.0 pix-outside 0.0.0.0 0.0.0.0 pix-inside

...............

Linux vpnclient stat Client Type(s): Linux Running on: Linux 2.4.21-4.EL #1 Fri Oct 3 18:13:58 EDT 2003 i686 Config file directory: /etc/opt/cisco-vpnclient

VPN tunnel information. Client address: 192.168.221.2 Encryption: 168-bit 3-DES Authentication: HMAC-SHA IP Compression: None NAT passthrough is active on port UDP 10000 Local LAN Access is disabled

VPN traffic summary. Time connected: 0 day(s), 00:27.20 Bytes in: 260822 Bytes out: 214704 Packets encrypted: 2856 Packets decrypted: 2010 Packets bypassed: 4046 Packets discarded: 0

Configured routes. Secured Network Destination Netmask 192.168.220.0 255.255.255.0

.......................

client ssh messages: ssh_exchange_identification: read: Connection reset by peer

pix log message: %PIX-4-402106: Rec'd packet not an IPSEC packet. (ip) dest_addr=

192.168.220.1, src_addr= 192.168.221.2, prot= TCP
Reply to
lfnetworking
Loading thread data ...

I haven't studied 7.x. In 6.x, the only way to ssh from the outside through to the inside interface, is to configure a vpn as a "management vpn" and come in through that. The "management vpn" so created can -only- be used to access the PIX itself; I think it uses the other kind of IPSec tunnel (one that is *required* by the IPSec specifications not to be used to gateway packets.)

Reply to
Walter Roberson

try the command "management-access inside"

Reply to
Brian V

thanks brian!

Reply to
lfnetworking

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.