Virtual private network

1
Virtual private network
VPN connectivity overview
A virtual private network (VPN) extends a
private network across a public network, such as
the Internet. It enables a computer to send and
receive data across shared or public networks as if
it were directly connected to the private network,
while benefiting from the functionality, security
and management policies of the private network.
[1]
This is done by establishing a virtual point-to-point
connection through the use of dedicated
connections, encryption, or a combination of the
two.
A VPN connection across the Internet is similar to
a wide area network (WAN) link between the sites.
From a user perspective, the extended network
resources are accessed in the same way as resources available from the private network.
VPNs allow employees to securely access their company's intranet while traveling outside the office. Similarly,
VPNs securely and cost-effectively connect geographically disparate offices of an organization, creating one
cohesive virtual network. VPN technology is also used by ordinary Internet users to connect to proxy servers for the
purpose of protecting one's identity.
Types
Early data networks allowed VPN-style remote connectivity through dial-up modems or through leased line
connections utilizing Frame Relay and Asynchronous Transfer Mode (ATM) virtual circuits, provisioned through a
network 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.
[2]
They have given way to
VPNs based on IP and IP/Multiprotocol Label Switching Networks (MPLS), due to significant cost-reductions and
increased bandwidth
[3]
provided by new technologies such as Digital Subscriber Line (DSL)
[4]
and fiber-optic
networks.
VPNs can be either remote-access (connecting an individual computer to a network) or site-to-site (connecting two
networks together). In a corporate setting, remote-access VPNs allow employees to access their company's intranet
from home or while traveling outside the office, and site-to-site VPNs allow employees in geographically disparate
offices to share one cohesive virtual network. A VPN can also be used to interconnect two similar networks over a
dissimilar middle network; for example, two IPv6 networks over an IPv4 network.
VPN systems may be classified by:
the protocols used to tunnel the traffic.
the tunnel's termination point location, e.g., on the customer edge or network-provider edge.
whether they offer site-to-site or remote-access connectivity.
the levels of security provided.
the OSI layer they present to the connecting network, such as Layer 2 circuits or Layer 3 network connectivity.
Internet VPN
lntemet
Remote! roaming users
Internet VPN
lntemet
Remote! roaming users
Internet VPN
lntemet
Remote! roaming users
Virtual private network
2
Security mechanisms
To prevent disclosure of private information, VPNs typically allow only authenticated remote access and make use
of encryption techniques.
VPNs provide security by the use of tunneling protocols and through security procedures such as encryption. The
VPN security model provides:
confidentiality such that even if the network traffic is sniffed at the packet level (see network sniffer and Deep
packet inspection), an attacker would only see encrypted data
sender authentication to prevent unauthorized users from accessing the VPN.
message integrity to detect any instances of tampering with transmitted messages
Secure VPN protocols include the following:
Internet Protocol Security (IPsec) as initially developed by the Internet Engineering Task Force (IETF) for IPv6,
which was required in all standards-compliant implementations of IPv6 before RFC 6434 made it only a
recommendation.
[5]
This standards-based security protocol is also widely used with IPv4 and the Layer 2
Tunneling Protocol. Its design meets most security goals: authentication, integrity, and confidentiality. IPsec uses
encryption, encapsulating an IP packet inside an IPsec packet. De-encapsulation happens at the end of the tunnel,
where the original IP packet is decrypted and forwarded to its intended destination.
Transport Layer Security (SSL/TLS) can tunnel an entire network's traffic (as it does in the OpenVPN project) or
secure an individual connection. A number of vendors provide remote-access VPN capabilities through SSL. An
SSL VPN can connect from locations where IPsec runs into trouble with Network Address Translation and
firewall rules.
Datagram Transport Layer Security (DTLS) - used in Cisco AnyConnect VPN and in OpenConnect VPN to solve
the issues SSL/TLS has with tunneling over UDP.
Microsoft Point-to-Point Encryption (MPPE) works with the Point-to-Point Tunneling Protocol and in several
compatible implementations on other platforms.
Microsoft Secure Socket Tunneling Protocol (SSTP) tunnels Point-to-Point Protocol (PPP) or Layer 2 Tunneling
Protocol traffic through an SSL 3.0 channel. (SSTP was introduced in Windows Server 2008 and in Windows
Vista Service Pack 1.)
Multi Path Virtual Private Network (MPVPN). Ragula Systems Development Company owns the registered
trademark "MPVPN".
[6]
Secure Shell (SSH) VPN - OpenSSH offers VPN tunneling (distinct from port forwarding) to secure remote
connections to a network or to inter-network links. OpenSSH server provides a limited number of concurrent
tunnels. The VPN feature itself does not support personal authentication.
[7][8][9]
Authentication
Tunnel endpoints must authenticate 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 user.
Virtual private network
3
Example use of a VPN tunnel
The following steps illustrate the principles of a VPN client-server interaction in simple terms are:
Assume a remote host with public IP address 1.2.3.4 wishes to connect to a server found inside a company network.
The server has internal address 192.168.1.10 and is not reachable publicly. Before the client can reach this server, it
needs to go through a VPN server / firewall device that has public IP address 5.6.7.8 and an internal address of
192.168.1.1. All data between the client and the server will need to be kept confidential, hence a secure VPN is used.
1. 1. The VPN client connects to a VPN server via an external network interface.
2. The VPN server assigns an IP address to the VPN client from the VPN server's subnet. The client gets internal IP
address 192.168.1.50, for example, and creates a virtual network interface through which it will send encrypted
packets to the other tunnel endpoint (the device at the other end of the tunnel). (This interface also gets the
address 192.168.1.50.)
3. 3. When the VPN client wishes to communicate with the company server, it prepares a packet addressed to
192.168.1.10, encrypts it and encapsulates it in an outer VPN packet, say an IPSec packet. This packet is then sent
to the VPN server at IP address 5.6.7.8 over the public Internet. The inner packet is encrypted so that even if
someone intercepts the packet over the Internet, they cannot get any information from it. They can see that the
remote host is communicating with a server/firewall, but none of the contents of the communication. The inner
encrypted packet has source address 192.168.1.50 and destination address 192.168.1.10. The outer packet has
source address 1.2.3.4 and destination address 5.6.7.8.
4. 4. When the packet reaches the VPN server from the Internet, the VPN server extracts the inner packet, decrypts it,
finds the destination address to be 192.168.1.10, and forwards it to the intended server at 192.168.1.10.
5. After some time, the VPN server receives a reply packet from 192.168.1.10, intended for 192.168.1.50. The VPN
server consults its routing table, and sees this packet is intended for a remote host that must go through VPN.
6. 6. The VPN server encrypts this reply packet, encapsulates it in a VPN packet and sends it out over the Internet. The
inner encrypted packet has source address 192.168.1.10 and destination address 192.168.1.50. The outer VPN
packet has source address 5.6.7.8 and destination address 1.2.3.4.
7. 7. The remote host receives the packet. The VPN client extracts the inner packet, decrypts it, and passes it to the
appropriate software at upper layers.
Overall, it is as if the remote computer and company server are on the same 192.168.1.0/24 network.
Routing
Tunneling protocols can operate in a point-to-point network topology that would theoretically not be considered 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-blocks
Depending on whether a provider-provisioned VPN (PPVPN)Wikipedia:Please clarify operates in layer 2 or layer 3,
the building blocks described below may be L2 only, L3 only, or combine them both. Multiprotocol label switching
(MPLS) functionality blurs the L2-L3 identity.
[citation needed]
Wikipedia:No original research
RFC 4026 generalized the following terms to cover L2 and L3 VPNs, but they were introduced in RFC 2547. More
information on the devices below can also be found in Lewis, Cisco Press.
Customer (C) devices
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.
Customer Edge device (CE)
Virtual private network
4
A device at the edge of the customer's network which provides access to the PPVPN. Sometimes it's just a
demarcation point between provider and customer responsibility. Other providers allow customers to configure it.
Provider edge device (PE)
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.
Provider device (P)
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 services
This section deals with the types of VPN considered in the IETF.
OSI Layer 2 services
Virtual LAN
A Layer 2 technique that allows for the coexistence of multiple 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).
Virtual private LAN service (VPLS)
Developed by IEEE, 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, rather than a private line, emulating the full functionality of a
traditional local area network (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.
In a VPLS, the provider network emulates a learning bridge, which optionally may include VLAN service.
Pseudo wire (PW)
PW is similar to VPWS, 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.
IP-only LAN-like service (IPLS)
A subset of VPLS, the CE devices must have L3 capabilities; the IPLS presents packets rather than frames. It may
support IPv4 or IPv6.
Virtual private network
5
OSI Layer 3 PPVPN architectures
This 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.
[10]
The provider must be able to disambiguate overlapping addresses in the multiple
customers' PPVPNs.
BGP/MPLS PPVPN
In the method defined by 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.
Virtual router PPVPN
The Virtual Router architecture,
[11][12]
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.
Plaintext tunnels
Some virtual networks may not use encryption to protect the data contents. While VPNs often provide security, an
unencrypted overlay network does not neatly fit within the secure or trusted categorization. For example a tunnel set
up between two hosts that used Generic Routing Encapsulation (GRE) would in fact be a virtual private network, but
neither secure nor trusted.
Besides the GRE example above, 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).
Trusted delivery networks
Trusted VPNs do not use cryptographic tunneling, and instead rely on the security of a single provider's network to
protect the traffic.
Multi-Protocol Label Switching (MPLS) often overlays VPNs, often with quality-of-service control over a trusted
delivery network.
Layer 2 Tunneling Protocol (L2TP)
[13]
which is a standards-based replacement, and a compromise taking the
good features from each, for two proprietary VPN protocols: Cisco's Layer 2 Forwarding (L2F)
[14]
(obsolete as of
2009[15]) and Microsoft's Point-to-Point Tunneling Protocol (PPTP).
[16]
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.
Virtual private network
6
VPNs in mobile environments
Mobile VPNs are used in a setting 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.
[17]
Mobile VPNs have been widely used in public safety, where they give law enforcement officers access to
mission-critical applications, such as computer-assisted dispatch and criminal databases, while they travel between
different subnets of a mobile network.
[18]
They are also used in field service management and by healthcare
organizations,
[19]
among other industries.
Increasingly, mobile VPNs are being adopted by mobile professionals who need reliable connections. They are used
for roaming seamlessly across networks and in and out of wireless-coverage areas without losing application
sessions or dropping the secure VPN session. A conventional VPN cannot survive such events because the network
tunnel is disrupted, causing applications to disconnect, time out, or fail, or even cause the computing device itself to
crash.
Instead of logically tying the endpoint of the network tunnel to the physical IP address, each tunnel is bound to a
permanently associated IP address at the device. The mobile VPN software handles the necessary network
authentication and maintains the network sessions in a manner transparent to the application and the user. The Host
Identity Protocol (HIP), under study by the Internet Engineering Task Force, is designed to support mobility of hosts
by separating the role of IP addresses for host identification from their locator functionality in an IP network. With
HIP a mobile host maintains its logical connections established via the host identity identifier while associating with
different IP addresses when roaming between access networks.
References
[1] Mason, Andrew G. Cisco Secure Virtual Private Network. Cisco Press, 2002, p. 7
[2] Cisco Systems, et al.. Internet working Technologies Handbook, Third Edition. Cisco Press, 2000, p. 232.
[3] Lewis, Mark. Comparing, Designing. And Deploying VPNs. Cisco Press, 20069, p. 5
[4] International Engineering Consortium. Digital Subscriber Line 2001. Intl. Engineering Consortium, 2001, p. 40.
[5] [5] RFC 6434, "IPv6 Node Requirements", E. Jankiewicz, J. Loughney, T. Narten (December 2011)
[6] Trademark Applications and Registrations Retrieval (TARR) (http:/ / tarr. uspto. gov/ servlet/ tarr?regser=serial& entry=78063238&
action=Request+ Status)
[7] OpenBSD ssh manual page, VPN section (http:/ / www. openbsd. org/ cgi-bin/ man. cgi?query=ssh#SSH-BASED+ VIRTUAL)
[8] Unix Toolbox section on SSH VPN (http:/ / cb.vu/ unixtoolbox. xhtml#vpn)
[9] Ubuntu SSH VPN how-to (https:/ / help.ubuntu.com/ community/ SSH_VPN)
[10] Address Allocation for Private Internets (http:/ / www. ietf. org/ rfc/ rfc1918. txt), RFC 1918, Y. Rekhter et al.,February 1996
[11] RFC 2917, A Core MPLS IP VPN Architecture
[12] [12] RFC 2918, E. Chen (September 2000)
[13] Layer Two Tunneling Protocol "L2TP" (http:/ / www. ietf. org/ rfc/ rfc2661. txt), RFC 2661, W. Townsley et al.,August 1999
[14] IP Based Virtual Private Networks (http:/ / www. ietf.org/ rfc/ rfc2341. txt), RFC 2341, A. Valencia et al., May 1998
[15] http:/ / en. wikipedia. org/ w/ index. php?title=Virtual_private_network& action=edit
[16] Point-to-Point Tunneling Protocol (PPTP) (http:/ / www. ietf. org/ rfc/ rfc2637. txt), RFC 2637, K. Hamzeh et al., July 1999
[17] Phifer, Lisa. "Mobile VPN: Closing the Gap" (http:/ / searchmobilecomputing. techtarget. com/ tip/ 0,289483,sid40_gci1210989_mem1,00.
html), SearchMobileComputing.com, July 16, 2006.
[18] Willett, Andy. "Solving the Computing Challenges of Mobile Officers" (http:/ / www. officer. com/ print/ Law-Enforcement-Technology/
Solving-the-Computing-Challenges-of-Mobile-Officers/ 1$30992), www.officer.com, May, 2006.
[19] Cheng, Roger. "Lost Connections" (http:/ / online.wsj. com/ article/ SB119717610996418467. html), The Wall Street Journal, December
11, 2007.
Virtual private network
7
Further reading
Kelly, Sean (August 2001). "Necessity is the mother of VPN invention" (http:/ / web. archive. org/ web/
20011217153420/ http:/ / www. comnews. com/ cgi-bin/ arttop. asp?Page=c0801necessity. htm). Communication
News: 2628. ISSN 0010-3632 (http:/ / www. worldcat. org/ issn/ 0010-3632). Archived from the original (http:/
/ www. comnews. com/ cgi-bin/ arttop. asp?Page=c0801necessity. htm) on 2001-12-17.
"VPN Buyers Guide". Communication News: 3438. August 2001. ISSN 0010-3632 (http:/ / www. worldcat.
org/ issn/ 0010-3632).
External links
JANET UK "Different Flavours of VPN: Technology and Applications" (https:/ / www. ja. net/ sites/ default/
files/ Different Flavours of VPN Technology and Applications. pdf)
Virtual Private Network Consortium - a trade association for VPN vendors (http:/ / www. vpnc. org/ )
CShip VPN-Wiki/List (http:/ / en. cship. org/ wiki/ Virtual_Private_Network)
Virtual Private Networks (http:/ / www. microsoft. com/ vpn) on Microsoft TechNet
Creating VPNs with IPsec and SSL/TLS (http:/ / www. linuxjournal. com/ article/ 9916) Linux Journal article by
Rami Rosen
curvetun (http:/ / netsniff-ng. org) a lightweight curve25519-based multiuser IP tunnel / VPN
Virtual Private Networks - In Depth Technical Details (http:/ / www. rawbytes. com/
virtual-private-networks-in-depth-technical-details/ )
Using VPN to bypass internet censorship (http:/ / en. flossmanuals. net/ bypassing-censorship/
ch025_what-is-vpn/ ) in How to Bypass Internet Censorship (http:/ / www. howtobypassinternetcensorship. org/ ),
a FLOSS Manual, 10 March 2011, 240 pp
Article Sources and Contributors
8
Article Sources and Contributors
Virtual private network Source: http://en.wikipedia.org/w/index.php?oldid=586524230 Contributors: (, 1984, 2005, 33rogers, A.amitkumar, ARTamb, Aaron north, Abune, Acole67, Adi4094,
Aditya, Aeon17x, Agaffin, Alansohn, Aldie, AlewisGB, Alexamies, AlexeyN, Allstarecho, Alphawave, Alvestrand, Americaninseoul, Amux, AndreasJS, Andrew Gray, Andrewpmk, Angelbo,
Anirvan, Anon lynx, Anthony Appleyard, AnthonyJ Lock, Apankrat, Apothecia, Armando, Art LaPella, Ashwin ambekar, Ausinha, Avaarga, Az1568, Azadk, Azerrima, Barek, Barek-public,
Bbbone, Belmontian, Ben 9876, BenAveling, Bevo, Bewildebeast, BiT, Bigjust12345, BirdValiant, Bishopolis, Blacklogic, Blonkm, BlueJaeger, BlueNovember, Bmusician, Boardista, Bobo192,
Borgx, Bovineone, Brainix, Brandon, Braviojk, Brwave, Bryan Derksen, Bswilson, Burroomens3, C.Fred, CWenger, CYD, Can't sleep, clown will eat me, Carbuncle, Cfleisch, CharlotteWebb,
Chealer, Chenghui, Chris Mounce, Chris the speller, Chris400, Chrisbolt, Chrisch, Chupacabras, Chuunen Baka, Cleared as filed, ClementSeveillac, Cligra, Closedmouth, Cometstyles,
Corinna128, Cpartsenidis, Cr0w, Crazytales, CutOffTies, Cwolfsheep, DBigXray, DKEdwards, Danno uk, David H Braun (1964), David Martland, David Woodward, Davidoff, Dbrodbeck,
Decltype, Deeahbz, Deice, Deli nk, Delldot, DerHexer, Dewritech, Dgtsyb, Diablo-D3, Discospinster, Djg2006, Dmktg, Dmol, Doctorfluffy, DoorsAjar, Dpotter, DrFausty, Drable, DreamGuy,
Drugonot, Dugnad, Dugosz, E. Ripley, EagleOne, Edcolins, Edderso, Eenu, Efa, ElTopo, Eli77e, Elinruby, Emmatheartist, EncMstr, EoGuy, Epater, Epbr123, Escape Orbit, Eubene, EuroCarGT,
Evansda, Everyking, Evice, Extraordinary, FAchi, FJPB, Falcon8765, Fancy steve, Fangfufu, Fieldday-sunday, Fijal, Fleminra, Flockmeal, Foggy Morning, Fosterbt, Foxb, Funnyfarmofdoom,
Fuzheado, GL, GSK, Gadfium, Gardar Rurak, Gary King, Gascreed, Gaurav.khatri, GenOrl, Gershwinrb, Gilliam, Gkstyle, Glane23, Glenn, Godsmoke, Gracefool, Gracenotes, GraemeL, Ground
Zero, Gurdipsclick, Hadal, Haemo, Hal 2001, Happysailor, Harryzilber, Hcberkowitz, Hellisp, Heron, HisSpaceResearch, Humannetwork, Hyakugei, Ianmacm, Iceb, Ieopo, Informedbanker,
Inkling, Intgr, Invenio, Ironman5247, Irulet, Isilanes, IvanStepaniuk, Izwalito, J'raxis, J.delanoy, JGXenite, JHunterJ, JNW, Ja 62, Jaan513, Jackcsk, Jackfork, Jadams76, Jags707, Jairo lopez,
JamesGeddes, Jamesmcmahon0, Jandalhandler, Jasper Deng, Jazappi, Jcap1ln, Jdzarlino, Jemappelleungarcon, Jeremiah.l.burns, Jerome Charles Potts, JidGom, Jim.henderson, Jim1138, Jino123,
Jlavepoze, Jleedev, Jmccormac, Jmundo, JoeSmack, John Vandenberg, John254, Johnuniq, Jojalozzo, JonHarder, Jonomacdrones, Joshk, Joy, Jrapo, Jrgetsin, Juliancolton, Jwp9023, K-secure,
Kaaveh Ahangar, Kamesg, Karlzt, Kateshortforbob, Katkay, Katkay1, Kbrose, Kevinzhouyan, Khag7, Kielvon, Kikbguy, Kilopi, Kimchi.sg, Kku, KnowledgeOfSelf, Kurt Jansson, Kuru, Kvng, L
Kensington, LOL, Leafyplant, LeaveSleaves, LeedsKing, Les boys, LetMeLookItUp, Lexicontra, Lightmouse, LindArlaud, LittleBenW, Lkstrand, Lmstearn, Lucaweb, Ludovic.ferre, Luna
Santin, M. B., Jr., MCB, MER-C, MFNickster, Ma8thew, MainFrame, Majorly, Manop, MarcoTolo, Mashouri, Materialscientist, Matt Crypto, MattTM, MattieTK, Maura Driscoll, Maxgrin,
Me.rs, MeToo, Mebden, Mercury543210, Mercy11, Mfalaura, Mhking, Miabchdave, Michaelas10, Mike Rosoft, Mindmatrix, Ministry of Truth, Minna Sora no Shita, Mjs1991, Mkidson,
Mmernex, Mohsen Basirat, Monkeyman, Movingonup, Mr.Clown, MrOllie, Mu Mind, Mxn, Naba san, Nacnud22032, Nardixsempre, Natalie Erin, Nealmcb, Negrulio, Neoalian, Netmotion1234,
Niffweed17, Nkansahrexford, Nklatt, Noah Salzman, Nobletripe, Novastorm, Nqtrung, Ntsimp, Nubiatech, Nuno Tavares, Nurg, Nuttycoconut, Octahedron80, Ohconfucius, Oli Filth,
Omicronpersei8, Optimist on the run, Ottawa4ever, OverlordQ, Pascalv, Paulehoffman, Pauli133, Pdcook, Pearle, Peteinterpol, Peter M Dodge, Phatom87, Philomathoholic, Phr, Pinchomic,
Pinethicket, Plat'Home, Plyd, Pmcm, Pnm, Pokrajac, PositiveNetworks, Prakash Nadkarni, Prari, ProfPolySci45, PuerExMachina, Quarl, R'n'B, R. S. Shaw, R00stare, RFightmaster, RHaworth,
RM MARTIN, Raanoo, Rafigordon, RainbowOfLight, Raprap321, Rashoba, Ray Dassen, RayAYang, Razorflame, Rearden9, RedHillian, Redlazer, Rees11, Regancy42, Reliablehosting,
Res2216firestar, Rgore, Rhobite, Rich45, Rjwilmsi, Rninneman, Robert Brockway, Rocketron5, Rosothefox, SPat, START-newsgroup, Saimhe, Sajjad36122061, Scarpy, Schecky4,
Scott.somohano, SecurityManager, Selah28, Sepersann, Sgarson, Shadowjams, Shandon, ShelleyAdams, Shierro, Shijiree88, ShorelineWA, Sijokjose, SilentAshes, Sintesia, Skarebo, Skier Dude,
Skizzik, Sleepsfortheweak, Slunkbroil, Smallman12q, SmartGuy Old, Smartchain, Smithkkj, Snaxe920, Snow Blizzard, Snowolf, SpaceFlight89, SqueakBox, Stdundon, Stephenb, Strike Eagle,
Student geek, Sujathasubhash, Sunny2who, Superpixelpro, Swartik, Sydbarrett74, Szquirrel, THEN WHO WAS PHONE?, Tahren B, Talinus, TastyPoutine, Tech editor007, TechyOne, TehPhil,
Teknetz, Thane, Thatguyflint, Thaurisil, The Anome, The Thing That Should Not Be, TheBilly, TheNeutroniumAlchemist, ThePromenader, TheRedPenOfDoom, Therefore, Thumperward, Tide
rolls, Timurx, Tlroche, Tobias Bergemann, Tom Foley, Tomlee1968, Tommy2010, TonyUK, Torqueing, Trailbum, Tryggvia, Tslocum, Tuxa, Tuxcrafter, TwoTwoHello, Unixer, Utcursch,
VPN.PRO, Vanderdecken, Vanisheduser12345, Veinor, Vicarious, Vickey2020, Visiting1, Vjardin, Vladkornea, W.F.Galway, WEJohnston, Wackywace, WakingLili, WarrenA, Wavelength,
WebHamster, Webster21, Webwat, Whaa?, Widefox, Widr, Wik, Wiki 101, Wikievil666, Wikingtubby, Williameboley, Wimt, Winchelsea, Winterst, Wknight94, Wodkreso, Woohookitty, Ww,
Xenomm, Xpclient, YUL89YYZ, Yama, Yamamoto Ichiro, YordanGeorgiev, Youssefsan, Ywalker79, ZeroOne, Zeroshell, Ziabhat, Zzuuzz, , 1437 anonymous edits
Image Sources, Licenses and Contributors
File:Virtual Private Network overview.svg Source: http://en.wikipedia.org/w/index.php?title=File:Virtual_Private_Network_overview.svg License: Creative Commons Attribution-Share Alike
Contributors: Ludovic.ferre
License
Creative Commons Attribution-Share Alike 3.0
//creativecommons.org/licenses/by-sa/3.0/