https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16212

Peter Wu <pe...@lekensteyn.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |CONFIRMED
                 CC|                            |pe...@lekensteyn.nl
            Summary|manuf.tmpl update;          |Resolved OUI and Ethernet
                   |Organization Code in Packet |names are truncated
                   |Details                     |
     Ever confirmed|0                           |1

--- Comment #2 from Peter Wu <pe...@lekensteyn.nl> ---
> 1. What is format of "manuf" file now? Can header comment in "manuf.tmpl" be
> updated?

It is partially described in
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16038#c2. Since then, I
learned that multiple tabs (1-2) can occur after the short name for alignment.

> 2. manuf.tmpl entry for 00:00:00 Xerox - cleanup?
> -------------------------------------------------
> Format for first Xerox entry in manuf.tmpl seems to have a double entry for
> 00:00:00

I think it is on purpose. 00:00:00:00:00:00 should be displayed as such, and
not as Xerox_00:00:00. Added in commit
49a2f32336053e230f1636f347d9c4ad2a21dd11.

> 3. Organization Code: truncated in Packet Details
> -------------------------------------------------
> Should the full long manufacturer description be shown or is the field
> length limited?

The maximum name for the resolved name is "MAXNAMELEN" minus 1, see "hashether"
and "hashmanuf" in epan/addr_resolv.c. If it is not defined by the operating
system, it will be 63. For you it is apparently 31. It can potentially be
changed if necessary.

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to