RE : [lwip-devel] Outgoing Ping support for LWIP...

[Frédéric BERNON]

I confirm, lwIP always support it. I do ping (at socket layer, that's why I ask 
you) and, it works...

But since this kind of code can be done at application level, I don't think we 
really need any icmp_write or icmp_recv.
 
  
====================================
Frédéric BERNON 
HYMATOM SA 
Chef de projet informatique 
Microsoft Certified Professional 
Tél. : +33 (0)4-67-87-61-10 
Fax. : +33 (0)4-67-70-85-44 
Email : address@hidden 
Web Site : http://www.hymatom.fr 
====================================
P Avant d'imprimer, penser à l'environnement
 


-----Message d'origine-----
De : address@hidden [mailto:address@hidden De la part de Goldschmidt Simon
Envoyé : mercredi 18 juillet 2007 17:15
À : lwip-devel
Objet : RE: [lwip-devel] Outgoing Ping support for LWIP...



> > I need to utilize outgoing Pings to support trace routing to aid in
> > debugging network problems in the field. From what I can tell LWIP 
[...]
> I think you're right in that the current code doesn't support it. 
> Normally ICMP echo requests are sent by an application (e.g. "ping" on
> unix) using a raw socket.  lwIP doesn't support raw sockets
> as such.  We could I suppose extend the lwIP raw API to 

It doesn't? I thought it would...

Anyway, look at /contrib/ports/unix/proj/unixsim/simhost.c
there is a function ping_send() which sends an icmp packet and uses
raw_new()/raw_recv() to set up a raw callback to filter all received IP 
packets, so you receive the ping packet.

> include an icmp_write() to match the existing tcp_write() and
> udp_write().  If you'd like to see such a feature, feel free 

We would have no icmp_recv, would we?


Simon.


_______________________________________________
lwip-devel mailing list
address@hidden http://lists.nongnu.org/mailman/listinfo/lwip-devel

Frédéric BERNON.vcf
Description: Frédéric BERNON.vcf