Scott Dowdle | 3 Feb 2009 23:03
Favicon

Updated contributed precreated OS Templates

Greetings,

Just wanted to mention that update my contributed precreated OS Templates for:

CentOS 4, 5 i386/x86_64

centos-4-i386-default-4.7-20090117.tar.gz   17-Jan-2009 15:35  115M
centos-4-i386-minimal-4.7-20090117.tar.gz   17-Jan-2009 15:37   95M 
centos-4-x86_64-default-4.7-20090117.tar.gz 17-Jan-2009 15:40  122M
centos-4-x86_64-minimal-4.7-20090117.tar.gz 17-Jan-2009 15:42  100M
centos-5-i386-default-5.2-20090117.tar.gz   17-Jan-2009 15:45  125M
centos-5-i386-minimal-5.2-20090117.tar.gz   17-Jan-2009 15:48  102M
centos-5-x86_64-default-5.2-20090117.tar.gz 17-Jan-2009 15:51  130M
centos-5-x86_64-minimal-5.2-20090117.tar.gz 17-Jan-2009 15:53  113M

Fedora 9, 10 i386/x86_64

fedora-9-i386-default-20090203.tar.gz       03-Feb-2009 13:54  140M 
fedora-9-i386-minimal-20090203.tar.gz       03-Feb-2009 13:57  118M
fedora-9-x86_64-default-20090203.tar.gz     03-Feb-2009 14:02  147M
fedora-9-x86_64-minimal-20090203.tar.gz     03-Feb-2009 14:06  137M
fedora-10-i386-default-20090203.tar.gz      03-Feb-2009 13:45  149M
fedora-10-x86_64-default-20090203.tar.gz    03-Feb-2009 13:50  170M

I re-based them all on them all on the newer "official" OS Templates that Kir posted last month.  The new
official OS Templates have udev installed and work well no matter what additional software you install. 
Older templates would often break if udev got installed.  That is no longer the case.

How do my contributed OS Templates differ from the "official" ones:

(Continue reading)

Scott Dowdle | 3 Feb 2009 23:17
Favicon

Re: Updated contributed precreated OS Templates

Greetings,

Opps, that last email had a number of typos so I'm resending the corrected/updated info:

- - - - -

Just wanted to mention that update my contributed precreated OS Templates for:

CentOS 4, 5 i386/x86_64

centos-4-i386-default-4.7-20090117.tar.gz   17-Jan-2009 15:35  115M
centos-4-i386-minimal-4.7-20090117.tar.gz   17-Jan-2009 15:37   95M
centos-4-x86_64-default-4.7-20090117.tar.gz 17-Jan-2009 15:40  122M
centos-4-x86_64-minimal-4.7-20090117.tar.gz 17-Jan-2009 15:42  100M
centos-5-i386-default-5.2-20090117.tar.gz   17-Jan-2009 15:45  125M
centos-5-i386-minimal-5.2-20090117.tar.gz   17-Jan-2009 15:48  102M
centos-5-x86_64-default-5.2-20090117.tar.gz 17-Jan-2009 15:51  130M
centos-5-x86_64-minimal-5.2-20090117.tar.gz 17-Jan-2009 15:53  113M

Fedora 9, 10 i386/x86_64

fedora-9-i386-default-20090203.tar.gz       03-Feb-2009 13:54  140M
fedora-9-i386-minimal-20090203.tar.gz       03-Feb-2009 13:57  118M
fedora-9-x86_64-default-20090203.tar.gz     03-Feb-2009 14:02  147M
fedora-9-x86_64-minimal-20090203.tar.gz     03-Feb-2009 14:06  137M
fedora-10-i386-default-20090203.tar.gz      03-Feb-2009 13:45  149M
fedora-10-x86_64-default-20090203.tar.gz    03-Feb-2009 13:50  170M

I re-based them all on the newer "official" OS Templates that Kir posted last month.  The new official OS
Templates have udev installed and work well no matter what additional software you install.  Older
(Continue reading)

Vitaliy Gusev | 4 Feb 2009 16:22
Favicon

Re: Putting DHCP server on VENET-connected node

Hi! 
On 30 January 2009 12:29:29 Dariush Pietrzak wrote:
> Hi,
>  the problem with DHCP and venet, is that dhcp packets are adressed to
> 255.255.255.255, and you can't route packets destined for 255.255.255.255
> with routing tables.
>  But, you sure can direct them towards venet-connected node using other means, 
> here's the one:

I wonder. Why don't you use veth interface for this purpose?

