天亮了说晚安's Blog

本文转自：https://www.cisco.com/c/en/us/td/docs/security/asa/asa98/configuration/vpn/asa-98-vpn-config/vpn-l2tp-ipsec.html Chapter: L2TP over IPsec Chapter Contents This chapter describes how to configure L2TP over IPsec/IKEv1 on the ASA. About L2TP over IPsec/IKEv1 VPNLicensing Requirements for L2TP over IPsecPrerequisites for Configuring L2TP over IPsecGuidelines and LimitationsConfiguring L2TP over Eclipse with CLIFeature History for L2TP over IPsec About L2TP over IPsec/IKEv1 VPN Layer 2 Tunneling Protocol (L2TP) is a VPN tunneling protocol that allows remote clients to use the public IP network to securely communicate with private corporate network servers. L2TP uses PPP over UDP (port 1701) to tunnel the data. L2TP protocol is based on the client/server model. The function is divided between the L2TP Network Server (LNS), and the L2TP Access Concentrator (LAC). The LNS typically runs on a network gateway such as a router, while the LAC can be a dial-up Ne......Read More

本文转自：https://www.cisco.com/c/en/us/td/docs/security/asa/asa98/configuration/vpn/asa-98-vpn-config/vpn-ike.html Chapter: IPsec and ISAKMP Chapter Contents About Tunneling, IPsec, and ISAKMPLicensing for IPsec VPNsGuidelines for IPsec VPNsConfigure IPsec About Tunneling, IPsec, and ISAKMP This topic describes the Internet Protocol Security (IPsec) and the Internet Security Association and Key Management Protocol (ISAKMP) standards used to build Virtual Private Networks (VPNs). Tunneling makes it possible to use a public TCP/IP network, such as the Internet, to create secure connections between remote users and a private corporate network. Each secure connection is called a tunnel. The ASA uses the ISAKMP and IPsec tunneling standards to build and manage tunnels. ISAKMP and IPsec accomplish the following: Negotiate tunnel parametersEstablish tunnelsAuthenticate users and dataManage security keysEncrypt and decrypt dataManage data transfer across the tunnel......Read More

本文转自：https://blog.csdn.net/u010531676/article/details/79733901 能找到这里，都是用Cisco VPN ，然后出现442错误吧。     说下我的情况，我这里本来是解决了一次，能连回公司，但昨天升到Win 10 1709时，开机看到提示说Cisco VPN不安全还是怎样，然后VPN服务被移除了。然后在控制面板修复了Cisco VPN，连接时就出现442。     先贴下可能帮你解决问题的链接：     1.https://supportforums.cisco.com/t5/vpn/reason-442-failed-to-enable-virtual-adapter-windows-7-64-bit/td-p/1782751     2.https://blog.csdn.net/gotomic/article/details/8113536     第三个是解决我的问题的原始链接，注册表的问题：Solved     解决步骤：         1.打开注册表中心 （Win + R , 输入regeidt );         2.在注册表中定位到 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CVirtA，双击右边”DisplayName”,将”Cisco Systems VPN Adapter for 64-bit Windows&......Read More

本文转自： https://blog.csdn.net/chentaocba/article/details/7704918 学防火墙必知的几个概念 一、区域概念（接口区域） 1、 TRUST 信任区域 UNTRUST 非信任区域 DMZ 非军事区 2、 INSIDE 信任区域 OUSIDE 非信任区域 DMZ 非军事区 二、接口模式 transparent模式：（透明模式） 在transparent模式下，设备检查通过防火墙的数据包，但并不改变ip包头中的任何源地址和目的地址信息。因为它不改变地址，所以保护网内的ip必须在untrust连接的网络内是有效且可寻路的，untrust很可能就接互连网了。 在transparent模式下，对于trust区和untrust区的ip地址就设为0.0.0.0，这样可以使防火墙在网络中不可见。但是，防火墙、vpn和流量管理还是要通过配置设备的策略来生效。防火墙相当于一个2层交换机（2层交换机本身是没有ip地址的）。 route模式（路由模式） 当设备处于route模式下，每一个接口都被设立为route模式或nat模式。不像transparent模式，所有的网口都处于不同的子网当中。这个网口处理通过的流量时不nat，即ip包头中的源地址和端口号都保持不变 NAT模式：（地址转换模式） 当一个网口处于nat模式，防火墙会把从trust口往外的ip包中的源......Read More

