Misplaced Pages

#781218

34-648: Not to be confused with VPN . VPM may refer to: Varying Permeability Model Ventral posteromedial nucleus , a nucleus of the thalamus; part of the brain. Virginia Payload Module , a weapon system planned for Block 5 of the US Navy's Virginia-class submarine Volcanic passive margin VPM Media Corporation VPM SnC, an Italian autogyro company, renamed Magni Gyro in 1996 Vranken Pommery Monopole Vel Phillips Memorial High School ,

68-521: A private network (i.e. any computer network which is not the public Internet ) across one or multiple other networks which are either untrusted (as they are not controlled by the entity aiming to implement the VPN) or need to be isolated (thus making the lower network invisible or not directly usable). A VPN can extend access to a private network to users who do not have direct access to it, such as an office network allowing secure access from off-site over

102-548: A web captive portal ). Remote-access VPNs, which are typically user-initiated, may use passwords , biometrics , two-factor authentication , or other cryptographic methods. People initiating this kind of VPN from unknown arbitrary network locations are also called "road-warriors". In such cases, it is not possible to use originating network properties (e.g. IP addresses) as secure authentication factors, and stronger methods are needed. Site-to-site VPNs often use passwords ( pre-shared keys ) or digital certificates . Depending on

136-542: A VPLS, the provider network emulates a learning bridge, which may include VLAN service optionally. PW is similar to VPLS but 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 ( RFC   3378 )

170-415: A consistent VPN protocol across their products but do not open up for customizations outside the use cases they intended to implement. This is often the case for appliances that rely on hardware acceleration of VPNs to provide higher throughput or support a larger amount of simultaneously connected users. Whenever a VPN is intended to virtually extend a private network over a third-party untrusted medium, it

204-410: A network interface, are not to be considered VPN implementations but may achieve the same or similar end-user goal of exchanging private contents with a remote network. Virtual private networks configurations can be classified depending on the purpose of the virtual extension, which makes different tunneling strategies appropriate for different topologies: In the context of site-to-site configurations,

238-701: A public high school in Madison, Wisconsin Radio stations [ edit ] VPM-FM , a radio station in Belize Three related public radio stations in Virginia WBBT-FM , branded as VPM Music, WWLB , branded as VPM Music WCVE-FM , branded as VPM News Topics referred to by the same term [REDACTED] This disambiguation page lists articles associated with the title VPM . If an internal link led you here, you may wish to change

272-425: A security protocol but a subset was introduced for trunking), and ATM LAN Emulation (LANE). Developed by Institute of Electrical and Electronics Engineers , 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,

306-542: A selection of VPN protocols which is subject to change over the years, as some have been proven to be unsecure with respect to modern requirements and expectations, and some others emerged. Desktop, smartphone and other end-user device operating systems do usually support configuring remote access VPN from their graphical or command-line tools. However, due to the variety of, often non standard, VPN protocols there exists many third-party applications that implement additional protocols not yet or no more natively supported by

340-532: A significantly complex business network, may be combined to enable remote access to resources located at any given site, such as an ordering system that resides in a data center. Apart from the general topology configuration, a VPN may also be characterized by: A variety of VPN technics exist to adapt to the above characteristics, each providing different network tunneling capabilities and different security model coverage or interpretation. Operating systems vendors and developers do typically offer native support to

374-399: Is also used to refer to VPN services which sell access to their own private networks for internet access by connecting their customers using VPN tunneling protocols. The goal of a virtual private network is to allow network hosts to exchange network messages across another network to access private content, as if they were part of the same network. This is done in a way that makes crossing

SECTION 10

#1732798262782

408-641: Is an Ethernet-over-IP tunneling protocol specification. EtherIP has only a packet encapsulation mechanism. It has no confidentiality or message integrity protection. EtherIP was introduced in the FreeBSD network stack and the SoftEther VPN 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. Ethernet VPN (EVPN)

442-627: Is an advanced solution for providing Ethernet services over IP-MPLS networks. In contrast to the VPLS architectures, EVPN enables control-plane-based MAC (and MAC,IP) learning in the network. PEs participating in the EVPN instances learn the customer's MAC (MAC,IP) routes in control-plane using MP-BGP protocol. Control-plane MAC learning brings a number of benefits that allow EVPN to address the VPLS shortcomings, including support for multi-homing with per-flow load balancing and avoidance of unnecessary flooding over

476-478: Is desirable that the chosen protocols match the following security model: VPN are not intended to make connecting users neither anonymous nor unidentifiable from the untrusted medium network provider perspective. If the VPN makes use of protocols that do provide the above confidentiality features, their usage can increase user privacy by making the untrusted medium owner unable to access the private data exchanged across

510-603: 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. Provider-provisioned VPN When internet service providers implement PPVPNs on their own networks,

544-556: The Internet. This is achieved by creating a link between computing devices and computer networks by the use of network tunneling protocols . It is possible to make a VPN secure to use on top of insecure communication medium (such as the public internet) by choosing a tunneling protocol that implements encryption . This kind of VPN implementation has the benefit of reduced costs and greater flexibility, with respect to dedicated communication lines, for remote workers . The term VPN

578-629: The L2–L3 identity. RFC   4026 generalized the following terms to cover L2 MPLS VPNs and L3 ( BGP ) VPNs, but they were introduced in RFC   2547 . VLAN is a Layer 2 technique that allows 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