> 
> host: # iptables -t mangle -A PREROUTING -d 255.255.255.255 -j ROUTE --gw 192.168.190.250
> 
> host: # iptables -nvL -t mangle:
> 12394 4069K ROUTE      0    --  *      *       0.0.0.0/0            255.255.255.255     ROUTE gw:192.168.190.250
> 
> then inside vz guest:
> 
> 
> tcpdump -n -i venet0:0
> 
> 02:31:34.337137 IP 192.168.190.138.68 > 192.168.190.250.67: BOOTP/DHCP, Request from
00:a1:3d:1d:b9:a5, length 548
> 
> 08:31:35.188004 IP 192.168.190.138.68 > 192.168.190.250.67: BOOTP/DHCP, Request from
00:a1:3b:1d:b9:a5, length 548
> 08:31:35.188040 IP 192.168.190.250 > 192.168.190.138: ICMP 192.168.190.250 udp port 67 unreachable,
length 556

(Continue reading)

Denis V. Lunev | 4 Feb 2009 18:15
Favicon

Re: Putting DHCP server on VENET-connected node

VENET device is explicitly NOARP, so this can't be fixed.
pls use VETH

Regards,
	Den

On Wed, 2009-02-04 at 18:22 +0300, Vitaliy Gusev wrote:
> Hi! 
> On 30 January 2009 12:29:29 Dariush Pietrzak wrote:
> > Hi,
> >  the problem with DHCP and venet, is that dhcp packets are adressed to
> > 255.255.255.255, and you can't route packets destined for 255.255.255.255
> > with routing tables.
> >  But, you sure can direct them towards venet-connected node using other means, 
> > here's the one:
> 
> I wonder. Why don't you use veth interface for this purpose?
> 
> > 
> > host: # iptables -t mangle -A PREROUTING -d 255.255.255.255 -j ROUTE --gw 192.168.190.250
> > 
> > host: # iptables -nvL -t mangle:
> > 12394 4069K ROUTE      0    --  *      *       0.0.0.0/0            255.255.255.255     ROUTE gw:192.168.190.250
> > 
> > then inside vz guest:
> > 
> > 
> > tcpdump -n -i venet0:0
> > 
> > 02:31:34.337137 IP 192.168.190.138.68 > 192.168.190.250.67: BOOTP/DHCP, Request from
(Continue reading)

dan | 5 Feb 2009 07:07
Picon
Gravatar

ubuntu precreated template problem

I'm having problems with the precreated 8.04-x86 template.

After setting the normal ipaddress/hostname/gateway settings and
starting the template, I get no networking.  The CentOS template works
fine, so its not my networking setup.  If I modify the
/etc/network/interfaces file to be like a typical system, networking
will restart without error, but I cannot access the network still.

The host node is Ubuntu 8.04.

Ideas? Suggestions?
dan

======================================
root <at> www:/# /etc/init.d/networking restart
 * Reconfiguring network interfaces...
/etc/network/interfaces:14: interface lo declared allow-auto twice
ifdown: couldn't read interfaces file "/etc/network/interfaces"
/etc/network/interfaces:14: interface lo declared allow-auto twice
ifup: couldn't read interfaces file "/etc/network/interfaces"
                                                      [fail]

======================================
root <at> www:/# cat /etc/network/interfaces
# This configuration file is auto-generated.
# WARNING: Do not edit this file, otherwise your changes will be lost.
# Please edit template /etc/network/interfaces.template instead.

auto lo
iface lo inet loopback
(Continue reading)

Thorsten Schifferdecker | 5 Feb 2009 07:15
Favicon

Re: ubuntu precreated template problem

remove the /etc/network/interfaces.template loopback entries:

 > auto lo
 > iface lo inet loopback
 > 	address 127.0.0.1
 > 	netmask 255.0.0.0
 > 	broadcast 127.255.255.255
 > 	up ip route replace 127.0.0.0/8 dev lo

and restart the container ...

or remove entries in /etc/network/interfaces and
restart networking or ifup lo

Seem to affected all precreated debian and ubunutu distros at 
http://download.openvz.org/template/precreated/ only

Bye,
Thorsten
--
OpenVZ Power User with a swirl
http://debian.systs.org/category/openvz/

dan schrieb:
> I'm having problems with the precreated 8.04-x86 template.
> 
> After setting the normal ipaddress/hostname/gateway settings and
> starting the template, I get no networking.  The CentOS template works
> fine, so its not my networking setup.  If I modify the
> /etc/network/interfaces file to be like a typical system, networking
(Continue reading)

Martin Maurer | 5 Feb 2009 10:32

RE: ubuntu precreated template problem

