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'm a newbie running slack 9.1 and I have ports 761, 763, and 765 open.
I'm not sure what exactly they are and why they are running.
761 is supposed to be kpwd but I don't really know what that is and why i'd use it. I can't find it being started up and I don't see the process when I do a ps -aux.
763 is supposed to be cycleserv, but again I don't know what it is or how I'm starting it. How do I shut this guy down?
765 is supposed to be webster. Webster?? like the dictionary? What process is starting it and how do I shut it down. What the heck would I need this for?
I do not see these being started up in my inetd.conf file so I'm at a loss as to where I'm supposed to find them.
Also, if you use the command netstat -nlp then you can see what programs are running on what ports. If the program doesn't need to be running, then close it. ps aux will give the process name/pid. Not having the program running that accepts tcp connections is better than simply just blocking it w/ a firewall.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.