site2site distance-VPN and access-PIX - no way?

Similar Questions

• SSL VPN and access to computers by computer name

  I have a SonicWall TZ 205 running SonicOS Enhanced 5.9.1.0 firmware - 22o. It seems that I have things to work except solve computers by computer name. Since the client SSL VPN Extender I can ping machines, I can reach their actions through \\192.168.1.12\myshare for example but not of \\mycomputername\myshare. I tried enabling NetBIOS settings but still does not. Thoughts please.

  Thank you

  OK so in this case you can resolve names of machine by completing the "Wins servers" section in the same pop-up down (if you have a wins server).

  Often the DNS servers are also the wins servers.

  If you don't have a wins server, then will not work without creating files on each machine that needs to resolve the name of the host computer.

  Technical Net Bios is not a routable protocol

• Allow VPN users access a VLAN different

  I have an ASA 5505.  I have configured remote access VPN so that users can connect to the VPN and access my main VIRTUAL local network (inside).  I want to set so that when a user s in VPN, they are permitted access only to the CCV vlan (Vlan 2) as seen in my configuration.  Please note that there is also a VPN LAN LAN 2, which has been set up as well.

  What Miss me?

  !
  interface Ethernet0/0
  switchport access vlan 4
  !
  interface Ethernet0/1
  !
  interface Ethernet0/2
  !
  interface Ethernet0/3
  !
  interface Ethernet0/4
  !
  interface Ethernet0/5
  !
  interface Ethernet0/6
  switchport access vlan 2
  !
  interface Ethernet0/7
  switchport access vlan 2
  !
  interface Vlan1
  nameif inside
  security-level 100
  IP 10.240.0.1 255.255.0.0
  !
  interface Vlan2
  prior to interface Vlan1
  nameif HVAC
  security-level 100
  IP address 172.16.128.1 255.255.255.0
  !
  interface Vlan4
  nameif outside
  security-level 0
  IP address 12.x.x.x 255.255.255.0
  !
  passive FTP mode
  IP 10.240.0.0 allow Access - list extended CDEO 255.255.0.0 10.0.0.0 255.0.0.0
  IP 10.240.0.0 allow Access - list extended sheep 255.255.0.0 10.0.0.0 255.0.0.0
  IP 10.240.0.0 allow Access - list extended sheep 255.255.0.0 172.16.129.0 255.255
  . 255.0
  IP 10.102.229.0 allow Access - list extended sheep 255.255.255.0 172.16.129.0 255
  . 255.255.0
  IP 172.16.129.0 allow Access - list extended sheep 255.255.255.0 10.102.229.0 255
  . 255.255.0
  access-list sheep extended ip 172.16.128.0 allow 255.255.255.0 172.16.129.0 255
  . 255.255.0
  IP 172.16.129.0 allow Access - list extended sheep 255.255.255.0 172.16.128.0 255
  . 255.255.0
  list of inbound icmp permitted access extended throughout entire echo response
  list of extended inbound icmp permitted access any source-quench any
  list of extended all inbound icmp permitted access all inaccessible
  access list entering permit icmp any once extended beyond
  coming out to the one permitted all ip extended access list
  standard vpn access list allows 10.240.0.0 255.255.0.0
  standard vpn access list allows 10.102.229.0 255.255.255.0
  list of access allowed standard vpn 172.16.128.0 255.255.255.0
  pager lines 24
  asdm of logging of information
  Within 1500 MTU
  Outside 1500 MTU
  MTU 1500 HVAC
  IP local pool 172.16.129.1 - 172.16.129.5 mask 255.255.255.0 shhfvpnpool
  ICMP unreachable rate-limit 1 burst-size 1
  don't allow no asdm history
  ARP timeout 14400
  Global 1 interface (outside)
  NAT (inside) 0 access-list sheep
  NAT (inside) 1 0.0.0.0 0.0.0.0
  Access-group out on the interface inside
  Access-group interface incoming outside
  Route outside 0.0.0.0 0.0.0.0 12.x.x.x 1
  dynamic-access-policy-registration DfltAccessPolicy
  the ssh LOCAL console AAA authentication
  No snmp server location
  No snmp Server contact
  Server enable SNMP traps snmp authentication linkup, linkdown cold start
  Crypto ipsec transform-set esp - esp-sha-hmac hand
  Crypto ipsec transform-set esp - esp-md5-hmac RIGHT
  life crypto ipsec security association seconds 28800
  Crypto ipsec kilobytes of life - safety 4608000 association
  Crypto-map dynamic dynmap 10 transform-set RIGHT
  life together - the association of security crypto dynamic-map dynmap 10 28800 seconds
  Crypto-map dynamic dynmap 10 kilobytes of life together - the association of safety 4608000
  Crypto-map dynamic dynmap 10 the value reverse-road
  CDEOVPN 35 crypto card matches the address CDEO
  CDEOVPN 35 crypto map set peer 64.x.x.x
  card crypto CDEOVPN 35 the transform-set hand value
  map CDEOVPN 100-isakmp ipsec crypto dynamic dynmap
  CDEOVPN interface card crypto outside
  crypto isakmp identity address
  crypto ISAKMP allow outside
  crypto ISAKMP policy 20
  preshared authentication
  the Encryption
  sha hash
  Group 1
  life 86400
  crypto ISAKMP policy 30
  preshared authentication
  the Encryption
  md5 hash
  Group 2
  life 86400

  Console timeout 0
  management-access inside

  a basic threat threat detection
  Statistics-list of access threat detection
  no statistical threat detection tcp-interception
  attributes of Group Policy DfltGrpPolicy
  VPN-idle-timeout no
  internal group shhf strategy
  attributes of shhf group policy
  VPN-idle-timeout 30
  VPN-session-timeout 1440
  VPN-filter no
  Protocol-tunnel-VPN IPSec
  Split-tunnel-policy tunnelspecified
  Split-tunnel-network-list value vpn

  tunnel-group 64.x.x.x type ipsec-l2l
  64.x.x.x group tunnel ipsec-attributes
  pre-shared key *.
  tunnel-group shhf type remote access
  tunnel-group shhf General attributes
  address shhfvpnpool pool
  strategy-group-by default shhf
  shhf group tunnel ipsec-attributes
  pre-shared key *.
  tunnel-group vpnclient type remote access
  !
  class-map inspection_default
  match default-inspection-traffic
  !
  !
  type of policy-card inspect dns preset_dns_map
  parameters
  maximum message length automatic of customer
  message-length maximum 512
  Policy-map global_policy
  class inspection_default
  inspect the preset_dns_map dns
  inspect the ftp
  inspect h323 h225
  inspect the h323 ras
  inspect the rsh
  inspect the rtsp
  inspect esmtp
  inspect sqlnet
  inspect the skinny
  inspect sunrpc
  inspect xdmcp
  inspect the sip
  inspect the netbios
  inspect the tftp
  Review the ip options
  !
  global service-policy global_policy
  context of prompt hostname
  no remote anonymous reporting call
  Cryptochecksum:1cbd55e987f9b41cd2ebcb320fa2e3b2
  : end

  This route to be applied on the switch, if your port eth0/7 on SAA is connected to a switch of later3.

  "Route ip 172.16.129.0 255.255.255.0 172.16.128.1.

  So, don't worry on this route, if you can not apply on the SAA.

  So are you saying that a PC is directly connected to eth0/7 on the SAA.

  What is the IP address, mask and gateway address on the PC connected on eth0/7?

  The trace package seems good.

