In/Out ACL by VPN on SAA

Similar Questions

• EZ VPN on SAA

  We have an ASA 5505 configured for EZ remote VPN. If assign us a static ip address for the external interface in our test lab, it remains standing. When we go out on the remote site, which has a FiOS connection with dhcp for the external interface address, it gives every hour. When we put a pix there, it remains standing. At sh crypto isakmp his on the side remote shows an AM_WAIT_MSG2 (when the SAA is in place and the tunnel fails) I have to restart the SAA, and then the tunnel will come back to the top. For an hour. Also has anyone seen this type of behavior? It has been very frustrating and I have a tac case, but they said that configuration seems fine.

  Today is your lucky day. I had this problem with my ASA5505 on my FiOS connection. Apparently Verizon ping your device before it will allow you to request or renew your IP address. When your ASA comes first in line they can it ping because you have ICMP enabled outside and the VPN tunnel is not. Once the tunnel is established and you do not use the split tunneling, they can't ping your ASA. If you drop the tunnel the dhcp lease does not expire. What I had to do was the tunneling split on the vpn group that I used for the ASA and enable ICMP on the external interface. After that the ASA would stay for good.

• Route Internet traffic against the default VPN on SAA route

  I want to transfer all internet traffic to a VPN connection via the internal network and not divided the digging of tunnels or direct connection to the internet from the OUTSIDE interface.

  I have a VPN connection default gateway, so all traffic is pushed back on the OUTSIDE interface when the VPN is in place and the user connects to the Internet.

  Is it possible to send Internet traffic to the INSIDE interface, internal network, to route to the Internet.

  I'm not looking for another solution, it's the design, I would like to implement.

  

  As always, any help is greatly appreciated.

  Of course you can, simply set the following text:

  Route inside 0.0.0.0 0.0.0.0 in tunnel

  The foregoing will force all VPN traffic after be decrypted to the next break of the SAA within the interface defined above

• ACL RA VPN

  Hello

  I have configured the Tunnel VPN RA, everything works fine, but now I want to allow only the http/www port because the vpn client should have access to my application server only, rest of the port should be blocked how to do this?

  Your ACL 2 line is totally incorrect.

  (1) HTTP is a protocol TCP, UDP, no

  (2) you can't have a port source www - because it is in the range of ports restrcited, your source port will ALWAYS be 1024 to 65535.

  Re - configure line: -.

  permit for line of RA-tunnel access list lengthened 2 tcp 192.168.1.0 255.255.255.0 10.0.0.0 255.255.255.0 eq www

  HTH >

• Download ACL for VPN users. ACS 4.1 & 1841 router

  Hello

  I have configured the router 1841 as a VPN server. All VPN users get authenticated using RADIUS ACS 4.1

  I need to apply downloadable ACLs by user.

  I configured the Downlodabale ACL ACS. Same ACS event report shows that the ACL is applied to the authenticated user, but traffic is not blocked or past accordingly.

  What is your configuration?

  I think that the more easy to do is to use IPSEC TIV in interfaces, as well as the aaa authorization network and on the radius server, use ip:inacl to the cisco av pair, as

  IP:inacl #1 = permit tcp any any eq 80

  IP:inacl #2 = permit tcp any any eq 443

  ...

  Some documents:

  http://www.Cisco.com/en/us/docs/iOS/12_3t/12_3t14/feature/guide/gtIPSctm.html#wp1090634

• Assign ACLs to VPN clients

  We have a client that VPN in a Pix 515. I inserted the configuration of intra-interface same-security-traffic allowed on the pix so that members of staff who use the VPN would be able to access a specific resource from the public side. What I would do is to continue to use the same-security-traffic intra-interface command permit, but restrict access to other resources to the VPN client. Can I assign an access list to the VPN client allowing 10.10.10.10 everything and refuse all other connections? Where can I insert this in the VPN structure?

  Thank you

  Yes.

  Kind regards

  Arul

  * Please note all useful messages *.

