[SOLVED] Disable the firewall on Debian Linux 2.6.32-5-686
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Hi, I need to disable my firewall on Debian. I do not know what is preventing inbound connections to my machine, as I have another Debian machine (also 2.6.* but 64-bit) which accepts inbound connections, and I have already flushed all my ipTables. I used the script @ http://www.linuxquestions.org/questi...rewall-763690/
What kind of 'inbound connections' are you talking about? If you flushed your iptables then you should be able to connect to your machine if you didn't install something else like for example firestarter. Could it be that you are trying to connect to something that's not listening, a service that didn't start up or so?
I tried this with numerous ports. I have a bittorrent client which uses port 27260 for incoming connections. Incoming connections are not working in the client. I also tried accessing a MySQL database on 3306 on my machine from another machine, and it does not work. Accessing 3306 on the local machine does work. (The SQL user has access from host %, i.e. anywhere).
For what MySQL concerns, did you configure the bind-address to the IP you want to connect to? Default installation has 127.0.0.1 set as bind-address so it's only normal that your MySQL instance isn't responding on a LAN / public IP if that's the case. Can you check what listening ports/service you have running? Run:
Cool beans! I forgot about the netstat utility. It seems the problem was with MySQL only listening on 127.0.0.1. The bind-address is now 0.0.0.0 and it's working. Some other ports are still not working, but those must be similar problems...
You're welcome! Glad you've found at least a solution for MySQL. I'm sure you'll figure out what's wrong with the other processes/services. If you need assistance, don't hesitate to post details about what process / service you need to configure.