|
From: | Greg Smith |
Subject: | Re: [lwip-users] Ping Causing "not enough space for new header size" Over PPP |
Date: | Mon, 23 May 2016 19:27:26 +0000 |
Hi, Simon. 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. Thanks! From: lwip-users [mailto:lwip-users-bounces+address@hidden Greg Smith wrote:
Yes, the call stack is: pbuf_header_impl() at pbuf.c:546
pbuf_header() at pbuf.c:605
icmp_input() at icmp.c:147
ip4_input() at ip4.c:671
ppp_input() at ppp.c:850
pppos_input() at pppos.c:581
taskPppGetBytes() at rs485if.c:329 (This is my application's task to read in bytes from the serial input buffer.) I am still unclear as to how the whole pbuf setup is architected. I've tried reading some wikia information on it, but it wasn't clear to me. Do you have any other resources I can read about it? It is something
I would like to have a better handle on.
Fortunately, I'll be running PPP only and I have Ethernet disabled. So whatever we need to make it run, I should be able to do. Likewise, if I can match the Ethernet settings and still have it work for PPP,
that would give me flexibility for the future. I've attached my lwipopts.h file, if that will also help troubleshoot. (It is nearly the same as I used for 1.4.1. If there are glaring misconfiguration, please let me know -- most of the options are a little
esoteric to me as to their effects.)
This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com |
lwipopts.h
Description: lwipopts.h
[Prev in Thread] | Current Thread | [Next in Thread] |