[EXT_EP-9633] TCP server sockets do not transition to listen state after call to listen() Created: 10/Feb/20 Updated: 19/Feb/20 Resolved: 11/Feb/20 |
|
| Status: | Fixed |
| Project: | Embedded Software & Tools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | TI User | Assignee: | TI User |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Product: | Network Development Kit |
| Internal ID: | NDK-356 |
| Found In Release: | 1.71 |
| Fix In Release: | NDK_3_75_00 |
| Description |
|
The server socket in the tcpEcho example, while blocked on accept(), was showing "CLOSED". The expected state here is "LISTEN". In the NDK stack, the transition to the "LISTEN" state doesn't happen until the listening socket receives a SYN request from a client. The if statement (that checks for a RX'd SYN) that encloses this state change also has a comment about the socket being in a listening state, although the code hasn't actually put it into that state yet: Seems that the parent socket should have been put into the listening state during the listen call. |