• VPN on SAA on IOS 8.4 remote access (2)

  IAM able to authenticate the VPN network with my name password user and also able to get the IP address of the VPN pool

  But is not able to access my home network to something (IE lan) or remote desktop on the server 172.17.100.10, 172.17.100.20

  mask Q8-VPN-pool 172.16.37.10 - 172.16.37.200 255.255.255.0 IP local pool

  NetworkTest_splitTunnelAcl list extended access permit tcp host 172.17.100.10 eq 3389 everything

  NetworkTest_splitTunnelAcl list extended access permit tcp host 172.17.100.20 eq 3389 everything

  NetworkTest_splitTunnelAcl list extended access permit tcp host 172.17.100.30 eq 22 all

  internal NetworkTest-VPN group policy
  NetworkTest-VPN group policy attributes
  value of server DNS 192.168.0.122 192.168.0.123
  Protocol-tunnel-VPN IPSec
  Split-tunnel-policy tunnelspecified
  value of Split-tunnel-network-list NetworkTest_splitTunnelAcl
  value by default-field Q8.com

  type tunnel-group NetworkTest-VPN remote access
  tunnel-group NetworkTest-VPN-global attributes
  address (inside) Q8-VPN-pool pool
  Q8-VPN-pool-pool of addresses
  authentication-server-group ACS
  authentication-server-group (inside) ACS LOCAL
  accounting-server-group ACS
  strategy-group-by default NetworkTest-VPN

  tunnel-group NetworkTest-VPN ipsec-attributes
  pre-shared key *.

  Under nat did not work so I created new Nat for 8.4

  inside_nat0_outbound list of allowed ip extended access all 172.16.37.0 255.255.255.0

  NAT (inside) 0-list of access inside_nat0_outbound

  New Nat for 8.4

  network of the RA-VPN-HOST object
  172.16.37.0 subnet 255.255.255.0
  !
  NAT (inside, outside) static source everything any static destination VPN-RA-RA-VPN-HOST

  Controlled split Tunneling routing in the tunnel. And this is done without L4-information (knowing that there are cases where this is done, but I do not see that in your scenario). And as said before, the filtering is performed using the vpn-filter.

  Works for nat, you must use the correct order of the sentences-nat (descendant). So this Exemption-NAT must be above the general NAT for internet access. You can control that with 'see the nat.

• ACL ASA5540 does not not for VPN access.

  I'm under code 8,03 and have a simple VPN L2L configured between two sites. It is in fact a test config in my lab, but I'm unable to restrict traffic using an ACL inside.

  I used the VPN Wizard to do the config initial and then added an Interior (out) ACL to restrict traffic once the tunnel rises.

  The encryption card is as follows:

  access extensive list ip 164.72.1.128 outside_1_cryptomap allow 255.255.255.240 host SunMed_pc

  Then I have an ACL to limit traffic to ping GHC_laptop, telnet to GHC_switch and denying the rest:

  inside_access_out list extended access allowed icmp host host SunMed_pc GHC_Laptop

  inside_access_out list extended access permit tcp host SunMed_pc host GHC_switch eq telnet

  inside_access_out deny ip extended access list a whole

  However SunMed_pc can also ping at GHC_switch and can FTP to GHC_laptop even if the 3rd entrance to deny any meter increases when I do this.

  I have attached a Word document that has the entire config with a screenshot showing the ACL and the shots.

  Should I configured incorrectly, or is ACL ACL actually does not work as expected?

  You can still keep all the IP for your acl interesting traffic. If you delete the sysopt, then you would write access in your acl 'inside_access' like you did above.

  If you are going to have dozens of tunnels l2l and will limit all, then I just remove the sysopt and use the acl interface.

  There is another option. You can leave the sysopt and use a vpn-filter. It is explained here and can be applied to l2l.

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

  http://www.Cisco.com/en/us/docs/security/ASA/asa80/command/reference/uz.html#wp1524559

• IOS router + VPN + ACS downloadable IP ACL

  I want to use the function "Downloadable IP ACL" 3825-router VPN (OI 12.4 T) in combination with a CBS.

  In many documents and discussions, I read that it is possible to use the DACLs on "devices Cisco IOS version 12.3 (8) T or higher.

  Authentication and authorization by the AEC works and the device gets some settings of the av-pair-feature.

  I have tried several things to apply the DACL as the use of av pairs or ACS "Downloadable IP ACL" function, but nothing works.

  In the debug log, I see that the av pair is transmitted to the device, but it is not used.

  --> Can you tell me, is it possible to use the DACLs on the IOS routers?

  --> How does it work? What can I change?

  --> Is there a good manual to apply it?

  Thanks for your help!

  Martin

  It would be useful to know the PURPOSE of what you're trying to do...

  AFAIR client config mode requires no ACL for filtering short tunnel split ACL... and I have no way to test right now.

  If you want to allow or not some clients access to certain subnets why not investigate tunneling ACL and vpn-filter in combination with ACS split will rather than for the DACL.

• Coming out of the IPSec VPN connection behind Pix535 problem: narrowed down for NAT-Associates

  Hello world

  Previously, I've seen a similar thread and posted my troubles with the outbound VPN connections inside that thread:

  https://supportforums.Cisco.com/message/3688980#3688980

  I had the great help but unfortunatedly my problem is a little different and connection problem.  Here, I summarize once again our configurations:

  hostname pix535 8.0 (4)

  all PC here use IP private such as 10.1.0.0/16 by dynamic NAT, we cannot initiate an OUTBOUND IPSec VPN (for example QuickVPN) at our offices, but the reverse (inbound) is very well (we have IPsec working long server /PP2P). I did a few tests of new yesterday which showed that if the PC a static NAT (mapped to a real public IP), outgoing connection VPN is fine; If the same PC has no static NAT (he hides behind the dynamic NAT firewall), outgoing VPN is a no-go (same IP to the same PC), so roughly, I have narrowed down our connection problem VPN is related to NAT, here are a few commands for NAT of our PIX:

  interface GigabitEthernet0
  Description to cable-modem
  nameif outside
  security-level 0
  IP 70.169.X.X 255.255.255.0
  OSPF cost 10
  !
  interface GigabitEthernet1
  Description inside 10/16
  nameif inside
  security-level 100
  IP 10.1.1.254 255.255.0.0
  OSPF cost 10
  !
  !
  interface Ethernet2
  Vlan30 description
  nameif dmz2
  security-level 50
  IP 30.30.30.30 255.255.255.0
  OSPF cost 10
  !
  permit same-security-traffic inter-interface
  permit same-security-traffic intra-interface

  ......

  Global interface 10 (external)
  Global (dmz2) interface 10
  NAT (inside) 0-list of access inside_nat0_outbound
  NAT (inside) 10 inside8 255.255.255.0
  NAT (inside) 10 Vlan10 255.255.255.0
  NAT (inside) 10 vlan50 255.255.255.0
  NAT (inside) 10 192.168.0.0 255.255.255.0
  NAT (inside) 10 192.168.1.0 255.255.255.0
  NAT (inside) 10 192.168.10.0 255.255.255.0
  NAT (inside) 10 pix-inside 255.255.0.0

  Crypto isakmp nat-traversal 3600

  -------

  Results of packet capture are listed here for the same PC for the same traffic to Server VPN brach, the main difference is UDP 4500 (PC with static NAT has good traffic UDP 4500, does not have the same PC with dynamic NAT):

  #1: when the PC uses static NAT, it is good of outgoing VPN:

  54 packets captured
  1: 15:43:51.112054 10.1.1.82.1608 > 76.196.10.57.443: S 1763806634:1763806634 (0) win 64240
  2: 15:43:54.143028 10.1.1.82.1608 > 76.196.10.57.443: S 1763806634:1763806634 (0) win 64240
  3: 15:44:00.217273 10.1.1.82.1608 > 76.196.10.57.443: S 1763806634:1763806634 (0) win 64240
  4: 15:44:01.724938 10.1.1.82.1609 > 76.196.10.57.60443: S 2904546955:2904546955 (0) win 64240
  5: 15:44:01.784642 76.196.10.57.60443 > 10.1.1.82.1609: S 2323205974:2323205974 (0) ack 2904546956 win 5808
  6: 15:44:01.784886 10.1.1.82.1609 > 76.196.10.57.60443:. ACK 2323205975 win 64240
  7: 15:44:01.785527 10.1.1.82.1609 > 76.196.10.57.60443: P 2904546956:2904547080 (124) ack 2323205975 win 64240
  8: 15:44:01.856462 76.196.10.57.60443 > 10.1.1.82.1609:. ACK 2904547080 win 5808
  9: 15:44:01.899596 76.196.10.57.60443 > 10.1.1.82.1609: P 2323205975:2323206638 (663) ack 2904547080 win 5808
  10: 15:44:02.056897 10.1.1.82.1609 > 76.196.10.57.60443:. ACK 2323206638 win 63577
  11: 15:44:03.495030 10.1.1.82.1609 > 76.196.10.57.60443: P 2904547080:2904547278 (198) ack 2323206638 win 63577
  12: 15:44:03.667095 76.196.10.57.60443 > 10.1.1.82.1609:. ACK 2904547278 win 6432
  13: 15:44:03.740592 76.196.10.57.60443 > 10.1.1.82.1609: P 2323206638:2323206697 (59) ack 2904547278 win 6432
  14: 15:44:03.741264 10.1.1.82.1609 > 76.196.10.57.60443: P 2904547278:2904547576 (298) ack 2323206697 win 63518
  15: 15:44:03.814029 76.196.10.57.60443 > 10.1.1.82.1609:. ACK 2904547576 win 7504
  16: 15:44:06.989008 76.196.10.57.60443 > 10.1.1.82.1609: P 2323206697:2323207075 (378) ack 2904547576 win 7504
  17: 15:44:06.990228 76.196.10.57.60443 > 10.1.1.82.1609: 2323207075:2323207075 F (0) ack 2904547576 win 7504
  18: 15:44:06.990564 10.1.1.82.1609 > 76.196.10.57.60443:. ACK 2323207076 win 63140
  19: 15:44:06.990656 10.1.1.82.1609 > 76.196.10.57.60443: P 2904547576:2904547613 (37) ack 2323207076 win 63140
  20: 15:44:06.990854 10.1.1.82.1609 > 76.196.10.57.60443: 2904547613:2904547613 F (0) ack 2323207076 win 63140
  21: 15:44:07.049359 76.196.10.57.60443 > 10.1.1.82.1609: R 2323207076:2323207076 (0) win 0
  22: 15:44:17.055417 10.1.1.82.500 > 76.196.10.57.500: udp 276
  23: 15:44:17.137657 76.196.10.57.500 > 10.1.1.82.500: udp 140
  24: 15:44:17.161475 10.1.1.82.500 > 76.196.10.57.500: udp 224
  25: 15:44:17.309066 76.196.10.57.500 > 10.1.1.82.500: udp 220
  26: 15:44:17.478780 10.1.1.82.4500 > 76.196.10.57.4500: udp 80
  27: 15:44:17.550356 76.196.10.57.4500 > 10.1.1.82.4500: 64 udp
  28: 15:44:17.595214 10.1.1.82.4500 > 76.196.10.57.4500: udp 304
  29: 15:44:17.753470 76.196.10.57.4500 > 10.1.1.82.4500: udp 304
  30: 15:44:17.763037 10.1.1.82.4500 > 76.196.10.57.4500: udp 68
  31: 15:44:17.763540 10.1.1.82.4500 > 76.196.10.57.4500: udp 56
  32: 15:44:18.054516 10.1.1.82.4500 > 76.196.10.57.4500: udp 68
  33: 15:44:18.124840 76.196.10.57.4500 > 10.1.1.82.4500: udp 68
  34: 15:44:21.835390 10.1.1.82.4500 > 76.196.10.57.4500: udp 72
  35: 15:44:21.850831 10.1.1.82.4500 > 76.196.10.57.4500: udp 80
  36: 15:44:21.901183 76.196.10.57.4500 > 10.1.1.82.4500: udp 72
  37: 15:44:22.063747 10.1.1.82.1610 > 76.196.10.57.60443: S 938188365:938188365 (0) win 64240
  38: 15:44:22.104746 76.196.10.57.4500 > 10.1.1.82.4500: udp 80
  39: 15:44:22.122277 76.196.10.57.60443 > 10.1.1.82.1610: S 1440820945:1440820945 (0) ack 938188366 win 5808
  40: 15:44:22.122536 10.1.1.82.1610 > 76.196.10.57.60443:. ACK 1440820946 win 64240
  41: 15:44:22.123269 10.1.1.82.1610 > 76.196.10.57.60443: P 938188366:938188490 (124) ack 1440820946 win 64240
  42: 15:44:22.187108 76.196.10.57.60443 > 10.1.1.82.1610:. ACK 938188490 win 5808
  43: 15:44:22.400675 76.196.10.57.60443 > 10.1.1.82.1610: P 1440820946:1440821609 (663) ack 938188490 win 5808
  44: 15:44:22.474600 10.1.1.82.1610 > 76.196.10.57.60443: P 938188490:938188688 (198) ack 1440821609 win 63577
  45: 15:44:22.533648 76.196.10.57.60443 > 10.1.1.82.1610:. ACK 938188688 win 6432
  46: 15:44:22.742286 76.196.10.57.60443 > 10.1.1.82.1610: P 1440821609:1440821668 (59) ack 938188688 win 6432
  47: 15:44:22.742927 10.1.1.82.1610 > 76.196.10.57.60443: P 938188688:938189002 (314) ack 1440821668 win 63518
  48: 15:44:22.802570 76.196.10.57.60443 > 10.1.1.82.1610:. ACK 938189002 win 7504
  49: 15:44:25.180486 76.196.10.57.60443 > 10.1.1.82.1610: P 1440821668:1440821934 (266) ack 938189002 win 7504
  50: 15:44:25.181753 76.196.10.57.60443 > 10.1.1.82.1610: 1440821934:1440821934 F (0) ack 938189002 win 7504
  51: 15:44:25.181997 10.1.1.82.1610 > 76.196.10.57.60443:. ACK 1440821935 win 63252
  52: 15:44:25.182134 10.1.1.82.1610 > 76.196.10.57.60443: P 938189002:938189039 (37) ack 1440821935 win 63252
  53: 15:44:25.182333 10.1.1.82.1610 > 76.196.10.57.60443: 938189039:938189039 F (0) ack 1440821935 win 63252
  54: 15:44:25.241869 76.196.10.57.60443 > 10.1.1.82.1610: R 1440821935:1440821935 (0) win 0

  #2: same PC with Dynamic NAT, VPN connection fails:

  70 packets captured
  1: 14:08:31.758261 10.1.1.82.1073 > 76.196.10.57.443: S 820187495:820187495 (0) win 64240
  2: 14:08:34.876907 10.1.1.82.1073 > 76.196.10.57.443: S 820187495:820187495 (0) win 64240
  3: 14:08:40.746055 10.1.1.82.1073 > 76.196.10.57.443: S 820187495:820187495 (0) win 64240
  4: 14:08:42.048627 10.1.1.82.1074 > 76.196.10.57.60443: S 3309127022:3309127022 (0) win 64240
  5: 14:08:42.120248 76.196.10.57.60443 > 10.1.1.82.1074: S 1715577781:1715577781 (0) ack 3309127023 win 5808
  6: 14:08:42.120568 10.1.1.82.1074 > 76.196.10.57.60443:. ACK 1715577782 win 64240
  7: 14:08:42.121102 10.1.1.82.1074 > 76.196.10.57.60443: P 3309127023:3309127147 (124) ack 1715577782 win 64240
  8: 14:08:42.183553 76.196.10.57.60443 > 10.1.1.82.1074:. ACK 3309127147 win 5808
  9: 14:08:42.232867 76.196.10.57.60443 > 10.1.1.82.1074: P 1715577782:1715578445 (663) ack 3309127147 win 5808
  10: 14:08:42.405145 10.1.1.82.1074 > 76.196.10.57.60443:. ACK 1715578445 win 63577
  11: 14:08:43.791340 10.1.1.82.1074 > 76.196.10.57.60443: P 3309127147:3309127345 (198) ack 1715578445 win 63577
  12: 14:08:43.850450 76.196.10.57.60443 > 10.1.1.82.1074:. ACK 3309127345 win 6432
  13: 14:08:44.028196 76.196.10.57.60443 > 10.1.1.82.1074: P 1715578445:1715578504 (59) ack 3309127345 win 6432
  14: 14:08:44.058544 10.1.1.82.1074 > 76.196.10.57.60443: P 3309127345:3309127643 (298) ack 1715578504 win 63518
  15: 14:08:44.116403 76.196.10.57.60443 > 10.1.1.82.1074:. ACK 3309127643 win 7504
  16: 14:08:47.384654 76.196.10.57.60443 > 10.1.1.82.1074: P 1715578504:1715578882 (378) ack 3309127643 win 7504
  17: 14:08:47.385417 76.196.10.57.60443 > 10.1.1.82.1074: 1715578882:1715578882 F (0) ack 3309127643 win 7504
  18: 14:08:47.394068 10.1.1.82.1074 > 76.196.10.57.60443:. ACK 1715578883 win 63140
  19: 14:08:47.394922 10.1.1.82.1074 > 76.196.10.57.60443: P 3309127643:3309127680 (37) ack 1715578883 win 63140
  20: 14:08:47.395151 10.1.1.82.1074 > 76.196.10.57.60443: 3309127680:3309127680 F (0) ack 1715578883 win 63140
  21: 14:08:47.457633 76.196.10.57.60443 > 10.1.1.82.1074: R 1715578883:1715578883 (0) win 0
  22: 14:08:57.258073 10.1.1.82.500 > 76.196.10.57.500: udp 276
  23: 14:08:57.336255 76.196.10.57.500 > 10.1.1.82.500: udp 40
  24: 14:08:58.334211 10.1.1.82.500 > 76.196.10.57.500: udp 276
  25: 14:08:58.412850 76.196.10.57.500 > 10.1.1.82.500: udp 40
  26: 14:09:00.333311 10.1.1.82.500 > 76.196.10.57.500: udp 276
  27: 14:09:00.410730 76.196.10.57.500 > 10.1.1.82.500: udp 40
  28: 14:09:02.412561 10.1.1.82.1075 > 76.196.10.57.443: S 968016865:968016865 (0) win 64240
  29: 14:09:04.349164 10.1.1.82.500 > 76.196.10.57.500: udp 276
  30: 14:09:04.431648 76.196.10.57.500 > 10.1.1.82.500: udp 40
  31: 14:09:05.442710 10.1.1.82.1075 > 76.196.10.57.443: S 968016865:968016865 (0) win 64240
  32: 14:09:11.380427 10.1.1.82.1075 > 76.196.10.57.443: S 968016865:968016865 (0) win 64240
  33: 14:09:12.349926 10.1.1.82.500 > 76.196.10.57.500: udp 276
  34: 14:09:12.421502 10.1.1.82.1076 > 76.196.10.57.60443: S 3856215672:3856215672 (0) win 64240
  35: 14:09:12.430794 76.196.10.57.500 > 10.1.1.82.500: udp 40
  36: 14:09:12.481832 76.196.10.57.60443 > 10.1.1.82.1076: S 248909856:248909856 (0) ack 3856215673 win 5808
  37: 14:09:12.527972 10.1.1.82.1076 > 76.196.10.57.60443:. ACK 248909857 win 64240
  38: 14:09:12.529238 10.1.1.82.1076 > 76.196.10.57.60443: P 3856215673:3856215797 (124) ack 248909857 win 64240
  39: 14:09:12.608275 76.196.10.57.60443 > 10.1.1.82.1076:. ACK 3856215797 win 5808
  40: 14:09:12.658581 76.196.10.57.60443 > 10.1.1.82.1076: P 248909857:248910520 (663) ack 3856215797 win 5808
  41: 14:09:12.664531 10.1.1.82.1076 > 76.196.10.57.60443: P 3856215797:3856215995 (198) ack 248910520 win 63577
  42: 14:09:12.725533 76.196.10.57.60443 > 10.1.1.82.1076:. ACK 3856215995 win 6432
  43: 14:09:12.880813 76.196.10.57.60443 > 10.1.1.82.1076: P 248910520:248910579 (59) ack 3856215995 win 6432
  44: 14:09:12.892272 10.1.1.82.1076 > 76.196.10.57.60443: P 3856215995:3856216293 (298) ack 248910579 win 63518
  45: 14:09:12.953029 76.196.10.57.60443 > 10.1.1.82.1076:. ACK 3856216293 win 7504
  46: 14:09:12.955043 76.196.10.57.60443 > 10.1.1.82.1076: 248910579:248910579 F (0) ack 3856216293 win 7504
  47: 14:09:12.955242 10.1.1.82.1076 > 76.196.10.57.60443:. ACK 248910580 win 63518
  48: 14:09:12.955516 10.1.1.82.1076 > 76.196.10.57.60443: P 3856216293:3856216330 (37) ack 248910580 win 63518
  49: 14:09:12.955730 10.1.1.82.1076 > 76.196.10.57.60443: 3856216330:3856216330 F (0) ack 248910580 win 63518
  50: 14:09:13.019743 76.196.10.57.60443 > 10.1.1.82.1076: R 248910580:248910580 (0) win 0
  51: 14:09:16.068691 10.1.1.82.500 > 76.196.10.57.500: udp 56
  52: 14:09:16.227588 10.1.1.82.1077 > 76.196.10.57.60443: S 3657181617:3657181617 (0) win 64240
  53: 14:09:16.283783 76.196.10.57.60443 > 10.1.1.82.1077: S 908773751:908773751 (0) ack 3657181618 win 5808
  54: 14:09:16.306823 10.1.1.82.1077 > 76.196.10.57.60443:. ACK 908773752 win 64240
  55: 14:09:16.307692 10.1.1.82.1077 > 76.196.10.57.60443: P 3657181618:3657181742 (124) ack 908773752 win 64240
  56: 14:09:16.370998 76.196.10.57.60443 > 10.1.1.82.1077:. ACK 3657181742 win 5808
  57: 14:09:16.411935 76.196.10.57.60443 > 10.1.1.82.1077: P 908773752:908774415 (663) ack 3657181742 win 5808
  58: 14:09:16.417870 10.1.1.82.1077 > 76.196.10.57.60443: P 3657181742:3657181940 (198) ack 908774415 win 63577
  59: 14:09:16.509388 76.196.10.57.60443 > 10.1.1.82.1077:. ACK 3657181940 win 6432
  60: 14:09:16.708413 76.196.10.57.60443 > 10.1.1.82.1077: P 908774415:908774474 (59) ack 3657181940 win 6432
  61: 14:09:16.887100 10.1.1.82.1077 > 76.196.10.57.60443: P 3657181940:3657182254 (314) ack 908774474 win 63518
  62: 14:09:16.948193 76.196.10.57.60443 > 10.1.1.82.1077:. ACK 3657182254 win 7504
  63: 14:09:19.698465 76.196.10.57.60443 > 10.1.1.82.1077: P 908774474:908774740 (266) ack 3657182254 win 7504
  64: 14:09:19.699426 76.196.10.57.60443 > 10.1.1.82.1077: 908774740:908774740 F (0) ack 3657182254 win 7504
  65: 14:09:20.060162 10.1.1.82.1077 > 76.196.10.57.60443:. ACK 908774741 win 63252
  66: 14:09:20.062191 76.196.10.57.60443 > 10.1.1.82.1077: P 908774474:908774740 (266) ack 3657182254 win 7504
  67: 14:09:20.063732 10.1.1.82.1077 > 76.196.10.57.60443:. ACK 908774741 win 63252
  68: 14:09:20.063900 10.1.1.82.1077 > 76.196.10.57.60443: P 3657182254:3657182291 (37) ack 908774741 win 63252
  69: 14:09:20.064098 10.1.1.82.1077 > 76.196.10.57.60443: 3657182291:3657182291 F (0) ack 908774741 win 63252
  70: 14:09:20.127694 76.196.10.57.60443 > 10.1.1.82.1077: R 908774741:908774741 (0) win 0
  70 packages shown

  We had this problem of connection VPN IPsec from the years (I first thought it is restriction access problem, but it does not work or if I disable all access lists, experience of yesterday for the same restriction of the access-list shows longer than PC is not the cause). All suggestions and tips are greatly appreciated.

  Sean

  Hi Sean, please remove th lines highlighted in your pix and try and let me know, that these lines are not the default configuration of the PIX.

  VPN-udp-class of the class-map

  corresponds to the list of access vpn-udp-acl

  vpn-udp-policy policy-map

  VPN-udp-class

  inspect the amp-ipsec

  type of policy-card inspect dns migrated_dns_map_1

  parameters

  message-length maximum 768

  Policy-map global_policy

  class inspection_default

  inspect the migrated_dns_map_1 dns

  inspect the ftp

  inspect h323 h225

  inspect the h323 ras

  inspect the http

  inspect the netbios

  inspect the rsh

  inspect the rtsp

  inspect the skinny

  inspect sqlnet

  inspect sunrpc

  inspect the tftp

  inspect the sip

  inspect xdmcp

  inspect the pptp

  inspect the amp-ipsec

  permit same-security-traffic inter-interface

  permit same-security-traffic intra-interface

  IP verify reverse path to the outside interface

  Thank you

  Rizwan James

