PIX from site to site VPN at the Juniper

Similar Questions

• PIX from Site to Site w / remote VPN Clients

  I posted accidentally this question in the wrong forum earlier today. I couldn't find a way to move it or delete it, so I apologize for the duplication.

  I set up a VPN site-to site between 2 Pix 506e. I have install the tunnle VPN using the VPN Wizard, and it seems to work fine.

  However, I also have users that VPN directly in the PIX via PPTP or a Cisco VPN client. These users are not able to access resources that are on the other end of the VPN tunnel. It seems that map ACL that triggers sending in the tunnel of the packages is not be matched, but I was not able to understand how to make this work correctly.

  PIX has a local subnet of 192.168.1.x/24. PIX B has a local subnet of 192.168.2.x/24. Traffic between these 2 subnets through the tunnel flow. However, when a person sets up a VPN on PIX B, they are also placed in the 192.168.2.x/24 subnet, but they are unable to access anything whatsoever in the 192.168.1.x/24 subnet. Is something like this? Config PIX B is attached. 

Any help you could offer would be greatly appreciated.

  Thank you

  -Steve

  This is not possible with Pix and 6.3 version of the code.

  If you are running 7.0 or higher on the Pix, so, yes it is possible. Please see the below URL for more configuration information. The feature you're looking for is called 'intra-interface.

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

  In addition, 7.0 and above are not supported on Pix 501, 506, and 520.

  Kind regards

  Arul

  * Please note all useful messages *.

• Site to site VPN with the VPN Client for both sites access?

  Current situation:

  Scenario is remote to the main office. Site IPSEC tunnel site (netscreen) remote in hand (506th pix). Cisco VPN Client of main office of remote access to users.

  It's that everything works perfectly.

  Problem:

  Now we want remote users who connect to the seat to also be able to access resources in the remote offices.

  This seems like it would be easy to implement, but I can't understand it.

  Thanks in advance.

  Rollo

  ----------

  #10.10.10.0 = Network1

  #10.10.11.0 = Network2

  #172.16.1.0 = vpn pool

  6.3 (4) version PIX

  access-list 101 permit ip 10.10.10.0 255.255.255.0 172.16.1.0 255.255.255.0

  access-list 101 permit ip 10.10.10.0 255.255.255.0 10.10.11.0 255.255.255.0

  splitTunnel 10.10.10.0 ip access list allow 255.255.255.0 any

  splitTunnel ip 10.10.11.0 access list allow 255.255.255.0 any

  access-list 115 permit ip any 172.16.1.0 255.255.255.0

  access-list 116 allow ip 10.10.10.0 255.255.255.0 10.10.11.0 255.255.255.0

  IP access-list 116 allow all 10.10.11.0 255.255.255.0

  access-list 116 allow ip 10.10.11.0 255.255.255.0 10.10.10.0 255.255.255.0

  ICMP allow all outside

  ICMP allow any inside

  Outside 1500 MTU

  Within 1500 MTU

  IP address outside 209.x.x.x 255.255.255.224

  IP address inside 10.10.10.1 255.255.255.0

  alarm action IP verification of information

  alarm action attack IP audit

  IP local pool 172.16.1.0 vpnpool - 172.16.1.50

  Global 1 interface (outside)

  Global (outside) 10 209.x.x.x 255.255.255.224

  (Inside) NAT 0-list of access 101

  NAT (inside) 10 10.10.10.0 255.255.255.0 0 0

  Access-group outside_access_in in interface outside

  Route outside 0.0.0.0 0.0.0.0 209.x.x.x 1

  Timeout xlate 01:00

  Timeout conn 01:00 half-closed 0:10:00 udp 0: CPP 02:00 0:10:00 01:00 h225

  H323 timeout 0:05:00 mgcp 0: sip from 05:00 0:30:00 sip_media 0:02:00

  Timeout, uauth 0:05:00 absolute

  enable floodguard

  Permitted connection ipsec sysopt

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

  crypto dynamic-map Clients_VPN-dynmap 10 transform-set RIGHT

  35 Myset1 ipsec-isakmp crypto map

  correspondence address 35 Myset1 map cryptographic 116

  card crypto Myset1 35 counterpart set x.x.x.x

  card crypto Myset1 35 set transform-set Myset1

  Myset1 card crypto ipsec 90-isakmp dynamic dynmap Clients_VPN

  client configuration address card crypto Myset1 launch

  client configuration address card crypto Myset1 answer

  interface Myset1 card crypto outside

  ISAKMP allows outside

  ISAKMP key * address x.x.x.x 255.255.255.255 netmask No.-xauth-no-config-mode

  ISAKMP identity address

  ISAKMP nat-traversal 20

  part of pre authentication ISAKMP policy 15

  ISAKMP policy 15 3des encryption

  ISAKMP policy 15 sha hash

  15 1 ISAKMP policy group

  ISAKMP duration strategy of life 15 28800

  part of pre authentication ISAKMP policy 20

  ISAKMP policy 20 3des encryption

  ISAKMP policy 20 chopping sha

  20 2 ISAKMP policy group

  ISAKMP duration strategy of life 20 3600

  part of pre authentication ISAKMP policy 25

  encryption of ISAKMP policy 25

  ISAKMP policy 25 md5 hash

  25 2 ISAKMP policy group

  ISAKMP living 25 3600 duration strategy

  part of pre authentication ISAKMP policy 30

  ISAKMP policy 30 aes-256 encryption

  ISAKMP policy 30 sha hash

  30 2 ISAKMP policy group

  ISAKMP duration strategy of life 30 86400

  vpngroup address vpnpool pool mygroup

  vpngroup dns-server dns1 dns2 mygroup

  vpngroup mygroup wins1 wins2 wins server

  vpngroup mygroup by default-domain mydomain

  vpngroup split splitTunnel tunnel mygroup

  vpngroup idle time 64000 mygroup

  mygroup vpngroup password *.

  Telnet timeout 5

  dhcpd lease 3600

  dhcpd ping_timeout 750

  dhcpd outside auto_config

  Hi Rollo,

  You can not be implemented for a simple reason, it is not supported on the version 6.x PIX. It relies on the PIX 7.x worm but 7.x is not supported on PIX 506. Thus, in a Word, it can be reached on a PIX 506. If you have an ASA, a PIX 515 running 7.x, a router or a hub as well, it can be reached.

  HTH,

  Please rate if this helps,

  Kind regards

  Kamal

