Wireshark-dev: [Wireshark-dev] New BT HCI wiretap decoder whose files don't have direction
From: Stephen Fisher <[email protected]>
Date: Sun, 16 Nov 2008 19:46:34 -0700
The new Apple PacketLogger file format wiretap decoder I've just written 
(still in testing - not in svn yet) reads in files that don't have a 
direction flag.  What does everyone think the best way to work around 
this is?

The decoder passes data to Wireshark as BTHCI.  The pseudo-header for 
BTHCI has a channel flag (which I can assign properly) and a gboolean 
sent flag.  Should we change this to another type of variable (I know, 
behind the scenes gboolean is something like a guint32, but this would 
be to make it clearer about what it is used for) so we can assign a 
third value such as -1?  Then update the code to show unknown direction 
or just don't show a direction.