I'm working on setting up Apache on my router (on which I've installed Tomato, a custom linux-based firmware package). I have succeeded with installing Apache, and believe I have configured it correctly, but cannot get the default "It works!" page to load.

Running netstat, I can see the value in the "Recv-Q" column increment every time I attempt to access the served file via the browser, but its as if Apache won't or can't respond to the request. Tailing the Apache error_log also yields nothing.

Does anyone see anything obvious, or have some suggestions for things to try in order to get things working? Can I provide any additional info that would help?

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.
If this question can be reworded to fit the rules in the help center, please edit the question.

1

Would someone mind clarifying why this question is off-topic? Also, if you think it would be more appropriate on another stack exchange site, feel free to mention that as well (SuperUser perhaps?). Thanks!
–
WilcoFeb 14 '13 at 17:55

3 Answers
3

In the firewall's INPUT chain, logdrop line kills your connection. It is a catch-all chain for dropping all unwanted traffic. The rule processing never reaches the web rules. You must move the ACCEPT rules above the logdrop rule.

Ah goot catch! I went ahead and tried that and now netstat correctly shows "0.0.0.0:80" but I still experience the same behavior (basically times out).
–
WilcoFeb 14 '13 at 0:43

check iptables now. Run iptables -L -n and see if connection to port 80 is allowed.
–
Daniel t.Feb 14 '13 at 0:45

just updated the post with the output from iptables -L
–
WilcoFeb 14 '13 at 1:00

did you use a web interface or command line to open the ports in iptables? Can you disable the firewall for a moment? Just wanted to see if this is a firewall or Apache config issue.
–
Daniel t.Feb 14 '13 at 1:16

I actually opened the ports directly via the command line. Went ahead and turned off the firewall and still can't seem to get Apache to respond.
–
WilcoFeb 14 '13 at 1:28