612-609: The MPLS core network to multiple PEs participating in the P2MP/MP2MP L2VPN (in the occurrence, for instance, of ARP query). It is defined RFC   7432 . 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

646-528: The OS. For instance, Android lacked native IPsec IKEv2 support until version 11, and people needed to install third-party apps in order to connect that kind of VPNs, while Microsoft Windows , BlackBerry OS and others got it supported in the past. Conversely, Windows does not support plain IPsec IKEv1 remote access native VPN configuration (commonly used by Cisco and Fritz!Box VPN solutions) which makes

680-562: 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. 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, and in other organizations with similar requirements such as field service management and healthcare. A limitation of traditional VPNs

714-413: The VPN protocol, they may store the key to allow the VPN tunnel to establish automatically, without intervention from the administrator. A virtual private network is based on a tunneling protocol, and may be possibly combined with other network or application protocols providing extra capabilities and different security model coverage. Trusted VPNs do not use cryptographic tunneling; instead, they rely on

SECTION 20

#1732798262782

748-522: The VPN. In order to prevent unauthorized users from accessing the VPN, most protocols can be implemented in ways that also enable authentication of connecting parties. This secures the joined remote network confidentiality, integrity and availability. Tunnel endpoints can be authenticated in various ways during the VPN access initiation. Authentication can happen immediately on VPN initiation (e.g. by simple whitelisting of endpoint IP address), or very lately after actual tunnels are already active (e.g. with

782-425: The intermediate network transparent to network applications. Users of a network connectivity service may consider such an intermediate network to be untrusted, since it is controlled by a third-party, and might prefer a VPN implemented via protocols that protect the privacy of their communication. In the case of a Provider-provisioned VPN , the goal is not to protect against untrusted networks, but to isolate parts of

816-434: The link to point directly to the intended article. Retrieved from " https://en.wikipedia.org/w/index.php?title=VPM&oldid=1236180939 " Category : Disambiguation pages Hidden categories: Short description is different from Wikidata All article disambiguation pages All disambiguation pages VPN Virtual private network ( VPN ) is a network architecture for virtually extending

850-450: 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 in a way that is transparent to the user, making the separate LAN segments behave as one single LAN. In

884-586: The most attention. One of the challenges of PPVPNs involves different customers using the same address space, especially the IPv4 private address space. The provider must be able to disambiguate overlapping addresses in the multiple customers' PPVPNs. PEs understand the topology of each VPN, which is interconnected with MPLS tunnels directly or via P routers. In MPLS terminology, the P routers are label switch routers without awareness of VPNs. Some virtual networks use tunneling protocols without encryption to protect

918-436: The network messages from one side to the other. The goal is to take network messages from applications on one side of the tunnel and replay them on the other side. Applications do not need to be modified to let their messages pass through the VPN, because the virtual network or link is made available to the OS. Applications that do implement tunneling or proxying features for themselves without making such features available as

952-424: The open source code of the OS itself. For instance, pfSense does not support remote access VPN configurations through its user interface where the OS runs on the remote host, while provides comprehensive support for configuring it as the central VPN gateway of such remote-access configuration scenario. Otherwise, commercial appliances with VPN features based on proprietary hardware/software platforms, usually support

986-461: The open source operating systems devoted to firewalls and network devices (like OpenWrt , IPFire , PfSense or OPNsense ) it is possible to add support for additional VPN protocols by installing missing software components or third-party apps. Similarly, it is possible to get additional VPN configurations working, even if the OS does not facilitate the setup of that particular configuration, by manually editing internal configurations of by modifying

1020-462: The provider's own network infrastructure in virtual segments, in ways that make the contents of each segment private with respect to the others. This situation makes many other tunneling protocols suitable for building PPVPNs, even with weak or no security features (like in VLAN ). How a VPN works depends on which technologies and protocols the VPN is built upon. A tunneling protocol is used to transfer

1054-492: The security model of typical PPVPN protocols is weaker with respect to tunneling protocols used in customer-provided VPN, especially for confidentiality, because data privacy may not be needed. Depending on whether a provider-provisioned VPN (PPVPN) operates in Layer 2 (L2) or Layer 3 (L3), the building blocks described below may be L2 only, L3 only, or a combination of both. Multiprotocol Label Switching (MPLS) functionality blurs

VPM - Misplaced Pages Continue

1088-467: The security of a single provider's network to protect the traffic. From a security standpoint, a VPN must either trust the underlying delivery network or enforce security with a mechanism 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. Mobile virtual private networks are used in settings where an endpoint of

1122-563: The terms intranet and extranet are used to describe two different use cases. An intranet site-to-site VPN describes a configuration where the sites connected by the VPN belong to the same organization, whereas an extranet site-to-site VPN joins sites belonging to multiple organizations. Typically, individuals interact with remote access VPNs, whereas businesses tend to make use of site-to-site connections for business-to-business , cloud computing, and branch office scenarios. However, these technologies are not mutually exclusive and, in

1156-451: The use of third-party applications mandatory for people and companies relying on such VPN protocol. Network appliances, such as firewalls, do often include VPN gateway functionality for either remote access or site-to-site configurations. Their administration interfaces do often facilitate setting up virtual private networks with a selection of supported protocols which have been integrated for an easy out-of-box setup. In some cases, like in

#781218