these are my current iptables settings:
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
DROP tcp -- anywhere anywhere tcp flags:FIN,SYN,RST,PSH,ACK,URG/NONE
DROP tcp -- anywhere anywhere tcp flags:!FIN,SYN,RST,ACK/SYN state NEW
DROP tcp -- anywhere anywhere tcp flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,RST,PSH,ACK,URG
ACCEPT all -- anywhere anywhere
ACCEPT tcp -- anywhere anywhere tcp dpt:ftp
ACCEPT tcp -- anywhere anywhere tcp dpt:http
ACCEPT tcp -- anywhere anywhere tcp dpt:https
ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
The problem is, that when I ping the server, I get this result:
PING XX.XX.XX.XX (XX.XX.XX.XX): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
etc...
So I guess it has something to do with the iptables. As you can see, the sites inside the server are running just fine:
nmap -p 80 XX.XX.XX.XX
Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-27 09:44 CDT
Nmap scan report for XX.XX.XX.XX
Host is up (0.0019s latency).
PORT STATE SERVICE
80/tcp open http
So, the question is: what can I do to avoid the ping timeout? (and what are the disadvantages of returning a ping timeout?)