@slaff custom lwip CAN be default, but tcp_mss should be configurable.. my knowledge isn't enough to say what is good default.. some time ago, with esp provided blob of lwip there was just two version - 1460 and 536.. first is too big, and second - too small... some investigation needed to find good default value...
@slaff not yet, I just start do dig lwip parameters.. :(
I think for now we can make open-lwip DEFAULT, leave TCP_MSS 1460 as default, but say in README.md that if one need access to device from internet/vpn/nat/etc there it is mandatory to fine tune TCP_MSS.. may be we can make the outside configurable by some Makefile knob..
ok. it would have been a viable workaround, provided that we don't break the absolute limit for spiffy's number of files in the file index
@piperpilot on a side note, is spiffy included in the 1M memory allocation limit of the ESP? in other words, is it possible to have the code take up the 1st 1M block on a 4M flash chip and move spiffy to the 3rd one?
yeah, I was trying to pre-process a hex file for PIC bootloading and ended up writing a script to do it before uploading it to the ESP, not nearly enough memory to process the file like I needed to on the ESP