Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
I checked in the script I use to make my firewall and I can't see anything that would create this rule, or see the port as open when I portscan my public IP (nmap with both -sS and -sT). Is this something I should be concerned about? I was doing some work on my iptables script last week, so I might just have put it in by accident then or something (don't remember doing it, but I did want port 80 open so I might have).
How do I remove the chain by the way? I know I use iptables -D, but can anyone tell me how I'd define the chain please?
If you don't have any particular reason to leave tcp port 8000 open on that computer then it's best to remove that rule. It might be useful to do use netstat to check what ports are listed as listening. "netstat -lptuw" would do the trick. I'd just do "iptables --line-numbers -L" to get the line number and then remove it using "iptables -D LINENUMBER".
The next thing to check would be if you did define a rule for port 80 or accidentally typed in a couple of extra zeros. It shouldn't be too much to worry about. Still, it's best to allow connections only to the required ports and nothing extra.
Distribution: Debian and Fedora for play and RHEL + Solaris for work
Posts: 172
Original Poster
Rep:
Thanks!
I checked and it belonged to some Dell management software the server came with, never used it so closed up the hole as instructed. I generally try not to run any services I don't need, cos I have enough to worry about as it is
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.