Paul Sokolovsky

Suspicion lies on packet retransmission issues, e.g. vendor codedrop has pretty magic code like https://github.com/pfalcon/lwip-esp8266/commit/79dc3436960563b201361917917e0f3c18fd65d8

> Are there plans to upgrade to lwip v2? Well, the idea is that it will make it possible, but I don't have any specific plans to got that far,...

@LongHairedHacker : I don't have time to look into that issue now (or soon), but feel free to provide exact steps on how you got to that issue so it...

@kadamski : Thanks for ping-back ;-). > Our methodology was very similar, I remember spending a lot of time looking at the disassembly of the Esperssif binary blobs too, though...

> Doesn't seem to be any way to create an issue on the /esp-lwip repo directly Github by default disables issue tracker in forked projects, considering that any communication should...

To xref other work: 1. @d-a-v's work on "non-OS" SDK upgrade to lwIP 2.0: https://github.com/kadamski/esp-lwip/issues/8#issuecomment-304589345 2. esp-open-rtos work to upgrade FreeRTOS-based env to lwIP 2.0: https://github.com/SuperHouse/esp-open-rtos/pull/389

@davydnorris: I didn't, I'm still in "reduced performance" mode. If you have any specific links, those would be welcome.

> now that i figured it's required to use this sdk to build pycopy for esp8266 it's not in usable state cry esp-open-sdk build and then pycopy esp8266 build using...

> i am using osx And I'm not using osx, sorry.

Did you see https://github.com/pfalcon/esp-open-sdk/issues/101 ?