the netmask "should" be irrelevant, I have over 100 virtual servers running 
where there IPs where from different subnets, rember that on the www we are 
all on the same subnet


At 07:49 PM 5/16/01 -0700, you wrote:
>Thanx Dave! yeah sorry the netmask is 255.255.255.224
>, that was a typo! How can I specify that netmask,
>suppose I want to add a virtual host with IP
>14.123.44.63 with netmask 255.255.255.224 how can I do
>that 'cuz when I add a Vhost with that IP the vsd
>always adds it with mask 255.255.255.255 and broadcast
>14.255.255.255 !!!
>
>--- "Dave C." <[EMAIL PROTECTED]> wrote:
> > > 1) I cant set the subnet-mask while I add a
> > virtual
> > > client with vsdadm, My subnet mask is
> > 255.255.255.40
> > > !!
> >
> > This is not a valid netmask. 255.255.255.240 looks
> > more like it.
> >
> > > 2)Another problem is my original servers httpd and
> > > telnet are not working and when I try to start
> > inetd I
> > > get an error for valid options!!
> >
> > You can't use any of the virtualized services on the
> > host server. This is
> > because virtuald binds to all ip addresses and all
> > used ports and there's no
> > way to tell it that a service must run on the
> > hosting server and not on a
> > virtual.
> >
> > > 3)Another problem is how can I install msql/mysql
> > and
> > > other apache modules in a virtual machine?
> >
> > Just the same way you would on a real server (use
> > the source Luke).
> >
> > > 4) how can I use tcpwrappers with my virtual
> > hosts???
> >
> > This is an interesting issue. You should use
> > tcpwrappers around virtuald. It
> > would be much better to have virtuald compiled
> > against the tcpwrappers
> > library....
> >
> > Dave.
> >
>
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! Auctions - buy the things you want at great prices
>http://auctions.yahoo.com/

Reply via email to