Re: [lwip-users] using loopback

[address@hidden]

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 127.0.0.1. 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.

Simon

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. 
>
>  
>
> Thanks.
>
>  
>
>
> 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 PM
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users