|
From: | Bryan Kirk |
Subject: | Re: [lwip-devel] ClicksAndWhistles doesn't connect to any IRC Server |
Date: | Mon, 17 Jun 2024 14:18:13 +0000 |
June 17, 2024 at 6:51 AM, "Bryan Kirk" <zero3k@openmbox.net> wrote:
I am using the Async Connection support PR athttps://github.com/reactos/reactos/pull/6349. It still happens with that and the upgraded LWIP PR. KrosUser mentjons this:
TCP operation failed: 0xc000013c (-11)
-11 means STATUS_REMOTE_DISCONNECT
(see : TCPTranslateError : https://git.reactos.org/?p=reactos.git;a=blob;f=sdk/lib/drivers/ip/transport/tcp/tcp.c#l267)
This is likely due to TF_RESET flag in tcp_input fromhttps://git.reactos.org/?p=reactos.git;a=blob;f=sdk/lib/drivers/lwip/src/core/tcp_in.c#l92 leading to ERR_RST error event being triggered.
/* TF_RESET means that the connection was reset by the other end. We then call the error callback to inform the application that the connection is dead before we deallocate the PCB. */
June 17, 2024 at 5:15 AM, "goldsimon--- via lwip-devel" <lwip-devel@nongnu.org> wrote:
Hi Bryan,Am 13.06.2024 um 16:25 schrieb Bryan Kirk:When using v2.2.0 in ReactOS by applying the PR for upgrading to thatversion (which is available athttps://github.com/reactos/reactos/pull/6788<https://github.com/reactos/reactos/pull/6788>), ClicksAndWhistles getsstuck on connecting to the server that I have chosen to connect to. Moreinfo about the issue can be found inhttps://jira.reactos.org/browse/CORE-11559I'm not at all familiar with reading ReactOS debug logs, but "AsyncConnect UNIMPLEMENTED!" makes me think this is by design?I think I need some more lwIP-related input to help here. Do you happento have a pcap so we can see the tx/rx packes involved here?Regards,Simon_______________________________________________lwip-devel mailing listlwip-devel@nongnu.orghttps://lists.nongnu.org/mailman/listinfo/lwip-devel
LWIP_220_Debug_ClicksAndWhistles_ReactOS.log
Description: Text document
[Prev in Thread] | Current Thread | [Next in Thread] |