[ronnie sahlberg <ronniesahlberg@xxxxxxxxx>]

Do you have a small example capture you can send me i can use to test
and verify a fix with?


On Thu, 07 Apr 2005 13:14:29 +0200, Radek Vokal <rvokal@xxxxxxxxxx> wrote:
> When ethereal displays the formatted packet for a bootp/dhcp DHCPACK
> that contains option 2 (time offset), the value is not calculated
> correctly.
> 
> Ethereal is treating the value as 32-bit UNsigned value, but it is
> supposed to be a SIGNED value. (See RFC 2132, section 3.4 Time Offset)
> 
> Actual Results:  Response from DHCP server ... 02 04 ff ff 9d 90 ...
> formatted as:
> 
> Option 2: Time Offset = 49709 days, 23 hours, 28 minutes, 16 seconds
> 
> 
> Expected Results:  The data portion of the data (0xff ff 9d 90) must be
> interpreted as a SIGNED number ( -25200 decimal) and is the number of
> seconds offset from UTC.
> This should display as:
> 
> Option 2: Time Offset = -7 hours
> or
> Option 2: Time Offset = 0 days, -7 hours, 0 minutes, 0 seconds
> 
> See Red Hat bugzilla
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=154082
> 
> -- 
> Radek Vokál     <rvokal@xxxxxxxxxx> 
> OS Systems Engineer
>         IT executives rate Red Hat #1 for value
>         http://www.redhat.com/promo/vendor/index.html
> 
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>