Latest Debian lenny (VE) breaks networking? [message #33235] |
Wed, 01 October 2008 13:54  |
gnutered
Messages: 12 Registered: April 2008
|
Junior Member |
|
|
I'm running Debian lenny both on my HN and in a VE. When creating the VE, I use the debian-5.0-minimal template from the debian-systs repository. When I assign an IP and then ping, it works.
If I then go through the apt-get dist-upgrade process, networking no longer works. Pings no longer get responded to.
I've tried using the official lenny+openvz kernel, and also the debian-systs lenny kernel, and the result is the same.
I can't think of a good way to fix this other than updating all those packages one at a time and see what breaks it.
Any clues from anyone else?
I'm not running any iptables, BTW, and just using bog standard networking.
|
|
|
Re: Latest Debian lenny (VE) breaks networking? [message #33278 is a reply to message #33235] |
Fri, 03 October 2008 14:56   |
gnutered
Messages: 12 Registered: April 2008
|
Junior Member |
|
|
Fixed, my bad.
I didn't understand the use of the dist files, and when I created a new template, I called it lenny.tar.gz. This meant, because of filename matches, vzctl didn't know that this was a debian distro, and was defaulting to treating it like a redhat one.
So, it was trying to set the IP address with the wrong command, and failing.
Correct naming of template, as described at http://wiki.openvz.org/Configuring_container_creation
|
|
|
|
|