Lon Hohberger <lhh@xxxxxxxxxx> wrote .. > On Fri, 2010-01-08 at 21:12 +0530, avi@xxxxxxxxxxxxxxxxx wrote: > > My problem is that I only have a single public IP address, to serve my web server > and my question is this: > > > > Is this the end of the road, for installing apache as a service with ONE public > IP address?? > > In order to manage the 'only possible' ip address on an interface or set > of interfaces, the ip.sh script would have to handle a whole lot more > than it was designed: > > - device activation > - module loading > - routing configuration > > This would it very complex. Right now, it is very simple: use existing > routes and devices. > > Possible solutions: > > * Edit the ip.sh script to do what you want directly. > > * Use a custom script to start apache & bring up your IP address rather > than using ip.sh to do it. > > * Statically assign a couple of IP addresses and mask them using noarp > option or arptables. > > -- Lon Thanks for the suggestion, but I went in for another public IP from my ISP, so this issue is resolved. ( lightened up my pocket a bit..but thats ok ;P )
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
