Patrick Klos wrote:
(I think if LWIP_ASSERT was enabled, the code generated by the macro
expansion would be enough to stop the warning, at least for 'prev'?)
Exactly. And honestly, I'm not sure if it makes sense to enable
"-Wnull-dereference" with asserts disabled. You enable half of the
On 4/26/2017 3:31 AM, Andreas Dinter wrote:
Potential NULL pointer access in ip4_frag.c
Hi,
When compiling ip4_frag.c with GCC option -Wnull-dereference, it
complains with the following warning.
../../../lwIp/src/core/ipv4/ip4_frag.c:327:16: warning: potential null
pointer dereference
Antoine Zen-Ruffinen wrote:
> I am worried about the case when both interface get the same private IP
> address (like 192.168.1.xxx) but in physically separated networks (I think
> that could happened).
In the past, we said lwIP does not support this. However, IPv6 should already
support it
dworkdev wrote:
>A short interrogation : Does LWIP supports DSCP marking ?
Yes.
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Hi all,
A short interrogation : Does LWIP supports DSCP marking ?
Thanks
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Hi list,
I need your expertise. I am developing a device that will have two Ethernet
interface using LwIP 2.0.1. The aim of having two interface on this device is
to have the device connected into two physicaly separated LANs, let's say
"management" LAN and "customer" LAN. I am worried about
Andreas Dinter wrote:
> ../../../lwIp/src/core/ipv4/ip4_frag.c:327:16: warning: potential null
> pointer dereference [-Wnull-dereference]
> This refers to this line: prev->next = ipr->next;
As far as I can tell, that line does not match any released versions of lwIP.
> In function:
Hi,
When compiling ip4_frag.c with GCC option -Wnull-dereference, it complains
with the following warning.
../../../lwIp/src/core/ipv4/ip4_frag.c:327:16: warning: potential null
pointer dereference [-Wnull-dereference]
This refers to this line: prev->next = ipr->next;
In function: