Stephen Fisher wrote:
Thanks for your contribution! I've committed your changes as SVN
revision 21304 with a minor change in a few places that won't affect
normal operation of the code:
I changed match_strval() to val_to_str() (see doc/README.developer for
usage notes - match_strval()
Greetings,
I'm creating a Firebird (and Interbase) dissector, the current
dissector only tells me the opcode, but I need it for some automated
query logging, without capturing the complete packets. (And without
the hassle of looking up the query in the hex view)
The current dissector calls the
Hello,
I have a problem with build wireshark under win xp.
I get follow ERR
C:\Programme\Microsoft Platform SDK for Windows Server 2003
R2\Include\W
inSock.h(903): Siehe Deklaration von 'WSAAsyncGetServByPort'
C:\Programme\Microsoft Platform SDK for Windows Server 2003
Hallo wrote:
Hello,
I have a problem with build wireshark under win xp.
I get follow ERR
C:\Programme\Microsoft Platform SDK for Windows Server 2003
R2\Include\W
inSock.h(903): Siehe Deklaration von 'WSAAsyncGetServByPort'
C:\Programme\Microsoft
Hi,
Thanks for your inputs.
The problem has been resolved with the inclusion of the epan/emem.h
for 64 bit environment.
Yes, the dissector is a proprietary one.
Regards,
Bhavani.
The information contained in this electronic message and any attachments to
this message are intended for
Luis,
I believe this bug is talking about the filter button on the Windows
file dialog that doesn't work, which didn't the last time I checked SVN
so it should remain open (or we need to open a new bug for it). The
filter button works in the GTK file dialog just fine.
On Thu, Apr 05, 2007 at
On Apr 5, 2007, at 3:19 AM, [EMAIL PROTECTED] wrote:
The problem has been resolved with the inclusion of the epan/
emem.h for 64 bit environment.
Code should *always* include the appropriate headers for any functions
it calls, to import the proper declarations for those functions;
On Wed, Apr 04, 2007 at 02:20:59PM +0200, Simon Ginsburg wrote:
BACnet is not easy to find. IMHO it's also a member of the
FieldbusProtocolFamily as is LON and EIB, the first using IP-852,
the latter EIBnet/IP for the transport over IP. Is it OK that I extend
the Wiki pages accordingly?
On Apr 5, 2007, at 3:35 PM, Stephen Fisher wrote:
On Wed, Apr 04, 2007 at 02:20:59PM +0200, Simon Ginsburg wrote:
BACnet is not easy to find. IMHO it's also a member of the
FieldbusProtocolFamily as is LON and EIB, the first using IP-852,
the latter EIBnet/IP for the transport over IP. Is
