Maybe I just haven't installed enough distros, but the times I've installed CentOS, I've had to remember that by default, iptables is blocking inbound port 80 requests. This leads me to believe that I have a non-OS firewall error because I can ping but not http request.
Is there a particular reason for this? Or is it a fail on my end?
Thanks,
David Sent from my Verizon Wireless BlackBerry
On Tue, Apr 7, 2009 at 6:57 PM, David M Lemcoe Jr. forum@lemcoe.com wrote:
Maybe I just haven't installed enough distros, but the times I've installed CentOS, I've had to remember that by default, iptables is blocking inbound port 80 requests. This leads me to believe that I have a non-OS firewall error because I can ping but not http request.
Is there a particular reason for this? Or is it a fail on my end?
Thanks, David
Not every server is a web server.
David M Lemcoe Jr. wrote:
Maybe I just haven't installed enough distros, but the times I've installed CentOS, I've had to remember that by default, iptables is blocking inbound port 80 requests. This leads me to believe that I have a non-OS firewall error because I can ping but not http request.
post install reboot, you would normally get a text/graphical UI that lets you setup firewall policy, selinux policy amongst other things. Just add port 80 to the list of ports you'd want open on all interfaces.
Sent from my Verizon Wireless BlackBerry
its still broken.
So wait, how do I fix my Blackberry for mailing lists? Does this method work? I'm using the GMAIL app for Blackberry.
On 4/7/09, Karanbir Singh mail-lists@karan.org wrote:
David M Lemcoe Jr. wrote:
Maybe I just haven't installed enough distros, but the times I've installed CentOS, I've had to remember that by default, iptables is blocking inbound port 80 requests. This leads me to believe that I have a non-OS firewall error because I can ping but not http request.
post install reboot, you would normally get a text/graphical UI that lets you setup firewall policy, selinux policy amongst other things. Just add port 80 to the list of ports you'd want open on all interfaces.
Sent from my Verizon Wireless BlackBerry
its still broken.
-- Karanbir Singh : http://www.karan.org/ : 2522219@icq _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
David Lemcoe wrote on Tue, 7 Apr 2009 19:12:33 -0400:
So wait, how do I fix my Blackberry for mailing lists? Does this method work? I'm using the GMAIL app for Blackberry.
Yes, this message contains in-reply-to/references. The others did not. Which means that there is no threading available for them.
Kai
So now I know to use the GMail app for Blackberry. Nice to know.
On 4/8/09, Karanbir Singh mail-lists@karan.org wrote:
David Lemcoe wrote:
So wait, how do I fix my Blackberry for mailing lists? Does this method work? I'm using the GMAIL app for Blackberry.
as Kai already pointed out - it has the in-reply-to headers, so thats one issue fixed. Would still be nice if you could trim your posts.
- KB
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Tue, 2009-04-07 at 22:57 +0000, David M Lemcoe Jr. wrote:
Maybe I just haven't installed enough distros, but the times I've installed CentOS, I've had to remember that by default, iptables is blocking inbound port 80 requests. This leads me to believe that I have a non-OS firewall error because I can ping but not http request.
Is there a particular reason for this? Or is it a fail on my end?
---- run program...
system-config-securitylevel
and you can select various well-known ports or just add your own 'lesser known' port numbers.
Craig
On 7 Apr 2009, at 15:57, David M Lemcoe Jr. wrote:
by default, iptables is blocking inbound port 80 requests. This leads me to believe that I have a non-OS firewall error because I can ping but not http request.
Is there a particular reason for this? Or is it a fail on my end?
it's a secure default.
David M Lemcoe Jr. wrote:
Maybe I just haven't installed enough distros, but the times I've installed CentOS, I've had to remember that by default, iptables is blocking inbound port 80 requests. This leads me to believe that I have a non-OS firewall error because I can ping but not http request.
Is there a particular reason for this? Or is it a fail on my end?
Very few ports are open out of the box. I'm not sure, but I think if you choose the webserver (or is it server ??) option at install it might have port 80 open.
Port 22 is open for ssh. I think 631 (cups) is as well, but not positive.
You can configure the firewall with system-config-securitylevel-tui after install (it runs during firstboot as well) where you can easily tell it to turn on port 80 (and/or 443) for web services.
pinging a box has nothing to do with ports are blocked, open, or closed. You can filter pings but I don't believe the firewall does by default.
Thank you for the reply. I think it's "server", and even though I select that, it is still blocked.
I mentioned being able to ping it because I thought it was a NIC problem or something, because apache didn't work when I started it.
Thanks agin for the reply!
On 4/7/09, Michael A. Peters mpeters@mac.com wrote:
David M Lemcoe Jr. wrote:
Maybe I just haven't installed enough distros, but the times I've installed CentOS, I've had to remember that by default, iptables is blocking inbound port 80 requests. This leads me to believe that I have a non-OS firewall error because I can ping but not http request.
Is there a particular reason for this? Or is it a fail on my end?
Very few ports are open out of the box. I'm not sure, but I think if you choose the webserver (or is it server ??) option at install it might have port 80 open.
Port 22 is open for ssh. I think 631 (cups) is as well, but not positive.
You can configure the firewall with system-config-securitylevel-tui after install (it runs during firstboot as well) where you can easily tell it to turn on port 80 (and/or 443) for web services.
pinging a box has nothing to do with ports are blocked, open, or closed. You can filter pings but I don't believe the firewall does by default. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Tue, Apr 07, 2009, David Lemcoe wrote:
Thank you for the reply. I think it's "server", and even though I select that, it is still blocked.
I mentioned being able to ping it because I thought it was a NIC problem or something, because apache didn't work when I started it.
What does ``lsof -n -i:80'' show? Perhaps the server is running, but listening only on 127.0.0.1, localhost?
Bill
On Tue, Apr 7, 2009 at 8:11 PM, Bill Campbell centos@celestial.com wrote:
On Tue, Apr 07, 2009, David Lemcoe wrote:
Thank you for the reply. I think it's "server", and even though I select that, it is still blocked.
I mentioned being able to ping it because I thought it was a NIC problem or something, because apache didn't work when I started it.
What does ``lsof -n -i:80'' show? Perhaps the server is running, but listening only on 127.0.0.1, localhost?
No I figured it out, thank you!
-
Bill Campbell -
Brian Mathis -
Craig White -
David Lemcoe -
David M Lemcoe Jr.
-
Jeremiah Heller -
Kai Schaetzl -
Karanbir Singh -
Michael A. Peters