From: Bernhard Duebi (bernhard.duebi_at_schweiz.ch)
Date: Wed 29 Sep 2004 - 20:30:14 BST
On Tue, 2004-09-28 at 10:42, Herbert Poetzl wrote:
> On Mon, Sep 27, 2004 at 10:20:00PM +0200, Bernhard Duebi wrote:
> > On Thu, 2004-09-23 at 19:14, Herbert Poetzl wrote:
> > > On Thu, Sep 23, 2004 at 01:44:39PM +0200, Bernhard Duebi wrote:
> > > > You can easely reproduce it. Just start portmapper within a vserver and
> > > > you see two lines in /var/log/messages
> > >
> > > well, tested here with 184.108.40.206, and the portmapd
> > > (mandrake) starts fine inside a vserver with limited
> > > IPs (chbind) ...
> > >
> > > you can also 'remove' or not set the VXF_HIDE_NETIF
> > > to make _all_ interfaces visible to a vserver
> > > (without givin any additional caps)
> > My host is SuSE Linux 9.1 Pro, with kernel 220.127.116.11-vs1.9.2 and
> > util-vserver 0.30.193. I have 3 vservers, 1 debian sarge, 1 fedora core
> > 2 and 1 suse 9.1, all created with vserver name build.
> > All vservers show the same problem. In the attached files you find some
> > information on the vservers and the kernel. Maybe you can tell me what's
> > wrong.
> first I'd remove those 127.x.x.x entries on lo
> those for sure will confuse some apps and are
> not needed ...
> then try with a single ip assigned as an alias
> and add the VXF_HIDE_NETIF to the config, let
> me know what your portmap reports with -dv
in the attachment you find 2 sets of files. The files with "flags" in
the name are with the VXF_HIDE_NETIF flag. The others are without any
flags. The results are basicaly the same.
Hope this helps.
Vserver mailing list