• ACL entering for public router VPN

  Hi all

  I set up our VPN router for access to all of our mobile customers. Our private VPN range is going to be 172.16.10.x/24. I have to add ACL allow rules for this range on our ACL entering all inside LANs to facilitate access for VPN users?

  for example int S0/0/0

  IP address 85.x.x.x

  IP access-group 100 to

  access-list 100 permit ip 172.16.10.0 0.0.0.255 192.168.1.0 0.0.0.255

  If I understand it, once the user connects the VPN tunnel to the inside of the interface, so is traffic through the VPN is encapsulated and therefore wouldn't appear as a private IP address?

  All comments are greatly appreciated.

  Paul

  Sorry I mean you should not change outside the acl for vpn traffic for the rest of the things you can do.

  Thank you

  Ajay

• Connected to the ASA via the "VPN Client" software, but cannot ping devices.

  I have a network that looks like this:

  

  I successfully connected inside the ASA via a software "Client VPN" tunnel network and got an IP address of 10.45.99.100/16.

  I am trying to ping the 10.45.99.100 outside 10.45.7.2, but the ping fails (request timed out).

  On the SAA, including the "logging console notifications" value, I notice the following message is displayed:

  "% 305013-5-ASA: rules asymmetrical NAT matched for flows forward and backward; "Connection for icmp src, dst outside: 10.45.99.100 inside: 10.45.7.2 (type 8, code 0) rejected due to the failure of reverse path of NAT.

  I have a vague feeling that I'm missing a NAT rule of course, but not all. What did I miss?

  Here is my configuration of ASA: http://pastebin.com/raw.php?i=ad6p1Zac

  Hello

  You seem to have a configured ACL NAT0 but is not actually in use with a command "nat"

  You would probably need

  NAT (inside) 0-list of access inside_nat0_outside

  He must manage the NAT0

  Personally, I would avoid using large subnets/networks. You probably won't ever have host behind ASA who would fill / 16 subnet mask.

  I would also keep the pool VPN as a separate network from LANs behind ASA. The LAN 10.45.0.0/16 and 10.45.99.100 - 200 are on the same network.

  -Jouni

