>> last night working around it -- because even though you can send DHCP
>> requests over such an interface, absolutely _no_ incoming packets are
>> processed, even if the packets are hardware broadcasts and there's an
>> existing UDP socket ready and waiting.
>
>Correct.
>
>> So, is "0.0.0.0" meaning "no IP" a bug or a feature?
>
>Its a bug fix. 2.0 actually doesnt quite do everything right for the
>DHCP case. Setting the local address to 0.0.0.0 is sort of a hack. People
It is? According to my TCP/IP protocols book, a DHCP client is suppose to
set the ip address to 0.0.0.0 before broadcasting the request for an
address. From what the book led me to understand it does this becuase every
machine on the network needs an address.
>have already fixed dhcpcd to handle this nicely.
>
>Alan
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.rutgers.edu
>Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html