On Wed, Nov 16, 2005 at 07:49:33PM -0800, gary ng wrote: > Hi, > > I read in this list a few days ago about the local > 127.0.0.x tricks of having internal communication > between vservers and it works well. However, I notice > a thing about the ip address: > ============================================================ > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue > link/loopback 00:00:00:00:00:00 brd > 00:00:00:00:00:00 > inet 127.0.0.13/8 brd 127.255.255.255 scope host > secondary lo:moresing > 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc > pfifo_fast qlen 1000 > link/ether 00:50:f2:9b:b4:ce brd ff:ff:ff:ff:ff:ff > inet 192.168.0.13/24 brd 127.255.255.255 scope > global secondary eth0:moresing1 > ============================================================= > As seen, the broadcast address has been picked based > on the first ip specified and is wrong for eth0. > > Is there a way to change this ? > > I am using 0.30.204 on debian sarge with the > 2.4/1.2.10 kernel but I believe this is 100% user > space tool thing and should not be affected by kernel.
please try with mainstream 0.30.209, and if the issue persists, please file a bug report to savannah (and of course, let us know how it went :) TIA, Herbert > thanks and regards, > > gary > > __________________________________ > Yahoo! Mail - PC Magazine Editors' Choice 2005 > http://mail.yahoo.com > _______________________________________________ > 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