• Remote access VPN clients

  Hello

  I've set up IPSec VPN remotely and it works fine. I need access to connected VPN clients, and it does not work. I have already added an entry to traffic allowing sheep ACL from inside my network to the VPN.

  More information:

  Inside of the net: 10.1.1.0/24

  Pool VPN: 172.30.1.0/24

  Is it possible to access from my internal network to the VPN users?

  Thanks in advance.

  Best regards.

  Marcelo

  VPN users have access to certain servers via the list of Tunnel from Split.

  Marcelo,

  Split tunnel ACLs must be an IP acl, it is not recommended and supported to set the TCP ports on the split tunnel ACL, the vpn client don't interpret this ACl as a lot are interested in IP, TCP ports, and that could cause you a problem. You can change your config to reflect this. Regarding ACL split tunnel, it must contain the server line. networks that this vpn, customers arrive, remind you this is two-way, as you know.

  So if IT supports the IP range is on this vpnExample ACL vpn clients will be able to reach the IT support guys and vice versa.

  I advise you to change your split tunnel ACLs to specific ports to only the desired servers and the presenters what these customers need to achieve.

  Remove the ports out of this Split tunnel ACLs.

  If you need to restrict services for vpn rather clients use VPN filters.

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

• Select the timeout on ASA Cisco Anyconnect VPN

  Hello world

  I use the Cisco Anyconnect VPN client with the ASA 5540 firewall. I need allow a time-out on the VPN clients, so they log off after x hours of inactivity.

  Thank you to

  Best respect

  Hello

  To my understanding of the default timeout value is 30 minutes

  You should be able to change this setting in the "username" configurations (if you use LOCAL AAA on the SAA) or under the configurations of the 'group policy' .

  The command is

  VPN-idle-timeout

  Here is the link of the commands reference

  http://www.Cisco.com/c/en/us/TD/docs/security/ASA/ASA-command-reference/...

  -Jouni

