lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] Ping Causing "not enough space for new header size" Ove


From: Greg Smith
Subject: Re: [lwip-users] Ping Causing "not enough space for new header size" Over PPP
Date: Mon, 23 May 2016 23:37:56 +0000

You're welcome.  I am on a fast-approaching deadline with my project and solutions need to come quickly. :-)

 

 

Thanks for the heads-up on the "severity level" of the debug messages.  I hadn't even paid attention to it being marked "serious".  Changing that will be helpful -- especially if I pay attention to that level as I'm debugging.

 

However, I notice I get that debug message on nearly every ping reply.  For example, I sent 100 pings and got the message 96 times.  (This was right after connecting via PPP.  No other traffic happened in between.)  Is this expected behavior or opportunity for improvement?

 

-- G

 

 

From: lwip-users [mailto:lwip-users-bounces+address@hidden
Sent: Monday, 23 May 2016 15:54
To: Mailing list for lwIP users <address@hidden>
Subject: Re: [lwip-users] Ping Causing "not enough space for new header size" Over PPP

 

Wow, that was fast! :-)

Greg Smith wrote:

Please see more information commingled below.

 

Before that, though, I want to add that I did just today find the reason for the dropped packets.  I was having buffer overruns on my serial port.  I have corrected that problem.  (The dropped packets themselves have been resolved.)  But I'm still getting the "not enough space" message.


Cool. The call stack below indicates that there is no problem at all. It's just a wrong debug level of that message: in icmp.c, pbuf_header() is called speculatively. The return value '1' is not "serious" (as indicated by the DEBUGF call). I'll change the debug level. Thanks for the input.


Simon




This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com

reply via email to

[Prev in Thread] Current Thread [Next in Thread]