• PIX - PIX VPN and Client VPN - cannot access core network

  I hub and spoke PIX and a VPN Client that connects to speak it PIX, much the same as the example configuration here: -.

  http://www.Cisco.com/en/us/products/HW/vpndevc/ps2030/products_configuration_example09186a00800948b8.shtml

  This example shows the client VPN access to the network behind PIX RADIUS. I want the client to also be able to access the central network, i.e. the client connects to the pix speaks via vpn, and traffic is routed through the vpn to PIX - PIX to the central site.

  How this would change the configuration contained in the example?

  See you soon,.

  Jon

  You can not do this, the PIX cannot route a package back on the same interface, it is entered in the. The only way to do that is to have the client connect to the hub PIX, but then they would not be able to get to the network behind PIX distance either.

  Or that the customer would connect on a different interface in the PIX of distance, but this would mean another connection ISP on this PIX. Example of config is here: http://www.cisco.com/warp/public/110/client-pixhub.html

• Site to Site VPN and remote access on PIX 6.3 (3)

  Hello

  I have a vpn site-to site to remote access configured on the pix device. Everything works like a charm until I decide to perform authentication of the local client for remote vpn clients using the same card encryption from site to site. Thus, the tunnel from site to site is broken because that is trying to authenticate the local user.

  Is it possible to use the authentication of the remote local user for vpn clients on PIX without breaking other tunnels that use the same cryptomap?

  If the answer is to use separate crypro card so how can I assign the other encryption to use outside of the interface card, if only a single encryption card can be assigned to any given interface?

  When you configure the isakmp key, use the command

  ISAKMP KeyString keys by the peer-address [mask netmask] [No.-xauth] [No.-config-mode]

  No.-xauth will tell the isakmp won't the isakmp xauth for L2L and non-config-mode does not distribute the ip address of the peer L2L.

  Let us know if it works

  -Vikas

• L2l VPN and remote access VPN

  Hello

  I have 2 Cisco Pix (Pix1, Pix2) 515E (8.0.4). Between these devices exist VPN L2L, which are configured on the external interfaces. On Pix2 I configured remote access VPN on the external interface, too.

  Is it possible to achieve LAN behind Pix1, by using remote access VPN on Pix2 then VPN L2L?

  I don't want to set up remote access on Pix1.

  Thank you very much.

  Kind regards

  Vladislav

  NAT (outside) 1 140.40.30.0 255.255.255.0 (PAT for RA vpn to access the internet if you complete tunnel)

  It is simply because I have configured tunnel RA as complete tunnel instead of split, nat (outside) 1 at the RA 140.40.30.0 pool have internet access through your firewall ASA_SITE_B and translate with global ID 1 who is your external interface of the firewall SA_SITE_B. This has nothing to do with what you are trying to accomplish, but I posted it because it was part of the very common scenario. There are some example PIX 6.3 cases where you will need split tunnel so that RA users have internet access not passing not through the encrypted tunnel code 6.0 does not feature of intra-interface support but 7.x above is of the code. Other examples are that some people configure split RA RA user tunnel will have access to their local resources in their homes as the printers network etc...

  It is therefore, I need to translate 172.27.1.0/24 RA pool?

  No there is no address translation in place in this scenario to work and you don't need to translate something too long, there is no of networks that overlap in one of the SITES u do not need to translate, this scenario is completely free sheep as you access lists free of nat in two firewalls for networks involved in communication in tunnels ASA_SITE_B.

  Because I want to see IP addresses from PIX_SITE_A to 172.27.1.0/24, not 140.40.30.0/24. Is it possible to do it this way?

  Im not clear on this issue, but if I think what it means, it's possible but you need to have political NATing but I think this will make complicated setup, I would say to make this as simple as possible.

  Concerning

  All helpful PLS rate valid if it helped

• AnyConnect VPN and LAN access

  When remote users to connect to the Cisco ASA VPN and authenticate with Cisco AnyConnect client, they then full access to the environment internal of LAN of business as if they were sitting at their desks in the Office of the Corporation.

  Right?

  After that the remote client authenticates to the AnyConnect VPN, it is sensible to then run remote users of traffic through the corporate firewall (outside to inside) before allowing LAN access full corporate?

  Remote_User - vpn - ANYCONNECT-(outside) (inside) firewall - CORP_LAN

  Thank you

  Frank

  Hello

  Yes, by default, all traffic will be sent through the tunnel.

  If there are users VPN shouldn't be able to reach the resources, you need to establish rules for access to it. The best way to do this is by using VPN filter.

• VPN list and access

  Hello

  I have a router Cisco SOHO 97 and I set up VPN to access through VPN client.

  There is no problem: VPN Client Connection--> OK, access to my network--> OK

  If I activate the IOS with CRTS Firewall: VPN Client Connection--> OK, but I can't access my network.

  This line is added when I activate the firewall:

  inspect the name myfw cuseeme timeout IP 3600

  inspect the IP name myfw ftp queue time 3600

  inspect the name myfw rcmd timeout IP 3600

  inspect the name myfw realaudio timeout IP 3600

  inspect the name myfw smtp timeout IP 3600

  inspect the IP name myfw tftp timeout 30

  inspect the IP name myfw udp timeout 15

  inspect the name myfw timeout tcp IP 3600

  inspect the name myfw timeout h323 IP 3600

  ------

  interface Dialer1

  .....

  IP access-group 111 to

  inspect the myfw over IP

  ...

  --------------------------

  access-list 111 allow a whole icmp administratively prohibited

  access-list 111 permit icmp any any echo

  access-list 111 permit icmp any any echo response

  access-list 111 permit icmp any a package-too-big

  access-list 111 permit icmp any one time exceed

  access-list 111 allow all unreachable icmp

  access-list 111 permit udp any eq bootps any eq bootpc

  access-list 111 permit udp any eq bootps any eq bootps

  access-list 111 permit udp any eq field all

  access-list 111 allow esp a whole

  access-list 111 permit udp any any eq isakmp

  access-list 111 permit udp any any eq 10000

  access list 111 permit tcp any any eq 1723

  access list 111 permit tcp any any eq 139

  access-list 111 permit udp any any eq netbios-ns

  access-list 111 permit udp any any eq netbios-dgm

  access-list 111 allow accord a

  111 refuse a whole ip access-list

  (1) when I use ip only inspect there is no problem, the VPN connection working well.

  (2) if I use the access list, the network is inaccessible by VPN

  I have enabled ipsec with this list of access permit udp any any eq isakmp

  Access list who should I add?

  Thanks for your help

  You must allow the form encypted traffic (which you did with the ESP and lists access UDP/500) and the unencrypted form of traffic (Yes, really).

  This is because the access list turned twice to the IPsec packets. The arives package in the interface as an IPsec packet, pass the LCD and is decrypted in the router. At this point, the router it back on the incoming interface to be treated accordingly. This means however that the decrypted packet is then run through the ACL check again.

  For VPN clients, add a line to ACL111 that says:

  > allow ip access-list 111

  It is the way that routers have always worked. There was a bug to change this behavior for quite a while now, but unfortunately would require a major change in the way in which the IPSec packets are handled internally in the router, so it's quite a difficult solution. Bug ID is CSCdz54626 (regular incoming ACL is treated twice for IPSec traffic).

  If you fear that it is a security risk, then don't be. If someone spoofs a bunch to look like it came from your VPN address pool, the first thing that would make the router is to recognize that this package have been encrypted. Because it is not, the router will drop the packet immediately.

• Site to Site and together on ASA 5505 VPN remote access

  Hello

  I tried to set up a VPN Site again on an ASA5505 where there already is a VPN remote on it.

  After you add the new configuration lines, I received the following message when I debug:

  04 Nov 07:06:06 [IKEv1]: group = , IP = , error QM WSF (P2 struct & 0xd91a4d10, mess id 0xeac05ec0).

  04 Nov 07:04:36 [IKEv1]: group = , IP = , peer of drop table Correlator has failed, no match!

  Someone knows what's the problem? And what to change in the config?

  Thanks in advance,

  Ruben

  Hello

  If the ASA had a remote access VPN and you add a new Site-to-Site you must make sure that the priority for the card encryption is weaker for the new Site-to - added Site.This is because otherwise traffic will always try to match the access tunnel at distance. You can check it with the command "sh run card cry"

  Federico.

