On Fri, Feb 18, 2005 at 10:58:20PM -0500, Stas Bekman wrote: > it's set in server/core.c: > > apr_sockaddr_ip_get(&c->remote_ip, c->remote_addr); > > it obtains this information from the live socket connected to a client, > whereas Apache-Test tries to resolve the hostname of your machine since at > the time when it sets this value there is no connection yet.
Thanks, Stas. This is what I needed to know. Based on testing that my hosting provider and I have done with the nonblock.c test program[1] that Joe wrote, we have discovered what appears to be differences in the way that a socket establishes connections when running inside of a jail. Basically, it appears safe to bind to 0.0.0.0 but trying to connect to this address fails. Replacing the default sin_addr with the 127.0.0.1 loopback works (as does using the code inside the #ifdef BEOS block; but that's only necessary for the client socket, not the listening socket). We've taken the discussion over to the FreeBSD developers list. I'll report back any findings if anyone on this list is interested in the behavior of sockets inside a FreeBSD jail. Otherwise, I'll keep the discussion on the test-dev list as Stas suggested. Thanks, William [1] http://www.apache.org/~jorton/nonblock.c -- Knowmad Services Inc. http://www.knowmad.com