本文转自： https://blog.csdn.net/chentaocba/article/details/7716109 要想配置思科的防火墙得先了解这些命令：　　常用命令有：nameif、interface、ip address、nat、global、route、static等。　　global　　指定公网地址范围：定义地址池。　　Global命令的配置语法：　　global (if_name) nat_id ip_address-ip_address [netmark global_mask]　　其中：　　(if_name)：表示外网接口名称，一般为outside。　　nat_id：建立的地址池标识(nat要引用)。　　ip_address-ip_address：表示一段ip地址范围。　　[netmark global_mask]：表示全局ip地址的网络掩码。　　nat　　地址转换命令，将内网的私有ip转换为外网公网ip。　　nat命令配置语法：nat (if_name) nat_id local_ip [netmark]　　其中：　　(if_name)：表示接口名称，一般为inside.　　nat_id： 表示地址池，由global命令定义。　　local_ip： 表示内网的ip地址。对于0.0.0.0表示内网所有主机。　　[netmark]：表示内网ip地址的子网掩码。　　route　　route命令定义静态路由。　　语法：　　route (if_name) 0 0 gateway_ip [metric]　　其中：　　(if_name)：表示接口名称。　　0 0 ：表示所有主机　　......Read More

本文转自：https://www.petenetlive.com/KB/Article/0000039 Problem You want to set up a Cisco ASA to authenticate users (VPN access for example). Solution Kerberos can only be used as an authentication protocol on the ASA, so its fine for allowing VPN connections but not for assigning policies etc. To work both the ASA and the domain need to be showing accurate time. Step 1: Set the ASA to get time from an External NTP Server 1. Log onto the ASA > Go to “Enable Mode” > Issue the following command; User Access Verification Password: Type help or '?' for a list of available commands. Petes-ASA> enable Password: ******** Petes-ASA# configure terminal Petes-ASA(config)# ntp server 130.88.212.143 source outside Note that’s a public time server in the UK (Manchester University) that I use. you may want to use another. 2. To check the ASA has synchronised issue the a ‘show ntp status‘ command, If you s......Read More

本文转自：https://www.petenetlive.com/KB/Article/0001104 Problem I got sent to Holland this week to look at a firewall deployment, and while I was sat in the Airport, I was going over the job I had to do, when I realised the solution I had suggested had a problem see below; My brief was to provide remote AnyConnect VPN into the network so the client could get their network setup, and manage things remotely. However as I drew the network out in my head I realised that the situation above was what was going to happen. How was I going to fix that? Well firstly I thought ‘Just put 192.16.1.1 on the management firewall, and move .2 and .3 to the main firewalls’. Well thats fine, but it does not leave me room for expansion, or if the client needs to add remote access to a production network. (Which will be needed in the future). Then I thought ‘Can I put a static route on the main firewalls to route 192.168.100.0/24 to the management firewall’. Which is a......Read More

本文转自：https://www.petenetlive.com/KB/Article/0000069 Problem Below is a walk through for setting up a client to gateway VPN Tunnel using a Cisco ASA appliance.This was done via the ASDM console. The video was shot with ASA version 8.4(2) and ASDM 6.4(5) and the setup process is a lot less painful than it used to be. The original article was written with ASA version 8.0(4) and ASDM 6.1(3), which was a little more difficult so I will leave that procedure below just in case 🙂 ASDM cannot be used on the normal port on the outside interface when using SSL VPN SSL VPN AnyConnect from within an RDP session is not supported (and fails – even with a /console switch). SSL (HTTPS ot TCPport 443) needs to be free (i.e. NOT port forwarded to a web server / exchange server etc). Solution For Older Versions of the ASA/ASDM 1. Open up the&nbs......Read More

本文转自：https://www.petenetlive.com/KB/Article/0000628 Problem Note: With Anyconnect 4 Cisco now use Plus and Apex AnyConnect licensing. When Cisco released the 8.2 version of the ASA code, they changed their licensing model for AnyConnect Licenses. There are two licensing models, Premium and Essentials. Solution Cisco ASA AnyConnect Premium Licenses. You get two of these free with your firewall*, with a ‘Premium License’ you can use the AnyConnect client software for remote VPN Access, and you can access Clientless SSL facilities via the web portal. *As pointed out by @nhomsany “The two default premium licenses available are NOT cross-platform, (i.e. only Mac or Windows). Additionally you can use this license’ model with the Advanced Endpoint Assessment License’, this is the license’ you require for Cisco Secure Desktop. You can also use this license’......Read More