Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Hi I need to know about the ports on the client computer. I am precisely talking about the ports viewed from tcptrack and can anybody explain why the client ports are in the range of 10000.The server ports are most of the time 80,443,25,110.
because the clients make a connection to the server (e.g. 80) and then the server 'moves' to a higher dynamic ports to operate with client only, thus no-one other is using the same data connection
The short answer is, source ports (what your seeing in tcptrack) are random unused ports.
In the case of web browsing for example, they are destined for port 80, but come from any port, this is how you can have multiple simultaneous connections to different servers, on the same destination port. Where if they all came back to you on the same port, things the client program (that sends the original requests), would get confused..
let's take the example of http server operating on port 80 on the server.
the server needs to stay on port 80 because this is the door the clients knock on to request http data.
all the clients talk to it from different IP addresses and different source ports. So the server can keep track of who is who.
The clients open a free port on the laptop before using it to talk to the server. they use this port to send the request to port 80 on the server, then listen on that port for an answer originating from port 80 of the server.
non root users cannot create sockets on ports with low numbers (I believe 1200 is the threshold, but not sure). This prevents a non root user from opening a socket on port 80 which would prevent the administrator from launching a http server that would need to own that port.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.