<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.openvz.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Blueroomhosting</id>
	<title>OpenVZ Virtuozzo Containers Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.openvz.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Blueroomhosting"/>
	<link rel="alternate" type="text/html" href="https://wiki.openvz.org/Special:Contributions/Blueroomhosting"/>
	<updated>2026-05-15T13:47:22Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.1</generator>
	<entry>
		<id>https://wiki.openvz.org/index.php?title=Hosting_providers&amp;diff=7323</id>
		<title>Hosting providers</title>
		<link rel="alternate" type="text/html" href="https://wiki.openvz.org/index.php?title=Hosting_providers&amp;diff=7323"/>
		<updated>2009-05-17T13:04:23Z</updated>

		<summary type="html">&lt;p&gt;Blueroomhosting: /* UK */ changed location of blue room hosting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;OpenVZ makes for a great hosting platform for VPS hosting. The providers below offer VPS services using OpenVZ.&lt;br /&gt;
&lt;br /&gt;
== Austria ==&lt;br /&gt;
&lt;br /&gt;
* [http://kapper.net/ kapper.net] kapper.net offers OpenVZ and Virtuozzo (and other HyperVisors) based server-solutions with kind support and 24x7 maintenance.&lt;br /&gt;
&lt;br /&gt;
* [https://www.vboxes.net/ vboxes] vboxes offers generous OpenVZ containers hosted on a very fast network with fast setup. Ubuntu, Debian, CentOS.&lt;br /&gt;
&lt;br /&gt;
== Canada ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.vistapages.com/vps Vistapages VPS] - IBM &amp;amp; Dell Hardware. MCI/Verizon Backbone. Distros: Centos, Fedora, Debian &amp;amp; more. Full management available. Located in Toronto.&lt;br /&gt;
* [http://vpsville.ca/ VPSVille] - Good network. Good CPU. Good choice of distros: Centos, Fedora, Debian, Ubuntu, Slackware, Gentoo, OpenSUSE, CERN. My favorite OpenVZ provider. [mailto:jak@isp2dial.com John Kelly]&lt;br /&gt;
* [http://compevo.com compevo Clustered VPS Server Hosting Provider] - We offer clustered VPS Servers to avoid downtime and dataloss. Our network and service is second to none and is used by businesses around the world.&lt;br /&gt;
&lt;br /&gt;
== Germany ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.ingate.de/managed-server.html Ingate] offers managed servers with openVZ virtualization. located in germany, great support.&lt;br /&gt;
* [http://www.synapseglobal.com/voip_vps.html SynapseGlobal.com] Elastix, Trixbox, PBX in a Flash and Asterisk VPS - OpenVZ based Asterisk VOIP servers located in Munich Germany.&lt;br /&gt;
&lt;br /&gt;
== Iran==&lt;br /&gt;
&lt;br /&gt;
* [http://www.cheapvps.ir Cheap Vps] - XEON Cpus , 8 gig Ram , western H.d.d. , Intel RAID and Multi data center network.&lt;br /&gt;
&lt;br /&gt;
== Lithuania ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.serveriai.lt/ Serveriai.lt] - Affordable OpenVZ containers on quality HP hardware. Wide choice of virtual dedicated servers up to 8 CPU cores and 8 GB RAM. Full management available. Located in Vilnius.&lt;br /&gt;
&lt;br /&gt;
== Malaysia ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.bakka.my/ Bakka Hosting] - OpenVZ VPS based in Malaysia. Ubuntu, Debian, Fedora, CentOS is available. Quad Core Xeon node. DirectAdmin also available.&lt;br /&gt;
&lt;br /&gt;
== Netherlands ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.signet.nl/ Signet VPS Hosting] - Signet delivers VPS hosting plans based on CentOS or Debian templates, including control-panel Virtualmin.&lt;br /&gt;
* [http://www.touchvps.com/ TouchVPS] is a company who offer Support and Managed Services for OpenVZ Servers ,also offer templates for openvz ready to go with cPanel , DirectAdmin , Plesk , Games, IRC Services, Desktop and many more.&lt;br /&gt;
* [http://www.voipcomplete.com/product-overview/dedicated-vps.html VOIPcomplete] offers dedicated VPS plans based on CentOS including a VPS management interface.&lt;br /&gt;
&lt;br /&gt;
== Portugal ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.efeito.net/ Weblevel.pt] - OpenVZ virtual servers based in Portugal.&lt;br /&gt;
&lt;br /&gt;
== Russia ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.demos.ru/service/datacenter/vps.html Demos-Internet] - we offer OpenVZ Virtual Private Server based on Linux.  All VPS come with ISPmanager control panel.&lt;br /&gt;
&lt;br /&gt;
== Singapore ==&lt;br /&gt;
&lt;br /&gt;
* [http://conceptlane.com/IT.php?section=plans_vps ConceptLane Pte Ltd] - OpenVZ VPS on Ubuntu Hardy 8.04 LTS host, on dual dual-core AMD Opterons.&lt;br /&gt;
&lt;br /&gt;
== South Africa ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.SoftDux.co.za/ SoftDux] - OpenVZ virtual servers based America &amp;amp; South Africa. All VPS's come with cPanel or Plesk control panels. XEN VPS's also available.&lt;br /&gt;
&lt;br /&gt;
== UK ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.xilo.net/virtual_private_servers-vps/ XILO] - UK-based hosting with UK-based support. VPS services offered with a choice of cPanel, Webmin and other useful applications, VoIP, SIP, VPN to name a few.&lt;br /&gt;
* [http://www.DubHosting.co.uk/ DubHosting] - DubHosting started in 2004 has been providing cost effective hosting to clients world wide. Fully managed OpenVZ servers based in Europe &amp;amp; US are one of their many strong points. They can provide you with a dedicated server and install openvz allowing you to sell your own vps servers.&lt;br /&gt;
* [http://www.vt6.co.uk/ VT6 Internet] - Affordable OpenVZ virtual servers based in the UK and USA. Choice of control panels and management options.&lt;br /&gt;
* [http://www.weycrest.co.uk/vps-hosting.php Weycrest VPS] - Low Cost, Stable OpenVZ and Parallels' Virtuozzo Virtual Private Server solutions. London UK Hosted at Coreix with a choice of operating systems, and root and control panel options.&lt;br /&gt;
* [http://blueroomhosting.com/plans.pxl Blue Room Hosting] - OpenVZ containers hosted at the 4D data centre in Byfleet, West London, UK&lt;br /&gt;
* [http://sysadminman.net/uk-voip-vps.html Trixbox, Elastix and Asterisk VPS in the UK] - OpenVZ based Asterisk VOIP servers based in the UK&lt;br /&gt;
&lt;br /&gt;
== Ukraine ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.gelihost.com/ Geliar Hosting Solutions] - Fast virtual dedicated servers based on OpenVZ. Geliar Hosting Solutions offering many control panels and other useful services.&lt;br /&gt;
&lt;br /&gt;
== USA ==&lt;br /&gt;
* [http://www.DubHosting.com/ DubHosting] - DubHosting started in 2004 has been providing cost effective hosting to clients world wide. Fully managed OpenVZ servers based in Europe &amp;amp; US are one of their many strong points. They can provide you with a dedicated server and install openvz allowing you to sell your own vps servers.&lt;br /&gt;
* [http://www.4domains.com/open_vps.html 4Domains] has been in the hosting business since 1998, offering VPS solutions for the majority of that time. We offer OpenVZ and Virtuozzo with Virtualmin or Plesk at competitive prices on any distribution of Linux with full shell access. Includes our award winning professional and personalized support.&lt;br /&gt;
* [http://www.a2hosting.com/services/vps-hosting/ A2 Hosting] offers affordable, developer friendly OpenVZ VPS Hosting. Experience the A2 Hosting Difference.&lt;br /&gt;
* [http://www.bittraffic.com/?cmd=vps BitTraffic] High Quality Hosting Solutions! Affordable, stable, reliable OpenVZ VPS Solutions!&lt;br /&gt;
* [http://www.tigerservers.com/ TigerServers] - Provides affordable managed VPS based on OpenVZ. Servers located in Chicago, Illinois.&lt;br /&gt;
* [http://www.silverrack.com/ SilverRack VPS Hosting] - SilverRack provides affordable VPS hosting using the OpenVZ platform.&lt;br /&gt;
* [http://www.buyavps.com/ BuyAVPS] - BuyAVPS provides stable yet affordable VPS hosting with a great support staff.&lt;br /&gt;
* [http://vpslink.com VPSLink.com] provides virtual private server hosting on the OpenVZ platform.&lt;br /&gt;
* [http://glesys.se GleSYS] is a hosting company specialized in serverhosting. Also offering VPS hosting mainly based on OpenVZ. GleSYS has provided access to server and Cisco hardware for developers from OpenVZ to find problem with VLAN implementation.&lt;br /&gt;
* [http://lylix.net LYLIX] offers affordable VPS hosting with a choice of eight different Linux distributions, dedicated VPS hosting, and specializes in Asterisk/VOIP based hosting including Trixbox, AsteriskNow, Elastix, and PBX-in-a-Flash.  Popular choice for unmanaged IP-PBX services; entire infrastructure built on a High-availability (HA) network across three regional NOCs.&lt;br /&gt;
* [http://www.servergrove.com ServerGrove] uses OpenVZ as the main virtualization platform for its state of the art VPS hosting services.&lt;br /&gt;
* [http://www.tektonic.net TekTonic] provides VPS hosting services using both Virtuozzo and OpenVZ technology.&lt;br /&gt;
* [http://www.micfo.com Micfo.com] offers VPS hosting services for both Linux VPS hosting and Window VPS hosting on affordable price combined with world-class 24x7x365 support.&lt;br /&gt;
* [http://www.alticon.net Alticon] has provided OpenVZ based VPS/VE hosting for over 2½ years.  Many clients use OpenVZ based VEs as a cost effective solution for hosting highly secured, customized versions of ZenCart &amp;amp; WordPress.  Other clients use OpenVZ for DNS mirroring, messages board hosting, and general use.&lt;br /&gt;
* [http://www.hostingrails.com Hosting Rails] offers Rails-targeted OpenVZ VPS Hosting and updated Rails-ready OS images.&lt;br /&gt;
* [http://www.byethost.com Byethost.com] offers OpenVZ based VPS Hosting as its main VPS solution, with the hypervm panel. Centos, Debian, Fedora, OpenSuse and Ubuntu Containers are available.&lt;br /&gt;
* [http://www.synapseglobal.com/voip_vps.html SynapseGlobal.com] Elastix, Trixbox, PBX in a Flash and Asterisk VPS - OpenVZ based Asterisk VOIP servers with 14 Tier 1 premium bandwidth providers.&lt;br /&gt;
* [http://www.zoidial.com/ Zoidial Hosting and VPS] - offers VPS and Virtual Dedicated Server solutions utilizing OpenVZ.  In business since 1998, Zoidial Incorporated is a small hosting provider focused on being security conscious, proactive, and offering a positive client experience.&lt;br /&gt;
* [http://railsplayground.com RailsPlayground.com] Ruby on Rails VPS with ready to go Rails images with the LxAdmin control panel&lt;br /&gt;
&lt;br /&gt;
== Venezuela ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.iguanahosting.com Iguanahosting.com] The Iguanahosting OpenVZ based VEs also called  &amp;quot;SDV&amp;quot;(Servidor Dedicado Virtual in Spanish). Running on Full Quality Nodes of up to 8 CPU and 8 GB RAM. XEN VPS's also will be available cooming soon. All VPS's come with cPanel, Fantastico and RVSkin and a Real 24/7/365  Technical Support.&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
&lt;br /&gt;
* [[Partners]]&lt;br /&gt;
* [[Download mirrors]]&lt;br /&gt;
* [[VPS vs Dedicated]]&lt;/div&gt;</summary>
		<author><name>Blueroomhosting</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.openvz.org/index.php?title=Common_Networking_HOWTOs&amp;diff=6083</id>
		<title>Common Networking HOWTOs</title>
		<link rel="alternate" type="text/html" href="https://wiki.openvz.org/index.php?title=Common_Networking_HOWTOs&amp;diff=6083"/>
		<updated>2008-06-13T00:17:32Z</updated>

		<summary type="html">&lt;p&gt;Blueroomhosting: Added static public addresses section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;While other pages do a great job of going into the details of veth and venet networking, this page is all about getting the results you want quickly.&lt;br /&gt;
&lt;br /&gt;
== Private VEs (not directly visible from the LAN) ==&lt;br /&gt;
&lt;br /&gt;
When starting with a new VE that should not be directly visible on the LAN it is important to choose an appropriate IP address. By running &amp;quot;ifconfig -a&amp;quot; on the host it is possible to see all the networks the host is connected to. The VE should reside on a a new private network, choosing one of the 192.168.X.Y/24 subnets is a good choice.&lt;br /&gt;
&lt;br /&gt;
For example, on a host which is already on a 192.168.1.0/24 subnet then the 192.168.2.0/24 subnet would be a reasonable choice (unless the host is already on that subnet too).&lt;br /&gt;
&lt;br /&gt;
In these examples the host has eth0 with address 192.168.1.53, and 192.168.2.0/24 is free so we will give the VE 192.168.2.1. The VE (101) is assumed to be freshly created and started, with no networking currently set up.&lt;br /&gt;
&lt;br /&gt;
=== Venet ===&lt;br /&gt;
&lt;br /&gt;
Venet routed networking is probably the simplest to set up, simply add the IP address to the VE:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# vzctl set 101 --ipadd 192.168.2.1 --save&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After this the host should be able to ping the VE.&lt;br /&gt;
&lt;br /&gt;
To allow the VE to access the rest of the LAN we must enable forwarding and masquerading, as all activity on the LAN must look like it is coming directly from host (with its IP address).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# echo 1 &amp;gt; /proc/sys/net/ipv4/ip_forward&lt;br /&gt;
[host-node]# iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Veth ===&lt;br /&gt;
&lt;br /&gt;
This is a stub&lt;br /&gt;
&lt;br /&gt;
== Public VEs (with their own IP addresses) ==&lt;br /&gt;
&lt;br /&gt;
=== Static addresses ===&lt;br /&gt;
&lt;br /&gt;
This is very similar to using private addresses, except there is no need for masquerading and the VE will be visible to others on the LAN.&lt;br /&gt;
&lt;br /&gt;
In this example the host has eth0 with address 192.168.1.53, and the VE will be set up with 192.168.1.101. The VE (101) is assumed to be freshly created and started, with no networking currently set up.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# vzctl set 101 --ipadd 192.168.1.101 --save&lt;br /&gt;
[host-node]# echo 1 &amp;gt; /proc/sys/net/ipv4/ip_forward&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== DHCP supplied addresses ===&lt;br /&gt;
&lt;br /&gt;
For this section the following assumptions have been made:&lt;br /&gt;
&lt;br /&gt;
* The host is connected to the LAN by eth0, and also uses DHCP.&lt;br /&gt;
* The DHCP server is another machine on the LAN.&lt;br /&gt;
&lt;br /&gt;
To make the VEs truly part of the LAN it is best to create a bridge that binds them, and the LAN, together.&lt;br /&gt;
Configuring the host to use a bridge when it boots is distribution specific and beyond the scope of this article.&lt;br /&gt;
It can be done from the command line as follows:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
bring eth0 down (distro dependent)&lt;br /&gt;
[host-node]# /etc/init.d/net.eth0 down&lt;br /&gt;
-- or --&lt;br /&gt;
[host-node]# ifdown eth0&lt;br /&gt;
etc.&lt;br /&gt;
&lt;br /&gt;
create the bridge&lt;br /&gt;
[host-node]# brctl addbr br0&lt;br /&gt;
&lt;br /&gt;
add eth0&lt;br /&gt;
[host-node]# brctl addif br0 eth0&lt;br /&gt;
&lt;br /&gt;
each bridge interface must be up, but with no ip address&lt;br /&gt;
[host-node]# ifconfig eth0 0&lt;br /&gt;
&lt;br /&gt;
now run DHCP for the bridge (client dependent)&lt;br /&gt;
[host-node]# dhcpcd br0&lt;br /&gt;
-- or --&lt;br /&gt;
[host-node]# dhclient3 br0&lt;br /&gt;
etc.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
At this stage the host should be present on the LAN (test with pings), much as it was before, only now it is using a bridge that can have other interfaces attached to it.&lt;br /&gt;
&lt;br /&gt;
Starting with a new VE (101), which should have no networking  configured and be running, it is now necessary to add a veth device. First the mac address of eth0 must be determined.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# ifconfig eth0&lt;br /&gt;
...&lt;br /&gt;
HWaddress 00:12:34:56:78:9B&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now a new mac address must be invented, preferably higher than eth0's address.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# easymac.sh -R&lt;br /&gt;
00:12:34:56:78:9A&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The new veth device can be assigned using the above information.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# vzctl set 101 --veth_add veth101.0,00:12:34:56:78:9A,eth0,00:12:34:56:78:9B --save&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now add the new device to the bridge and bring it up on the host.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# ifconfig veth101.0 0&lt;br /&gt;
[host-node]# brctl addif br0 veth101.0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, the network should be fully in place, so run the DHCP client inside the VE&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# vzctl enter 101&lt;br /&gt;
101# dhcpcd venet0:0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category: HOWTO]]&lt;br /&gt;
[[Category:Networking]]&lt;/div&gt;</summary>
		<author><name>Blueroomhosting</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.openvz.org/index.php?title=Common_Networking_HOWTOs&amp;diff=6081</id>
		<title>Common Networking HOWTOs</title>
		<link rel="alternate" type="text/html" href="https://wiki.openvz.org/index.php?title=Common_Networking_HOWTOs&amp;diff=6081"/>
		<updated>2008-06-12T16:06:39Z</updated>

		<summary type="html">&lt;p&gt;Blueroomhosting: /* Private VEs (not directly visible from the LAN) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;While other pages do a great job of going into the details of veth and venet networking, this page is all about getting the results you want quickly.&lt;br /&gt;
&lt;br /&gt;
== Private VEs (not directly visible from the LAN) ==&lt;br /&gt;
&lt;br /&gt;
When starting with a new VE that should not be directly visible on the LAN it is important to choose an appropriate IP address. By running &amp;quot;ifconfig -a&amp;quot; on the host it is possible to see all the networks the host is connected to. The VE should reside on a a new private network, choosing one of the 192.168.X.Y/24 subnets is a good choice.&lt;br /&gt;
&lt;br /&gt;
For example, on a host which is already on a 192.168.1.0/24 subnet then the 192.168.2.0/24 subnet would be a reasonable choice (unless the host is already on that subnet too).&lt;br /&gt;
&lt;br /&gt;
In these examples the host has eth0 with address 192.168.1.53, and 192.168.2.0/24 is free so we will give the VE 192.168.2.1. The VE (101) is assumed to be freshly created and started, with no networking currently set up.&lt;br /&gt;
&lt;br /&gt;
=== Venet ===&lt;br /&gt;
&lt;br /&gt;
Venet routed networking is probably the simplest to set up, simply add the IP address to the VE:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# vzctl set 101 --ipadd 192.168.2.1 --save&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After this the host should be able to ping the VE.&lt;br /&gt;
&lt;br /&gt;
To allow the VE to access the rest of the LAN we must enable forwarding and masquerading, as all activity on the LAN must look like it is coming directly from host (with its IP address).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# echo 1 &amp;gt; /proc/sys/net/ipv4/ip_forward&lt;br /&gt;
[host-node]# iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Veth ===&lt;br /&gt;
&lt;br /&gt;
This is a stub&lt;br /&gt;
&lt;br /&gt;
== Public VEs (with their own IP addresses) ==&lt;br /&gt;
&lt;br /&gt;
=== Static addresses ===&lt;br /&gt;
&lt;br /&gt;
This is a stub.&lt;br /&gt;
&lt;br /&gt;
=== DHCP supplied addresses ===&lt;br /&gt;
&lt;br /&gt;
For this section the following assumptions have been made:&lt;br /&gt;
&lt;br /&gt;
* The host is connected to the LAN by eth0, and also uses DHCP.&lt;br /&gt;
* The DHCP server is another machine on the LAN.&lt;br /&gt;
&lt;br /&gt;
To make the VEs truly part of the LAN it is best to create a bridge that binds them, and the LAN, together.&lt;br /&gt;
Configuring the host to use a bridge when it boots is distribution specific and beyond the scope of this article.&lt;br /&gt;
It can be done from the command line as follows:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
bring eth0 down (distro dependent)&lt;br /&gt;
[host-node]# /etc/init.d/net.eth0 down&lt;br /&gt;
-- or --&lt;br /&gt;
[host-node]# ifdown eth0&lt;br /&gt;
etc.&lt;br /&gt;
&lt;br /&gt;
create the bridge&lt;br /&gt;
[host-node]# brctl addbr br0&lt;br /&gt;
&lt;br /&gt;
add eth0&lt;br /&gt;
[host-node]# brctl addif br0 eth0&lt;br /&gt;
&lt;br /&gt;
each bridge interface must be up, but with no ip address&lt;br /&gt;
[host-node]# ifconfig eth0 0&lt;br /&gt;
&lt;br /&gt;
now run DHCP for the bridge (client dependent)&lt;br /&gt;
[host-node]# dhcpcd br0&lt;br /&gt;
-- or --&lt;br /&gt;
[host-node]# dhclient3 br0&lt;br /&gt;
etc.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
At this stage the host should be present on the LAN (test with pings), much as it was before, only now it is using a bridge that can have other interfaces attached to it.&lt;br /&gt;
&lt;br /&gt;
Starting with a new VE (101), which should have no networking  configured and be running, it is now necessary to add a veth device. First the mac address of eth0 must be determined.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# ifconfig eth0&lt;br /&gt;
...&lt;br /&gt;
HWaddress 00:12:34:56:78:9B&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now a new mac address must be invented, preferably higher than eth0's address.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# easymac.sh -R&lt;br /&gt;
00:12:34:56:78:9A&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The new veth device can be assigned using the above information.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# vzctl set 101 --veth_add veth101.0,00:12:34:56:78:9A,eth0,00:12:34:56:78:9B --save&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now add the new device to the bridge and bring it up on the host.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# ifconfig veth101.0 0&lt;br /&gt;
[host-node]# brctl addif br0 veth101.0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, the network should be fully in place, so run the DHCP client inside the VE&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# vzctl enter 101&lt;br /&gt;
101# dhcpcd venet0:0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category: HOWTO]]&lt;br /&gt;
[[Category:Networking]]&lt;/div&gt;</summary>
		<author><name>Blueroomhosting</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.openvz.org/index.php?title=Common_Networking_HOWTOs&amp;diff=6080</id>
		<title>Common Networking HOWTOs</title>
		<link rel="alternate" type="text/html" href="https://wiki.openvz.org/index.php?title=Common_Networking_HOWTOs&amp;diff=6080"/>
		<updated>2008-06-12T15:50:46Z</updated>

		<summary type="html">&lt;p&gt;Blueroomhosting: Added to HOWTO and Networking categories&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;While other pages do a great job of going into the details of veth and venet networking, this page is all about getting the results you want quickly.&lt;br /&gt;
&lt;br /&gt;
== Private VEs (not directly visible from the LAN) ==&lt;br /&gt;
&lt;br /&gt;
This is a stub.&lt;br /&gt;
&lt;br /&gt;
== Public VEs (with their own IP addresses) ==&lt;br /&gt;
&lt;br /&gt;
=== Static addresses ===&lt;br /&gt;
&lt;br /&gt;
This is a stub.&lt;br /&gt;
&lt;br /&gt;
=== DHCP supplied addresses ===&lt;br /&gt;
&lt;br /&gt;
For this section the following assumptions have been made:&lt;br /&gt;
&lt;br /&gt;
* The host is connected to the LAN by eth0, and also uses DHCP.&lt;br /&gt;
* The DHCP server is another machine on the LAN.&lt;br /&gt;
&lt;br /&gt;
To make the VEs truly part of the LAN it is best to create a bridge that binds them, and the LAN, together.&lt;br /&gt;
Configuring the host to use a bridge when it boots is distribution specific and beyond the scope of this article.&lt;br /&gt;
It can be done from the command line as follows:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
bring eth0 down (distro dependent)&lt;br /&gt;
[host-node]# /etc/init.d/net.eth0 down&lt;br /&gt;
-- or --&lt;br /&gt;
[host-node]# ifdown eth0&lt;br /&gt;
etc.&lt;br /&gt;
&lt;br /&gt;
create the bridge&lt;br /&gt;
[host-node]# brctl addbr br0&lt;br /&gt;
&lt;br /&gt;
add eth0&lt;br /&gt;
[host-node]# brctl addif br0 eth0&lt;br /&gt;
&lt;br /&gt;
each bridge interface must be up, but with no ip address&lt;br /&gt;
[host-node]# ifconfig eth0 0&lt;br /&gt;
&lt;br /&gt;
now run DHCP for the bridge (client dependent)&lt;br /&gt;
[host-node]# dhcpcd br0&lt;br /&gt;
-- or --&lt;br /&gt;
[host-node]# dhclient3 br0&lt;br /&gt;
etc.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
At this stage the host should be present on the LAN (test with pings), much as it was before, only now it is using a bridge that can have other interfaces attached to it.&lt;br /&gt;
&lt;br /&gt;
Starting with a new VE (101), which should have no networking  configured and be running, it is now necessary to add a veth device. First the mac address of eth0 must be determined.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# ifconfig eth0&lt;br /&gt;
...&lt;br /&gt;
HWaddress 00:12:34:56:78:9B&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now a new mac address must be invented, preferably higher than eth0's address.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# easymac.sh -R&lt;br /&gt;
00:12:34:56:78:9A&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The new veth device can be assigned using the above information.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# vzctl set 101 --veth_add veth101.0,00:12:34:56:78:9A,eth0,00:12:34:56:78:9B --save&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now add the new device to the bridge and bring it up on the host.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# ifconfig veth101.0 0&lt;br /&gt;
[host-node]# brctl addif br0 veth101.0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, the network should be fully in place, so run the DHCP client inside the VE&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# vzctl enter 101&lt;br /&gt;
101# dhcpcd venet0:0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category: HOWTO]]&lt;br /&gt;
[[Category:Networking]]&lt;/div&gt;</summary>
		<author><name>Blueroomhosting</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.openvz.org/index.php?title=Common_Networking_HOWTOs&amp;diff=6079</id>
		<title>Common Networking HOWTOs</title>
		<link rel="alternate" type="text/html" href="https://wiki.openvz.org/index.php?title=Common_Networking_HOWTOs&amp;diff=6079"/>
		<updated>2008-06-12T15:43:02Z</updated>

		<summary type="html">&lt;p&gt;Blueroomhosting: New page: While other pages do a great job of going into the details of veth and venet networking, this page is all about getting the results you want quickly.  == Private VEs (not directly visible ...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;While other pages do a great job of going into the details of veth and venet networking, this page is all about getting the results you want quickly.&lt;br /&gt;
&lt;br /&gt;
== Private VEs (not directly visible from the LAN) ==&lt;br /&gt;
&lt;br /&gt;
== Public VEs (with their own IP addresses) ==&lt;br /&gt;
&lt;br /&gt;
=== Static addresses ===&lt;br /&gt;
&lt;br /&gt;
=== DHCP supplied addresses ===&lt;br /&gt;
&lt;br /&gt;
For this section the following assumptions have been made:&lt;br /&gt;
&lt;br /&gt;
* The host is connected to the LAN by eth0, and also uses DHCP.&lt;br /&gt;
* The DHCP server is another machine on the LAN.&lt;br /&gt;
&lt;br /&gt;
To make the VEs truly part of the LAN it is best to create a bridge that binds them, and the LAN, together.&lt;br /&gt;
Configuring the host to use a bridge when it boots is distribution specific and beyond the scope of this article.&lt;br /&gt;
It can be done from the command line as follows:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
bring eth0 down (distro dependent)&lt;br /&gt;
[host-node]# /etc/init.d/net.eth0 down&lt;br /&gt;
-- or --&lt;br /&gt;
[host-node]# ifdown eth0&lt;br /&gt;
etc.&lt;br /&gt;
&lt;br /&gt;
create the bridge&lt;br /&gt;
[host-node]# brctl addbr br0&lt;br /&gt;
&lt;br /&gt;
add eth0&lt;br /&gt;
[host-node]# brctl addif br0 eth0&lt;br /&gt;
&lt;br /&gt;
each bridge interface must be up, but with no ip address&lt;br /&gt;
[host-node]# ifconfig eth0 0&lt;br /&gt;
&lt;br /&gt;
now run DHCP for the bridge (client dependent)&lt;br /&gt;
[host-node]# dhcpcd br0&lt;br /&gt;
-- or --&lt;br /&gt;
[host-node]# dhclient3 br0&lt;br /&gt;
etc.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
At this stage the host should be present on the LAN (test with pings), much as it was before, only now it is using a bridge that can have other interfaces attached to it.&lt;br /&gt;
&lt;br /&gt;
Starting with a new VE (101), which should have no networking  configured and be running, it is now necessary to add a veth device. First the mac address of eth0 must be determined.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# ifconfig eth0&lt;br /&gt;
...&lt;br /&gt;
HWaddress 00:12:34:56:78:9B&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now a new mac address must be invented, preferably higher than eth0's address.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# easymac.sh -R&lt;br /&gt;
00:12:34:56:78:9A&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The new veth device can be assigned using the above information.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# vzctl set 101 --veth_add veth101.0,00:12:34:56:78:9A,eth0,00:12:34:56:78:9B --save&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now add the new device to the bridge and bring it up on the host.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# ifconfig veth101.0 0&lt;br /&gt;
[host-node]# brctl addif br0 veth101.0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, the network should be fully in place, so run the DHCP client inside the VE&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[host-node]# vzctl enter 101&lt;br /&gt;
101# dhcpcd venet0:0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Blueroomhosting</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.openvz.org/index.php?title=Hosting_providers&amp;diff=5820</id>
		<title>Hosting providers</title>
		<link rel="alternate" type="text/html" href="https://wiki.openvz.org/index.php?title=Hosting_providers&amp;diff=5820"/>
		<updated>2008-04-19T08:37:39Z</updated>

		<summary type="html">&lt;p&gt;Blueroomhosting: /* UK */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;OpenVZ makes for a great hosting platform for VPS hosting. The providers below offer VPS services using OpenVZ.&lt;br /&gt;
&lt;br /&gt;
== Canada ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.vistapages.com/vps Vistapages VPS] - IBM &amp;amp; Dell Hardware. MCI/Verizon Backbone. Distros: Centos, Fedora, Debian &amp;amp; more. Full management available. Located in Toronto.&lt;br /&gt;
* [http://vpsville.ca/ VPSVille] - Good network. Good CPU. Good choice of distros: Centos, Fedora, Debian, Ubuntu, Slackware, Gentoo, OpenSUSE, CERN. My favorite OpenVZ provider. [mailto:jak@isp2dial.com John Kelly]&lt;br /&gt;
&lt;br /&gt;
== USA ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.silverrack.com/ SilverRack VPS Hosting] - SilverRack provides affordable VPS hosting using the OpenVZ platform.&lt;br /&gt;
* [http://www.buyavps.com/ BuyAVPS] - BuyAVPS provides stable yet affordable VPS hosting with a great support staff.&lt;br /&gt;
* [http://vpslink.com VPSLink.com] provides virtual private server hosting on the OpenVZ platform.&lt;br /&gt;
* [http://glesys.se GleSYS] is a hosting company specialized in serverhosting. Also offering VPS hosting mainly based on OpenVZ. GleSYS has provided access to server and Cisco hardware for developers from OpenVZ to find problem with VLAN implementation.&lt;br /&gt;
* [http://lylix.net LYLIX] offers affordable VPS hosting with a choice of eight different Linux distributions, dedicated VPS hosting, and specializes in Asterisk/VOIP based hosting including Trixbox, AsteriskNow, Elastix, and PBX-in-a-Flash.  Popular choice for unmanaged IP-PBX services; entire infrastructure built on a High-availability (HA) network across three regional NOCs.&lt;br /&gt;
* [http://www.servergrove.com ServerGrove] uses OpenVZ as the main virtualization platform for its state of the art VPS hosting services.&lt;br /&gt;
* [http://www.tektonic.net TekTonic] provides VPS hosting services using both Virtuozzo and OpenVZ technology.&lt;br /&gt;
&lt;br /&gt;
== UK ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.vt6.co.uk/ VT6 Internet] - Affordable OpenVZ virtual servers based in the UK and USA. Choice of control panels and management options.&lt;br /&gt;
&lt;br /&gt;
* [http://www.weycrest.co.uk/vps-hosting.php Weycrest VPS] - Low Cost, Stable OpenVZ and Parallel's Virtuozzo Virtual Private Server solutions. London UK Hosted at Coreix with a choice of operating systems, and root and control panel options.&lt;br /&gt;
&lt;br /&gt;
* [http://blueroomhosting.com/plans.pxl Blue Room Hosting] - OpenVZ containers hosted at the Bluesquare data centre in Maidenhead, UK&lt;br /&gt;
&lt;br /&gt;
== Portugal ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.efeito.net/ Weblevel.pt] - OpenVZ virtual servers based in Portugal.&lt;br /&gt;
&lt;br /&gt;
== South Africa ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.SoftDux.co.za/ SoftDux] - OpenVZ virtual servers based America &amp;amp; South Africa. All VPS's come with cPanel or Plesk control panels. XEN VPS's also available.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
&lt;br /&gt;
* [[Partners]]&lt;br /&gt;
* [[Download mirrors]]&lt;br /&gt;
* [[VPS vs Dedicated]]&lt;/div&gt;</summary>
		<author><name>Blueroomhosting</name></author>
		
	</entry>
	<entry>
		<id>https://wiki.openvz.org/index.php?title=Hosting_providers&amp;diff=5819</id>
		<title>Hosting providers</title>
		<link rel="alternate" type="text/html" href="https://wiki.openvz.org/index.php?title=Hosting_providers&amp;diff=5819"/>
		<updated>2008-04-19T08:37:17Z</updated>

		<summary type="html">&lt;p&gt;Blueroomhosting: /* UK */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;OpenVZ makes for a great hosting platform for VPS hosting. The providers below offer VPS services using OpenVZ.&lt;br /&gt;
&lt;br /&gt;
== Canada ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.vistapages.com/vps Vistapages VPS] - IBM &amp;amp; Dell Hardware. MCI/Verizon Backbone. Distros: Centos, Fedora, Debian &amp;amp; more. Full management available. Located in Toronto.&lt;br /&gt;
* [http://vpsville.ca/ VPSVille] - Good network. Good CPU. Good choice of distros: Centos, Fedora, Debian, Ubuntu, Slackware, Gentoo, OpenSUSE, CERN. My favorite OpenVZ provider. [mailto:jak@isp2dial.com John Kelly]&lt;br /&gt;
&lt;br /&gt;
== USA ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.silverrack.com/ SilverRack VPS Hosting] - SilverRack provides affordable VPS hosting using the OpenVZ platform.&lt;br /&gt;
* [http://www.buyavps.com/ BuyAVPS] - BuyAVPS provides stable yet affordable VPS hosting with a great support staff.&lt;br /&gt;
* [http://vpslink.com VPSLink.com] provides virtual private server hosting on the OpenVZ platform.&lt;br /&gt;
* [http://glesys.se GleSYS] is a hosting company specialized in serverhosting. Also offering VPS hosting mainly based on OpenVZ. GleSYS has provided access to server and Cisco hardware for developers from OpenVZ to find problem with VLAN implementation.&lt;br /&gt;
* [http://lylix.net LYLIX] offers affordable VPS hosting with a choice of eight different Linux distributions, dedicated VPS hosting, and specializes in Asterisk/VOIP based hosting including Trixbox, AsteriskNow, Elastix, and PBX-in-a-Flash.  Popular choice for unmanaged IP-PBX services; entire infrastructure built on a High-availability (HA) network across three regional NOCs.&lt;br /&gt;
* [http://www.servergrove.com ServerGrove] uses OpenVZ as the main virtualization platform for its state of the art VPS hosting services.&lt;br /&gt;
* [http://www.tektonic.net TekTonic] provides VPS hosting services using both Virtuozzo and OpenVZ technology.&lt;br /&gt;
&lt;br /&gt;
== UK ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.vt6.co.uk/ VT6 Internet] - Affordable OpenVZ virtual servers based in the UK and USA. Choice of control panels and management options.&lt;br /&gt;
&lt;br /&gt;
* [http://www.weycrest.co.uk/vps-hosting.php Weycrest VPS] - Low Cost, Stable OpenVZ and Parallel's Virtuozzo Virtual Private Server solutions. London UK Hosted at Coreix with a choice of operating systems, and root and control panel options.&lt;br /&gt;
&lt;br /&gt;
* [http://blueroomhosting.com/plans.pxl] - OpenVZ containers hosted at the Bluesquare data centre in Maidenhead, UK&lt;br /&gt;
&lt;br /&gt;
== Portugal ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.efeito.net/ Weblevel.pt] - OpenVZ virtual servers based in Portugal.&lt;br /&gt;
&lt;br /&gt;
== South Africa ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.SoftDux.co.za/ SoftDux] - OpenVZ virtual servers based America &amp;amp; South Africa. All VPS's come with cPanel or Plesk control panels. XEN VPS's also available.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
&lt;br /&gt;
* [[Partners]]&lt;br /&gt;
* [[Download mirrors]]&lt;br /&gt;
* [[VPS vs Dedicated]]&lt;/div&gt;</summary>
		<author><name>Blueroomhosting</name></author>
		
	</entry>
</feed>