We have quite new a good tested standard templates for Debian Etch, Lenny, Ubuntu 8.04 - 32 and 64 bit.
See ftp://pve.proxmox.com/appliances/system/
(or http://pve.proxmox.com/appliances/system/)

FYI, all are build using the dab:
http://pve.proxmox.com/wiki/Debian_Appliance_Builder

Br, Martin

http://pve.proxmox.com

> -----Original Message-----
> From: users-bounces@...
[mailto:users-bounces@...] On
> Behalf Of dan
> Sent: Donnerstag, 05. Februar 2009 07:08
> To: users@...
> Subject: [Users] ubuntu precreated template problem
> 
> I'm having problems with the precreated 8.04-x86 template.
> 
> After setting the normal ipaddress/hostname/gateway settings and
> starting the template, I get no networking.  The CentOS template works
> fine, so its not my networking setup.  If I modify the
> /etc/network/interfaces file to be like a typical system, networking
> will restart without error, but I cannot access the network still.
> 
> The host node is Ubuntu 8.04.
> 
> Ideas? Suggestions?
(Continue reading)

Jason Voorhees | 5 Feb 2009 16:26
Picon

Broadcast traffic on veth interfaces

Hi people:

I'm a newbie in OpenVZ world yet. With a little help of Google and
OpenVZ wiki I understood that it's necessary to use veth instead of
venet to be able to deal with broadcast traffic in a VE. This is true,
right?
So I created the corresponding veth to my VE and attached it to a
bridge. Now my VE has an eth0 interface, it has its own IP address and
works nicely: send and receive ICMP messages (with ping), I can get
into VE trough SSH, etc.

But I can see that broadcast traffic isn't working very well yet. My
VE is running a Samba server but I can't find its netbios name (from
the HN) using nmblookup. Also from the VE I can't find any netbios
host in my network using nmblookup except the VE host itself.

I followed the steps of the wiki:
http://wiki.openvz.org/Veth#Virtual_Ethernet_devices_can_be_joined_in_one_bridge

Do I need to do anything else in my OpenVZ environment?

Kernel: 2.6.18-92.1.18.el5.028stab060.2
vzctl version: vzctl version 3.0.23

Any help would be appreciated. Thanks, bye
dan | 5 Feb 2009 17:07
Picon
Gravatar

Re: ubuntu precreated template problem

Thanks Thorsten & Martin.  Both options worked well.

dan

On Thu, Feb 5, 2009 at 4:32 AM, Martin Maurer <martin@...> wrote:
> We have quite new a good tested standard templates for Debian Etch, Lenny, Ubuntu 8.04 - 32 and 64 bit.
> See ftp://pve.proxmox.com/appliances/system/
> (or http://pve.proxmox.com/appliances/system/)
>
> FYI, all are build using the dab:
> http://pve.proxmox.com/wiki/Debian_Appliance_Builder
>
> Br, Martin
>
> http://pve.proxmox.com
>
>
>> -----Original Message-----
>> From: users-bounces@...
[mailto:users-bounces@...] On
>> Behalf Of dan
>> Sent: Donnerstag, 05. Februar 2009 07:08
>> To: users@...
>> Subject: [Users] ubuntu precreated template problem
>>
>> I'm having problems with the precreated 8.04-x86 template.
>>
>> After setting the normal ipaddress/hostname/gateway settings and
>> starting the template, I get no networking.  The CentOS template works
>> fine, so its not my networking setup.  If I modify the
(Continue reading)

Scott Dowdle | 5 Feb 2009 23:46
Favicon

Re: ubuntu precreated template problem

Dan,

----- "dan" <dantrevino@...> wrote:

> I'm having problems with the precreated 8.04-x86 template.
> 
> After setting the normal ipaddress/hostname/gateway settings and
> starting the template, I get no networking.  The CentOS template
> works
> fine, so its not my networking setup.  If I modify the
> /etc/network/interfaces file to be like a typical system, networking
> will restart without error, but I cannot access the network still.
> 
> The host node is Ubuntu 8.04.
> 
> Ideas? Suggestions?
> dan
> 
> 
> ======================================
> root <at> www:/# /etc/init.d/networking restart
>  * Reconfiguring network interfaces...
> /etc/network/interfaces:14: interface lo declared allow-auto twice
> ifdown: couldn't read interfaces file "/etc/network/interfaces"
> /etc/network/interfaces:14: interface lo declared allow-auto twice
> ifup: couldn't read interfaces file "/etc/network/interfaces"
>                                                       [fail]
> 
> ======================================
> root <at> www:/# cat /etc/network/interfaces
(Continue reading)


Gmane