Bug 154082
Summary: | decodes bootp/dhcp option 2 incorrectly | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Don Russell <don> | ||||
Component: | ethereal | Assignee: | Radek Vokál <rvokal> | ||||
Status: | CLOSED UPSTREAM | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i586 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-04-15 07:26:57 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Don Russell
2005-04-07 05:11:10 UTC
Can you provide an example capture file? Created attachment 112985 [details]
A small packet trace capturing the bootp/dhcp packets with a West of UTC time offset
As requested, a small capture showing the time offset option (option 2)
Specifically, see packet 2.
In my original report I suggested the form to display the offset, but that gets a little ugly for offsets that are not whole hours. Since offsets can't exceed 12 hours, including 0 days ia little redundant. Perhaps a more "traditional" format of display "time" in hours, minutes and seconds... Perhaps strftime with %X format flag: "Preferred time representation for the current locale but without the date". (Though you definately don't want any sort of am/pm indication) Or, something like: Option 2: Time Offset: UTC +/-hh:mm:ss or Option 2: Time Offest: West (UTC-) 7:00:00 or Option 2: Time Offset: East (UTC+) 3:00:00 if the offset exceeds +/- 12 hours, just report it as the raw hex data and a possible warning: Option 2: Time Offset: (Exceeds +/- 12 hours) 0xaa bb cc dd Well, just an idea. :-) Thanks, Don Just got a message from ethereal upstream that this will be fixed in next release. It prints that packet as ... -7 hours ... |