Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

Wi-Fi Combo Forum Discussions

Anonymous
Not applicable

Greetings!

In normal 'sockets' programming, after creating a socket, you then use a 'bind' call with "any port" specified so that you can receive a request for a TCP connection from a remote host regardless of the TCP Port used.  This would seem to be the case with the equivalent WICED WiFi TCP calls, since we have a 'create' and a 'bind' with WICED_ANY_PORT.

However, the normal 'listen' call then specifies that socket and (typically) the depth of the incoming queue (say '5').  However, with WICED, the TCP Port is required in the 'listen' command as the 2nd parameter.  Now, this negates the 'any port' specification of the port!

So, the question is:  how do I create a listen (and a following 'accept') for an incoming TCP connection request from ANY port?

0 Likes
4 Replies
SeyhanA_31
Employee
Employee
100 likes received 50 likes received 25 likes received

Hi,

Are using LwIP, NetX, or NetX_Duo?

Thanks,
Seyhan

0 Likes
Anonymous
Not applicable

Greetings!

   We're using NetX_Duo in our current app.

   Cheers, Robert

0 Likes

Hi,

Did you resolve your issue or find a work around?

Seyhan

0 Likes
Anonymous
Not applicable

Seyhan:

    No work around.  Had to completely change the way that we use TCP connections.  The WICED TCP API should really follow 'Berkeley Sockets' standards, which are over two decades old!

Cheers, Robert

0 Likes