Hi Joerg,
On Sun, Mar 4, 2012 at 10:50 PM, Joerg Mayer jma...@loplof.de wrote:
Hello Alexis,
nice piece of work. I have one annotation and one question:
You might try the following instructions for cmake:
http://www.cmake.org/Wiki/CMake:How_To_Build_Qt4_Software
but I'd be willing to do
Hello Alexis,
On Mon, Mar 05, 2012 at 10:10:40AM +0100, Alexis La Goutte wrote:
You might try the following instructions for cmake:
http://www.cmake.org/Wiki/CMake:How_To_Build_Qt4_Software
but I'd be willing to do this once internationalization is committed.
I tried but... no work !
On Mon, Mar 5, 2012 at 12:14 PM, Joerg Mayer jma...@loplof.de wrote:
Hello Alexis,
On Mon, Mar 05, 2012 at 10:10:40AM +0100, Alexis La Goutte wrote:
You might try the following instructions for cmake:
http://www.cmake.org/Wiki/CMake:How_To_Build_Qt4_Software
but I'd be willing to do
On Sun, Mar 04, 2012 at 08:21:14PM +0100, Alexis La Goutte wrote:
I realized a patch to add the i10n version of QtShark. The goal is only to
translate the Gui (not dissector)
Actually, there is only a french translations !
To test, launch qtshark with LANG=fr ./qtshark (in ui/qt folder)
On Mon, Mar 05, 2012 at 03:45:09PM +0100, Joerg Mayer wrote:
OK, some summary feedback (we talked about some of this already):
One more thing ;-)
- It looks like the qt-specific initialization is done in wireshark_main.cpp
while you do the i18 stuff in main.cpp.
ciao
Jörg
--
Joerg Mayer
Hi Ashish,
My protocol is registered, when I type it in the filter box it turns green.
Also, I've built again wireshark (hope that's what you meant by creating a
new workspace) but I still get the dissector not found error when I'm
editing the DLT user in the GUI as you advice me. What could be
On Mon, Mar 05, 2012 at 10:10:40AM +0100, Alexis La Goutte wrote:
You might try the following instructions for cmake:
http://www.cmake.org/Wiki/CMake:How_To_Build_Qt4_Software
but I'd be willing to do this once internationalization is committed.
I tried but... no work ! (for the
Hi Alex,
The plugin you attached is meant to open filetypes different than pcap,
right? I don't understand how to use this knowledge with my problem. I'm
using a pcap file, thing is I want wireshark to dissect a protocol in the
link layer which is not included in wireshark.
Armando Vázquez
For this to work your dissector needs to be registered by name. To get
that it needs to call register_dissector().
Armando Vázquez wrote:
Thanks ashis!
When I tried this my protocol does not show up as a valid protocol, why
is that? I tried using my dissector for the header protocol, but it
I did so by using this function:
void proto_register_myprotocol(void)
{
...
register_dissector(MY_PROTOCOL, dissect_myprotocol, proto_my_protocol);
}
Armando Vázquez Ramírez
On Mon, Mar 5, 2012 at 11:07 AM, Jeff Morriss jeff.morriss...@gmail.comwrote:
For this to work your dissector needs
Would it make any sense to be able to store application specific
information in a pcapng file ?
E.g., selected Wireshark prefs so that Wireshark can act on same ?
This would be useful when a capture file reqires specific dissector
preferences to properly dissect the file.
Would this fit (at
Hi Bill,
I don't know if the format's developers ever contemplated that use
case - although they designed it to be fairly extensible, and I'm sure
that someone could design a new type of block that stores serialised
application preferences (in compressed XML, JSON, or some other
format?), after
Hi,
I think there is two paths that can be taken either add options and/or
blocks as needed to the file format or
encode the comment in some way, using the preferences simple format is
one option.
I'm leaning towards using the comments somehow. One could have Wireshark
begin/end tags for
Anders Broman skrev 2012-03-05 20:03:
Hi,
I think there is two paths that can be taken either add options and/or
blocks as needed to the file format or
encode the comment in some way, using the preferences simple format is
one option.
I'm leaning towards using the comments somehow. One could
On Mar 5, 2012, at 11:03 AM, Anders Broman wrote:
I think there is two paths that can be taken either add options and/or blocks
as needed to the file format or
encode the comment in some way, using the preferences simple format is one
option.
I'm leaning towards using the comments
Bill Meier wrote:
Would it make any sense to be able to store application specific
information in a pcapng file ?
E.g., selected Wireshark prefs so that Wireshark can act on same ?
This would be useful when a capture file reqires specific dissector
preferences to properly dissect the file.
Is it possible to tell how longer would it be before Wireshark 1.6.6 is
released ?
On Mon, Mar 5, 2012 at 1:31 AM, Guy Harris g...@alum.mit.edu wrote:
On Mar 4, 2012, at 8:24 PM, Jeff Morriss wrote:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5939
It's scheduled to be fixed in
Hi Armando,
By creating a new workspace I meant deleting the first one completely and
taking the new one and implementing the changes again.
In the mean time can you post the code.
2012/3/5 Armando Vázquez avr...@gmail.com
I did so by using this function:
void proto_register_myprotocol(void)
18 matches
Mail list logo
