bind()/connect() to port 0 question for tcp/udp

[Geoffrey Lee <snailtalk@linux-mandrake.com>]

Hi list,



I want to ask a question:

In sockets, what is the correct behavior when we try to connect() to port 0
for tcp / udp?


It seems that FreeBSD returns EADDRNOTAVAIL, as does Solaris.

So something like this will fail on Solaris and FreeBSD:

[...]
saddr.sin_port = htons(0);
[...]

connect(AF_INET, (struct sockaddr *)&saddr, sizeof(struct sockaddr));


We don't do this however, and Linux will merrily accept a port of 0 in
a connect(), though most probably your connect() wouldn't succeed.

Making it return EADDRNOTAVAIL to user space would be a trivial task, so
I want to ask, is this a buglet in the Linux implementation, or is FreeBSD
and Solaris wrong?



	- G.