Re: [Wireshark-dev] Interface names on Windows

On Oct 28, 2012, at 3:25 PM, Graham Bloice wrote: > There is also a fourth possible component; the "friendly" name assigned to > the interface in the Control Panel "Network Connections" applet. This is > held in the registry and is easily retrieved given the interface "guid" and a > few line

Re: [Wireshark-dev] RFD: The Future of Memory Management in Wireshark

On Sun, Oct 28, 2012 at 7:26 PM, Jakub Zawadzki wrote: > On Sun, Oct 28, 2012 at 10:12:41AM -0400, Evan Huus wrote: >> We might be able to fake the proper scoping using thread-local globals >> if we wrap everything in functions that assert the state of a >> dissection. Something like: >> >> __thre

Re: [Wireshark-dev] Interface names on Windows

On Oct 28, 2012, at 4:08 PM, Jakub Zawadzki wrote: > if user description: > - not set than: format("%s (%s)", friendly_name, interface_description) > - set: only user descr. > > Anyway such code should imho go to winpcap. Which code? The code to get the friendly name, or that code and the c

Re: [Wireshark-dev] RFD: The Future of Memory Management in Wireshark

On Sun, Oct 28, 2012 at 10:12:41AM -0400, Evan Huus wrote: > We might be able to fake the proper scoping using thread-local globals > if we wrap everything in functions that assert the state of a > dissection. Something like: > > __thread wmem_allocator_t *packet_scope; > __thread gboolean packet_

Re: [Wireshark-dev] Interface names on Windows

Hi, On Sun, Oct 28, 2012 at 10:25:30PM +, Graham Bloice wrote: > I've been hacking around trying to improve the display of interface names > on Windows. > > Currently there are 3 components displayed in various dialogs and command > line responses; the interface "guid" > (\Device\NPF_{C2E403B

[Wireshark-dev] Interface names on Windows

I've been hacking around trying to improve the display of interface names on Windows. Currently there are 3 components displayed in various dialogs and command line responses; the interface "guid" (\Device\NPF_{C2E403B5-FAD0-479C-96FD-0E44EB22CD74}), the interface description from WinPCap (Intel(R

[Wireshark-dev] WinPCap / Windows 8 Support

It's been years since Wireshark recommended a new version of WinPCap (it's been v4.1.2 for years). Is this packet capture library still alive? When I run the Windows 8 Upgrade Assistant, it reports that Win

Re: [Wireshark-dev] [Wireshark-bugs] [Bug 7922] Buildbot crash output: fuzz-2012-10-27-11126.pcap

On 10/28/2012 4:24 PM, bugzilla-dae...@wireshark.org wrote: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7922 Evan Huus changed: What|Removed |Added Status|NEW

Re: [Wireshark-dev] Direction definition on packet bus with no direction info in packet header

On Oct 28, 2012, at 11:22 AM, Martin Kaiser wrote: > The solution we came up with is to have one DLT. The pcap packet data > consists of a pseudo-header and the actual bytes that are transfered. > The dissector picks up the direction from the pseudo-header. > The capturing tool has to create the

Re: [Wireshark-dev] Direction definition on packet bus with no direction info in packet header

Hi, Thus wrote Andrew Lonsdale (calonsda...@gmail.com): > I'm writing a dissector for an interface which doesn't indicate direction > of data flow in the packet headers. I currently capture separate files in > pcapng format for uplink and downlink (separate streams), but I could merge > the two i

[Wireshark-dev] LTE S102/A21 decoding support

Hi to all, is there any plan to support in wireshark the decoding of CDMA A21 messages for S102 and S1AP LTE interfaces? Is there anybody already working on this and that can share some pcap file? If so If I would be glad to collaborate on this work. Thanks Mau

Re: [Wireshark-dev] RFD: The Future of Memory Management in Wireshark

On Sat, Oct 27, 2012 at 3:09 PM, Evan Huus wrote: > On Sat, Oct 27, 2012 at 2:17 PM, Dirk Jagdmann wrote: >>> General thoughts from the list on whether or not this would be a good idea? >> >> some general comments on the whole wmem idea: >> memory allocation is done almost everywhere in Wireshark