Re: eth1 on VPS [message #7483 is a reply to message #7459] |
Sun, 15 October 2006 16:28 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to previous message](/theme/ovz3/images/down.png) |
ferp2
Messages: 29 Registered: May 2006
|
Junior Member |
|
|
Thanks for your response, John. Your suggestion sounds like a good one. I have not yet had the chance to verify it, but would like to add the following about the VE 104 set up:
VE 104 was initially set up to use 192.168.0.4 on the venet0 interface. Later, I decided to add add eth1 to VE 104 using the Quote: | vzctl set 104 --netdev_add eth1 --save
| command.
If I log in to VE 104 and do ifconfig -a I can see the eth1 interface, although it is not functioning. Problems occur once I set eth1 within VE 104 to 192.168.0.4. Vass posted the following:
Quote: | However the presense of venet device should not break network connectivity.
|
This is true, perhaps, if venet0 has not been previously set to an ipaddress. In my case, I had already set the VE 104 ipaddress from the HN, as in:
Quote: | vzctl set 104 --ipadd 192.168.0.104 --save
|
Although I haven't yet determined if this is the solution ,I look forward to hearing what Vass has to say about this.
Ferp2
|
|
|