Virtual Networks: Difference between revisions
pc>Yuron m (Yuron moved page Extra:Virtual Networks to Virtual Networks without leaving a redirect) |
 W81054ch [   PHRhYmxlIGNsYXNzPSJ0d3BvcHVwIj48dHI+PHRkIGNsYXNzPSJ0d3BvcHVwLWVudHJ5dGl0bGUiPkdyb3Vwczo8L3RkPjx0ZD51c2VyPGJyIC8+YnVyZWF1Y3JhdDxiciAvPmludGVyZmFjZS1hZG1pbjxiciAvPnN5c29wPGJyIC8+PC90ZD48L3RyPjwvdGFibGU+] (talk | contribs) m (1 revision imported) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{#set: Priority=2 | Summary=One wire can support several independent connections.}}<!-- | {{#set: Priority=2 | Summary=One wire can support several independent connections.}}<!-- | ||
-->{{#invoke:Dependencies|add|Virtualisation,3}} | -->{{#invoke:Dependencies|add|Virtualisation,3}} | ||
A traditional computer network – if there was such a thing – | A traditional computer network – if there was such a thing – comprised some form of interconnection hardware (wires) with some | ||
comprised some form of interconnection hardware (wires) with some | software to control these. Sometimes the software imposed some [[Security | security]], e.g. it restricted what could communicate with what. | ||
software to control these. Sometimes the software imposed some | |||
[[Security | security]], e.g. it restricted what could communicate with | |||
what. | |||
In one sense, once the network extends beyond your local | In one sense, once the network extends beyond your local interconnection, it may be [[Virtualisation|virtualised]], so remote | ||
interconnection, it may be [[Virtualisation | virtualised]], so remote | machines still appear as if they were locally connected: the need to send messages via satellites (or whatever) can be hidden from the user. | ||
machines still appear as if they were locally connected: the need to | |||
send messages via satellites (or whatever) can be hidden from the user. | |||
Alternatively a virtual network may be confined entirely within a | Alternatively a virtual network may be confined entirely within a single computer, which is itself running multiple [[Hypervisor|virtual computers]]: this could be, for example, a means of running both Windows and Linux applications together if you only have a single physical machine. On a slightly smaller scale this might be interconnecting [[containers]] within a machine. | ||
single computer, which is itself running multiple [Hypervisor virtual | |||
computers]: this could be, for example, a means of running | |||
both Windows and Linux applications together if you only have a single | |||
physical machine. On a slightly smaller scale this might be | |||
interconnecting [[ | |||
Another approach to virtualisation is typified by the [https://en.wikipedia.org/wiki/Virtual_private_network Virtual Private Network] (VPN) | Another approach to virtualisation is typified by the [https://en.wikipedia.org/wiki/Virtual_private_network Virtual Private Network] (VPN) which builds what looks to users like a separate network <em>within</em> a large network (such as the Internet). This allows existing infrastructure to be exploited whilst maintaining the privacy of a local private network. | ||
which builds what looks to users like a separate network <em>within</em> a | |||
large network (such as the Internet). This allows existing | |||
infrastructure to be exploited whilst maintaining the privacy of a | |||
local private network. | |||
Of course, because the data is transported across a public medium, | Of course, because the data is transported across a public medium, various [[security]] precautions are necessary, such as: | ||
various [[ | |||
*<strong>Authentication</strong>: are correspondents really who they say they are? | *<strong>Authentication</strong>: are correspondents really who they say they are? | ||
| Line 32: | Line 17: | ||
*<strong>Integrity</strong>: are messages being tampered with? | *<strong>Integrity</strong>: are messages being tampered with? | ||
However, other than the <em>principle</em> of virtualisation this is moving | However, other than the <em>principle</em> of virtualisation this is moving more into networks than operating systems, so that’s enough for here. | ||
more into networks than operating systems, so that’s enough for here. | |||
---- | ---- | ||
{{PageGraph}} | {{PageGraph}} | ||
Latest revision as of 10:03, 5 August 2019
| Depends on | Virtualisation |
|---|
A traditional computer network – if there was such a thing – comprised some form of interconnection hardware (wires) with some software to control these. Sometimes the software imposed some security, e.g. it restricted what could communicate with what.
In one sense, once the network extends beyond your local interconnection, it may be virtualised, so remote machines still appear as if they were locally connected: the need to send messages via satellites (or whatever) can be hidden from the user.
Alternatively a virtual network may be confined entirely within a single computer, which is itself running multiple virtual computers: this could be, for example, a means of running both Windows and Linux applications together if you only have a single physical machine. On a slightly smaller scale this might be interconnecting containers within a machine.
Another approach to virtualisation is typified by the Virtual Private Network (VPN) which builds what looks to users like a separate network within a large network (such as the Internet). This allows existing infrastructure to be exploited whilst maintaining the privacy of a local private network.
Of course, because the data is transported across a public medium, various security precautions are necessary, such as:
- Authentication: are correspondents really who they say they are?
- Encryption: messages will, in principle, be visible to third parties; is there meaning kept hidden?
- Integrity: are messages being tampered with?
However, other than the principle of virtualisation this is moving more into networks than operating systems, so that’s enough for here.
