Hi Simon. Thanks for the reply.
The IP-Address and Port are very well in existence; we have thousands of (other kinds of) devices already connected to our server. (Just for the record, our server is a MQTT-broker server. Currently I am trying to connect our device to port 1883 on the server. 1883 is an unsecured port, so no SSL-related issues). The device we are using is a SOC, using ATSAM4E8CA-AUR controller, with KSZ8051MNL ethernet-module. What is the best/recommended way to take a wireshark-dump in this case (I am sorry, I have only taken wireshark-dump on OS-based systems with full-fledged shell. Currently, no experience in taking wireshark-dumps on an embedded-SOC). Thanks and Regards, Ajay On Mon, Sep 25, 2017 at 11:11 PM, goldsi...@gmx.de <goldsi...@gmx.de> wrote: > Ajay Garg wrote: >> >> We are using lwip-1.4.1 with FreeRTOS on Atmel-Studio-7, on Windows. >> >> During the call to netconn_connect, the resultant err_t code being >> returned is ERR_ABRT. >> [..] >> I have googled, and I see a lot of people have this issue. > > > Great. This means the remote host did not respond to your connect request. > I'm not suprised others see this as well :-) > >> Unfortunately/Surprisingly, I was unable to land on a concrete solution :( > > > One possible solution would be to get the remote host responding ;-) > > Or more seriously: you might have a problem with transmitting or receiving > tcp segments. I assume your lwip port or something else is new and untested. > Wireshark is your friend in that case ;-) > However, it could be also just be a non-existing IP address... > > Simon > > _______________________________________________ > lwip-users mailing list > lwip-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/lwip-users -- Regards, Ajay _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users