Re: [lwip-users] Force PPP TermReq (Lwip 2.0.0 RC2)

[Greg Smith]

Hi, Sylvain and Patrick.
Thank you for your replies.

I did turn on the LCP Echo function and that has made the whole system more stable by at least trying to reconnect after a failed peer.  However, there is still a state that I can get into where even that doesn't break the link on the non-Lwip peer and where that same peer appears to be ignoring new LCP negotiation.  But I haven't figured out how to reliably(?) get into this failed state to really do good debugging.

> From: lwip-users
> On Behalf Of Sylvain Rochet
> Sent: Friday, 05 August 2016 06:33
> On Fri, Aug 05, 2016 at 10:02:39AM +0200, Sylvain Rochet wrote:
> > On Thu, Aug 04, 2016 at 08:08:40PM -0400, Patrick Klos wrote:
> > >
> > > At this point, I think a packet (or byte) trace is the best
> > > diagnostic to show what's happening here.
> >
> > Yes ! :)
> 
> Greg, you can enable PRINTPKT_SUPPORT, PPP_PROTOCOLNAME, and PPP_DEBUG support
> in your lwipopts.h, you need to write the port section about debugging support
> if this is not already done and you can then dump the lwIP debug output
> wherever you want and then extract it later. If you have a free UART to output
> the trace in a live fashion that's even better ;-)
> 
I totally agree this would be nice to have a data trace.  I do already have a facility to output printf() data to a console or Telnet session. However, when I turned on all those options (PRINTPKT_SUPPORT was the only one I didn't already have on), I don't see it outputting any packet data during LCP.  Should I be seeing payload bytes during this phase?

I am running an RS485 bus, so I could hook another device in to "listen" to all the traffic.  Unfortunately, that's going to get me a lot of bytes, but minimal decoding.  Do you know of any good tools where I could dump raw bytes and get packet decoding back out?  (Or even a tool to hang on the serial line and decode live?)

Thanks.
-- G

---

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

---