Binding 40 Sockets to 40 different IP addresses

Question

0.00/5 (No votes)

See more:

, +

I am working on udp server/client application. I want my single server to handle 40 clients at a time. For this, I want to create 40 dedicated threads, each dedicated for one single client. Since there are 40 threads one for each client, I want to create 40 dedicated sockets as well. But the problem that I don't know what will be the 40 IP addresses to which I shall bind() my sockets. (since as far as I now, I have to bind() to my Server\s IP address.) Normally I bind() to "INADDR_ANY" when there is only single socket. But what should be the IP addresses at which I should bind() each of my 40 sockets? Please help me. Any comment/ help is appreciated.

Posted 12-Apr-13 0:43am

ayesha hassan

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Manfred Rudolf Bihy · Accepted Answer · 2013-04-12T01:07:00

You're trying this the wrong way round. The server should have one socket (IP-adress and port) on which it accepts connections and then it will spawn a separate thread for each client that connects. If you were to do it your way you'd need either 40 IP adresses and listening on one designated port or use one IP adress listening on 40 different ports. The former is a waste of IP adress space and the latter a pain in the arse configuration management wise as each client would have to be configured with a different port to connect to the server.
Since I cannot imagine this being a requirement I suggest you look at the ample samples available on the internet to see how a server using sockets is implemented and go by that route.

Socket server sample:
http://www.tutorialspoint.com/unix_sockets/socket_server_example.htm[^]

Threading C Windows:
Multithreading with C and Win32 [^]

Regards,

— Manfred

jsolutions_uk · Accepted Answer · 2013-04-12T01:02:00

Solution 1

If you want a multi client server (who wouldn't?) you shouldn't need to listen on 40 different sockets, but rather a single socket. On recieving a connection, spawn a thread to handle the connection... or a process if you want to go old school :)

In fact here's a good example Beginning Winsock Programming - Multithreaded TCP server with client[^]

Posted 12-Apr-13 1:02am

jsolutions_uk

Updated 12-Apr-13 1:10am

v2

Comments

ayesha hassan 12-Apr-13 7:10am

If there is only a single thread and all of the 40 clients send data simultaneously on this single socket, there are chances that data of each client may get dropped.
Due to this reason, I shifted towards creating dedicated sockets for each client.

Manfred Rudolf Bihy 12-Apr-13 7:14am

They can't send data simultaneously as they have to connect first. After the connection is made there already exists a separate thread for each client, so no worries. The backlog for simultaneous connections is something like 5, but that really only matters if way more than 40 clients would try to connect at the same time and if the code spawning a new thread would do some lengthy calculations (which it shouldn't BTW).

jsolutions_uk 12-Apr-13 7:20am

You state that you are using UDP? UDP does not provide a guarantee of deliver, so if you are worried about that, perhaps use TCP which provides a greater level of reliability. 40 clients sending data simultaneously should not be a problem as IP packets should effectively be queued by the server OS, if I understand correctly.

Manfred Rudolf Bihy 12-Apr-13 7:10am

Exactly! 5+

ayesha hassan 12-Apr-13 7:18am

but there is no connect() or listen() in UDP :(

ayesha hassan 12-Apr-13 7:24am

@jsolutions_uk : Thanks for sharing about receive queue. But upto what limit will the data be queued in such a buffer? There must be a limit after which the queue is full and moreincoming data will be discarded, if I'm not worng in understanding the concept.

jsolutions_uk 12-Apr-13 7:27am

I believe there is a limit, there are also some other parameters relating to recieving packets. I suspect they are OS dependent, probably configurable.... but much more than that I would be in google territory :)