Firewall still not completely disabled on SuSe 9.0 after shorewall clear
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Firewall still not completely disabled on SuSe 9.0 after shorewall clear
Hi, I am trying to run a few services on a SUSE 9.0 machine (on a private LAN), such as webmin on 10000 and XServer on port 6000. At first I tried to use the SUSE firewall to no longer disable connections. Unfortunately, nmap still showed all ports to be closed. After giving up, I uninstalled the SUSE firewall and installed Shorewall.
After running 'shorewall clear', nmap showed the desired ports to be opened. However, connecting to them is still not possible.
Does anybody know how to get rid of SuSe's apparent extra restrictions, so I can just use ShoreWall?
Try doing killall iptables as root. Then do ps -ef to verify that iptables is not running. Then try connecting. If you still can't connect then you know that it is an application level problem rather than iptables/netfilter related.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Are you running nmap against localhost? If so, that won't help your remote hosts. You need to run nmap from one of the hosts you're trying to connect from.
If the ports show as open from a remote host (on your LAN), but you can't connect to the services, then there's a good possibility that your server is using tcp wrappers. Make the appropriate entries in /etc/hosts.allow to allow your LAN clients to connect.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.