Is bind() necessary if I want to receive data from a server using UDP?

Question

Is it necessary to have in the client bind, if I want to receive data from a server?

I've seen a schema (look at the image below), and it seems that it's not necessary. But from what I know, bind is necessary to give an address to a socket. If I don't "bind" the socket, how can I send data to it?

UDP client/server

score 2 · Answer 1 · edited Dec 02 '18 at 22:22

2

A call to bind() only binds a socket to a port. Hence, in this case, it is required for a server to bind to a port.

A client, on the other hand, just needs to send to or receive data from a specific port (server); hence, it just connect()s and then does a recvfrom() and sendto().

Read last paragraph of section 5.3: http://beej.us/guide/bgnet/output/html/singlepage/bgnet.html

edited Dec 02 '18 at 22:22

nbro

15,395
32
113
196

answered Apr 14 '14 at 20:10

brokenfoot

11,083
10
59
80

score 1 · Accepted Answer · edited Apr 11 '20 at 01:02

1

As a client, the application needs to be aware of the server port to which it needs to connect, and as a server, the application needs to be aware of the server port to which it needs to listen. Therefore, the server needs to bind to an IP address and port so that the client can connect to it.

The client can simply create a socket and call connect(). Binding to an available IP address and ephemeral port shall implicitly happen. But, yes, nothing prevents you from having the client bind to a particular IP address and port.

In the case of UDP, despite there being no "connection" mechanism, servers still need to bind to IP addresses and ports to allow the clients to send data to them.

edited Apr 11 '20 at 01:02

nairware

3,090
9
37
58

answered Apr 14 '14 at 20:22

Prabhu

3,443
15
26

Maybe I've understood... The binding on the client is not necessary because the client has contacted the server first? I mean, sendto() from the client to the server MUST be executed before than sendto() from the server to the client? – testermaster Apr 14 '14 at 20:29
Right. In case of UDP,since connection mechanism isn't there, the communication process should get initiated by the client by sendto() – Prabhu Apr 14 '14 at 20:32

score 0 · Answer 3 · answered Apr 14 '14 at 21:23

On most systems, if you call sendto with a UDP socket that has not been bound, it implicitly binds it to INADDR_ANY and some currently unused port, so if that's what you want (which is the common case), there is no need for an explicit bind on the client.

On some systems, trying to send with a unbound udp socket will give you a 'socket not bound' error, so if you want maximum portability, you should bind the client socket (to INADDR_ANY with port 0 to pick any currently unused port) before you try to send.

score -1 · Answer 4 · answered Apr 14 '14 at 20:12

You either need to bind and then you can sendto(fd,data,destination) + recvfrom(fd), or you can just connect the socket and use send(fd,data) (without destination) and recv(fd). The connect will do an implicit binding by using a more or less random port number and an local IP suitable for reaching the given target.

Is bind() necessary if I want to receive data from a server using UDP?

4 Answers4