[Top][All Lists]

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

Re: [lwip-users] using loopback

From: Ben Bobbitt
Subject: Re: [lwip-users] using loopback
Date: Fri, 6 Jun 2008 08:35:00 -0700 (PDT)

Yes, It would be more accurate to say that I need to check that a thread is 
running. It sounds like there is no current capability to use the loopback to 
do that. The thread that I want to monitor this way will be blocked on a 
netconn read call using a netif that is not a loopif type. 

Ben Bobbitt

On Jun 6, 2008, at 9:46 AM, "address@hidden" <address@hidden> wrote:

I don't think I fully understand what you want to achieve: do you want to check 
if your an ethernet interface is up or if a thread is running? If you want to 
check the ethernet interface, loopif.c won't help you much: it is designed to 
be an additional lwip netif that passes packets to/from However, 
there is some work going on to get loopif functionality into _all_ netifs, but 
that is not supported in 1.3.0 and it might take a while until it is finished 
in CVS.


Ben Bobbitt schrieb:

I’m trying to use a loopback mechanism on a periodic basis as a way of checking 
that an interface is still up and running. 

It appears that loopback capability is included in the loopif.c module with the 
LWIP_HAVE_LOOPIF option in opt.h set... however,  I’m not clear on how one 
would actually use that.  Does the netif that you want to periodically test 
with a loopback message have to be initialized under a new model?   

I’m using the netconn api, and I simply want to have another thread 
periodically send a ping to the port that another thread is listening to – but 
since it’s a blocking read, I can’t really test that the thread is still up 
unless he receives data.  Hopefully that makes sense. 


No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.24.6/1484 - Release Date: 6/4/2008 4:40 


lwip-users mailing list

lwip-users mailing list

reply via email to

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