|
From: | Martin Honeywill |
Subject: | RE: [lwip-users] lwip 1.3.0 "ping of death" |
Date: | Mon, 7 Apr 2008 18:02:26 +0100 |
I Guess it should still not cause LWIP to crash, even if
the packets are fragmented.
Martin From: Bill Auerbach [mailto:address@hidden Sent: 07 April 2008 17:00 To: 'Mailing list for lwIP users' Subject: RE: [lwip-users] lwip 1.3.0 "ping of death" Maybe ICMP doesnt
support fragmentation and you need to use ping f to tell it not to
fragment? Bill From:
address@hidden
[mailto:address@hidden On Behalf Of Martin Birkebæk, IO-Connect
ApS Hi list, I
have succesfully ported lwip 1.3.0 to LPC2468. Lwip is running in a threaded
environment, FreeRTOS. I have a basic example running, with a
webserver. I
have enabled ip reassembly, see my lwipopts.h file attached to this
mail. I
have a webbrowser running, which is requesting a webpage from the webserver each
second, and I am pinging the system continually, through the
command The
system is running ok. But if I ping the system with a lot of data bytes, i.e.
ping <ip> -l 2048. The system crashes. I end
up in an data abort exception. The reason for this exception, is a pointer, r,
in function ip_reass() is containing an invalid
address. The
line in C code is: iprh
= (struct
ip_reass_helper*)r->payload;
// line number: 572 in ip_frag.c What
can I do, to avoid this ping of death ? P.S.:
Please be aware that I have yet to optimize the system regarding values in
lwipopts.h. But that will be a topic for another question on this
list. Regards, Martin |
[Prev in Thread] | Current Thread | [Next in Thread] |