• Another problem with the configuration of Cisco VPN Client access VPN Site2site

  We have a Cisco ASA 5505 at our CORP. branch I configured the VPN Site2Site to our COLO with a Juniper SRX220h, to another site works well, but when users access the home Cisco VPN client, they cannot ping or SSH through the Site2Site.  JTACS contacted and they said it is not on their end, so I tried to contact Cisco TAC, no support.  So here I am today, after for the 3 days (including Friday of last week) of searching the Internet for more than 6 hours per day and try different examples of other users. NO LUCK. The VPN client shows the route secure 10.1.0.0

  Sorry to post this, but I'm frustrated and boss breathing down my neck to complete it.

  CORP netowrk 192.168.1.0

  IP VPN 192.168.12.0 pool

  Colo 10.1.0.0 internal ip address

  Also, here's an example of my config ASA

  : Saved

  :

  ASA Version 8.2 (1)

  !

  hostname lwchsasa

  names of

  name 10.1.0.1 colo

  !

  interface Vlan1

  nameif inside

  security-level 100

  IP 192.168.1.1 255.255.255.0

  !

  interface Vlan2

  backup interface Vlan12

  nameif outside_pri

  security-level 0

  IP 64.20.30.170 255.255.255.248

  !

  interface Vlan12

  nameif backup

  security-level 0

  IP 173.165.159.241 255.255.255.248

  !

  interface Ethernet0/0

  switchport access vlan 2

  !

  interface Ethernet0/1

  switchport access vlan 12

  !

  interface Ethernet0/2

  !

  interface Ethernet0/3

  !

  interface Ethernet0/4

  !

  interface Ethernet0/5

  !

  interface Ethernet0/6

  !

  interface Ethernet0/7

  !

  passive FTP mode

  permit same-security-traffic inter-interface

  permit same-security-traffic intra-interface

  object-group network NY

  object-network 192.168.100.0 255.255.255.0

  BSRO-3387 tcp service object-group

  port-object eq 3387

  BSRO-3388 tcp service object-group

  port-object eq 3388

  BSRO-3389 tcp service object-group

  EQ port 3389 object

  object-group service tcp OpenAtrium

  port-object eq 8100

  object-group service Proxy tcp

  port-object eq 982

  VOIP10K - 20K udp service object-group

  10000 20000 object-port Beach

  the clientvpn object-group network

  object-network 192.168.12.0 255.255.255.0

  APEX-SSL tcp service object-group

  Description of Apex Dashboard Service

  port-object eq 8586

  object-group network CHS-Colo

  object-network 10.1.0.0 255.255.255.0

  the DM_INLINE_NETWORK_1 object-group network

  object-network 192.168.1.0 255.255.255.0

  host of the object-Network 64.20.30.170

  object-group service DM_INLINE_SERVICE_1

  the purpose of the ip service

  ICMP service object

  service-object icmp traceroute

  the purpose of the service tcp - udp eq www

  the tcp eq ftp service object

  the purpose of the tcp eq ftp service - data

  the eq sqlnet tcp service object

  EQ-ssh tcp service object

  the purpose of the service udp eq www

  the eq tftp udp service object

  object-group service DM_INLINE_SERVICE_2

  the purpose of the ip service

  ICMP service object

  EQ-ssh tcp service object

  inside_nat0_outbound to access ip 192.168.1.0 scope list allow 255.255.255.0 clientvpn object-group

  inside_nat0_outbound to access ip 192.168.1.0 scope list allow 255.255.255.0 object-group NY

  inside_nat0_outbound to access ip 192.168.1.0 scope list allow 255.255.255.0 object-group CHS-Colo

  inside_nat0_outbound list of allowed ip extended access any 192.168.12.0 255.255.255.0

  outside_pri_1_cryptomap to access ip 192.168.1.0 scope list allow 255.255.255.0 object-group NY

  outside_pri_access_in list extended access permit tcp any interface outside_pri eq www

  outside_pri_access_in list extended access permit tcp any outside_pri eq https interface

  outside_pri_access_in list extended access permit tcp any interface outside_pri eq 8100

  outside_pri_access_in list extended access permit tcp any outside_pri eq idle ssh interface

  outside_pri_access_in list extended access permit icmp any any echo response

  outside_pri_access_in list extended access permit icmp any any source-quench

  outside_pri_access_in list extended access allow all unreachable icmp

  outside_pri_access_in list extended access permit icmp any one time exceed

  outside_pri_access_in list extended access permit tcp any 64.20.30.168 255.255.255.248 eq 8586

  levelwingVPN_splitTunnelAcl list standard access allowed 192.168.1.0 255.255.255.0

  levelwingVPN_splitTunnelAcl list standard access allowed 10.1.0.0 255.255.255.0

  outside_pri_cryptomap to access ip 192.168.1.0 scope list allow 255.255.255.0 object-group CHS-Colo

  backup_nat0_outbound list extended access allowed object-group DM_INLINE_NETWORK_1 192.168.12.0 ip 255.255.255.0

  outside_pri_cryptomap_1 list extended access allow DM_INLINE_SERVICE_2 of object-group 192.168.1.0 255.255.255.0 10.1.0.0 255.255.255.0

  outside_19_cryptomap to access extended list ip 192.168.12.0 allow 255.255.255.0 10.1.0.0 255.255.255.0

  inside_nat0_outbound_1 to access ip 192.168.1.0 scope list allow 255.255.255.0 object-group CHS-Colo

  VPN-Corp-Colo extended access list permits object-group DM_INLINE_SERVICE_1 192.168.12.0 255.255.255.0 10.1.0.0 255.255.255.0

  Note to OUTSIDE-NAT0 NAT0 customer VPN remote site access-list

  OUTSIDE-NAT0 192.168.12.0 ip extended access list allow 255.255.255.0 10.1.0.0 255.255.255.0

  L2LVPN to access extended list ip 192.168.12.0 allow 255.255.255.0 10.1.0.0 255.255.255.0

  pager lines 24

  Enable logging

  debug logging in buffered memory

  exploitation forest asdm warnings

  record of the rate-limit unlimited level 4

  destination of exports flow inside 192.168.1.1 2055

  timeout-rate flow-export model 1

  Within 1500 MTU

  outside_pri MTU 1500

  backup of MTU 1500

  local pool LVCHSVPN 192.168.12.100 - 192.168.12.254 255.255.255.0 IP mask

  no failover

  ICMP unreachable rate-limit 100 burst-size 5

  ICMP allow any inside

  ICMP allow any outside_pri

  don't allow no asdm history

  ARP timeout 14400

  NAT-control

  interface of global (outside_pri) 1

  Global 1 interface (backup)

  NAT (inside) 0-list of access inside_nat0_outbound

  NAT (inside) 0 inside_nat0_outbound_1 list of outdoor access

  NAT (inside) 1 0.0.0.0 0.0.0.0

  NAT (outside_pri) 0-list of access OUTSIDE-NAT0

  backup_nat0_outbound (backup) NAT 0 access list

  static TCP (inside outside_pri) interface https 192.168.1.45 https netmask 255.255.255.255 dns

  static TCP (inside outside_pri) interface 192.168.1.45 www www netmask 255.255.255.255 dns

  static TCP (inside outside_pri) interface 8586 192.168.1.45 8586 netmask 255.255.255.255 dns

  static (inside, inside) tcp interface 8100 192.168.1.45 8100 netmask 255.255.255.255 dns

  Access-group outside_pri_access_in in the outside_pri interface

  Route 0.0.0.0 outside_pri 0.0.0.0 64.20.30.169 1 track 1

  Backup route 0.0.0.0 0.0.0.0 173.165.159.246 254

  Timeout xlate 03:00

  Conn Timeout 0:00:00 half-closed 0:30:00 udp icmp from 01:00 0:00:02

  Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00

  Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-0: 03:00 sip - disconnect 0:02:00

  Timeout sip-provisional-media 0:02:00 01:00 uauth uauth absolute inactivity from 01:00

  timeout tcp-proxy-reassembly 0:01:00

  dynamic-access-policy-registration DfltAccessPolicy

  AAA authentication enable LOCAL console

  AAA authentication http LOCAL console

  the ssh LOCAL console AAA authentication

  http server enable 981

  http 192.168.1.0 255.255.255.0 inside

  http 0.0.0.0 0.0.0.0 outside_pri

  http 0.0.0.0 0.0.0.0 backup

  SNMP server group Authentication_Only v3 auth

  SNMP-server host inside 192.168.1.47 survey community lwmedia version 2 c

  No snmp server location

  No snmp Server contact

  Server enable SNMP traps snmp authentication linkup, linkdown cold start

  Sysopt connection tcpmss 1200

  monitor SLA 123

  type echo protocol ipIcmpEcho 216.59.44.220 interface outside_pri

  Annex ALS life monitor 123 to always start-time now

  Crypto ipsec transform-set ESP-AES-256-SHA 256 - aes - esp esp-sha-hmac

  Crypto ipsec transform-set ESP-DES-SHA esp - esp-sha-hmac

  Crypto ipsec transform-set ESP-DES-MD5 esp - esp-md5-hmac

  Crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac

  Crypto ipsec transform-set ESP-3DES-MD5-esp-3des esp-md5-hmac

  Crypto ipsec transform-set ESP-AES-128-SHA aes - esp esp-sha-hmac

  Crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac

  Crypto ipsec transform-set ESP-AES-128-MD5-esp - aes esp-md5-hmac

  Crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac

  Crypto ipsec transform-set esp-3des-sha1 esp-3des esp-sha-hmac

  Crypto ipsec transform-set esp-SHA-ESP-3DES-3des esp-sha-hmac

  life crypto ipsec security association seconds 28800

  Crypto ipsec kilobytes of life - safety 4608000 association

  Crypto ipsec df - bit clear-df outside_pri

  crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 pfs Group1 set

  Crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 value transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA MD5-ESP-3DES ESP-DES-SHA ESP-DES-MD5

  card crypto outside_pri_map 1 match address outside_pri_1_cryptomap

  card crypto outside_pri_map 1 set pfs

  peer set card crypto outside_pri_map 1 50.75.217.246

  card crypto outside_pri_map 1 set of transformation-ESP-AES-256-MD5

  card crypto outside_pri_map 2 match address outside_pri_cryptomap

  peer set card crypto outside_pri_map 2 216.59.44.220

  card crypto outside_pri_map 2 the value transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA MD5-ESP-3DES ESP-DES-SHA ESP-DES-MD5

  86400 seconds, duration of life card crypto outside_pri_map 2 set security-association

  card crypto outside_pri_map 3 match address outside_pri_cryptomap_1

  peer set card crypto outside_pri_map 3 216.59.44.220

  outside_pri_map crypto map 3 the value transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA MD5-ESP-3DES ESP-DES-SHA ESP-DES-MD5

  outside_pri_map card crypto 65535-isakmp dynamic ipsec SYSTEM_DEFAULT_CRYPTO_MAP

  card crypto outside_pri_map interface outside_pri

  crypto isakmp identity address

  ISAKMP crypto enable outside_pri

  crypto ISAKMP policy 5

  preshared authentication

  3des encryption

  sha hash

  Group 2

  life 86400

  crypto ISAKMP policy 10

  preshared authentication

  the Encryption

  sha hash

  Group 2

  life 86400

  crypto ISAKMP policy 30

  preshared authentication

  aes-256 encryption

  md5 hash

  Group 2

  life 86400

  crypto ISAKMP policy 50

  preshared authentication

  aes encryption

  md5 hash

  Group 2

  life 86400

  !

  track 1 rtr 123 accessibility

  Telnet timeout 5

  SSH 192.168.1.0 255.255.255.0 inside

  SSH timeout 5

  Console timeout 0

  management-access inside

  dhcpd auto_config outside_pri

  !

  dhcpd address 192.168.1.51 - 192.168.1.245 inside

  dhcpd dns 8.8.8.8 8.8.4.4 interface inside

  rental contract interface 86400 dhcpd inside

  dhcpd field LM inside interface

  dhcpd allow inside

  !

  a basic threat threat detection

  statistical threat detection port

  Statistical threat detection Protocol

  Statistics-list of access threat detection

  a statistical threat detection host number rate 2

  no statistical threat detection tcp-interception

  WebVPN

  port 980

  allow inside

  Select outside_pri

  enable SVC

  attributes of Group Policy DfltGrpPolicy

  VPN-idle-timeout no

  Protocol-tunnel-VPN IPSec l2tp ipsec svc webvpn

  internal GroupPolicy2 group strategy

  attributes of Group Policy GroupPolicy2

  Protocol-tunnel-VPN IPSec svc

  internal levelwingVPN group policy

  attributes of the strategy of group levelwingVPN

  Protocol-tunnel-VPN IPSec svc webvpn

  Split-tunnel-policy tunnelspecified

  value of Split-tunnel-network-list levelwingVPN_splitTunnelAcl

  username password encrypted Z74.JN3DGMNlP0H2 privilege 0 aard

  aard attribute username

  VPN-group-policy levelwingVPN

  type of remote access service

  rcossentino 4UpCXRA6T2ysRRdE encrypted password username

  username rcossentino attributes

  VPN-group-policy levelwingVPN

  type of remote access service

  bcherok evwBWqKKwrlABAUp encrypted password username

  username bcherok attributes

  VPN-group-policy levelwingVPN

  type of remote access service

  rscott nIOnWcZCACUWjgaP encrypted password privilege 0 username

  rscott username attributes

  VPN-group-policy levelwingVPN

  sryan 47u/nJvfm6kprQDs password encrypted username

  sryan username attributes

  VPN-group-policy levelwingVPN

  type of nas-prompt service

  username, password cbruch a8R5NwL5Cz/LFzRm encrypted privilege 0

  username cbruch attributes

  VPN-group-policy levelwingVPN

  type of remote access service

  apellegrino yy2aM21dV/11h7fR password encrypted username

  username apellegrino attributes

  VPN-group-policy levelwingVPN

  type of remote access service

  username rtuttle encrypted password privilege 0 79ROD7fRw5C4.l5

  username rtuttle attributes

  VPN-group-policy levelwingVPN

  username privilege 15 encrypted password vJFHerTwBy8dRiyW levelwingadmin

  username password nbrothers Amjc/rm5PYhoysB5 encrypted privilege 0

  username nbrothers attributes

  VPN-group-policy levelwingVPN

  clong z.yb0Oc09oP3/mXV encrypted password username

  clong attributes username

  VPN-group-policy levelwingVPN

  type of remote access service

  username, password finance 9TxE6jWN/Di4eZ8w encrypted privilege 0

  username attributes finance

  VPN-group-policy levelwingVPN

  Protocol-tunnel-VPN IPSec l2tp ipsec svc webvpn

  type of remote access service

  IPSec-attributes tunnel-group DefaultL2LGroup

  Disable ISAKMP keepalive

  tunnel-group 50.75.217.246 type ipsec-l2l

  IPSec-attributes tunnel-group 50.75.217.246

  pre-shared-key *.

  Disable ISAKMP keepalive

  type tunnel-group levelwingVPN remote access

  tunnel-group levelwingVPN General-attributes

  address LVCHSVPN pool

  Group Policy - by default-levelwingVPN

  levelwingVPN group of tunnel ipsec-attributes

  pre-shared-key *.

  tunnel-group 216.59.44.221 type ipsec-l2l

  IPSec-attributes tunnel-group 216.59.44.221

  pre-shared-key *.

  tunnel-group 216.59.44.220 type ipsec-l2l

  IPSec-attributes tunnel-group 216.59.44.220

  pre-shared-key *.

  Disable ISAKMP keepalive

  !

  !

  !

  Policy-map global_policy

  !

  context of prompt hostname

  Cryptochecksum:ed7f4451c98151b759d24a7d4387935b

  : end

  Hello

  It seems to me that you've covered most of the things.

  You however not "said" Configuring VPN L2L that traffic between the pool of VPN and network camp should be in tunnel

  outside_pri_cryptomap to access extended list ip 192.168.12.0 allow 255.255.255.0 object-group CHS-Colo

  Although naturally the remote end must also the corresponding configurations for users of VPN clients be able to pass traffic to the site of the camp.

  -Jouni

