RE: RE : RE : [lwip-users] APIPA / AutoIP / Zeroconf / RFC 3927 Module

[Spies, Dominik]

Yes you are right, it's based on the last stable release because my application 
is based on the last stable release.
And no, I don't think APIPA is the name if Microsoft's implementation. It's 
just a name for that mechanism, the name is widely spread on the internet and 
also reffered e.g. in Gentoo documentation..
But I'm not 100% sure..

Dominik

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Frédéric BERNON
Sent: Dienstag, 22. Mai 2007 15:42
To: Mailing list for lwIP users
Subject: RE : RE : [lwip-users] APIPA / AutoIP / Zeroconf / RFC 3927 Module

I note your patch is not done on last CVS HEAD code... 
  
====================================
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 Spies, Dominik
Envoyé : mardi 22 mai 2007 15:20
À : Mailing list for lwIP users
Objet : RE : [lwip-users] APIPA / AutoIP / Zeroconf / RFC 3927 Module


Hi!

I finished step one of my APIPA Module today, but there are some remaining 
problems, espacially the include thing I sent on the list this morning.

I think this APIPA module is fully compliant to RFC 3927 and works ok. There 
are some thing to do, so e.g. reset all TCP-Connections at a retreat and 
cooperation with the dhcp client.

It would be great if some guys could have a quick look over it, maybe compile 
it and give me a hint with the compiler-warning thing:

warning: 'struct etharp_hdr' declared inside parameter list lwip/include/lwip 
apipa.h line 93
warning: its scope is only this definition or declaration, which is probably 
not what you want lwip/include/lwip apipa.h line 93
warning: passing argument 2 of 'apipa_arp_reply' from incompatible pointer type 
lwip/arch etharp.c line 547

Regards,

Dominik