Ok, I can see that it isn't the loopback addresses as such that are the problem, probably more the routing. I can see that the loopback address is available in all virtual servers and that applications on each virtual server can bind to ports on that address and that these will not be accessible from other vservers or the host. However, this doesn't help if I want to assign real ip addresses to the loopback address. Jeff Gustavo wrote: > Hi, I didn't use private loopback as far as I know but they are still > working fine for me, did you try with nodev option? > > I hope it helps. If you need I can send you my config. > > Regards > Gustavo > > > On 8/22/07, *Jeff Williams* <jeffw@globaldial.com > <mailto:jeffw@globaldial.com>> wrote: > > I read in a post by Herbert Poetzl on the Tue, 31 Jul that private > loopback addresses per virtual server are available in the devel > releases. > > Will it be possible to alias these private loopback addresses and > still > be private from the other servers? I have some virtual servers sitting > behind a load balancer. They have loopback aliases from the load > balancer virtual IP. However, if I add a alias to the loopback on one > vserver, all of the vservers on that host use that vserver rather > than > going through the load balancer. Will private loopbacks fix this? > > Or, how can I tell a vserver that it should responded to an IP > address, > without all of the other vservers seeing that IP address? > > Regards, > Jeff > > > > > > -- > -------------------------------------------------------------- > Promové la cultura, compartí tus libros