WZ5500

[S. Petrukhin]

Hello, friends!

Who has experience using the WZ5500, please tell me, is this chip capable of opening connections with the same port on several sockets?
If I configure 2 or more sockets to listen on the same port, how does it distribute requests from different IP addresses?

[nctnico]

Hello, friends!

Who has experience using the WZ5500, please tell me, is this chip capable of opening connections with the same port on several sockets?
If I configure 2 or more sockets to listen on the same port, how does it distribute requests from different IP addresses?

In general: You can't. A port can only be handled by one socket.

[S. Petrukhin]

Hello, friends!

Who has experience using the WZ5500, please tell me, is this chip capable of opening connections with the same port on several sockets?
If I configure 2 or more sockets to listen on the same port, how does it distribute requests from different IP addresses?

In general: You can't. A port can only be handled by one socket.

It's sad... A small web server will not work on it... 

[nctnico]

Hello, friends!

Who has experience using the WZ5500, please tell me, is this chip capable of opening connections with the same port on several sockets?
If I configure 2 or more sockets to listen on the same port, how does it distribute requests from different IP addresses?

In general: You can't. A port can only be handled by one socket.

It's sad... A small web server will not work on it... 

Ofcourse it will. The way it works that each connection get's in own socket at the time it comes in and the connection will be handled on that (new) socket while the original socket keeps listening for new incoming connections. Just look for out a basic (multi client) telnet server example.

[S. Petrukhin]

You just wrote:

In general: You can't. A port can only be handled by one socket.

 

[ejeffrey]

Hello, friends!

Who has experience using the WZ5500, please tell me, is this chip capable of opening connections with the same port on several sockets?
If I configure 2 or more sockets to listen on the same port, how does it distribute requests from different IP addresses?

Yes.  If you configure two or more sockets to listen on the same port they will both work.  Incoming connections will be assigned to the first available socket.  If they are all full, the client will get a connection refused error.

[S. Petrukhin]

Hello, friends!

Who has experience using the WZ5500, please tell me, is this chip capable of opening connections with the same port on several sockets?
If I configure 2 or more sockets to listen on the same port, how does it distribute requests from different IP addresses?

Yes.  If you configure two or more sockets to listen on the same port they will both work.  Incoming connections will be assigned to the first available socket.  If they are all full, the client will get a connection refused error.

Thank you, Ejeffrey! 

[ejeffrey]

Hello, friends!

Who has experience using the WZ5500, please tell me, is this chip capable of opening connections with the same port on several sockets?
If I configure 2 or more sockets to listen on the same port, how does it distribute requests from different IP addresses?

In general: You can't. A port can only be handled by one socket.

It's sad... A small web server will not work on it... 

Ofcourse it will. The way it works that each connection get's in own socket at the time it comes in and the connection will be handled on that (new) socket while the original socket keeps listening for new incoming connections. Just look for out a basic (multi client) telnet server example.

This is not how the wiznet API works.  They have an API that is similar to but not the same as berkley sockets.

They do not have a separation between "listen" and "accept" sockets.  Rather, you configure a socket in listen mode.  When a connection comes in, the listen socket transitions to the accepted state and you use it to communicate.  It does not allocate a new socket the way normal listening sockets work. Once the connection ends you put the socket back into listen mode to wait for the next connection. In order to allow multiple simultaneous connections you need to put multiple sockets in the listen state.

[nctnico]

Aha. That is different to the normal way (Berkley) sockets work indeed.