[En-Nut-Discussion] No DNS addresses with DHCP

[Dusan Ferbas]

Hi Pierre,

Michel mentioned 4 DHCP messages. In your contribution there were only 1st 
2 of them described. If your client does not send DHCP request, then server 
cannot answer with acknowledge packet.

DHCP_MSG_DISCOVER       1       /* DHCPDISCOVER message */
DHCP_MSG_OFFER          2       /* DHCPOFFER message */
DHCP_MSG_REQUEST        3       /* DHCPREQUEST message */
DHCP_MSG_ACK            5       /* DHCPACK message */

For more details see RFC 951, 1534, 1542, 2131 and 2132.

Dusan

>Michel,
>thanks for your help.
>
>DHCP is in sleep state. (70E1 dhcpc 64 SLP 0000 0944 70CD 492 OK )
>
>Even when the server answers "DHCP offer" and this frame well received
>(within 2 seconds),
>NutDhcpIfConfig call is freezed the "timeout time"  and it always returns
>"OK" after.
>No "last msg" to DHCP is sniffed...
>
>Sometimes (10% of case?),  NutDnsConfig2 is called by DHCP subroutine
>(printf trace) and DNS IP addresses well set. Perhaps "last msg" is sent in
>this case?
>
>Sometimes, DHCP ParseReply seems to recognize DNS IP adresses fields twice
>times (seen by printf trace) and NutDnsConfig2 is then called.
>
>Nut/OS NutVersionString() returns  "3.9.1 pre".
>
>
>
>Jean Pierre
>
>
>-----Message d'origine-----
>De : en-nut-discussion-bounces at egnite.de
>[mailto:en-nut-discussion-bounces at egnite.de] De la part de Michel
>Envoyé : jeudi 30 décembre 2004 09:15
>À : 'Ethernut User Chat (English)'
>Objet : RE: [En-Nut-Discussion] No DNS addresses with DHCP
>
>Yes, there are only 4 messages going back and forth.
>If NutOs does not get the last message to DHCP, your problem would occur.
>Can you check in which state the DHCP task is?
>
>Michel