• Syntax error of ACLs in PIX list after upgrade, need urgent help!

  Hello everyone

  We have a facility including Cisco ACS + a VPN 3005 concentrator and a PIX 515E (7.2.4)

  We have improved the version 7.0 to 7.2.4 PIX and suddenly our downloadable access list has been getting refused when authenticated users against GBA.

  What radius of debugging in the PIX we found typing this line in the list of downloadable access gives the error and prevent users from the ACL list.

  "deny ip any 192.168.0.0 0.0.255.255.

  PIX refused to treat their auth request when it encounters this line.

  Very well, we said, we changed the ACL syntax for that: deny ip any 192.168.0.0 255.255.0.0

  Does the PIX treat the ACL.

  We were happy to some time until what VPN users started complaining.

  It seems that the VPN 3005 cannot process the syntax we entered the PIX!

  VPN 3005 does not seem to be able to manage the acl line "deny ip any 192.168.0.0 255.255.0.0.

  It can handle that "deny ip any 192.168.0.0 0.0.255.255!

  Who cannot manage the PIX...

  I am a loss for what to do here...

  We got the VPN users who cannot surf now with these problems of ACL.

  What can I do? Someone else encountered this?

  We have improved the VPN 3005 to the latest SW version

  Really need help here guys!

  Thank you

  I don't think that Cisco has never changed anything on the PIX. It uses from day one subnet masks as far as I KNOW and Conc VPN use masks with joker as IOS. You can use the convert-netmask-acl command on the SAA to solve this problem. In this way, you define a willdcard ACL on the ACS/AAA server, then use this command on the ASA to use the downloadable ACLs even for both devices (PIX, VPNC).

  http://www.Cisco.com/en/us/docs/security/ASA/asa81/command/ref/A2.html#wp1622944

  Please note so useful.

  Concerning

  Farrukh