Ports are closed but iptables is disabled?

July 1, 2012 at 13:24:48
Specs: CentOS 6.0
I'm running CentOS Core on Amazon EC2's platform. I'm trying to open port 5060 and 69 but I can't get it to work. In EC2 I have the security group edited to open those ports, and I have even stopped the IPTables service, but I can't access those ports. If I use an online tool to test to see if they're open it reports those ports are closed.
Am I missing something? How could those ports be closed if I have them open in EC2's firewall, and have disabled iptables?

I'm running CentOS 6 on Amazon EC2. Is there another firewall or something else that could be keeping those ports closed? Thanks!


See More: Ports are closed but iptables is disabled?

Report •

#1
July 1, 2012 at 13:45:44
Silly question, but do you actually have services running on those two ports? Without a program opening the port they are not going to show as open in an online tool. IPTables should be the only firewall on a Centos system, so stopping the service should let anything in (not a very good idea, although it sounds as if Amazon provide their own firewall).

I can't think why port 69 (TFTP) should be a problem if you are running a TFTP server, but be aware that some ISPs block port 5060 (Session Initiation Protocol).

If all else fails I'd say that your best bet is to talk to Amazon support.


Report •
Related Solutions


Ask Question