Re: [Vserver] Network problem

2005-12-19 Thread Jairo Enrique Serrano Castañeda 
WORKs!!THANKS! a LOT men!!!:)---iptables -t nat -I POSTROUTING -s 172.16.3.103
 -j SNAT --to 172.16.3.102---the [EMAIL PROTECTED]@%/$ router! not help me!-- Jairo Enrique Serrano Castañeda
Ingeniero de Sistemas UTBhttp://www.jsnat.comhttp://www.drupal.org.es
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Network problem

2005-12-19 Thread Herbert Poetzl 
On Mon, Dec 19, 2005 at 02:19:50PM -0500, Jairo Enrique Serrano Castañeda wrote:
> 2005/12/19, Herbert Poetzl <[EMAIL PROTECTED]>:
> >
> > On Mon, Dec 19, 2005 at 01:00:48PM -0500, Jairo Enrique Serrano Castañeda
> > wrote:
> > > >
> > > >
> > > > not unexpected, unless your router (172.16.3.16)
> > > > also masquerades private addresses like 192.168.1.2
> > >
> > >
> > > my unusual router are 172.16.3.16
> > >
> > > > how do it?
> > > >
> > > > simple:
> > > >
> > > iptables -t nat -I POSTROUTING -s 192.168.1.2 -j SNAT --to 172.16.3.102
> > >
> > >
> > > i have a "real" network ip of my lan... 172.16.3.103, i do a ip alias
> > >
> > > # Original
> > > iface eth0 inet static
> > > address 172.16.3.102
> > > netmask 255.255.255.0
> > > network 172.16.3.0
> > > broadcast 172.16.3.255
> > > gateway 172.16.3.16
> > > # dns-* options are implemented by the resolvconf package, if
> > > installed
> > > dns-nameservers 200.106.128.4
> > >
> > > #alias
> > > iface eth0:1 inet static
> > > address 172.16.3.103
> > > netmask 255.255.255.0
> > > network 172.16.3.0
> > > broadcast 172.16.3.255
> > > gateway 172.16.3.16
> >
> > the second gateway is confusing ... at least it might
> > give strange results for 'different' gateways/networks
> >
> > dns-nameservers 200.106.128.4
> > >
> > >
> > > in the virtual server have:
> > > [EMAIL PROTECTED]:/# route
> > > Kernel IP routing table
> > > Destination Gateway Genmask Flags Metric RefUse
> > > Iface
> > > 172.16.3.0  *   255.255.255.0   U 0  00
> > eth0
> > > default 172.16.3.16 0.0.0.0 UG0  00
> > eth0
> > > default 172.16.3.16 0.0.0.0 UG0  00
> > eth0
> > >
> > > in the Host server have:
> > > [EMAIL PROTECTED]:~$ route
> > > Kernel IP routing table
> > > Destination Gateway Genmask Flags Metric RefUse
> > > Iface
> > > localnet*   255.255.255.0   U 0  00
> > eth0
> > > default 172.16.3.16 0.0.0.0 UG0  00
> > eth0
> > > default 172.16.3.16 0.0.0.0 UG0  00
> > eth0
> > >
> > > looks equal...
> >
> > yep, should be fine too, your last email contained
> > a guest setup with 192.168.x.x though ...
> 
> 
> sorry for the change... in not know to do... ;)
> 
> > the two ips are functional...
> > >
> > 
> > >
> > > [EMAIL PROTECTED]:~$ ping 172.16.3.102
> > > PING 172.16.3.102 (172.16.3.102) 56(84) bytes of data.
> > > 64 bytes from 172.16.3.102: icmp_seq=1 ttl=64 time=0.023 ms
> > > 64 bytes from 172.16.3.102: icmp_seq=2 ttl=64 time=0.007 ms
> > > --- 172.16.3.102 ping statistics ---
> >
> > as you see, this doesn't tell anything, it just
> > contacts localhost, and the packet is transmitted
> > via the loopback device (does not even hit the
> > network or router)
> >
> > > 2 packets transmitted, 2 received, 0% packet loss, time 999ms
> > > rtt min/avg/max/mdev = 0.007/0.015/0.023/0.008 ms
> > >
> > >
> > 
> > >
> > > [EMAIL PROTECTED]:~$ ping 172.16.3.103
> > > PING 172.16.3.103 (172.16.3.103) 56(84) bytes of data.
> > > 64 bytes from 172.16.3.103: icmp_seq=1 ttl=64 time=0.018 ms
> > > 64 bytes from 172.16.3.103: icmp_seq=2 ttl=64 time=0.008 ms
> > > --- 172.16.3.103 ping statistics ---
> > > 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
> > > rtt min/avg/max/mdev = 0.008/0.013/0.018/0.005 ms
> > >
> > >
> > 
> >
> > try the following (on the host) just to verify that
> > your router is doing the proper stuff:
> >
> > ping -c 2 -I 172.16.3.102 www.google.com
> 
> --
> in the server..
> [EMAIL PROTECTED]:/home/savio# ping -c 2 -I 172.16.3.102 www.google.com
> PING www.l.google.com (64.233.187.104) from 172.16.3.102 : 56(84) bytes of
> data.
> 64 bytes from 64.233.187.104: icmp_seq=1 ttl=242 time=159 ms
> 64 bytes from 64.233.187.104: icmp_seq=2 ttl=242 time=213 ms
> 
> --- www.l.google.com ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 1002ms
> rtt min/avg/max/mdev = 159.191/186.328/213.466/27.140 ms
> --
> in the vserver...
> [EMAIL PROTECTED]:/home/savio# vserver sv1 enter
> mesg: /dev/pts/0: Operation not permitted
> [EMAIL PROTECTED]:/# ping -c 2 -I 172.16.3.102 www.google.com
> ping: unknown host www.google.com
> 

