Re: [Wireshark-dev] Introduction and first questions/suggestions
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 it OK that I >> extend >> the Wiki pages accordingly? > > Please do! ...which is, generally, the default answer for a wiki; the whole point of a wiki is to let as many people contribute as possible. ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Introduction and first questions/suggestions
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? Please do! Steve ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Segmentation fault in dissector
On Apr 5, 2007, at 3:19 AM, [EMAIL PROTECTED] wrote: > The problem has been resolved with the inclusion of the 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; otherwise, you will see problems such as this. Make sure you're including all the necessary header files. ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] [Wireshark-bugs] [Bug 942] File -> Open dialog's Filter button does nothing
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 07:33:23PM +, [EMAIL PROTECTED] wrote: > http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=942 > > > [EMAIL PROTECTED] changed: > >What|Removed |Added > > Status|NEW |RESOLVED > Resolution||WORKSFORME > Version|0.99.0 |0.99.6 > > > > > --- Comment #6 from [EMAIL PROTECTED] 2007-04-05 19:33 GMT --- > If I understand well this is a problem on how the word "filter" is > interpreted. > > Being it in the open file dialog someone will naturally interpret it as file > filter like in "*.cap" > > But being in wireshark the "filter" term is interpreted as a wireshark display > filter. > > I think the solution is to rename the field of the open dialog into "display > filter" > > > IMHO if the issue is about memory we should be using libpcap filters instead > of > wireshark ones. > > > -- > Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email > --- You are receiving this mail because: --- > You are the assignee for the bug, or are watching the assignee. > ___ > Wireshark-bugs mailing list > Wireshark-bugs@wireshark.org > http://www.wireshark.org/mailman/listinfo/wireshark-bugs ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] problems with building wireshark unter win xp
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 Platform SDK for Windows Server 2003 > R2\Include\WinSock2. > > h(2432) : error C2375: 'WSAAsyncGetProtoByName': Neudefinition; > unterschiedliche > > Bindung > > C:\Programme\Microsoft Platform SDK for Windows Server 2003 > R2\Include\W > > inSock.h(911): Siehe Deklaration von 'WSAAsyncGetProtoByName' > > C:\Programme\Microsoft Platform SDK for Windows Server 2003 > R2\Include\WinSock2. > > h(2457) : error C2375: 'WSAAsyncGetProtoByNumber': Neudefinition; > unterschiedlic > > he Bindung > > C:\Programme\Microsoft Platform SDK for Windows Server 2003 > R2\Include\W > > inSock.h(918): Siehe Deklaration von 'WSAAsyncGetProtoByNumber' > > C:\Programme\Microsoft Platform SDK for Windows Server 2003 > R2\Include\WinSock2. > > h(2482) : error C2375: 'WSAAsyncGetHostByName': Neudefinition; > unterschiedliche > > Bindung > > C:\Programme\Microsoft Platform SDK for Windows Server 2003 > R2\Include\W > > inSock.h(925): Siehe Deklaration von 'WSAAsyncGetHostByName' > > C:\Programme\Microsoft Platform SDK for Windows Server 2003 > R2\Include\WinSock2. > > h(2509) : error C2375: 'WSAAsyncGetHostByAddr': Neudefinition; > unterschiedliche > > Bindung > > C:\Programme\Microsoft Platform SDK for Windows Server 2003 > R2\Include\W > > inSock.h(932): Siehe Deklaration von 'WSAAsyncGetHostByAddr' > > C:\Programme\Microsoft Platform SDK for Windows Server 2003 > R2\Include\WinSock2. > > h(2532) : error C2375: 'WSACancelAsyncRequest': Neudefinition; > unterschiedliche > > Bindung > > C:\Programme\Microsoft Platform SDK for Windows Server 2003 > R2\Include\W > > inSock.h(941): Siehe Deklaration von 'WSACancelAsyncRequest' > > C:\Programme\Microsoft Platform SDK for Windows Server 2003 > R2\Include\WinSock2. > > h(2552) : error C2375: 'WSAAsyncSelect': Neudefinition; unterschiedliche > Bindung > > > > C:\Programme\Microsoft Platform SDK for Windows Server 2003 > R2\Include\W > > inSock.h(943): Siehe Deklaration von 'WSAAsyncSelect' > > > > > > what is worng??? > Are you building from SVN, if so are you up to date. I checked in a fix for similar errors yesterday in r21335. I'd also like to point out that a list of compiler errors is not very helpful without a context, i.e. the compiler line that preceded the errors. -- Regards, Graham Bloice ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] Segmentation fault in dissector
Hi, Thanks for your inputs. The problem has been resolved with the inclusion of the 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 the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] problems with building wireshark unter win xp
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 R2\Include\WinSock2. h(2432) : error C2375: 'WSAAsyncGetProtoByName': Neudefinition; unterschiedliche Bindung C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Include\W inSock.h(911): Siehe Deklaration von 'WSAAsyncGetProtoByName' C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Include\WinSock2. h(2457) : error C2375: 'WSAAsyncGetProtoByNumber': Neudefinition; unterschiedlic he Bindung C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Include\W inSock.h(918): Siehe Deklaration von 'WSAAsyncGetProtoByNumber' C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Include\WinSock2. h(2482) : error C2375: 'WSAAsyncGetHostByName': Neudefinition; unterschiedliche Bindung C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Include\W inSock.h(925): Siehe Deklaration von 'WSAAsyncGetHostByName' C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Include\WinSock2. h(2509) : error C2375: 'WSAAsyncGetHostByAddr': Neudefinition; unterschiedliche Bindung C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Include\W inSock.h(932): Siehe Deklaration von 'WSAAsyncGetHostByAddr' C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Include\WinSock2. h(2532) : error C2375: 'WSACancelAsyncRequest': Neudefinition; unterschiedliche Bindung C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Include\W inSock.h(941): Siehe Deklaration von 'WSACancelAsyncRequest' C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Include\WinSock2. h(2552) : error C2375: 'WSAAsyncSelect': Neudefinition; unterschiedliche Bindung C:\Programme\Microsoft Platform SDK for Windows Server 2003 R2\Include\W inSock.h(943): Siehe Deklaration von 'WSAAsyncSelect' what is worng??? Best Regards Klaus ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] Firebird/Interbase dissector questions
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 protocol 'ib', but I wondered if this is the best/preffered name. The name IANA gives it is 'gds_db', I use it for my new dissector, but really, I don't know what it even stands for ;) Possible other names are 'fb' or 'ib/fb', that give more credit to the shared protocol between the 2 spinoffs. I tend to go for gds_db, but I suppose others might not recognize the packets when called this way. Also I wonder about how to best display the information in the packets. The first 4 bytes are the opcode for the packet, and it pretty much describes the contents of the remaining packet. The packet is mostly a flat binary list of information, and I wonder where to put that information on the packet tree. 1. I might put the information in a flat style after the opcode. 2. I might make a subtree on the opcode, and put the information in there. 3. I might make a subtree on a node beneath the opcode. The problem with 1 is that the packet tree for the firebird packet looks almost completely different every time there is another opcode. The problem with 2 is that the firebird packet tree has 1 node, witch is a subtree, with more nodes. And the problem with 3 is that the information in the opcode is duplicated somewhat. What is the best/preffered way to handle this? -- Mvg Môshe van der Sterre http://www.moshe.nl/ http://www.coecu.nl/ ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