• Failed to get site - site VPN to the top

  I have two PIX runing version 6.3 (3) and 7.1 (1). Here's my topology and attached config showing running configuration and debugs.

  (PC)172.16.10.10/24<-->172.16.10.1/24-PIX(6.3)--1.1.1.2/30---WAN(X-Over cable)---1.1.1.1/30--PIX (7.1)--10.10.10.1/24<--->10.10.10.10/24(PC)

  What Miss me?

  Thank you

  Moreover, it is the only thing that catches my attention from the 6.3 debugs you provided:

  ISAKMP (0): ITS been pre-shared key, using id ID_FQDN type authentication

  One thing you can try is to put both sides ISAKMP identities:

  address of ISAKMP identity (side 6.3)

  cry isakmp identity address (on the side of 7.x)

• Ports from Site to site behind another PIX

  Have a client who we are going to set up a site to site VPN. The remote site is behind another PIX firewall that has private inside IP addresses. Next to the static nat, which ports must be open in order to make a site to site?

  If the VPN tunnel ends on PIX - B, then PIX - A must be opened for the following ports (in two senses - incoming and outgoing).

  -The ESP protocol (that's the protocol 50)

  -Port UDP 500

  -UDP 4500 port

  Thus, orders ACLs on PIX - A will be:

  outside_ACL udp IP_of_SiteA-PIX IP_of_PIX-B eq 500 allowed access list

  outside_ACL list of permitted access eq of IP_of_PIX from IP_of_SiteA-PIX-B udp 4500

  outside_ACL list of permitted access esp IP_of_SiteA-PIX-IP_of_PIX-B

  That should do the trick.

• IPSEC VPN from Site to Site - NAT problem with address management

  Hi all

  I have two Cisco ASA 5505 performing of IPSEC Site to Site VPN. All traffic inside each firewall through the VPN tunnel and I have full connectivity. From site A, I can connect to the inside address of the ASA at the site B and launch of the ASDM or SSH, etc.

  The problem I have is when I'm logged on the ASA site B management traffic is given the external address. I created this as interesting traffic to get it to go through the VPN but I need to use the inside address of ASA B. The following is possible:

  • If I can make the ASA Site B to use inside interface as its address management (I already have management access to the inside Interface)
  • I have NAT can address external interfaces to Site B before moving through the VPN tunnel management traffic so that it appears to come from Site B inside the address
  • I can NAT VPN traffic as it appears in the Site A for management traffic to Site B on the right address.

  The problem is that my PRACTICE Please also come from this address and I need the application before being on an internal address to even if my CA.

  Thanks for any help.

  Ian

  Thanks, I understand what you are trying to achieve now.

  However, I think that I don't have good news for you. Unfortunately PEIE request can be initiated of the SAA within the interface, as there is no option to start the query from the inside interface. With other features of management such as AAA, logging, you have an option to specify what ASA desired originally to demand from interface, but CEP doesn't have this option.

  Here's how you can configure under the trustpoint crypto, but unfortunately by specifying the interface doesn't not part of option:

  http://www.Cisco.com/en/us/docs/security/ASA/asa84/command/reference/C5.html#wp2262210

• Redundancy of site to Site VPN

  Hello

  I have two ASA 5510 configured with tunnel from site to site. on both sides of the ASA 5510 I set up the links of redundancy (completed 2 ISP links) which works very well.

  Now, I need to configure site-to-site vpn for the help link.

  Please suggest me how to configure the redundancy of a site on both sites.

  Kind regards

  Ramanantsoa

  I don't know exactly the topology of your network, but it is possible to define two peers for site-to-site VPN connection. You can do this in

  toSanJose 20 ipsec-isakmp crypto map

  correspondence address card crypto 20 90 toSanJose

  toSanJose 20 set transformation-strong crypto card

  card crypto toSanJose 20 peers set 209.165.200.229 125.126.127.22

  The first pair is always given priority, in case if it is not available it failovers exchange of a second.

  It will be useful.

  Kind regards

  Rohan

• Tunnel from site to site VPN that overlap within the network

  Hi all

  I need to connect 2 networks via a tunnel VPN site to site. On the one hand, there is a 506th PIX by the termination of the VPN. The other side, I'm not too sure yet.

  However, what I know, is that both sides of the tunnel using the exact same IP subnet 192.168.1.0/24.

  This creates a problem when I need to define the Routing and the others when it comes to VPN and what traffic should be secure etc.

  However, read a lot for the review of CERT. Adv. Cisco PIX and noticed that outside NAT can solve my 'small' problem.

  That's all it is said, but I'd really like to see an example of configuration of this or hear from someone who has implemented it.

  Anyone?

  Steffen

  How is it then?

  http://www.Cisco.com/en/us/Tech/tk583/TK372/technologies_configuration_example09186a00800949f1.shtml

• Inside Source NAT from the remote host and VPN from Site to Site

  Hi all

  I was in charge of the construction of a vpn tunnel with a firewall PIX of our business partner company and ASA of the other company of the firewall.  Traffic will be A partner business users will access my company Citrix server.  I want to source-pat the user traffic partner company to PIX of my business within the interface to its entry in my LAN to access my company Citrix server.  The partner company will be PAT'ing their traffic from users to a single ip address - Let's say for discussion end is 65.99.100.101.  There is the site to site vpn configuration, and configure nat be performed to allow this traffic in accordance with the above provisions.

  I'm more concerned about the accuracy of the configuration of the domain encryption because NAT is involved in this whole upward.  My goal is to NAT (of the other company company a) ip address to a routable ip address in my company network.

  The fundamental question here is should I include the ip address of real source (65.99.100.101) of the company the user or IP natted (10.200.11.9) in the field of encryption.

  In other words should the encryption field looks like this

  OPTION A.

  permit ip host 10.200.11.103 65.99.100.101

  OR

  OPTION B

  permit ip host 10.200.11.103 10.200.11.9

  I'm inclined to think it should look like OPTION A.  Here's the part of MY complete SOCIETY of the VPN configuration.  I've also attached a diagram illustrating this topology.

  Thanks in advance,

  Adil

  CONFIG BELOW

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

  #################################################

  Object-group Config:

  #################################################

  the COMPANY_A_NETWORK object-group network

  Description company network access my company A firm Citrix

  host of the object-Network 65.99.100.101

  the MYCOMPANY_CITRIX_FARM object-group network

  Description farm Citrix accessible Takata by Genpact

  host of the object-Network 10.200.11.103

  ################################################

  Config of encryption:

  ################################################

  crypto ISAKMP policy 20

  preshared authentication

  3des encryption

  sha hash

  Group 2

  life 86400

  ********************************

  CRYPTO MAP

  ********************************

  crypto Outside_map 561 card matches the address Outside_561_cryptomap

  card crypto Outside_map 561 set peer 55.5.245.21

  Outside_map 561 transform-set ESP-3DES-SHA crypto card game

  ********************************

  TUNNEL GROUP

  ********************************

  tunnel-group 55.5.245.21 type ipsec-l2l

  IPSec-attributes tunnel-group 55.5.245.21

  pre-shared-key * 55.5.245.21

  *******************************

  FIELD OF CRYPTO

  *******************************

  Outside_561_cryptomap list extended access permitted ip object-group MYCOMPANY_CITRIX_FARM-group of objects COMPANY_A_NETWORK

  ###########################################

  NAT'ing

  ###########################################

  Global (inside) 9 10.200.11.9

  NAT (9 genpact_source_nat list of outdoor outdoor access)

  genpact_source_nat list extended access permit ip host 65.99.100.101 all

  genpact_source_nat list extended access permit ip host 65.99.100.102 all

  ! For not natting ip address of the Citrix server

  Inside_nat0 list extended access permitted ip object-group MYCOMPANY_CITRIX_FARM-group of objects COMPANY_A_NETWORK

  You must include pre - nat ip 65.99.x.x in your crypto-card, like you did.

  For me, config you provided here looks good and meets your needs.

  One thing, I do not see here the nat rule real 0, but there is the ACL that NAT. probably, you just forgot this rule.

  65.99.100.101 #sthash.mQm0FIOM.dpuf

• Cisco 3640 to the PIX 501 site 2 site VPN performance specifications.

  I intend on creating a site-2-site VPN in Star configuration with a Cisco 3640 as the hub and PIX 501 at the remote sites. My question is around the plug that I read.

  .

  The specifications for a PIX-501-BUN-K9 tell PIX 501 3DES Bundle (chassis, SW, 10 users, 3DES).

  .

  A question is what really "10 users. Which is the limit of the number of concurrent sessions, I have on the VPN at a given time, or that it means something else?

  .

  I also read the specs say that the Maximum number of VPN tunnels that can support a PIX 501 is 5. Because I'm not going to make a tunnel between the PIX 501 at the remote site and the 3640 on the central site, I think I would be OK. Is that correct or is the max value talk the maximum number of concurrent sessions on the tunnel tunnels?

  .

  Thank you.

  UDP traffic always creates a session in the PIX so that the return traffic will be allowed in. The UDP timeout is 2 minutes but IIRC. If you go around NAT with a statement of "nat 0" should not create an xlate I think.

  The real time is hard to say really, probably around 2 minutes for a UDP-only user, you would probably make a few 'local sho' orders on the PIX to really see for sure however.

• You try to run a Site to site VPN and remote VPN from the same IP remotely

  We currently have a site to site VPN configuration between our offices call center and a 3rd party that allows them to access our training to their employees to use environment while being trained on our systems. This tunnel is running between our ASA and their ASA without problem; However, when we have managers come out to the call center, they are unable to use remote VPN to access our office.

  Apparently the same IP peer remote that we use for our site to the other tunnel is the same IP that our managers use to access the internet when they are on-site with the customer. When I look at the logs it shows the VPN attempt and then I get treatment Information Exchange has failed. So from what I can understand when our managers are trying to connect to our firewall from the same IP address as the counterpart of site to site it automatically tries to create a tunnel, according to the information of the site to the other tunnel. If our managers are anywhere else, they can connect through remote VPN with no problems.

  My question is if anyone knows of a way to make the firewall allow VPN site to site and remote connections with the same remote IP address.

  Hi John,.

  Basically, in older versions, when you hit a static encryption card and you does not match this static encryption completely map the connection continues until the dynamic encryption card. For this reason, you can connect your IPSec clients before. A bug has been opened on this vulnerability.

  CSCuc75090  Details of bug

  The crypto IPSec Security Association are created by dynamic crypto map to static peers

  Symptom:

  When a static VPN peer adds all traffic to the ACL crypto, a surveillance society is based even if the pair IP is not allowed in the acl to the main façade encryption. Are these SA finally put in correspondence and commissioning the dynamic crypto map instance.

  Conditions:

  It was a planned design since the first day that allowed customers to fall through in the case of static crypto map did not provide a necessary cryptographic services.

  The SA must be made from a peer configured statically and a dynamic crypto map instance must be configured on the receiving end.

  Workaround solution:

  N/A

  Some possible workarounds are:

  Configure a static nat device when you try to use the remote VPN if the firewall remotely will be hit with a different public IP address. It would be a good solution, but it will depend on how many ip addresses public you have available, if you really want one of these ip addresses for that access.

  Also, I thought you could use AnyConnect instead of the IPSec VPN client. I don't know how many users need to connect from your PC to the remote site, but the ASA has 2 licenses SSL available that you could use. Because Anyconnect uses the SSL protocol, it won't have a problem on your environment.

  Below some information:

  http://www.Cisco.com/c/en/us/TD/docs/security/ASA/asa84/configuration/guide/asa_84_cli_config/vpn_anyconnect.html

  Hope this helps,

  Luis.

• Refuse the remote user VPN to access PC using VPN from Site users to partner Site

  Hi Experts,

  Installation program:

  We have configured IPSEC Site - Site VPN between Cisco ASA 5510 and Sonicwall.

  Tunnel is in place and working well, we are able to access the remote workstation to partner and Vis Versa.

  
  

  Requirment: We want to deny remote VPN users, who are our partners access to the workstation.

  Example:

  Remote IP address range: 192.168.200.x/2r4

  Local IP address range: 192.168.10.x/24

  Deny traffic from 192.168.200.x/24 to 192.168.10.x/24

  Thanks in advance

  Kiran Kumar CH

  Hi Kiran,

  You want to deny certain IP addresses of the Remote LAN (of the L2L tunnel), to connect to your workstation?

  Thus, if the remote network 192.168.200.0/24, want to deny some of these machines to connect to 192.168.10.x?

  If this is the case, you can create ACL VPN (VPN filters) on the SAA to restrictive traffic through the tunnel from the IPs.

  Please clarify if I have misunderstood.

  Federico.

• Help the Site VPN Site PIX 501

  Hello

  I'm pretty new to PIX firewall, so I hope someone here can help me.

  I have two PIX and try to create a private network virtual between the two PIX. I posted the configs below.

  The problem is that I can ping PIX on a PIX two, but I can't ping the servers behind TWO PIX. On two PIX, I cannot ping PIX ONE or all the servers behind it.

  Any advice would be appreciated.

  Thank you

  PIX 1

  6.2 (2) version PIX

  ethernet0 nameif outside security0

  nameif ethernet1 inside the security100

  hostname TMAXWALES

  domain ciscopix.com

  fixup protocol ftp 21

  fixup protocol http 80

  fixup protocol h323 h225 1720

  fixup protocol h323 ras 1718-1719

  fixup protocol they 389

  fixup protocol rsh 514

  fixup protocol rtsp 554

  fixup protocol smtp 25

  fixup protocol sqlnet 1521

  fixup protocol sip 5060

  fixup protocol 2000 skinny

  names of

  inside_outbound_nat0_acl ip 192.168.254.0 access list allow 255.255.255.0 192.1

  68.1.0 255.255.255.0

  outside_cryptomap_20 ip 192.168.254.0 access list allow 255.255.255.0 192.168.1

  .0 255.255.255.0

  pager lines 24

  interface ethernet0 10baset

  interface ethernet1 10full

  Outside 1500 MTU

  Within 1500 MTU

  IP address outside of *. *.198.139 255.255.255.248

  IP address inside 192.168.254.1 255.255.255.0

  alarm action IP verification of information

  alarm action attack IP audit

  location of PDM 192.168.254.10 255.255.255.255 inside

  location of PDM 192.168.1.0 255.255.255.0 outside

  history of PDM activate

  ARP timeout 14400

  Global 1 interface (outside)

  NAT (inside) 0-list of access inside_outbound_nat0_acl

  NAT (inside) 1 0.0.0.0 0.0.0.0 0 0

  Route outside 0.0.0.0 0.0.0.0 *. * 1.198.137

  Timeout xlate 03:00

  Timeout conn 0 half-closed 01:00:10: 00 udp 0:02:00 CPP 0: h323 from 10:00 0:05:00 TR

  p 0:30:00 sip_media 0:02:00

  Timeout, uauth 0:05:00 absolute

  GANYMEDE + Protocol Ganymede + AAA-server

  RADIUS Protocol RADIUS AAA server

  AAA-server local LOCAL Protocol

  Enable http server

  http 192.168.254.10 255.255.255.255 inside

  No snmp server location

  No snmp Server contact

  SNMP-Server Community public

  No trap to activate snmp Server

  enable floodguard

  Permitted connection ipsec sysopt

  No sysopt route dnat

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

  outside_map 20 ipsec-isakmp crypto map

  card crypto outside_map 20 match address outside_cryptomap_20

  card crypto outside_map 20 peers set *. *.198.138

  outside_map crypto 20 card value transform-set ESP-3DES-SHA

  outside_map interface card crypto outside

  ISAKMP allows outside

  ISAKMP key * address *. *.198.138 netmask 255.255.255.255 No.-xauth non - co

  Nfig-mode

  part of pre authentication ISAKMP policy 20

  ISAKMP policy 20 3des encryption

  ISAKMP policy 20 chopping sha

  20 2 ISAKMP policy group

  ISAKMP duration strategy of life 20 86400

  Telnet timeout 5

  SSH timeout 5

  Terminal width 80

  PIX 2

  6.2 (2) version PIX

  ethernet0 nameif outside security0

  nameif ethernet1 inside the security100

  hostname tmaxbangor

  domain ciscopix.com

  fixup protocol ftp 21

  fixup protocol http 80

  fixup protocol h323 h225 1720

  fixup protocol h323 ras 1718-1719

  fixup protocol they 389

  fixup protocol rsh 514

  fixup protocol rtsp 554

  fixup protocol smtp 25

  fixup protocol sqlnet 1521

  fixup protocol sip 5060

  fixup protocol 2000 skinny

  names of

  permit 192.168.1.0 ip access list inside_outbound_nat0_acl 255.255.255.0 192.168

  . 254.0 255.255.255.0

  permit 192.168.1.0 ip access list outside_cryptomap_20 255.255.255.0 192.168.254

  .0 255.255.255.0

  pager lines 24

  opening of session

  debug logging in buffered memory

  interface ethernet0 10baset

  interface ethernet1 10full

  Outside 1500 MTU

  Within 1500 MTU

  IP address outside of *. *.198.138 255.255.255.248

  IP address inside 192.168.1.1 255.255.255.0

  IP verify reverse path to the outside interface

  IP verify reverse path inside interface

  the IP audit info action alarm reset drop

  reset the IP audit attack alarm drop action

  location of PDM 192.168.1.0 255.255.255.0 inside

  PDM logging 100 information

  history of PDM activate

  ARP timeout 14400

  Global 1 interface (outside)

  NAT (inside) 0-list of access inside_outbound_nat0_acl

  NAT (inside) 1 0.0.0.0 0.0.0.0 0 0

  Route outside 0.0.0.0 0.0.0.0 *. * 1.198.137

  Timeout xlate 03:00

  Timeout conn 0 half-closed 01:00:10: 00 udp 0:02:00 CPP 0: h323 from 10:00 0:05:00 TR

  p 0:30:00 sip_media 0:02:00

  Timeout, uauth 0:05:00 absolute

  GANYMEDE + Protocol Ganymede + AAA-server

  RADIUS Protocol RADIUS AAA server

  AAA-server local LOCAL Protocol

  Enable http server

  http 192.168.1.0 255.255.255.0 inside

  http 192.84.7.111 255.255.255.255 inside

  http 192.168.1.10 255.255.255.255 inside

  No snmp server location

  No snmp Server contact

  SNMP-Server Community public

  No trap to activate snmp Server

  enable floodguard

  Permitted connection ipsec sysopt

  No sysopt route dnat

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

  outside_map 20 ipsec-isakmp crypto map

  card crypto outside_map 20 match address outside_cryptomap_20

  card crypto outside_map 20 peers set *. *.198.139

  outside_map crypto 20 card value transform-set ESP-3DES-SHA

  outside_map interface card crypto outside

  ISAKMP allows outside

  ISAKMP key * address *. *.198.139 netmask 255.255.255.255 No.-xauth non - co

  Nfig-mode

  part of pre authentication ISAKMP policy 20

  ISAKMP policy 20 3des encryption

  ISAKMP policy 20 chopping sha

  20 2 ISAKMP policy group

  ISAKMP duration strategy of life 20 86400

  Telnet 192.168.1.0 255.255.255.0 inside

  Telnet timeout 50

  SSH timeout 5

  Terminal width 80

  Can't see anything obviously wrong with the configs. You have these connected back to back on the same subnet, it looks that it even if you have xxx out IP addresses? If so it's maybe a routing problem, in what they send everything to the default gateway of xxx.x.198.137 rather than to the other.

  Try to add a static route to the remote subnet to each PIX that points directly to the peer, so on PIX1 you should have:

  Route outside 192.168.1.0 255.255.255.0 xxx.x.198.138

  and on PIX2 do:

  Route outside 192.168.254.0 255.255.255.0 xxx.x.198.139

  and see if that makes a difference. Note that you wouldn't encounter this problem when these two PIX is on separate networks and uses the default gateway for all routing decisions.

  If this still fails, run 'debug cryp isa' and ' debug cry ipsec "on the two PIX are trying to build a tunnel again, and then and send us the output.

  Also, make sure your tests that you're rattling to a host behind a PIX to a host behind the other PIX, ping PIX to PIX or host because of PIX that won't test your VPN connection.

• Between the VPN Client and VPN from Site to Site

  Looking for an example of ASA 8.0 configuration allowing traffic between a Cisco VPN client host and destination of remote access connected via LAN/Site-to-Site tunnel.  The remote access client and the tunnel site-to-site terminate on the same device of the SAA.

  Thanks in advance.

  -Rey

  Hi Rey,

  Here is an example of a config for what you are looking for.

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

  I hope this helps.

  PS: This uses GANYMEDE + for authentication, you can replace it with your authentication method.

  Kind regards

  Assia

• PIX-Sonicwall Site-to-Site and Cisco VPN Client

  I have a firewall 506th PIX with a VPN site-to site for a firewall Sonicwall 330 Pro which works perfectly. I would like to add the functionality of remote users connecting to the network using the client VPN from Cisco PIX. I'm under the question of having only a single card encryption applied to the external interface. I need the feature to have the tunnel between the site to site VPN can be undertaken on other, so I can't use a dynamic encryption card. Does anyone have suggestions or knowledge on how to achieve this?

  Thank you.

  You don't need to add another card encryption to the external interface. You simply add customer information to your existing card for example:

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

  YOURMAP 10 ipsec-isakmp crypto map

  card crypto YOURMAP 10 corresponds to 100 address

  card crypto YOURMAP 10 set counterpart x.x.x.x

  crypto YOURMAP 10 the transform-set YOURSET value card

  set of 10 CUSTOMERS crypto dynamic-map transform-set YOURSET

  card crypto YOURMAP 90-isakmp dynamic ipsec CLIENTS