词条 | Virtual private network |
释义 |
A virtual private network (VPN) extends a private network across a public network, and enables users to send and receive data across shared or public networks as if their computing devices were directly connected to the private network. Applications running across a VPN may therefore benefit from the functionality, security, and management of the private network. Encryption is a common though not an inherent part of a VPN connection.[1] VPN technology was developed to allow remote users and branch offices to access corporate applications and resources. To ensure security, the private network connection is established using an encrypted layered tunneling protocol and VPN users use authentication methods, including passwords or certificates, to gain access to the VPN. In other applications, Internet users may secure their transactions with a VPN, to circumvent geo-restrictions and censorship, or to connect to proxy servers to protect personal identity and location to stay anonymous on the Internet. However, some websites block access to known VPN technology to prevent the circumvention of their geo-restrictions, and many VPN providers have been developing strategies to get around these roadblocks. A VPN is created by establishing a virtual point-to-point connection through the use of dedicated circuits or with tunneling protocols over existing networks. A VPN available from the public Internet can provide some of the benefits of a wide area network (WAN). From a user perspective, the resources available within the private network can be accessed remotely.[2] TypesEarly data networks allowed VPN-style connections to remote sites through dial-up modem or through leased line connections utilizing X.25, Frame Relay and Asynchronous Transfer Mode (ATM) virtual circuits, provided through networks owned and operated by telecommunication carriers. These networks are not considered true VPNs because they passively secure the data being transmitted by the creation of logical data streams.[3] They have been replaced by VPNs based on IP and IP/Multi-protocol Label Switching (MPLS) Networks, due to significant cost-reductions and increased bandwidth[4] provided by new technologies such as digital subscriber line (DSL)[5] and fiber-optic networks. VPNs can be characterized as host-to-network or remote access by connecting a single computer to a network, or as site-to-site for connecting two networks. In a corporate setting, remote-access VPNs allow employees to access the company's intranet from outside the office. Site-to-site VPNs allow collaborators in geographically disparate offices to share the same virtual network. A VPN can also be used to interconnect two similar networks over a dissimilar intermediate network; for example, two IPv6 networks over an IPv4 network.[6] VPN systems may be classified by:
Security mechanismsVPNs cannot make online connections completely anonymous, but they can usually increase privacy and security. To prevent disclosure of private information, VPNs typically allow only authenticated remote access using tunneling protocols and encryption techniques. The VPN security model provides:
Secure VPN protocols include the following:
AuthenticationTunnel endpoints must be authenticated before secure VPN tunnels can be established. User-created remote-access VPNs may use passwords, biometrics, two-factor authentication or other cryptographic methods. Network-to-network tunnels often use passwords or digital certificates. They permanently store the key to allow the tunnel to establish automatically, without intervention from the administrator. RoutingTunneling protocols can operate in a point-to-point network topology that would theoretically not be considered as a VPN, because a VPN by definition is expected to support arbitrary and changing sets of network nodes. But since most router implementations support a software-defined tunnel interface, customer-provisioned VPNs often are simply defined tunnels running conventional routing protocols. Provider-provisioned VPN building-blocksDepending on whether a provider-provisioned VPN (PPVPN) operates in layer 2 or layer 3, the building blocks described below may be L2 only, L3 only, or combine them both. Multi-protocol label switching (MPLS) functionality blurs the L2-L3 identity.{{citation needed|date=June 2013}}{{original research inline|date=June 2013}} {{IETF RFC|4026}} generalized the following terms to cover L2 and L3 VPNs, but they were introduced in {{IETF RFC|2547}}.[15] More information on the devices below can also be found in Lewis, Cisco Press.[16]
A device that is within a customer's network and not directly connected to the service provider's network. C devices are not aware of the VPN.
A device at the edge of the customer's network which provides access to the PPVPN. Sometimes it is just a demarcation point between provider and customer responsibility. Other providers allow customers to configure it.
A PE is a device, or set of devices, at the edge of the provider network which connects to customer networks through CE devices and presents the provider's view of the customer site. PEs are aware of the VPNs that connect through them, and maintain VPN state.
A P device operates inside the provider's core network and does not directly interface to any customer endpoint. It might, for example, provide routing for many provider-operated tunnels that belong to different customers' PPVPNs. While the P device is a key part of implementing PPVPNs, it is not itself VPN-aware and does not maintain VPN state. Its principal role is allowing the service provider to scale its PPVPN offerings, for example, by acting as an aggregation point for multiple PEs. P-to-P connections, in such a role, often are high-capacity optical links between major locations of providers. User-visible PPVPN servicesOSI Layer 2 services{{refimprove section|date=August 2016}}
Virtual LAN (VLAN) is a Layer 2 technique that allow for the coexistence of multiple local area network (LAN) broadcast domains, interconnected via trunks using the IEEE 802.1Q trunking protocol. Other trunking protocols have been used but have become obsolete, including Inter-Switch Link (ISL), IEEE 802.10 (originally a security protocol but a subset was introduced for trunking), and ATM LAN Emulation (LANE).
Developed by Institute of Electrical and Electronics Engineers, Virtual LANs (VLANs) allow multiple tagged LANs to share common trunking. VLANs frequently comprise only customer-owned facilities. Whereas VPLS as described in the above section (OSI Layer 1 services) supports emulation of both point-to-point and point-to-multipoint topologies, the method discussed here extends Layer 2 technologies such as 802.1d and 802.1q LAN trunking to run over transports such as Metro Ethernet. As used in this context, a VPLS is a Layer 2 PPVPN, emulating the full functionality of a traditional LAN. From a user standpoint, a VPLS makes it possible to interconnect several LAN segments over a packet-switched, or optical, provider core; a core transparent to the user, making the remote LAN segments behave as one single LAN.[17] In a VPLS, the provider network emulates a learning bridge, which optionally may include VLAN service.
PW is similar to VPLS, but it can provide different L2 protocols at both ends. Typically, its interface is a WAN protocol such as Asynchronous Transfer Mode or Frame Relay. In contrast, when aiming to provide the appearance of a LAN contiguous between two or more locations, the Virtual Private LAN service or IPLS would be appropriate.
EtherIP ({{IETF RFC|3378}})[18] is an Ethernet over IP tunneling protocol specification. EtherIP has only packet encapsulation mechanism. It has no confidentiality nor message integrity protection. EtherIP was introduced in the FreeBSD network stack[19] and the SoftEther VPN[20] server program.
A subset of VPLS, the CE devices must have Layer 3 capabilities; the IPLS presents packets rather than frames. It may support IPv4 or IPv6. OSI Layer 3 PPVPN architecturesThis section discusses the main architectures for PPVPNs, one where the PE disambiguates duplicate addresses in a single routing instance, and the other, virtual router, in which the PE contains a virtual router instance per VPN. The former approach, and its variants, have gained the most attention. One of the challenges of PPVPNs involves different customers using the same address space, especially the IPv4 private address space.[21] The provider must be able to disambiguate overlapping addresses in the multiple customers' PPVPNs.
In the method defined by {{IETF RFC|2547}}, BGP extensions advertise routes in the IPv4 VPN address family, which are of the form of 12-byte strings, beginning with an 8-byte route distinguisher (RD) and ending with a 4-byte IPv4 address. RDs disambiguate otherwise duplicate addresses in the same PE. PEs understand the topology of each VPN, which are interconnected with MPLS tunnels, either directly or via P routers. In MPLS terminology, the P routers are Label Switch Routers without awareness of VPNs.
The virtual router architecture,[22][23] as opposed to BGP/MPLS techniques, requires no modification to existing routing protocols such as BGP. By the provisioning of logically independent routing domains, the customer operating a VPN is completely responsible for the address space. In the various MPLS tunnels, the different PPVPNs are disambiguated by their label, but do not need routing distinguishers. Unencrypted tunnelsSome virtual networks use tunneling protocols without encryption for protecting the privacy of data. While VPNs often do provide security, an unencrypted overlay network does not neatly fit within the secure or trusted categorization.[24] For example, a tunnel set up between two hosts with Generic Routing Encapsulation (GRE) is a virtual private network, but neither secure nor trusted.[25][26] Native plaintext tunneling protocols include Layer 2 Tunneling Protocol (L2TP) when it is set up without IPsec and Point-to-Point Tunneling Protocol (PPTP) or Microsoft Point-to-Point Encryption (MPPE).[27] Trusted delivery networksTrusted VPNs do not use cryptographic tunneling, and instead rely on the security of a single provider's network to protect the traffic.[28]
From the security standpoint, VPNs either trust the underlying delivery network, or must enforce security with mechanisms in the VPN itself. Unless the trusted delivery network runs among physically secure sites only, both trusted and secure models need an authentication mechanism for users to gain access to the VPN. VPNs in mobile environmentsUsers utilize mobile virtual private networks in settings where an endpoint of the VPN is not fixed to a single IP address, but instead roams across various networks such as data networks from cellular carriers or between multiple Wi-Fi access points without dropping the secure VPN session or losing application sessions.[32] Mobile VPNs are widely used in public safety, where they give law-enforcement officers access to applications such as computer-assisted dispatch and criminal databases[33], and in other organizations with similar requirements such as Field service management and healthcare[34]{{qn|date=June 2018}}. VPN on routersWith the increasing use of VPNs, many have started deploying VPN connectivity on routers for additional security and encryption of data transmission by using various cryptographic techniques.[35] Home users usually deploy VPNs on their routers to protect devices, such as smart TV Many router manufacturers supply routers with built-in VPN clients. Some use open-source firmware such as DD-WRT, OpenWRT and Tomato, in order to support additional protocols such as OpenVPN. Setting up VPN services on a router requires a deep knowledge of network security and careful installation. Minor misconfiguration of VPN connections can leave the network vulnerable. Performance will vary depending on the Internet service provider (ISP).[37] Networking limitationsA limitation of traditional VPNs is that they are point-to-point connections, and do not tend to support broadcast domains. Therefore, communication, software, and networking, which are based on layer 2 and broadcast packets, such as NetBIOS used in Windows networking, may not be fully supported as on a local area network. Variants on VPN, such as Virtual Private LAN Service (VPLS), and layer 2 tunneling protocols, are designed to overcome this limitation.{{citation needed|date=April 2018}} See also
References1. ^{{cite book |author= Mason, Andrew G. |title=Cisco Secure Virtual Private Network |publisher= Cisco Press |date= 2002 |page= 7}} 2. ^{{cite web |publisher= Microsoft Technet |title= Virtual Private Networking: An Overview |url= https://technet.microsoft.com/en-us/library/bb742566.aspx |date=September 4, 2001}} 3. ^Cisco Systems, et al. Internet working Technologies Handbook, Third Edition. Cisco Press, 2000, p. 232. 4. ^Lewis, Mark. Comparing, Designing. And Deploying VPNs. Cisco Press, 2006, p. 5 5. ^International Engineering Consortium. Digital Subscriber Line 2001. Intl. Engineering Consortium, 2001, p. 40. 6. ^{{cite web|last=Technet Lab |title=IPv6 traffic over VPN connections |url=http://lab.technet.microsoft.com/en-us/magazine/cc138002 |deadurl=yes |archiveurl=https://web.archive.org/web/20120615203602/http://lab.technet.microsoft.com/en-us/magazine/cc138002 |archivedate=15 June 2012 |df= }} 7. ^{{IETF RFC|6434}}, "IPv6 Node Requirements", E. Jankiewicz, J. Loughney, T. Narten (December 2011) 8. ^{{cite web|url=http://www.softether.org/1-features/1._Ultimate_Powerful_VPN_Connectivity#SoftEther_VPN's_Solution:_Using_HTTPS_Protocol_to_Establish_VPN_Tunnels|title=1. Ultimate Powerful VPN Connectivity |publisher=SoftEther VPN Project|website=www.softether.org}} 9. ^{{cite web |url=http://www.infradead.org/openconnect/index.html |title = OpenConnect |accessdate =2013-04-08 |quote =OpenConnect is a client for Cisco's AnyConnect SSL VPN [...] OpenConnect is not officially supported by, or associated in any way with, Cisco Systems. It just happens to interoperate with their equipment.}} 10. ^{{Cite web|url=http://sites.inka.de/~W1011/devel/tcp-tcp.html|title=Why TCP Over TCP Is A Bad Idea|website=sites.inka.de|access-date=2018-10-24}} 11. ^{{cite web|url=http://tarr.uspto.gov/servlet/tarr?regser=serial&entry=78063238&action=Request+Status|title=Trademark Status & Document Retrieval|website=tarr.uspto.gov}} 12. ^{{cite web|url=https://man.openbsd.org/ssh.1#SSH-BASED_VIRTUAL_PRIVATE_NETWORKS|title=ssh(1) – OpenBSD manual pages|website=man.openbsd.org}} 13. ^{{cite web|url=http://cb.vu/unixtoolbox.xhtml#vpn|title=Unix Toolbox|first=Colin Barschel|last=c@cb.vu|website=cb.vu}} 14. ^{{cite web|url=https://help.ubuntu.com/community/SSH_VPN|title=SSH_VPN – Community Help Wiki|website=help.ubuntu.com}} 15. ^{{cite news |url=http://www.ietf.org/rfc/rfc2547.txt |rfc=2547 |title=BGP/MPLS VPNs |author=E. Rosen & Y. Rekhter |date=March 1999 |publisher=Internet Engineering Task Force (IETF) }} 16. ^{{cite book|last=Lewis|first=Mark|title=Comparing, designing, and deploying VPNs|year=2006|publisher=Cisco Press|location=Indianapolis, Ind.|isbn=1587051796|pages=5–6|edition=1st print.}} 17. ^{{citation |url=http://openvpn.net/index.php/access-server/howto-openvpn-as/214-how-to-setup-layer-2-ethernet-bridging.html |title=Ethernet Bridging (OpenVPN)}} 18. ^{{cite web|url=http://tools.ietf.org/search/rfc3378|title=EtherIP: Tunneling Ethernet Frames in IP Datagrams|first1=Scott|last1=Hollenbeck|first2=Russell|last2=Housley|publisher=}} 19. ^Glyn M Burton: [https://securethoughts.com/9-rfc-3378-etherip-with-freebsd/ RFC 3378 EtherIP with FreeBSD], 03 February 2011 20. ^net-security.org news: Multi-protocol SoftEther VPN becomes open source, January 2014 21. ^Address Allocation for Private Internets, {{IETF RFC|1918}}, Y. Rekhter et al., February 1996 22. ^{{IETF RFC|2917}}, A Core MPLS IP VPN Architecture 23. ^{{IETF RFC|2918}}, E. Chen (September 2000) 24. ^{{Cite journal|last=Yang|first=Yanyan|date=2006|title=IPsec/VPN security policy correctness and assurance|url=http://eds.a.ebscohost.com/eds/pdfviewer/pdfviewer?vid=28&sid=c9456fca-f448-407a-b7a2-d71291936697%40sessionmgr4009|journal=Journal of High Speed Networks|volume=15|pages=275-289|via=}} 25. ^{{cite web |title=Overview of Provider Provisioned Virtual Private Networks (PPVPN) |url=https://securethoughts.com/overview-provider-provisioned-virtual-private-networks-ppvpn/ |publisher=Secure Thoughts |accessdate = 29 August 2016}} 26. ^{{IETF RFC|1702}}: Generic Routing Encapsulation over IPv4 networks. October 1994. 27. ^IETF (1999), {{IETF RFC|2661}}, Layer Two Tunneling Protocol "L2TP" 28. ^{{cite book| author =Cisco Systems, Inc.| title =Internetworking Technologies Handbook| url =https://books.google.com/books?id=3Dn9KlIVM_EC| accessdate =2013-02-15| edition =4| series =Networking Technology Series| year =2004| publisher =Cisco Press| isbn =9781587051197| page =233| quote =[...] VPNs using dedicated circuits, such as Frame Relay [...] are sometimes called trusted VPNs, because customers trust that the network facilities operated by the service providers will not be compromised.}} 29. ^Layer Two Tunneling Protocol "L2TP", {{IETF RFC|2661}}, W. Townsley et al., August 1999 30. ^IP Based Virtual Private Networks, {{IETF RFC|2341}}, A. Valencia et al., May 1998 31. ^Point-to-Point Tunneling Protocol (PPTP), {{IETF RFC|2637}}, K. Hamzeh et al., July 1999 32. ^Phifer, Lisa. "Mobile VPN: Closing the Gap", SearchMobileComputing.com, July 16, 2006. 33. ^Willett, Andy. "Solving the Computing Challenges of Mobile Officers", www.officer.com, May, 2006. 34. ^Cheng, Roger. [https://www.wsj.com/articles/SB119717610996418467 "Lost Connections"], The Wall Street Journal, December 11, 2007. 35. ^{{cite web|title = Encryption and Security Protocols in a VPN|url = http://computer.howstuffworks.com/vpn7.htm|accessdate = 2015-09-23}} 36. ^{{cite web |title=VPN |website=Draytek |date= |url=http://www.draytek.co.uk/information/our-technology/vpn-overview |author= |accessdate= 19 October 2016}} 37. ^{{Cite news|url=https://searchenterprisewan.techtarget.com/answer/How-can-incorrectly-configuring-VPN-clients-lead-to-a-security-breach|title=How can incorrectly configuring VPN clients lead to a security breach?|work=SearchEnterpriseWAN|access-date=2018-08-14|language=en-US}} Further reading
5 : Network architecture|Computer network security|Internet privacy|Crypto-anarchism|Virtual private networks |
随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识,基本涵盖了大多数领域的百科知识,是一部内容自由、开放的电子版国际百科全书。