EthernetClient connect does not read data after a previous client is closed (but it can write)

[davehummel]

In a scenario where I am handling a reconnect after the server restarts, I am starting a new client as follows:

EthernetClient client = EthernetClient();

client.connect(ip, port);

FDOS_LOG.printf("Ethernet client connect:%d\n", client.connected());

While this works perfectly the first time, the second time this client will never have bytes available() for reading. It does write properly (the remote server sees the data). Similar code works fine with the WifiClient (esp32 implementation).

Before creating the new client, I am calling .stop on the previous one.

[Stefar77]

Had the same issue.. (but using the older version buildin platformio teensy)
in NativeEthernetClient.cpp EthernetClient::available() the error handler always gets called even if there is no error.
You need to move the error_handler = fnet_error_get() part under/in the if(ret == -1){ container to fix this.

I don't need TLS for my project so not using the latest version myself however the latest version here on github should not have this problem so make sure you include the correct one and it should receive after you reconnect.