• PIX-to-client VPN and how to reach on other interfaces systems

  Hi all

  I've implemented a Pix-to-Client VPN and it seems works ok.

  As you can see, customer gets the same inside the class address (192.168.100.x) so I can reach across systems.

  My questions are:

  If I give different subnet pool addresses, how can 1 I still reach inside systems?

  2 if I have other systems on these interfaces such dmz1 (192.168.10.0) dmz2 (192.168.20.0) how to get to these systems of the

  even the client vpn access?

  Concerning

  Alberto Brivio

  IP local pool vpnpool1 192.168.100.70 - 192.168.100.80

  access-list 102 permit ip 192.168.100.0 255.255.255.0 192.168.100.0 255.255.255.0

  NAT (inside) - 0 102 access list

  Permitted connection ipsec sysopt

  Crypto ipsec transform-set esp - esp-md5-hmac trmset1

  Crypto-map dynamic map2 10 set transform-set trmset1

  map map1 10 ipsec-isakmp crypto dynamic map2

  map1 outside crypto map interface

  ISAKMP allows outside

  ISAKMP identity address

  part of pre authentication ISAKMP policy 10

  encryption of ISAKMP policy 10

  ISAKMP policy 10 md5 hash

  10 2 ISAKMP policy group

  ISAKMP life duration strategy 10 86400

  vpngroup address vpnpool1 pool test

  vpngroup split tunnel 102 test

  vpngroup test 1800 idle time

  test vpngroup password *.

  It is generally preferable to use another range of IP addresses. The PIX will know that the VPN Client uses that vary and route it properly whitch is not the case when you are using the same IP range as the inside interface.

  To access another interface use the SHEEP (your ACL 102) access list which disables NAT between the VPN and the neworks to which you want to connect.

  Example of config:

  access-list allowed SHEEP Internalnet ISubnetMask VPN-pool 255.255.255.0 ip

  access-list allowed SHEEP DMZnet DMZSubnetMask VPN-pool 255.255.255.0 ip

  NAT (inside) 0 SHEEP

  AAA-server local LOCAL Protocol

  AAA authentication secure-http-client

  Permitted connection ipsec sysopt

  Crypto ipsec transform-set esp-3des esp-md5-hmac TRANS

  Crypto-map dynamic outside_dyn_map 20 game of transformation-TRANS

  card crypto 65535 REMOTE ipsec-isakmp dynamic outside_dyn_map

  REMOTE client authentication card crypto LOCAL

  interface card crypto remotely outside

  ISAKMP allows outside

  ISAKMP identity address

  ISAKMP nat-traversal 20

  part of pre authentication ISAKMP policy 10

  ISAKMP policy 10 3des encryption

  ISAKMP policy 10 md5 hash

  10 2 ISAKMP policy group

  ISAKMP life duration strategy 10 86400

  IP pool local VPNPool x.y.z.1 - x.y.z.254

  vpngroup VPNGroup address pool VPNPool

  vpngroup VPNGroup dns-server dns1 dns2

  vpngroup VPNGroup default-domain localdomain

  vpngroup idle 1800 VPNGroup-time

  vpngroup VPNGroup password grouppassword

  username, password vpnclient vpnclient-password

  sincerely

  Patrick

