Re: [lwip-devel] ClicksAndWhistles doesn't connect to any IRC Server

[Bryan Kirk]

<simonelombardo> @julenuri Took a quick glance - that ClickAndWhistles process seems to use interthread communication via socket - it calls socket functions on 0.0.0.0 (so all local machine interfaces) on a random port and then it tries to connect via the loopback interface (127.0.0.1) on that port before doing anything. The connection fails in ReactOS. So or 0.0.0.0 does not bound in loopback interface or interthread communication fails because the thread with the server socket is not awaken..?

<simonelombardo> I guess a quick test case or checking in windows could help.

June 19, 2024 at 8:17 AM, "Bryan Kirk" <zero3k@openmbox.net> wrote:

I made a bug report for it. It can be found at https://savannah.nongnu.org/bugs/?65875.

June 17, 2024 at 10:18 AM, "Bryan Kirk" <zero3k@openmbox.net> wrote:

Here's a debug log that contains that has full verbosity of the LWIP source code and is showing what happens when trying to connect to two different IRC servers via ClicksAndWhistles under ReactOS.

June 17, 2024 at 6:51 AM, "Bryan Kirk" <zero3k@openmbox.net> wrote:

I am using the Async Connection support PR at 

https://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 that

version (which is available at

https://github.com/reactos/reactos/pull/6788

<https://github.com/reactos/reactos/pull/6788>), ClicksAndWhistles gets

stuck on connecting to the server that I have chosen to connect to. More

info about the issue can be found in

https://jira.reactos.org/browse/CORE-11559

I'm not at all familiar with reading ReactOS debug logs, but "Async

Connect UNIMPLEMENTED!" makes me think this is by design?

I think I need some more lwIP-related input to help here. Do you happen

to have a pcap so we can see the tx/rx packes involved here?

Regards,

Simon

_______________________________________________

lwip-devel mailing list

lwip-devel@nongnu.org

https://lists.nongnu.org/mailman/listinfo/lwip-devel