the second ping is also supposed to be done

Re: [Vserver] Network problem

2005-12-19 Thread Jairo Enrique Serrano Castañeda 
2005/12/19, Herbert Poetzl <[EMAIL PROTECTED]>:
On Mon, Dec 19, 2005 at 01:00:48PM -0500, Jairo Enrique Serrano Castañeda wrote:> >> >> > not unexpected, unless your router (172.16.3.16)> > also masquerades private addresses like 
192.168.1.2>>> my unusual router are 172.16.3.16>> > how do it?> >> > simple:> >> iptables -t nat -I POSTROUTING -s 
192.168.1.2 -j SNAT --to 172.16.3.102>>> i have a "real" network ip of my lan... 172.16.3.103
, i do a ip alias>> # Original> iface eth0 inet static> address 172.16.3.102> netmask 255.255.255.0
> network 172.16.3.0> broadcast 172.16.3.255> gateway 172.16.3.16> # dns-* options are implemented by the resolvconf package, if
> installed> dns-nameservers 200.106.128.4>> #alias> iface eth0:1 inet static> address 172.16.3.103
> netmask 255.255.255.0> network 172.16.3.0> broadcast 172.16.3.255
> gateway 172.16.3.16the second gateway is confusing ... at least it mightgive strange results for 'different' gateways/networks
> dns-nameservers 200.106.128.4>>> in the virtual server have:> [EMAIL PROTECTED]:/# route> Kernel IP routing table> Destination Gateway Genmask Flags Metric RefUse
> Iface> 172.16.3.0  *   255.255.255.0   U 0  00 eth0> default 172.16.3.16
 0.0.0.0 UG0  00 eth0> default 172.16.3.16 0.0.0.0 UG0  00 eth0
>> in the Host server have:> [EMAIL PROTECTED]:~$ route> Kernel IP routing table> Destination Gateway Genmask Flags Metric RefUse> Iface> localnet*   
255.255.255.0   U 0  00 eth0> default 172.16.3.16 0.0.0.0 UG0  00 eth0
> default 172.16.3.16 0.0.0.0 UG0  00 eth0>> looks equal...yep, should be fine too, your last email contained
a guest setup with 192.168.x.x though ...sorry for the change... in not know to do... ;)  
> the two ips are functional...> >> [EMAIL PROTECTED]:~$ ping 172.16.3.102
> PING 172.16.3.102 (172.16.3.102) 56(84) bytes of data.> 64 bytes from 172.16.3.102: icmp_seq=1 ttl=64 time=
0.023 ms> 64 bytes from 172.16.3.102: icmp_seq=2 ttl=64 time=0.007 ms> --- 172.16.3.102 ping statistics ---as you see, this doesn't tell anything, it just
contacts localhost, and the packet is transmittedvia the loopback device (does not even hit thenetwork or router)> 2 packets transmitted, 2 received, 0% packet loss, time 999ms> rtt min/avg/max/mdev = 
0.007/0.015/0.023/0.008 ms>> >> [EMAIL PROTECTED]:~$ ping 172.16.3.103
> PING 172.16.3.103 (172.16.3.103) 56(84) bytes of data.> 64 bytes from 172.16.3.103: icmp_seq=1 ttl=64 time=
0.018 ms> 64 bytes from 172.16.3.103: icmp_seq=2 ttl=64 time=0.008 ms> --- 172.16.3.103 ping statistics ---> 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
> rtt min/avg/max/mdev = 0.008/0.013/0.018/0.005 ms>> try the following (on the host) just to verify that
your router is doing the proper stuff: ping -c 2 -I 172.16.3.102 www.google.com--
in the server..[EMAIL PROTECTED]:/home/savio# ping -c 2 -I 172.16.3.102 www.google.comPING www.l.google.com (
64.233.187.104) from 172.16.3.102 : 56(84) bytes of data.64 bytes from 64.233.187.104: icmp_seq=1 ttl=242 time=159 ms64 bytes from 
64.233.187.104: icmp_seq=2 ttl=242 time=213 ms--- www.l.google.com ping statistics ---2 packets transmitted, 2 received, 0% packet loss, time 1002msrtt min/avg/max/mdev = 
159.191/186.328/213.466/27.140 ms--in the vserver...[EMAIL PROTECTED]:/home/savio# vserver sv1 enter
mesg: /dev/pts/0: Operation not permitted[EMAIL PROTECTED]:/# ping -c 2 -I 172.16.3.102 www.google.comping: unknown host 
www.google.com:( dont works... --
 ping -c 2 -I 172.16.3.103 www.google.comif one of those fails (or both) then something isbroken with your routeri try to see in the router (not work with that - the firewall administrator its other people...)
> but not resolv functional...verify that /etc/resolv.conf has proper nameserver
entries inside the guest (i.e. very likely the sameones you have on the host)server:[EMAIL PROTECTED]:/home/savio# cat /etc/resolv.confnameserver 200.106.128.4
vserver:[EMAIL PROTECTED]:/# cat /etc/resolv.confnameserver 200.106.128.4
HTH,Herbert> > any fault

Re: [Vserver] Network problem

2005-12-19 Thread Herbert Poetzl 
On Mon, Dec 19, 2005 at 01:00:48PM -0500, Jairo Enrique Serrano Castañeda wrote:
> >
> >
> > not unexpected, unless your router (172.16.3.16)
> > also masquerades private addresses like 192.168.1.2
> 
> 
> my unusual router are 172.16.3.16
> 
> > how do it?
> >
> > simple:
> >
> iptables -t nat -I POSTROUTING -s 192.168.1.2 -j SNAT --to 172.16.3.102
> 
> 
> i have a "real" network ip of my lan... 172.16.3.103, i do a ip alias
> 
> # Original
> iface eth0 inet static
> address 172.16.3.102
> netmask 255.255.255.0
> network 172.16.3.0
> broadcast 172.16.3.255
> gateway 172.16.3.16
> # dns-* options are implemented by the resolvconf package, if
> installed
> dns-nameservers 200.106.128.4
> 
> #alias
> iface eth0:1 inet static
> address 172.16.3.103
> netmask 255.255.255.0
> network 172.16.3.0
> broadcast 172.16.3.255
> gateway 172.16.3.16

the second gateway is confusing ... at least it might
give strange results for 'different' gateways/networks

> dns-nameservers 200.106.128.4
> 
> 
> in the virtual server have:
> [EMAIL PROTECTED]:/# route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> 172.16.3.0  *   255.255.255.0   U 0  00 eth0
> default 172.16.3.16 0.0.0.0 UG0  00 eth0
> default 172.16.3.16 0.0.0.0 UG0  00 eth0
> 
> in the Host server have:
> [EMAIL PROTECTED]:~$ route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> localnet*   255.255.255.0   U 0  00 eth0
> default 172.16.3.16 0.0.0.0 UG0  00 eth0
> default 172.16.3.16 0.0.0.0 UG0  00 eth0
> 
> looks equal...

yep, should be fine too, your last email contained
a guest setup with 192.168.x.x though ...

> the two ips are functional...
> 
> 
> [EMAIL PROTECTED]:~$ ping 172.16.3.102
> PING 172.16.3.102 (172.16.3.102) 56(84) bytes of data.
> 64 bytes from 172.16.3.102: icmp_seq=1 ttl=64 time=0.023 ms
> 64 bytes from 172.16.3.102: icmp_seq=2 ttl=64 time=0.007 ms
> --- 172.16.3.102 ping statistics ---

as you see, this doesn't tell anything, it just
contacts localhost, and the packet is transmitted
via the loopback device (does not even hit the
network or router)

> 2 packets transmitted, 2 received, 0% packet loss, time 999ms
> rtt min/avg/max/mdev = 0.007/0.015/0.023/0.008 ms
> 
> 
> 
> [EMAIL PROTECTED]:~$ ping 172.16.3.103
> PING 172.16.3.103 (172.16.3.103) 56(84) bytes of data.
> 64 bytes from 172.16.3.103: icmp_seq=1 ttl=64 time=0.018 ms
> 64 bytes from 172.16.3.103: icmp_seq=2 ttl=64 time=0.008 ms
> --- 172.16.3.103 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
> rtt min/avg/max/mdev = 0.008/0.013/0.018/0.005 ms
> 
> 

try the following (on the host) just to verify that
your router is doing the proper stuff:

 ping -c 2 -I 172.16.3.102 www.google.com
 ping -c 2 -I 172.16.3.103 www.google.com

if one of those fails (or both) then something is
broken with your router

> but not resolv functional...

verify that /etc/resolv.conf has proper nameserver
entries inside the guest (i.e. very likely the same
ones you have on the host)

HTH,
Herbert

> > any fault in the config???
> >
> > no, looks fine, although I'd add a prefix (e.g.
> > containing 24) to the interfaces/0
> >
> > HTH,
> > Herbert
> >
> > > --
> > > Jairo Enrique Serrano Castañeda
> > > Ingeniero de Sistemas UTB
> > > http://www.jsnat.com
> > > http://www.drupal.org.es
> >
> > > ___
> > > Vserver mailing list
> > > Vserver@list.linux-vserver.org
> > > http://list.linux-vserver.org/mailman/listinfo/vserver
> >
> >
> 
> 
> --
> Jairo Enrique Serrano Castañeda
> Ingeniero de Sistemas UTB
> http://www.jsnat.com
> http://www.drupal.org.es

> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Network problem

2005-12-19 Thread Jairo Enrique Serrano Castañeda 
not unexpected, unless your router (172.16.3.16)
also masquerades private addresses like 192.168.1.2my unusual router are 172.16.3.16 
> how do it?simple:iptables -t nat -I POSTROUTING -s 
192.168.1.2 -j SNAT --to 172.16.3.102i have a "real" network ip of my lan... 172.16.3.103, i do a ip alias# Original
iface eth0 inet static    address 172.16.3.102    netmask 255.255.255.0    network 172.16.3.0
    broadcast 172.16.3.255    gateway 172.16.3.16    # dns-* options are implemented by the resolvconf package, if installed    dns-nameservers 
200.106.128.4#aliasiface eth0:1 inet static    address 172.16.3.103    netmask 255.255.255.0
    network 172.16.3.0    broadcast 172.16.3.255    gateway 172.16.3.16    dns-nameservers 
200.106.128.4in the virtual server have:[EMAIL PROTECTED]:/# routeKernel IP routing tableDestination Gateway Genmask Flags Metric Ref    Use Iface
172.16.3.0  *   255.255.255.0   U 0  0    0 eth0default 172.16.3.16 0.0.0.0 UG    0  0    0 eth0
default 172.16.3.16 0.0.0.0 UG    0  0    0 eth0in the Host server have:[EMAIL PROTECTED]:~$ routeKernel IP routing table
Destination Gateway Genmask Flags Metric Ref    Use Ifacelocalnet    *   255.255.255.0   U 0  0    0 eth0default 
172.16.3.16 0.0.0.0 UG    0  0    0 eth0default 172.16.3.16 0.0.0.0 UG    0  0    0 eth0
looks equal...the two ips are functional...[EMAIL PROTECTED]:~$ ping 172.16.3.102
PING 172.16.3.102 (172.16.3.102) 56(84) bytes of data.64 bytes from 172.16.3.102: icmp_seq=1 ttl=64 time=0.023
 ms64 bytes from 172.16.3.102: icmp_seq=2 ttl=64 time=0.007 ms--- 172.16.3.102 ping statistics ---2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.007/0.015/0.023/0.008 ms[EMAIL PROTECTED]:~$ ping 172.16.3.103