• remote VPN and vpn site to site vpn remote users unable to access the local network

  As per below config remote vpn and vpn site to site vpn remote users unable to access the local network please suggest me a required config

  The local 192.168.215.4 not able ping server IP this server connectivity remote vpn works fine but not able to ping to the local network vpn users.

  ASA Version 8.2 (2)
  !
  host name
  domain kunchevrolet
  activate r8xwsBuKsSP7kABz encrypted password
  r8xwsBuKsSP7kABz encrypted passwd
  names of
  !
  interface Ethernet0/0
  nameif outside
  security-level 0
  PPPoE client vpdn group dataone
  IP address pppoe
  !
  interface Ethernet0/1
  nameif inside
  security-level 50
  IP 192.168.215.2 255.255.255.0
  !
  interface Ethernet0/2
  nameif Internet
  security-level 0
  IP address dhcp setroute
  !
  interface Ethernet0/3
  Shutdown
  No nameif
  no level of security
  no ip address
  !
  interface Management0/0
  Shutdown
  No nameif
  no level of security
  no ip address
  management only
  !
  passive FTP mode
  clock timezone IST 5 30
  DNS server-group DefaultDNS
  domain kunchevrolet
  permit same-security-traffic intra-interface
  object-group network GM-DC-VPN-Gateway
  object-group, net-LAN
  access extensive list ip 192.168.215.0 sptnl allow 255.255.255.0 192.168.2.0 255.255.255.0
  192.168.215.0 IP Access-list extended sheep 255.255.255.0 allow 192.168.2.0 255.255.255.0
  tunnel of splitting allowed access list standard 192.168.215.0 255.255.255.0
  pager lines 24
  Enable logging
  asdm of logging of information
  Outside 1500 MTU
  Within 1500 MTU
  MTU 1500 Internet
  IP local pool VPN_Users 192.168.2.1 - 192.168.2.250 mask 255.255.255.0
  ICMP unreachable rate-limit 1 burst-size 1
  enable ASDM history
  ARP timeout 14400
  NAT-control
  Global 1 interface (outside)
  NAT (inside) 1 0.0.0.0 0.0.0.0
  Route outside 0.0.0.0 0.0.0.0 59.90.214.1 1
  Timeout xlate 03:00
  Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
  Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00
  Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-0: 03:00 sip - disconnect 0:02:00
  Timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
  timeout tcp-proxy-reassembly 0:01:00
  dynamic-access-policy-registration DfltAccessPolicy
  the ssh LOCAL console AAA authentication
  AAA authentication LOCAL telnet console
  AAA authentication http LOCAL console
  AAA authentication enable LOCAL console
  LOCAL AAA authentication serial console
  Enable http server
  x.x.x.x 255.255.255.252 out http
  http 192.168.215.0 255.255.255.252 inside
  http 192.168.215.0 255.255.255.0 inside
  No snmp server location
  No snmp Server contact
  Server enable SNMP traps snmp authentication linkup, linkdown cold start
  Crypto ipsec transform-set esp-3des esp-sha-hmac RIGHT
  life crypto ipsec security association seconds 28800
  Crypto ipsec kilobytes of life - safety 4608000 association
  Crypto-map dynamic dynmap 65500 transform-set RIGHT
  card crypto 10 VPN ipsec-isakmp dynamic dynmap
  card crypto VPN outside interface
  card crypto 10 ASA-01 set peer 221.135.138.130
  card crypto 10 ASA - 01 the transform-set RIGHT value
  crypto ISAKMP allow outside
  crypto ISAKMP policy 10
  preshared authentication
  3des encryption
  sha hash
  Group 2
  life 86400
  crypto ISAKMP policy 65535
  preshared authentication
  the Encryption
  sha hash
  Group 2
  lifetime 28800
  Telnet 192.168.215.0 255.255.255.0 inside
  Telnet timeout 5
  SSH 0.0.0.0 0.0.0.0 outdoors
  SSH timeout 5
  Console timeout 0
  management-access inside
  VPDN group dataone request dialout pppoe
  VPDN group dataone localname bb4027654187_scdrid
  VPDN group dataone ppp authentication chap
  VPDN username bb4027654187_scdrid password * local store
  interface for identifying DHCP-client Internet customer
  dhcpd dns 218.248.255.141 218.248.245.1
  !
  dhcpd address 192.168.215.11 - 192.168.215.254 inside
  dhcpd allow inside
  !
  a basic threat threat detection
  Statistics-list of access threat detection
  no statistical threat detection tcp-interception
  Des-sha1 encryption SSL
  WebVPN
  allow outside
  tunnel-group-list activate
  internal kun group policy
  kun group policy attributes
  VPN - connections 8
  Protocol-tunnel-VPN IPSec
  Split-tunnel-policy tunnelspecified
  Split-tunnel-network-list value split tunnel
  kunchevrolet value by default-field
  test P4ttSyrm33SV8TYp encrypted password username
  username kunauto password bSHrKTGl8PUbvus / encrypted privilege 15
  username kunauto attributes
  Strategy Group-VPN-kun
  Protocol-tunnel-VPN IPSec
  tunnel-group vpngroup type remote access
  tunnel-group vpngroup General attributes
  address pool VPN_Users
  Group Policy - by default-kun
  tunnel-group vpngroup webvpn-attributes
  the vpngroup group alias activation
  vpngroup group tunnel ipsec-attributes
  pre-shared key *.
  type tunnel-group test remote access
  tunnel-group x.x.x.x type ipsec-l2l
  tunnel-group ipsec-attributes x.x.x.x
  pre-shared key *.
  !
  class-map inspection_default
  match default-inspection-traffic
  !
  !
  type of policy-card inspect dns preset_dns_map
  parameters
  maximum message length automatic of customer
  message-length maximum 512
  Policy-map global_policy
  class inspection_default
  inspect the preset_dns_map dns
  inspect the ftp
  inspect h323 h225
  inspect the h323 ras
  Review the ip options
  inspect the netbios
  inspect the rsh
  inspect the rtsp
  inspect the skinny
  inspect esmtp
  inspect sqlnet
  inspect sunrpc
  inspect the tftp
  inspect the sip
  inspect xdmcp
  inspect the icmp
  !
  global service-policy global_policy
  context of prompt hostname
  call-home
  Profile of CiscoTAC-1
  no active account
  http https://tools.cisco.com/its/service/oddce/services/DDCEService destination address
  email address of destination [email protected] / * /
  destination-mode http transport
  Subscribe to alert-group diagnosis
  Subscribe to alert-group environment
  Subscribe to alert-group monthly periodic inventory
  monthly periodicals to subscribe to alert-group configuration
  daily periodic subscribe to alert-group telemetry
  Cryptochecksum:0d2497e1280e41ab3875e77c6b184cf8
  : end
  kunauto #.

  Hello

  Looking at the configuration, there is an access list this nat exemption: -.

  192.168.215.0 IP Access-list extended sheep 255.255.255.0 allow 192.168.2.0 255.255.255.0

  But it is not applied in the States of nat.

  Send the following command to the nat exemption to apply: -.

  NAT (inside) 0 access-list sheep

  Kind regards

  Dinesh Moudgil

  P.S. Please mark this message as 'Responded' If you find this information useful so that it brings goodness to other users of the community

