Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

TCP_NODELAY has the wrong value on ESP32 (newlib / LWIP based) #3774

Closed
jothan opened this issue Jul 18, 2024 · 0 comments · Fixed by #3920
Closed

TCP_NODELAY has the wrong value on ESP32 (newlib / LWIP based) #3774

jothan opened this issue Jul 18, 2024 · 0 comments · Fixed by #3920
Labels
C-bug Category: bug E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. O-newlib
Milestone
1.0

Comments

@jothan
Copy link

jothan commented Jul 18, 2024

In short, libc exposes a value of 8193, when the IP stack is expecting 1 as the value of the TCP_NODELAY option.

Initial issue: esp-rs/rust#218
Related PR (unmerged): #3345
@jothan jothan added the C-bug Category: bug label Jul 18, 2024
@tgross35 tgross35 added the E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. label Aug 29, 2024
@tgross35 tgross35 added this to the 1.0 milestone Aug 29, 2024
@SergioGasquez SergioGasquez mentioned this issue Sep 16, 2024
Merged
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
C-bug Category: bug E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. O-newlib
Projects
None yet
Milestone
1.0
Development

Successfully merging a pull request may close this issue.

Fix ESP-IDF constants and structs SergioGasquez/libc
2 participants
@jothan @tgross35