> Hello all.
>
> I am trying to find a way to have services running on my own system
> which have web-like interfaces. At the same time, I may also be
> running an actual web-server. I could avoid conflict by chosing
> another port, (but that's ugly), or perhaps by putting some object
> in the filesystem (non-portable), but the best way I've come up with
> so far is to define a new domain name, giving the new services URLs
> such as http://myservice.local/.
> This has several problems, which I would like to know the possibility
> of overcoming, namely:
>
> 0) Can I declare a second looback device, and if so, must the address
> come out of the 127. address space ?
> 1) Can the resulting interface be configured so that servers intending
>
> to serve the machine as a whole (via INADDR_ANY) will be unable to
> find it, and will not contend with it ?
>
> If (1) is not possible, would adding this functionality
> (reserved/private interfaces) to the existing kernel be acceptable ?
> Would it be generally useful ? Would it interact badly with anything ?
>
> Thanks
> Martin.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]
Set up a domainname and a virtual server in apache. Limit the incoming
connections to 127.0.0.1/lo and x.y.z.a/eth0...
Have fun...
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
