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.
[ta@tom-ws01 ~]$ nmap -sT new-dev
Starting Nmap 5.51 ( http://nmap.org ) at 2014-09-09 10:18 PDT
Nmap scan report for new-dev (10.0.38.20)
Host is up (0.0032s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
111/tcp open rpcbind
Nmap done: 1 IP address (1 host up) scanned in 0.27 seconds
[ta@tom-ws01 ~]$ nmap -sT new-dev -p 8000
Starting Nmap 5.51 ( http://nmap.org ) at 2014-09-09 10:21 PDT
Nmap scan report for new-dev (10.0.38.20)
Host is up (0.0015s latency).
PORT STATE SERVICE
8000/tcp closed http-alt
Nmap done: 1 IP address (1 host up) scanned in 0.14 seconds
Your iptables configuration does not block anything. To block any incoming packets, you need INPUT-rules with targets DROP/REJECT or (even better) an INPUT policy DROP. From iptables' view, everything is open.
For a port to be really open, you need a program listening to that port. As yzT! suggested, maybe your program does only listen to the loopback interface. What is the exact output of the netstat command:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.