PING 172.16.3.103 (172.16.3.103) 56(84) bytes of data.64 bytes from 172.16.3.103: icmp_seq=1 ttl=64 time=0.018
 ms64 bytes from 172.16.3.103: icmp_seq=2 ttl=64 time=0.008 ms--- 172.16.3.103 ping statistics ---2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.008/0.013/0.018/0.005 msbut not resolv functional...
> any fault in the config???no, looks fine, although I'd add a prefix (e.g.containing 24) to the interfaces/0HTH,Herbert> --> Jairo Enrique Serrano Castañeda> Ingeniero de Sistemas UTB
> http://www.jsnat.com> http://www.drupal.org.es> ___> Vserver mailing list
> Vserver@list.linux-vserver.org> http://list.linux-vserver.org/mailman/listinfo/vserver
-- Jairo Enrique Serrano CastañedaIngeniero de Sistemas UTBhttp://www.jsnat.comhttp://www.drupal.org.es

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

RE: [Vserver] all network interfaces go down with util-vserver-0.30.209

2005-12-19 Thread metaworx lists 

hi enrico 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> lukas.rueegg [pixworx multimedia]
> Sent: Montag, 19. Dezember 2005 08:58
> To: vserver@list.linux-vserver.org
> Subject: [Vserver] all network interfaces go down with 
> util-vserver-0.30.209
> 
> hi
> 
> we have a setup with kernel 2.6.14.4, just upgraded, patcht against
> vserver 2.0.1. the hosts use bridged network interfaces vor L2
> redundancy. also, we are working with VLANs to separate 
> traffic between
> hosts and vservers.
> 
> when we were installing util-vserver-0.30.209 every time we stopped a
> vserver, not only his private interface got down, but the whole bridge
> including all other interfaces of all vservers...

as far as I could understand vserver.functions the script
(_processSingleInterface) checks if the vlan-device is already created. if
not, it would be done by the script with a dummy address while enabling the
interface.

the same thing happens of course when the interface gets disabled. but
normally the interface then exists, so it won't be put into the
INTERFACE_CMDS_i array and therefore *not* removed.

now I suppose a bug in the line where you test the existance of the
interface:

test -f /proc/net/vlan

will allways fail (at least on our system) since it's a directory. the file
you should check against is

test -f "/proc/net/vlan/$dev"

right? if done so, it works on our installation.

here's the diff

[EMAIL PROTECTED]:/usr/local/lib/util-vserver$ diff vserver.functions{,.orig}
1c1
< # $Id: vserver.functions,v 1.63mdr 2005/12/19 17:32:53 mdr Exp $  --*- sh
-*--
---
> # $Id: vserver.functions,v 1.63 2005/10/30 10:01:41 ensc Exp $  --*- sh
-*--
528c528
<   test -f "/proc/net/vlan/$dev" || {
---
>   test -f /proc/net/vlan || {


regards,
martin.

___

Martin Rueegg Owner and IT staff member
 http://metaworx.ch
metaworx rueegg  mailto:[EMAIL PROTECTED]

Site Office Germany Head Office Switzerland
Birkentalstrasse 4  Ruetiweg 13
DE-97209 Veitshoechheim   CH-8610 Uster

tel: +49 (931) 710 55 90tel: +41 (44) 99 44 044
fax: +49 (931) 970 90 88fax: +41 (44) 99 44 043

gsm: +49 (1520) 8 563 549   gsm: +41 (79) 312 50 15
mailto:[EMAIL PROTECTED] skype: martin.rueegg
___
 

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Network problem

2005-12-19 Thread Herbert Poetzl 
On Mon, Dec 19, 2005 at 10:50:47AM -0500, Jairo Enrique Serrano Castañeda wrote:
> Hello, this its my first message to the list...
> 
> im use Ubuntu server edition, and have a "Linux sv0 2.6.12-vserver #1 SMP
> Thu Dec 15 15:46:41 COT 2005 x86_64 GNU/Linux" recently compiled.
> 
> mi network interface declared -->
> iface eth0 inet static
> address 172.16.3.102
> netmask 255.255.255.0
> network 172.16.3.0
> broadcast 172.16.3.255
> gateway 172.16.3.16
> dns-nameservers 200.106.128.4
> 
> [EMAIL PROTECTED]:/usr/src$ cat /etc/vservers.conf
> # Configuration file for the vservers service
> # BACKGROUND=yes
> # start the vservers on tty9, in background so the rest of the
> # boot process end early
> BACKGROUND=no
> 
> [EMAIL PROTECTED]:/usr/src$ cat /etc/vservers/newvserver-vars
> # Configuration file for newvserver
> # See man newvserver for the variables that you can set here.
> #/etc/vserver/newvserver-vars
> 
> # Architecture: overide on non-Debian host such as Redhat otherwise dpkg
> # will detect whether we are i386/powerpc/sparc/etc
> #ARCH=""
> 
> # Which debian distribution (Warning. unstable and testing distributions
> # change frequently so you can not expect it to work out of the box).
> DIST="breezy"
> 
> # Local or nearest location of a debian mirror (must include the /debian)
> MIRROR="http://archive.ubuntu.com/ubuntu/";
> 
> # Default network interface for vservers:
> INTERFACE="eth0"
> 
> # Package caching
> PKGCACHE=1
> ---
> [EMAIL PROTECTED]:/usr/src$ cat /etc/vservers/sv1/interfaces/0/dev
> eth0
> ---
> [EMAIL PROTECTED]:/usr/src$ cat /etc/vservers/sv1/interfaces/0/ip
> 192.168.1.2
>  kernel config
> #
> # Linux VServer
> #
> CONFIG_VSERVER_LEGACY=y
> # CONFIG_VSERVER_LEGACY_VERSION is not set
> # CONFIG_VSERVER_NGNET is not set
> CONFIG_VSERVER_PROC_SECURE=y
> CONFIG_VSERVER_HARDCPU=y
> CONFIG_VSERVER_HARDCPU_IDLE=y
> # CONFIG_INOXID_NONE is not set
> # CONFIG_INOXID_UID16 is not set
> # CONFIG_INOXID_GID16 is not set
> CONFIG_INOXID_UGID24=y
> # CONFIG_INOXID_INTERN is not set
> # CONFIG_INOXID_RUNTIME is not set
> # CONFIG_XID_TAG_NFSD is not set
> # CONFIG_VSERVER_DEBUG is not set
> 
> 
> [EMAIL PROTECTED]:/# ping 66.94.234.13
> PING 66.94.234.13 (66.94.234.13) 56(84) bytes of data.
> 
> --- 66.94.234.13 ping statistics ---
> 2 packets transmitted, 0 received, 100% packet loss, time 1000ms
> 
> [EMAIL PROTECTED]:/# ping google.com
> 
> [EMAIL PROTECTED]:/# vi /etc/resolv.conf
> [EMAIL PROTECTED]:/# cat /etc/resolv.conf
> #search unitecnologica.edu.co
> nameserver 200.106.130.235
> [EMAIL PROTECTED]:/# cat /etc/network/interfaces
> # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
> # /usr/share/doc/ifupdown/examples for more information.
> [EMAIL PROTECTED]:/# ifconfig
> eth0  Link encap:Ethernet  HWaddr 00:11:25:1E:76:BA
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:5483 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:746 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:568480 (555.1 KiB)  TX bytes:115507 (112.7 KiB)
>   Interrupt:24
> 
> 
> i have dns problems in the virtual server 1,

not unexpected, unless your router (172.16.3.16)
also masquerades private addresses like 192.168.1.2

> how do it?

simple:

 iptables -t nat -I POSTROUTING -s 192.168.1.2 -j SNAT --to 172.16.3.102

> any fault in the config???

no, looks fine, although I'd add a prefix (e.g. 
containing 24) to the interfaces/0

HTH,
Herbert

> --
> Jairo Enrique Serrano Castañeda
> Ingeniero de Sistemas UTB
> http://www.jsnat.com
> http://www.drupal.org.es

> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] all network interfaces go down with util-vserver-0.30.209

