Uvoksc daily struggle.
"Huh?? Why does the LwIP stack send an ACK for a second incoming TCP connection?? I only accept one at a time!?!?"
Apparently, that's a "backlog", and it's suffering you can't turn off completely.
If I really want to only work with one client at a time, I probably have to accept and close the other sockets immediately?
(No, setting backlog to 0 on listen doesn't help)
#esp32 #lwip #networking
uvok /
npub1k9…sag6a
2024-09-19 14:48:51
Author Public Key
npub1k90996tz8kj3eljxqqsw0k385zrdu7z8xxh82hsth98f78q38jeqdsag6aPublished at
2024-09-19 14:48:51Event JSON
{
"id": "47b68baf33e6d76ee8ba9f1f483f1252706f8a3e1115db22dd0ab8db0f552758",
"pubkey": "b15e52e9623da51cfe460020e7da27a086de784731ae755e0bb94e9f1c113cb2",
"created_at": 1726757331,
"kind": 1,
"tags": [
[
"t",
"ESP32"
],
[
"t",
"lwip"
],
[
"t",
"networking"
],
[
"proxy",
"https://furry.engineer/users/uvok/statuses/113164768472130764",
"activitypub"
]
],
"content": "Uvoksc daily struggle.\n\n\"Huh?? Why does the LwIP stack send an ACK for a second incoming TCP connection?? I only accept one at a time!?!?\"\n\nApparently, that's a \"backlog\", and it's suffering you can't turn off completely.\nIf I really want to only work with one client at a time, I probably have to accept and close the other sockets immediately?\n\n(No, setting backlog to 0 on listen doesn't help)\n\n#esp32 #lwip #networking",
"sig": "b85044af1bc1a2312fea9c393065b07c5f96af228f8345d6958fb4e0c097e12743702f676a22d006f684b5267d67d0dfe962f71273429322f77a3b720177b877"
}