I don't think this is possible given the current architecture of the vsd.
It operates at the network layer...for what you propose it would have to
operate at the application layer. So, in effect, it would have to be a
proxy for every service that you want to virtualize (I guess--since it
would have to interpret the request to find the name being requested).
Not nearly as simple a task as selecting a chroot based on the incoming
IP. I may be wrong...I'm not intimately familiar with the internals of
FreeVSD, but I'm making a guess that it's similar to (or is derived
from?) virtuald, which operates on IP.
I'd welcome someone to prove me wrong. But I think virtual services in
the traditional sense (with good tools for allowing users to still
manipulate their 'own' virtual servers) are as close as you'll get to
what you request.
Just my .02
John Sechrest wrote:
> This is a great idea.
>
> I would love to see this.
>
>
>
>
> "denny @ d - Rex . net" <[email protected]> writes:
>
> % because the cost of ip addresses,
> % why not implement NAT/ipchain in VSD, so that each virtual domain
> % have one local ip (192.168.x.x) instead of real ip.
> % all share only one (or two for dns) real ip and then VSD decide
> % which local ip to use.
> %
> % this will also make the whole system more SECURE.
> % because virtual host do not have real ip, it's invisible to outsider.
> % this way, VSD automagically function as a firewall too.
> %
> %
> %
> %
> %
>
> -----
> John Sechrest . Helping people use
> CEO PEAK - . computers and the Internet
> Public Electronic . more effectively
> Access to Knowledge,Inc .
> 1600 SW Western, Suite 180 . Internet: [EMAIL PROTECTED]
> Corvallis Oregon 97333 . (541) 754-7325
> . http://www.peak.org/~sechrest
--
--
Joe Cooper <[EMAIL PROTECTED]>
Affordable Web Caching Proxy Appliances
http://www.swelltech.com
