dhcpcd-discuss

Hi Konold

On Mon, 2010-12-06 at 13:02 +0100, EXTERNAL Konold Martin (Firma,
RtP2/TEF72) wrote:
> Thanks to you for looking into this issue!
> 
> > So yes, any broadcast for renewal is a bug.
> > Could you state which versions suffer from this?
> 
> dhcpcd-3.2.3     <-- definetly has the problem (used with OpenSUSE 11.0, 11.1, 11.2, 11.3 and Factory)
> dhcpcd-1.3.22pl4 <-- fine (used with SuSE Linux Enterprise Server 9 and 10)
> dhcpcd-5.2.9     <-- does not work as a drop in replaceemnt with OpenSUSE 11.0 or 11.3 and
>                      therefore I just made some source code checks. It looks to me like
>                      this uptodate version has the same problem. (E.g. it does not differ between the different type
>                      of DHCP REQUESTs most of them are broadcasts though a renewal must be a unicasdt directly to the DHCP server
>                      or to the gateway in case the dhcp server is in another network). Though I might be wrong here.

OK, I'm not interested in fixing dhcpcd-3

> I am also not sure how to test with dhcpcd-5.2.9 as according to the documentation the semantics of "dhcpcd -n" has changed.

Yes, the semantics have changed.
However, you can test by requesting a short lease time. I use this to
test
dhcpcd -dBl 20
You can then watch dhcpcd go about it's business. It will also inform
you how long a lease it actually got, incase server enforces a lease
longer than the requested 20 seconds.

I tested dhcpcd-5.2.9 and wireshark confirms correct operation in regard
to your query with RFC2131. I suggest you carry out your own testing
instead of just taking my word for it :)

BTW, dhcpcd-4 had compile time options so allow full compat with
dhcpcd-3 and earlier the idea being that distros could then change to
the new world. dhcpcd-5 removed this layer. If SuSE had kept up to date,
then it would be likey dhcpcd-5 would have just dropped in.

Thanks

Roy