Simon,
Thank you for highlighting the potential conflicts with 'sockets.h' and for
recommending the use of accessor functions for 'ip_addr'. We are applying these
insights in a test environment to evaluate their impact on our existing issues.
I will keep you updated on our progress and any
Scott,
Your suggestion prompted us to consider a link between the 'ip_addr' struct
issue and the IPv6 configuration. We are currently setting up a separate
development environment to review this aspect. Once we have some concrete
results, I'll be sure to update you on our findings.
Best,
On 10.01.2024 03:46, Timothy Martin via lwip-users wrote:
I'm including a zip file containing all the updated headers and source
files of LWIP for your reference.
[..]
Here are the details of the issues I'm facing:
*
*Error #137 in |lwiplib.c| (Path: /NetworkModule/utils)*:
o
I'm afraid I don't have time to review your files, and I've only been
through that upgrade process once, but based on that first error I'd
look first at whether you've got IPv6 enabled. Off the top of my head, I
think the ip_addr struct only has "addr" as a field if IPv6 is disabled.
And make
Hi Scott,
Yes, we have updated both the headers and the source files in the includes
directory when upgrading LWIP from version 1.4.1 to 2.2.0.
Best,
Timothy
Sent with [Proton Mail](https://proton.me/) secure email.
On Wednesday, January 10th, 2024 at 11:24 AM, Scott Miller
wrote:
> I'll
I'll start with the obvious question - when you say you updated the
headers, do you mean you updated ONLY the headers or did you also
update all of the library files as well?
Scott
On 1/9/2024 4:39 PM, Timothy Martin via lwip-users wrote:
Dear LWIP Community,
I am Timothy, currently
