Maybe it's possible to implement the network connections in a vserver as a sort of virtual ethernet devices. so issueing an ifconfig command gives you a list of the virtual lo device and the virtual ethernet device(s).
-----Oorspronkelijk bericht----- Van: Bill Brigden [mailto:[EMAIL PROTECTED]] Verzonden: dinsdag 3 december 2002 17:22 Aan: [EMAIL PROTECTED] Onderwerp: Re: [vserver] Re: merging into the mainstream kernel in the future Speaking as an observer - I think he is saying we need private network loopback devices - ie. 127.0.0.1 within each vserver - so it is not shared between other vservers - and not publicly available... ----- Original Message ----- From: "John Goerzen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 03, 2002 2:41 PM Subject: [vserver] Re: merging into the mainstream kernel in the future > In article <[EMAIL PROTECTED]>, Jacques Gelinas wrote: > > -We also need private network loopback devices. > > I think you're saying we need a way to have vservers communicate with each > other internally using TCP/IP. > > They already can, thanks to the kernel's dummy driver. Just set an IP for > the host, and one for each vserver, and they can all communicate with those > IPs. > > Of course, the problem is that vserver doesn't yet support multiple IP > addresses from different subnets, so at the moment they can't communicate to > anyone else. I'm just saying, if that problem gets fixed, then you get this > one for free :-) > > >
