I’m still using Panther - I’ll upgrade to Tiger when I’ve finished backing up everything.
In the meantime, I noticed something quite weird the other day. If I attempt to view my web pages stored on this computer (ie, the one I’m typing this in from, ny iMac at home) then it only works some of the time.
Specifically, if I try to use the real IP address, given to me by my ISP, or the domain name (again given to me by my ISP, dialup0-1213.optusnet.com.au, or whatever it is at that moment), then it times out.
If I use 192.168.1.2, or the local hostname, then it works fine.
I wonder if there’s a setting somewhere which only allows http access from those addresses. I can’t figure it out - with no firewall there shouldn’t be a reason this doesn’t work, unless Optus is blocking incoming traffic to addresses within it’s domain.
Update: This would seem to be it. I can ssh into my machine, but not http in.
Well, as early as 2001 and as late as 7/2005, there are indeed postings online discussing Optus blocking inbound traffic on port 80. I’d try changing your webserver port by editing httpd.conf and seeing if you can then access the site from the outside world - either that, or getting nmap and running a port scan against yourself.
1 hour, 18 minutes after the fact.
Thanks Zach. I’ve used OS X’s port scan, and it indeed shows that port 80 is blocked under Optus. I did google this, but didn’t find a hit - I didn’t look that hard though.
Other blocked ports are: 111 (sunrpc), 139 (netbios-ssn), 515 (printer), 548 (afpovertcp), 631 (ipp) and 3306 (mysql).
I’ve mucked around with using rinetd to remap another port to 80, and since I’m planning on running a web server on my nslu2, i’d like to be able to do proper port forwarding over nat, but it doesn’t seem to work too well.
I haven’t yet tried creating a virtualhost under apache, using another port, but I’ll try that next.
8 hours, 30 minutes after the fact.