• Installation of site to site VPN IPSec using PIX and ASA

  / * Style definitions * / table. MsoNormalTable {mso-style-name : « Table Normal » ; mso-tstyle-rowband-taille : 0 ; mso-tstyle-colband-taille : 0 ; mso-style-noshow:yes ; mso-style-priorité : 99 ; mso-style-qformat:yes ; mso-style-parent : » « ;" mso-rembourrage-alt : 0 à 5.4pt 0 à 5.4pt ; mso-para-margin : 0 ; mso-para-marge-bottom : .0001pt ; mso-pagination : widow-orphelin ; police-taille : 11.0pt ; famille de police : « Calibri », « sans-serif » ; mso-ascii-font-family : Calibri ; mso-ascii-theme-font : minor-latin ; mso-fareast-font-family : « Times New Roman » ; mso-fareast-theme-font : minor-fareast ; mso-hansi-font-family : Calibri ; mso-hansi-theme-font : minor-latin ; mso-bidi-font-family : « Times New Roman » ; mso-bidi-theme-font : minor-bidi ;}

  I am a site configuration to site IPSec VPN using a PIX515E to site A and ASA5520 to Site B.

  I have attached the lab diagram. Consider PIX and ASA are in default configuration, which means that nothing is configured on both devices.

  According to the scheme

  ASA5520

  External interface is the level of security 11.11.10.1/248 0

  The inside interface is 172.16.9.2/24 security level 100

  Default route is 0.0.0.0 0.0.0.0 11.11.10.2 1

  PIX515E

  External interface is the level of security 123.123.10.2/248 0

  The inside interface is 172.16.10.1/24 security level 100

  Default route is 0.0.0.0 0.0.0.0 123.123.10.1 1

  / * Style definitions * / table. MsoNormalTable {mso-style-name : « Table Normal » ; mso-tstyle-rowband-taille : 0 ; mso-tstyle-colband-taille : 0 ; mso-style-noshow:yes ; mso-style-priorité : 99 ; mso-style-qformat:yes ; mso-style-parent : » « ;" mso-rembourrage-alt : 0 à 5.4pt 0 à 5.4pt ; mso-para-margin : 0 ; mso-para-marge-bottom : .0001pt ; mso-pagination : widow-orphelin ; police-taille : 11.0pt ; famille de police : « Calibri », « sans-serif » ; mso-ascii-font-family : Calibri ; mso-ascii-theme-font : minor-latin ; mso-fareast-font-family : « Times New Roman » ; mso-fareast-theme-font : minor-fareast ; mso-hansi-font-family : Calibri ; mso-hansi-theme-font : minor-latin ; mso-bidi-font-family : « Times New Roman » ; mso-bidi-theme-font : minor-bidi ;}

  Could someone tell me how to set up this configuration? I tried but didn't workout. Here is the IKE protocol I have used.

  IKE information:

  IKE Encrytion OF

  MD5 authentication method

  Diffie Helman Group 2

  Failure to life

  IPSEC information:

  IPsec encryption OF

  MD5 authentication method

  Failure to life

  Please enter the following command

  on asa

  Sysopt connection permit VPN

  on pix not sure of the syntax, I think it is

  Permitted connection ipsec sysopt

  What we are trying to do here is basically allowing vpn opening ports

  Alternatively you can open udp 500 and esp (or port ip 50) out to in on the two firewalls

• CSA with the Client VPN and remote access

  Hello world!

  I have the folowing isue: I have to tune in to the CSA for a clinet it connects remote with VPN Client only. He should not be able to connect to any other network or lan or dial-up.

  No idea what the policy should change or tune?

  Thank you

  You can create an access network rule that depends on a State of the system. The State of the system can be defined to have a game of skill, which belongs to the range of VPN and the network access rule would declare that the client computer cannot act as a server on UDP/TCP ports when the State of the system is ensured.

  So, if the laptop is not connected to the VPN, it would not be able to act as a server for connections to all and will be locked out. You will need to create an exception for the IP address of the VPN server to your corporate offices and allow the CSA client opening these ports.

• VPN inside a PIX (General Questions)

  Hello

  I'm trying to implement a scenario of communication between a customer inside a pix that talks to a server on the outside. The customer must have an ipsec inside connection. I have the following config and a few questions I´d be very happy to get an answer for...

  Backup on the interface outside the security0 Server

  Client safety within 100 interface

  The client IP address is 200.200.212.194

  backup server address is 200.200.202.201

  I want to implement a VPN client connection to the inside interface, and therfore have implemented the following configuration.

  external IP 200.200.202.200 255.255.255.0

  IP address inside 200.200.212.193 255.255.255.192

  access-list 100 permit host 200.200.202.201 ip 10.3.3.0 255.255.255.0

  IP local pool privada 10.3.3.1 - 10.3.3.254

  Crypto ipsec transform-set esp-3des esp-sha-hmac RIGHT

  Crypto-map dynamic dynmap 10 transform-set RIGHT

  map mymap 10-isakmp ipsec crypto dynamic dynmap

  client configuration address map mymap crypto initiate

  client configuration address map mymap crypto answer

  mymap map crypto inside interface

  ISAKMP allows inside

  ISAKMP key * address 0.0.0.0 netmask 0.0.0.0

  ISAKMP identity address

  part of pre authentication ISAKMP policy 10

  ISAKMP policy 10 3des encryption

  ISAKMP policy 10 sha hash

  10 2 ISAKMP policy group

  ISAKMP life duration strategy 10 86400

  vpngroup address private pool PRIVADAGROUP

  PRIVADAGROUP vpngroup password *.

  vpngroup split tunnel 100 PRIVADAGROUP

  I have a few questions about this configuration maybe some kind soul able to respond.

  1. the VPN clients receive an address (10.3.3.1) for example through the IKE negotiation. When I ping my server from the client with the active VPN tunnel I assume the real package that passes through the wire has 10.3.3.1 a source address and a destination of 200.200.212.193 (endpoint the VPN and inside interface). Within IPSEC, the package is my real ip with a source 200.200.212.194 address (address of the real client) and a destination address of 200.200.202.201 (address of the backup server that I am trying to ping). If all this makes sense and is correct could you confirm the following point.

  2 when the PIX deencrypts the package and removes the IPSEC header I find myself with my IP packet of origin with a source 200.200.212.194 address (address of the real client) and a destination address of 200.200.202.201 (address of the backup server that I am trying to ping). I don't know if I need then the following configuration to allow the package to be transferred to the backup without NAT server:

  access-list allowed sheep host ip 200.200.212.194 255.255.255.0 200.200.202.0 255.255.255.0

  NAT (inside) 0 access-list sheep

  I was previously using the following configuration and it seemed to work but the more I think the less sense it seems to do as I´d wait for the SENATE to run on the dencypted package. I must be missing something or confused, or both.

  IP 10.3.3.0 allow Access-list sheep 255.255.255.0 200.200.202.0 255.255.255.0

  NAT (inside) 0 access-list sheep

  3. as a last and probably least I m pretty sure I don't have to line "isakmp key * address 0.0.0.0 netmask 0.0.0.0" when connecting with a VPN client software only. Somone can confirm that for me.

  I'm actually trying to get this to work remotely with someone else doing the actual work and we don't speak the same language.

  Any help to store my confused brain would be appreciated.

  1. No, it's the other way around. The real package that passes through the wire has the address IP of the PC (200.200.212.194) as a source. Within the IPSec packet is allocated 10.3.3.1 as source IP address. When the PIX decrypts the packet, the outer header is removed, and the package has a source of 10.3.3.1 as it is sent to your server on the outside. The external server will respond to 10.3.3.1 so it must be routed to the PIX for her to work.

  Think of this as the normal instance with the PC to the outside through the Internet. A package from of and sent to 10.3.3.1 would never do to the original PC. The encrypted IPSec packet always contains the VPN endpoints real IP source and destination addresses. The decrypted original deck contains allocated as source IP and the actual destination as destination (usually also a private address) computer.

  2. This should make more sense now that you know the answer to 1.

  3. you don't need that if you have a "vpngroup password xxxx" command. This command «isakmp key...» "If there is no specific vpngroup key, or someone connects with a different groupname.