omshell lease ends field invalid characters

[Rick Dicaire]

Wow great catch...the date value of your hex conversion corresponds with
what I see in dhcpd.leases.
I can try and script for this, but should a bug be filed, or could this be
a terminal issue (I get same result from console terminal and xterm/ssh
session)?

On Tue, Sep 29, 2020 at 12:09 PM Rick Dicaire <kritek at gmail.com> wrote:

> Wow great catch...the date value of your hex conversion corresponds with
> what I see in dhcpd.leases.
> I can try and script for this, but should a bug be filed, or could this be
> a terminal issue (I get same result from console terminal and xterm/ssh
> session)?
>
> On Tue, Sep 29, 2020 at 8:32 AM Bruce Hudson <Bruce.Hudson at dal.ca> wrote:
>
>> > ends = "_sz-"
>> > starts = 5f:72:d1:6d
>>
>> > As shown above, 'ends' field does not have a hex value.
>> > Any thoughts as to what's causing this?
>>
>>     I suspect this is just an anomaly cause by omshell's more
>> generic output algorithm. Because all four bytes of the ends
>> value correspond to printable characters, it displays it as
>> a string instead of the raw octects. A (failed in this case)
>> effort to be more user friendly.
>>
>>     Looking at the ord's of the four characters in hex:
>>
>>         "_sz-" ==> 5f:73:7a:2d
>> --
>> Bruce A. Hudson                         | Bruce.Hudson at Dal.CA
>> ITS, Networks and Systems               |
>> Dalhousie University                    |
>> Halifax, Nova Scotia, Canada            | (902) 494-3405
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20200929/be56b451/attachment.htm>