PDA

View Full Version : [ubuntu] can't find ways to open ports



imparja2
March 12th, 2009, 03:58 AM
I've installed firestarter and added rules to allow service to several of these ports but for some reason when I run tests to check if they're open they say they're all closed. Is there something wrong with the test or is firestarter to cause of blocking ports I want to open? please How can I determine and fix it step by step?

madverb
March 12th, 2009, 04:13 AM
paste the output of

sudo iptables -L
here.

cdenley
March 12th, 2009, 02:38 PM
I've installed firestarter and added rules to allow service to several of these ports but for some reason when I run tests to check if they're open they say they're all closed. Is there something wrong with the test or is firestarter to cause of blocking ports I want to open? please How can I determine and fix it step by step?

How are you testing your ports? Are you using a router? What are you trying to accomplish with a firewall? Also, posting the output for this command in addition to the one mentioned may be helpful:


netstat -tln

Neo_The_User
March 12th, 2009, 05:01 PM
My dad uses Firestarter (used to use the SELinux GUI in Fedora) to secure out LAN. Might wanna try those out.

The Cog
March 12th, 2009, 05:26 PM
If the the test is saying that the ports are closed then the firewall is probably allowing the packets through. If a firewall is blocking packets to a port, then you would normally get no reply when you try to talk to the port. My guess is that the operating system is replying to your connection request and saying the port is closed because there is no application listening for incoming calls on the port.

Use netstat to see if there is in fact an application listening on the port in question.

imparja2
March 15th, 2009, 11:11 PM
so for example if I'm downloading from p2p connections the closed ports will then open since I'm running this application. So how do I get the ports listening what commands should I use. If they're listening will that mean the test at grc shieldsup will confirm they're open?. Is this the type of test I should be doing?

bodhi.zazen
March 16th, 2009, 03:37 AM
Not exactly.

Take a look at the tcp protocol. new packets are rejected, so your ports are closed.

related and established packets are accepted, but even though these packets are accepted your ports are still closed.

"grc shieldsup" is not really considered to be the best source of information.

http://en.wikipedia.org/wiki/Transmission_Control_Protocol#Connection_establish ment

Then you will need to look at how iptables works.

http://bodhizazen.net/Tutorials/iptables