OpenVZ Forum: Support » *solved* howto install network in a newly created VE with ext IP?

Home » General » Support » *solved* howto install network in a newly created VE with ext IP?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

*solved* howto install network in a newly created VE with ext IP? [message #15839]

Wed, 15 August 2007 02:28

locutius
Messages: 125
Registered: August 2007

Senior Member

standard install of CentOS 4.5 on a twin dual-core 2GB remote server

- i have installed the ovzkernel 2.6.18-8.1.8.el5.028stab039.1PAE
- 1 have created a VE 101 with centos-4i386-default
- i have set the external IP into VE 101
- i have set the VE to start on HN boot
- i have set the hostname
- i have set the the diskspace

i can ping the VE IP from the HN

ssh is running in the VE, i can update and install in the VE using vzyum

problem: there is no network in the VE. from within the VE i cannot reach any host. from a remote desktop if i ssh to the VE i land in the HN

the Wiki and the PDF User Gude do not cover this problem

i have been told by a senior member of the forum that 10,000 of people have successfully installed OpenZV. is there anyone plz who knows why the VE is not networked?

thanks in advance

[Updated on: Sat, 18 August 2007 19:25]

Report message to a moderator

Re: howto install network in a newly created VE with ext IP? [message #15862 is a reply to message #15839]

Wed, 15 August 2007 06:44

vaverin
Messages: 708
Registered: September 2005

Senior Member

Most interesting fact here is that external connections lands in HW.

Could you please try to ping VE when VE is stopped?

thank you,
Vasily Averin

Report message to a moderator

Re: howto install network in a newly created VE with ext IP? [message #16012 is a reply to message #15862]

Sat, 18 August 2007 19:17

dowdle
Messages: 261
Registered: December 2005
Location: Bozeman, Montana

Senior Member

This problem has been solved... it turned out that the hn was configured to have eth0:0 - eth0:9 and the hn was trapping the network traffic before it was getting to the vps. Removing the eth0:0 - eth0:9 configuration on the hn resolved the problem.

--
TYL, Scott Dowdle
Belgrade, Montana, USA

Report message to a moderator