This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
manuals:vps:vpsadminos [2018/07/11 06:14] – rene.la | manuals:vps:vpsadminos [2018/09/30 13:11] – Removed network configuration Aither | ||
---|---|---|---|
Line 47: | Line 47: | ||
===== Changes in VPS behaviour ===== | ===== Changes in VPS behaviour ===== | ||
- | ==== Network configuration ==== | ||
- | Linux kernel doesn' | ||
- | find a different way. Networking is done by a pair of veth interfaces: | ||
- | one on the host, the other in the VPS. IP addresses are routed through | ||
- | an interconnecting network that is assigned to every VPS. | ||
- | |||
- | For example, let's say the assigned interconnecting network is | ||
- | '' | ||
- | '' | ||
- | IP addresses are then routed via '' | ||
- | would be routed as '' | ||
- | in the VPS would be set as '' | ||
- | interface on the host is configured automatically by '' | ||
- | will also generate configuration files inside your VPS, depending on your | ||
- | distribution. The init system from your VPS will then read those files | ||
- | and setup the network interface. The first address on the interface will be | ||
- | the address from the interconnecting network, not the public address, as has | ||
- | been the case on OpenVZ. If you have some custom network configuration, | ||
- | you need to be aware of how the networking is supposed to work. | ||
- | |||
==== User namespaces ==== | ==== User namespaces ==== | ||
VPS in vpsAdminOS are using so called //user namespaces// | VPS in vpsAdminOS are using so called //user namespaces// |