Itzik Levi wrote:
What I can do is work on an executable which dynamically loads lwip's
stack(I can make it a shared object).
Will that be good enough?
Ehrm, no, sorry. What I want is something that I can reproduce it
without 3rd party code that I can't check. In other words if I check
this,
On 11/09/2017 03:41 AM, Giuseppe Modugno wrote:
Il 08/11/2017 16:34, Joel Cunningham ha scritto:
The ping works well if I launch "ping 192.168.1.156" command from
*another* computer on the same network.
You're most likely running into a checksum offload problem since you
can't contact the LwI
Thanks for your hints, I think I found the issue.
The modbus stack i'm using was processing frames in different context
than lwip..
I reworked it now to directly process frames after beeing received and
it now seems to be running way more stable. Had no further issues so far.
Am 03/11/2017 um
Il 08/11/2017 18:20, Gisle Vanem ha scritto:
Giuseppe Modugno wrote:
So I have an Ethernet interface with two IP and MAC addresses. It
seems it works, except for one thing.
I tested connectivity by running "ping 192.168.1.156" command from a
shell on the same computer. No reply!
The ARP table
Il 08/11/2017 16:34, Joel Cunningham ha scritto:
The ping works well if I launch "ping 192.168.1.156" command from
*another* computer on the same network.
You're most likely running into a checksum offload problem since you
can't contact the LwIP stack from the Windows host, but you CAN from
an
