domain/IP + server problem (moreinfo)

[Sam DeVore]

On 4/6/02 8:46 AM, "Paul Welty" <1pwelty at bellsouth.net> wrote:

> Ok, here is the current situation, and I apologize for taking up time with
> this, but I just cannot figure it out.
> 
> Here's what I tried (based on the advice so far).
> 
> -restarted OS X
> -started Frontier
> -stopped the server
> -ran "userland.portForward(80,8080)" (it asked for admin password; took a
> second or two; returned 'true', which I guess means it went okay)
> -started server
> -checked "Server/Set Port" and it says "8080"
> 
> Control Panel works (on 127.0.0.1:8080) but still nothing else does. I can
> create a Manila site, but I can't get to it.
> 
> But, going to 127.0.0.1 gives me the correct response based on the "default"
> setting in config.mainResponder.domains. So, it looks like the webserver is
> working and the port forwarding is working.
> 
> I triple-checked that my domain name->dynamic IP resolves correctly, and
> I've tried using the IP address in the browser, too. I've checked the
> FileMaker server on port 81, and it works fine, so the IP side of it seems
> correct.
> 
> All this leads me to think that I'm having a repeat of whatever problem I
> had previously with config.mainResponder.domains. I tried deleting all
> domains except "default" but nothing changes in the behavior.
> 
> It seems crucial to me that 127.0.0.1 works but that the IP address doesn't.
> But, I have no idea what that might mean.

There are some kind of strange things that happen when you have internal
lookbacks and such on os x and you are using ip forwarding.  Eric helped me
to sort some of them out, you might try typing this in the console and see
if it helps

sudo ipfw add 102 fwd 127.0.0.1,8080 tcp from any to 127.0.0.1 80 in

Sam D