Hi
When updating lwip from 1.3.2 to 1.4.1 I see some asserts checking for
alignment equal 4. They are hard coded.
Does this mean lwip can only be used with MEM_ALIGNMENT equal 4 from this
Release on?
Regards Thomas
___
lwip-users mailing list
Thanks for the input!
I'll try to provide a concrete example. The device has two network
interfaces. One of them (X) is physically connected to a network of
organization A, another (Y) - to a network of organization B. Since
those networks are completely out of our control, we can not discount
Hi Mark,
I understand the picture now, including your examples. You have
two completely uncoordinated networks, and you need to connect
them together. Not only can you have name conflicts, you can also
have address conflicts.
My advice -- don't do it. Not just because the configuration is wrong
tm...@web.de wrote:
When updating lwip from 1.3.2 to 1.4.1 I see some asserts checking for
alignment equal 4. They are hard coded.
Does this mean lwip can only be used with MEM_ALIGNMENT equal 4 from this
Release on?
No.
You might get a more detailed answer by telling us exactly which
Alain Mouette wrote:
Hi, I have do do something a little odd, and I would like to have your
advice about it and to know if anyone has ever seen anything like it
I need to simulate the interface available on the Arduino (with the
WizChip), I believe that wiht such an interface I could use some
Having read that, I'm not sure lwip is the right stack to do that. Its simply
not meant for such a setup. And like Z wrote, even if you get it running,
there's no guarantee future changes to lwip will leave your setup intact.
I'd suggest to either get an OS with support for separated processes