2005-12-19 Thread Herbert Poetzl 
On Mon, Dec 19, 2005 at 08:44:55AM +0100, lukas.rueegg [pixworx multimedia] 
wrote:
> hi
> 
> we have a setup with kernel 2.6.14.4, just upgraded, patcht against 
> vserver 2.0.1. the hosts use bridged network interfaces vor L2 
> redundancy. also, we are working with VLANs to separate traffic between 
> hosts and vservers.
> 
> when we were installing util-vserver-0.30.209 every time we stopped a 
> vserver, not only his private interface got down, but the whole bridge 
> including all other interfaces of all vservers...
> 
> after downgrading to util-vserver-0.30.207, everything works fine again.
> 
> a sample configuration of a vserver:
> $ more 0/*
> ::
> 0/dev
> ::
> br0.2
> ::
> 0/ip
> ::
> 62.12.154.32
> ::
> 0/name
> ::
> public
> ::
> 0/prefix
> ::
> 24
> 
> 
> the relevant part output part of ifconfig (on the host):
> $ sudo ifconfig
> 
> br0.2 Link encap:Ethernet  HWaddr 00:11:43:E3:11:39
>   inet addr:62.12.154.12  Bcast:62.255.255.255  Mask:255.255.255.0
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:2808646 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:3383124 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:424670986 (404.9 MiB)  TX bytes:1168460377 (1.0 GiB)
> 
> br0.2:pub Link encap:Ethernet  HWaddr 00:11:43:E3:11:39
>   inet addr:62.12.154.32  Bcast:62.12.154.255  Mask:255.255.255.0
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> 
> the first is the host bridge br0.2. the second is the aliased interface 
> of the vserver. both are in VLAN 2.
> 
> 
> output of ip addr list:
> 
> $ ip addr list
> 1: lo:  mtu 16436 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:11:43:e3:11:39 brd ff:ff:ff:ff:ff:ff
> 3: eth1:  mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:11:43:e3:11:3a brd ff:ff:ff:ff:ff:ff
> 4: eth2:  mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:12:17:54:de:1e brd ff:ff:ff:ff:ff:ff
> 5: br0:  mtu 1500 qdisc noqueue
> link/ether 00:11:43:e3:11:39 brd ff:ff:ff:ff:ff:ff
> 6: br0.2:  mtu 1500 qdisc noqueue
> link/ether 00:11:43:e3:11:39 brd ff:ff:ff:ff:ff:ff
> inet 62.12.154.12/24 brd 62.255.255.255 scope global br0.2
> inet 62.12.154.102/24 brd 62.12.154.255 scope global secondary br0.2:0
> inet 62.12.154.57/24 brd 62.12.154.255 scope global secondary 
> br0.2:public
> inet 62.12.154.56/24 brd 62.12.154.255 scope global secondary 
> br0.2:public
> inet 62.12.154.32/24 brd 62.12.154.255 scope global secondary 
> br0.2:public

didn't even know that it was possible to do that?
IMHO the interface names are supposed to be _unique_
which is definitely wrong here (for the aliases)

I'd suggest to avoid the alias at all, unless you
require them for very old tools (like ifconfig)

> where all br0.2:public are vserver interfaces.
> 
> we first where thinking that it could cause problems that all vserver 
> interface aliases are the same. but because also the host interface 
> (br0.2) gets down, we aren't convinced of this anymore...
> 
> does anyone has a hint about this?

well, as soon as the 62.12.154.12/24 IP is taken 
down, all others will follow. that's how the linux
networking people consider it proper ...

but as far as I understood, that one should not be
used by a guest, or is it? if so, please assign a
dummy IP to the host (e.g. 62.12.154.2/24) and be
done ...

HTH,
Herbert

> thanks and regards
> lukas.rueegg
> 
> 
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

[Vserver] Network problem

2005-12-19 Thread Jairo Enrique Serrano Castañeda 
Hello, this its my first message to the list...im use Ubuntu server edition, and have a "Linux sv0 2.6.12-vserver #1 SMP Thu Dec 15 15:46:41 COT 2005 x86_64 GNU/Linux" recently compiled.mi network interface declared -->
iface eth0 inet static    address 172.16.3.102    netmask 255.255.255.0    network 172.16.3.0
    broadcast 172.16.3.255    gateway 172.16.3.16    dns-nameservers 200.106.128.4
[EMAIL PROTECTED]:/usr/src$ cat /etc/vservers.conf# Configuration file for the vservers service# BACKGROUND=""># start the vservers on tty9, in background so the rest of the# boot process end earlyBACKGROUND=""
[EMAIL PROTECTED]:/usr/src$ cat /etc/vservers/newvserver-vars# Configuration file for newvserver# See man newvserver for the variables that you can set here.#/etc/vserver/newvserver-vars
# Architecture: overide on non-Debian host such as Redhat otherwise dpkg# will detect whether we are i386/powerpc/sparc/etc#ARCH=""# Which debian distribution (Warning. unstable and testing distributions
# change frequently so you can not expect it to work out of the box).DIST="breezy"# Local or nearest location of a debian mirror (must include the /debian)MIRROR="
http://archive.ubuntu.com/ubuntu/"# Default network interface for vservers:INTERFACE="eth0"# Package cachingPKGCACHE=1---[EMAIL PROTECTED]:/usr/src$ cat /etc/vservers/sv1/interfaces/0/dev
eth0---[EMAIL PROTECTED]:/usr/src$ cat /etc/vservers/sv1/interfaces/0/ip192.168.1.2 kernel config
## Linux VServer#CONFIG_VSERVER_LEGACY=y# CONFIG_VSERVER_LEGACY_VERSION is not set# CONFIG_VSERVER_NGNET is not setCONFIG_VSERVER_PROC_SECURE=yCONFIG_VSERVER_HARDCPU=yCONFIG_VSERVER_HARDCPU_IDLE=y
# CONFIG_INOXID_NONE is not set# CONFIG_INOXID_UID16 is not set# CONFIG_INOXID_GID16 is not setCONFIG_INOXID_UGID24=y# CONFIG_INOXID_INTERN is not set# CONFIG_INOXID_RUNTIME is not set# CONFIG_XID_TAG_NFSD is not set
# CONFIG_VSERVER_DEBUG is not set[EMAIL PROTECTED]:/# ping 66.94.234.13PING 66.94.234.13 (
66.94.234.13) 56(84) bytes of data.--- 66.94.234.13 ping statistics ---2 packets transmitted, 0 received, 100% packet loss, time 1000ms[EMAIL PROTECTED]:/# ping 
google.com[EMAIL PROTECTED]:/# vi /etc/resolv.conf[EMAIL PROTECTED]:/# cat /etc/resolv.conf#search unitecnologica.edu.conameserver 200.106.130.235
[EMAIL PROTECTED]:/# cat /etc/network/interfaces# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or# /usr/share/doc/ifupdown/examples for more information.[EMAIL PROTECTED]:/# ifconfigeth0  Link encap:Ethernet  HWaddr 00:11:25:1E:76:BA
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1  RX packets:5483 errors:0 dropped:0 overruns:0 frame:0  TX packets:746 errors:0 dropped:0 overruns:0 carrier:0  collisions:0 txqueuelen:1000
  RX bytes:568480 (555.1 KiB)  TX bytes:115507 (112.7 KiB)  Interrupt:24i have dns problems in the virtual server 1, how do it?any fault in the config???
-- Jairo Enrique Serrano CastañedaIngeniero de Sistemas UTBhttp://www.jsnat.comhttp://www.drupal.org.es
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Script testfs.sh on Reiser3

2005-12-19 Thread Michael S. Zick 
On Mon December 19 2005 09:00, micah wrote:
> 
> Michael S. Zick wrote:
> > wolf466:/mnt# showattr dir_one
> > ---bui- dir_one
> > 
> > wolf466:/mnt# setattr --barrier dir_one
> > wolf466:/mnt# showattr dir_one
> > ---Bui- dir_one
> 
> What version of util-vserver are you using? When you do the setattr
> --barrier it should result in:
> 
> ---BUi- dir_one
>
That is a directory, not a file.

Since a directory can not be hard linked,
should not that be ---Bui- dir_one like it
is on Reiser3?

> 
> This was fixed in version 0.30.208 of util-vserver.
>
The above is the  "over clipped" follow-up for Reiser4.

- - - -

Linux: 2.6.14
Reiser4: 1.0.5
Vserver: 2.0.1
util-vserver: 0.30.209

Mike
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Script testfs.sh on Reiser3

2005-12-19 Thread micah 


Michael S. Zick wrote:
> wolf466:/mnt# showattr dir_one
> ---bui- dir_one
> 
> wolf466:/mnt# setattr --barrier dir_one
> wolf466:/mnt# showattr dir_one
> ---Bui- dir_one

What version of util-vserver are you using? When you do the setattr
--barrier it should result in:

---BUi- dir_one

This was fixed in version 0.30.208 of util-vserver.

Micah
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Script testfs.sh on Reiser3

2005-12-19 Thread Michael S. Zick 
On Mon December 19 2005 07:06, Michael S. Zick wrote:
> On Sun December 18 2005 21:39, Herbert Poetzl wrote:
> > 
> - - - - -
> > 
> > > PS: anyone tried this on reiser4?
> > 
> > PS: did it get into to the kernel yet?
> > 
> It is in Linux-2.6.14-mm2 but it is
> still only a namesys.com patch for plain Linux-2.6.14
> Which applies cleanly to Linux-2.6.14+Vserver-2.0.1
> 
Sort of works - Just enough to mislead someone.

The Vserver utils...

wolf466:/mnt# showattr dir_one
---bui- dir_one

wolf466:/mnt# setattr --barrier dir_one
wolf466:/mnt# showattr dir_one
---Bui- dir_one

But the stock extended attributes and acl functions
are not yet included.  Meaning that when they are
incorporated, you will probably wipe out any of
the Vserver bits.

wolf466:/mnt# chattr +d dir_one
chattr: Inappropriate ioctl for device while reading flags on dir_one

wolf466:/mnt# lsattr dir_one
wolf466:/mnt#
- - - neither error message nor display of attributes - - -

And the ACL functions:

wolf466:/mnt# getfacl dir_one
# file: dir_one
# owner: root
# group: root
user::rwx
group::r-x
other::---

wolf466:/mnt# setfacl -d -m g:mszick:-x dir_one
setfacl: dir_one: Operation not supported

But the make filesystem command for Reiser4 will tell you
what is built-in:
(If you presume "permission" == "extended attributes")

wolf466:mkfs# ./mkfs.reiser4 -p /dev/loop0
/Builds/BLDS/reiser4progs-1.0.5/progs/mkfs/.libs/lt-mkfs.reiser4 1.0.5
Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed by 
reiser4progs/COPYING.

Default profiles:
format: "format40" (id:0x0 type:0x8)
journal:"journal40" (id:0x0 type:0xf)
oid:"oid40" (id:0x0 type:0x9)
alloc:  "alloc40" (id:0x0 type:0xe)
key:"key_large" (id:0x1 type:0x10)
node:   "node40" (id:0x0 type:0x2)
statdata:   "stat40" (id:0x0 type:0x1)
nodeptr:"nodeptr40" (id:0x3 type:0x1)
direntry:   "cde40" (id:0x2 type:0x1)
tail:   "plain40" (id:0x6 type:0x1)
extent: "extent40" (id:0x5 type:0x1)
acl:"absent (id:0x4 type:0x1)"
permission: "absent (id:0x0 type:0x6)"
regular:"reg40" (id:0x0 type:0x0)
directory:  "dir40" (id:0x1 type:0x0)
symlink:"sym40" (id:0x2 type:0x0)
special:"spl40" (id:0x3 type:0x0)
hash:   "r5_hash" (id:0x1 type:0x3)
fibration:  "ext_1_fibre" (id:0x2 type:0x4)
formatting: "smart" (id:0x2 type:0x5)

Block size 4096 will be used.
Linux 2.6.14-vs2-r4 is detected.
Uuid 888f553a-78a8-4565-aa48-aad2dddcd2d6 will be used.
Reiser4 is going to be created on /dev/loop0.
(Yes/No): no

- - - -
I guess that makes it official for the current version.

Mike

___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Script testfs.sh on Reiser3

2005-12-19 Thread Michael S. Zick 
On Sun December 18 2005 21:39, Herbert Poetzl wrote:
> 
- - - - -
> 
> > PS: anyone tried this on reiser4?
> 
> PS: did it get into to the kernel yet?
> 
It is in Linux-2.6.14-mm2 but it is
still only a namesys.com patch for plain Linux-2.6.14
Which applies cleanly to Linux-2.6.14+Vserver-2.0.1

Will give the thing a try - 
First hint: No extended attribute or ACL questions
shown on menuconfig -
Either they aren't there yet or they are "standard" (like xfs).
The namesys.com pages give them an "honorable mention".
- - - -

# uname -a
Linux wolf466 2.6.14-vs2-r4 #1 PREEMPT Sun Dec 18 08:11:06 CST 2005 i686 
GNU/Linux

Mike
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Re: [Vserver] Script testfs.sh on Reiser3

2005-12-19 Thread Michael S. Zick 
On Sun December 18 2005 21:39, Herbert Poetzl wrote:
> On Sat, Dec 17, 2005 at 12:39:44PM -0600, Michael S. Zick wrote:
> > Group,
> > 
> > The only conclusion I can reach is either
> > something is broke or incomplete in lsattr
> 
> humm, why?
>
A new-comer's mistake - I foolishly thought that
the stock extended attribute lister would also
show the vserver portion of the extended attributes.
 
> > or Perhaps the script should not be expecting 
> > that the output of lsattr on a reiser3 filesystem 
> > to make any sense.
> 
> again, why? for me it looks pretty fine?
> please elaborate what am I missing ...
> 
Documentation induced cockpit error -

I configured kernel and util-vserver without the 
legacy interface as recommended.

Then happened to cut and paste the usage of
testfs.sh from an example that included the
" -l " (ell) option.

Test script works much better when you don't
tell it to use an interface that isn't there.

A corrected example and some other Reiserfs
gotch's are in my summary mail.

Mike
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

[Vserver] all network interfaces go down with util-vserver-0.30.209

2005-12-19 Thread lukas.rueegg [pixworx multimedia] 

hi

we have a setup with kernel 2.6.14.4, just upgraded, patcht against
vserver 2.0.1. the hosts use bridged network interfaces vor L2
redundancy. also, we are working with VLANs to separate traffic between
hosts and vservers.

when we were installing util-vserver-0.30.209 every time we stopped a
vserver, not only his private interface got down, but the whole bridge
including all other interfaces of all vservers...

after downgrading to util-vserver-0.30.207, everything works fine again.

a sample configuration of a vserver:
$ more 0/*
::
0/dev
::
br0.2
::
0/ip
::
62.12.154.32
::
0/name
::
public
::
0/prefix
::
24


the relevant part output part of ifconfig (on the host):
$ sudo ifconfig

br0.2 Link encap:Ethernet  HWaddr 00:11:43:E3:11:39
  inet addr:62.12.154.12  Bcast:62.255.255.255  Mask:255.255.255.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:2808646 errors:0 dropped:0 overruns:0 frame:0
  TX packets:3383124 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:424670986 (404.9 MiB)  TX bytes:1168460377 (1.0 GiB)

br0.2:pub Link encap:Ethernet  HWaddr 00:11:43:E3:11:39
  inet addr:62.12.154.32  Bcast:62.12.154.255  Mask:255.255.255.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

the first is the host bridge br0.2. the second is the aliased interface
of the vserver. both are in VLAN 2.


output of ip addr list:

$ ip addr list
1: lo:  mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:11:43:e3:11:39 brd ff:ff:ff:ff:ff:ff
3: eth1:  mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:11:43:e3:11:3a brd ff:ff:ff:ff:ff:ff
4: eth2:  mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:12:17:54:de:1e brd ff:ff:ff:ff:ff:ff
5: br0:  mtu 1500 qdisc noqueue
link/ether 00:11:43:e3:11:39 brd ff:ff:ff:ff:ff:ff
6: br0.2:  mtu 1500 qdisc noqueue
link/ether 00:11:43:e3:11:39 brd ff:ff:ff:ff:ff:ff
inet 62.12.154.12/24 brd 62.255.255.255 scope global br0.2
inet 62.12.154.102/24 brd 62.12.154.255 scope global secondary br0.2:0
inet 62.12.154.57/24 brd 62.12.154.255 scope global secondary
br0.2:public
inet 62.12.154.56/24 brd 62.12.154.255 scope global secondary
br0.2:public
inet 62.12.154.32/24 brd 62.12.154.255 scope global secondary
br0.2:public


where all br0.2:public are vserver interfaces.


we first where thinking that it could cause problems that all vserver
interface aliases are the same. but because also the host interface
(br0.2) gets down, we aren't convinced of this anymore...

does anyone has a hint about this?

thanks and regards
lukas.rueegg



___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

[Vserver] all network interfaces go down with util-vserver-0.30.209

2005-12-19 Thread lukas.rueegg [pixworx multimedia] 

hi

we have a setup with kernel 2.6.14.4, just upgraded, patcht against 
vserver 2.0.1. the hosts use bridged network interfaces vor L2 
redundancy. also, we are working with VLANs to separate traffic between 
hosts and vservers.


when we were installing util-vserver-0.30.209 every time we stopped a 
vserver, not only his private interface got down, but the whole bridge 
including all other interfaces of all vservers...


after downgrading to util-vserver-0.30.207, everything works fine again.

a sample configuration of a vserver:
$ more 0/*
::
0/dev
::
br0.2
::
0/ip
::
62.12.154.32
::
0/name
::
public
::
0/prefix
::
24


the relevant part output part of ifconfig (on the host):
$ sudo ifconfig

br0.2 Link encap:Ethernet  HWaddr 00:11:43:E3:11:39
  inet addr:62.12.154.12  Bcast:62.255.255.255  Mask:255.255.255.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:2808646 errors:0 dropped:0 overruns:0 frame:0
  TX packets:3383124 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:424670986 (404.9 MiB)  TX bytes:1168460377 (1.0 GiB)

br0.2:pub Link encap:Ethernet  HWaddr 00:11:43:E3:11:39
  inet addr:62.12.154.32  Bcast:62.12.154.255  Mask:255.255.255.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

the first is the host bridge br0.2. the second is the aliased interface 
of the vserver. both are in VLAN 2.



output of ip addr list:

$ ip addr list
1: lo:  mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0:  mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:11:43:e3:11:39 brd ff:ff:ff:ff:ff:ff
3: eth1:  mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:11:43:e3:11:3a brd ff:ff:ff:ff:ff:ff
4: eth2:  mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:12:17:54:de:1e brd ff:ff:ff:ff:ff:ff
5: br0:  mtu 1500 qdisc noqueue
link/ether 00:11:43:e3:11:39 brd ff:ff:ff:ff:ff:ff
6: br0.2:  mtu 1500 qdisc noqueue
link/ether 00:11:43:e3:11:39 brd ff:ff:ff:ff:ff:ff
inet 62.12.154.12/24 brd 62.255.255.255 scope global br0.2
inet 62.12.154.102/24 brd 62.12.154.255 scope global secondary br0.2:0
inet 62.12.154.57/24 brd 62.12.154.255 scope global secondary 
br0.2:public
inet 62.12.154.56/24 brd 62.12.154.255 scope global secondary 
br0.2:public
inet 62.12.154.32/24 brd 62.12.154.255 scope global secondary 
br0.2:public



where all br0.2:public are vserver interfaces.


we first where thinking that it could cause problems that all vserver 
interface aliases are the same. but because also the host interface 
(br0.2) gets down, we aren't convinced of this anymore...


does anyone has a hint about this?

thanks and regards
lukas.rueegg


___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver