I was looking at the Windows buildbot status to see if the compiling step would
fail at the same place as it fails for me, namely here:
Generating Code...
Linking dumpcap.exe
link @C:\DOCUME~1\cmaynard\LOCALS~1\Temp\nmi02488.
Hello Guy,
I am using asn1 BER encoding at the sending side. And It is hard to figure
it out what exactly is the length byte. I have read the hexdump for some
different messages, they are varying.
I might be trying your suggestion when I get time. But thanks anyway.
Zongjun
On 9/27/07, Guy Harr
Hi Didier and Guys,
I finally figured it out! The only change I need to do is change "offset +=
offset_thisRound; " to "offset = offset_thisRound". Actually I was using
offset_thisRound for debugging information, to show how many bytes each time
we consume. We can just remove offset_thisRound vari
On 9/27/07, Zongjun <[EMAIL PROTECTED]> wrote:
>
> Hey Didier,
>
> I put "offset_thisRound =
> dissect_MyProtoMessage_PDU(tvb,pinfo,myproto_tree); " after if(tree){...},
> and IT WORKS! I can have multiple different PDUs in one segment! Amazing!
>
> The only thing is now I get much frequenter cas
On Sep 27, 2007, at 4:30 PM, Zongjun wrote:
> I could have 30 different kinds of messages and I just can't know
> the fix length. However, using tcp_dissect_pdus you have to give the
> fix length.
No.
Using tcp_dissect_pdus() you have to give:
1) a fixed minimum length, which:
On Sep 27, 2007, at 2:01 PM, Ulf Lamping wrote:
> Yes, I guess one of the problematic things to include pcapng into
> Wireshark is to find a good interface between libwiretap and Wireshark
> (or probably no interface at all). There are a lot of new concepts in
> pcapng that has no counterpart in
- Original Message -
From: "Ulf Lamping" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Thursday, September 27, 2007 5:22 PM
Subject: Re: [Wireshark-dev] [ntar-workers] Extending Wireshark libpcap
format support, or start using pcapng now ?!?
> Gianluca Varenni s
Gianluca Varenni schrieb:
>> I have reviewed that doc for a few hours today. Now I have a printout
>> with lot's of minor comments probably worth to be included. Most of them
>> is about clarifying stuff and make the document easier to read (well,
>> and some typos). The only really questionable th
- Original Message -
From: "Ulf Lamping" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark"
Sent: Thursday, September 27, 2007 2:01 PM
Subject: Re: [Wireshark-dev] [ntar-workers] Extending Wireshark libpcap
format support, or start using pcapng now ?!?
> Gianluca Varenni s
Hey Didier,
I put "offset_thisRound =
dissect_MyProtoMessage_PDU(tvb,pinfo,myproto_tree); " after if(tree){...},
and IT WORKS! I can have multiple different PDUs in one segment! Amazing!
The only thing is now I get much frequenter cases of "malformed packet".
I don't understand your point #3.
Ronnie,
I could have 30 different kinds of messages and I just can't know the fix
length. However, using tcp_dissect_pdus you have to give the fix length.
Zongjun
On 9/27/07, ronnie sahlberg <[EMAIL PROTECTED]> wrote:
>
> try using tcp_dissect_pdus() to handle the case with pdus transported
> on
try using tcp_dissect_pdus() to handle the case with pdus transported
ontop of tcp
it will take care of this for you automatically
On 9/28/07, Zongjun <[EMAIL PROTECTED]> wrote:
> Hey guys,
>
> According to my capture, I don't have situations where ONE PDU spans over
> multiple TCP segment. In st
On Thu, 27 Sep 2007 13:13:17 -0700, Zongjun wrote
> On 9/27/07, Zongjun <[EMAIL PROTECTED]> wrote:Hey Didier,
>
> You mean like
>
> gint offset_thisRound = 0; // of course, outside if(tree)block.
>
> if (tree) {
> myproto_item = proto_tree_add_item(tree, proto_myproto, tvb, o
Ulf Lamping schrieb:
> Gerald Combs schrieb:
>
>> Ulf Lamping wrote:
>>
>>
>>> Hi!
>>>
>>> Gerald, could you have a look?
>>>
>>>
>> The tests are failing with "** ERROR **: file capture-wpcap.c: line 181:
>> assertion failed (has_wpcap) aborting..." I restarted the builder,
We'd like to have one or two sessions on VoIP at SHARKFEST. At the moment,
we're having trouble finding a speaker. Is anyone interested in giving a
presentation on VoIP, or moderating a VoIP birds-of-a-feather session?
___
Wireshark-dev mailing list
Wir
Hi.
The t38 dissector does not compile on UN*X because the T38(2002).asn
file contains un-escaped parentheses in Makefile.common. I suppose
the simplest solution is to rename the file?
--
Stig Bjørlykke
___
Wireshark-dev mailing list
Wireshark-
Gianluca Varenni schrieb:
> First of all, sorry for taking a bit of time to answer this thread, I was
> working on libpcap/WinPcap. libpcap 1.0 is planned to come out soon...
>
No problem, a few hours is still a good value ;-)
> It's true. Consider that PPI and pcap-ng/ntar have different objec
On 9/27/07, Zongjun <[EMAIL PROTECTED]> wrote:
>
> Hey Didier,
>
> You mean like
gint offset_thisRound = 0; // of course, outside if(tree) block.
if (tree) {
> myproto_item = proto_tree_add_item(tree, proto_myproto, tvb,
> offset, -1, FALSE);
> myproto_tree = proto_i
Hey Didier,
You mean like
if (tree) {
gint offset_thisRound = 0
myproto_item = proto_tree_add_item(tree, proto_myproto, tvb,
offset, -1, FALSE);
myproto_tree = proto_item_add_subtree(myproto_item, ett_myproto);
offset_thisRound =
dissect_MyProtoMessage_PDU(tvb,
First of all, sorry for taking a bit of time to answer this thread, I was
working on libpcap/WinPcap. libpcap 1.0 is planned to come out soon...
Replies embedded below.
Have a nice
GV
- Original Message -
From: "Ulf Lamping" <[EMAIL PROTECTED]>
To: "Developer support list for Wireshark
Jeff Morriss schrieb:
> First, thanks for doing it! :-)
>
Thanks for helping me out :-)
> Second: I don't know much about it but I just committed something that
> works for me.
>
Seems others are satisfied as well :-)
> It seems (based on my somewhat limited testing) that we don't need to
>
Gerald Combs schrieb:
> Ulf Lamping wrote:
>
>> Hi!
>>
>> Gerald, could you have a look?
>>
>
> The tests are failing with "** ERROR **: file capture-wpcap.c: line 181:
> assertion failed (has_wpcap) aborting..." I restarted the builder, but it ran
> into the same error
Strange, it's runni
Gerald Combs schrieb:
> Pekka Pietikainen wrote:
>
>> Oh. If you add a new DLT_ value, having it in a way that is extensible
>> + has a way of saying "Here's the raw packet data. It's plain old
>> DLT_EN10MB". And the next one might be 802.11 and the next one 802.11 with
>> a radiotap header.
Hi
On Thu, 27 Sep 2007 12:02:32 -0700, Zongjun wrote
> Hey guys,
>
> According to my capture, I don't have situations where ONE PDU spans over
> multiple TCP segment. In stead, mine is the other round: Single segment
> having multiple PDUs.
>
> But using the folling code, what I observed is wi
Hi
On Thu, 27 Sep 2007 12:02:32 -0700, Zongjun wrote
> Hey guys,
>
> According to my capture, I don't have situations where ONE PDU spans over
> multiple TCP segment. In stead, mine is the other round: Single segment
> having multiple PDUs.
>
> But using the folling code, what I observed is wi
Hey guys,
According to my capture, I don't have situations where ONE PDU spans over
multiple TCP segment. In stead, mine is the other round: Single segment
having multiple PDUs.
But using the folling code, what I observed is wireshark did put multiple
PDU info inside the Detail Window after TCP,
On Thu, Sep 27, 2007 at 07:09:15PM +0100, Martin Warnes wrote:
>
> Attached is a small patch that correct an issue with reading certain IBM
> iSeries Comms traces.
Committed revision 23000.
Two small suggestions for future patches :
- could you submit future patches through http://bugs.wireshar
Pekka Pietikainen wrote:
> Oh. If you add a new DLT_ value, having it in a way that is extensible
> + has a way of saying "Here's the raw packet data. It's plain old
> DLT_EN10MB". And the next one might be 802.11 and the next one 802.11 with
> a radiotap header.
The Per-Packet Information heade
Ulf Lamping wrote:
> Hi!
>
> Gerald, could you have a look?
The tests are failing with "** ERROR **: file capture-wpcap.c: line 181:
assertion failed (has_wpcap) aborting..." I restarted the builder, but it ran
into the same error.
___
Wireshark-dev ma
Hi/
Attached is a small patch that correct an issue with reading certain IBM
iSeries Comms traces.
Traces where data has been dropped for whatever reason now have the
packet number suffixed with an asterix "*", this causes the current
iSeries wiretap routine to report a "bad" header. The attached
Ulf Lamping wrote:
> Hi!
>
> Gerald, could you have a look?
The tests are failing with "** ERROR **: file capture-wpcap.c: line 181:
assertion failed (has_wpcap) aborting..." I restarted the builder, but it ran
into the same error.
___
Wireshark-dev ma
On Thu, Sep 27, 2007 at 12:04:13PM -0400, Jeff Morriss wrote:
> Could other *NIX users test tshark to see if it works (I'll see in a
> while if the buildbots are happy about it)?
Tshark works fine now on MacOS X. Thanks!
Steve
___
Wireshark-dev mail
> Could other *NIX users test tshark to see if it works (I'll see in a
> while if the buildbots are happy about it)?
> ___
> Wireshark-dev mailing list
> Wireshark-dev@wireshark.org
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
It works for
Ulf Lamping wrote:
> Where I'm now lacking knowledge of is the best way to implement the pipe
> related stuff for the unix side - I need some help here. The current
> implementation uses a dummy function which runs into a g_assert(),
> therefore the buildbot test step and thark capturing fails
Sorry but I been very busy lately.
Most lua functions are just wrappers for functions of wireshark's
"API". Don't use the Lua wrappers, use the very same C functions they
use instead, you can use the code in them instead!
you can take the code in wslua_retap_packets() and
wslua_register_menu() an
On Thu, Sep 27, 2007 at 01:10:42PM +0200, Ulf Lamping wrote:
> Hi List!
>
> I have demand for storing some meta information into the capture file and
> later display it in Wireshark. This information is available in a separate
> capture tool and currently cannot be transferred to Wireshark to be
>
I've been seeing the following linking problem on Windows over the last
few days. What's strange though is that if I simply run nmake again,
everything works fine. Anyone else seeing this?
CVPACK : fatal error CK1024: ringbuffer.obj cannot use program database
c:\svn\wireshark\vc60.pdb : signatu
Jeff Morriss <[EMAIL PROTECTED]> has asked for review_for_checkin:
Bug 1870: new protocol dissector for the protocol PCE
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1870
--- Additional Comments from Jeff Morriss <[EMAIL PROTECTED]>
To be reviewed for checkin
___
>
> Hi
> can anybody tell me how i can use lua functions (f.e.retap_packets() )
> from
> plugin which written in C ?
> -- next part --
>
Nobody know how it use?
f.e. wslua_retap_packets(lua_State *L) or wslua_register_menu(lua_State *L)
what is lua_State? how make it work?
2007/9/27, Kukosa, Tomas <[EMAIL PROTECTED]>:
>
> > > Restored 'asn1\h245\h245-exp.cnf'
> > [...]
> > > Why are they removed when compiling? My guess is that they
> > probably shouldn't be removed. Either that, or they're no
> > longer needed at all? Anyway, I figured I would report it.
> >
> >
Hi List!
I have demand for storing some meta information into the capture file and later
display it in Wireshark. This information is available in a separate capture
tool and currently cannot be transferred to Wireshark to be displayed :-(
This would range from generic information like "which E
Hello,
We were to develop a SS7 protocol analyzer, from the scratch
for our final year UG project. But this nice piece of SW in Wireshark,
made our lives easy, But now, though our professor, welcomed the
usage of wireshark, wants us to go more with something extra.
So we thought of decoding raw U
> > Restored 'asn1\h245\h245-exp.cnf'
> [...]
> > Why are they removed when compiling? My guess is that they
> probably shouldn't be removed. Either that, or they're no
> longer needed at all? Anyway, I figured I would report it.
>
> They are in the process of being removed and being automati
> >
> > I think you forgot to add some Makefile.am/Makefile.common
> > files here :)
> >
>
> Oh, you are right. Thanks!
> I was not good start of this day. :(
The bad day continues. :(
I have committed config.nmake instead of config.in
Fix will follow.
_
Hi!
Gerald, could you have a look?
Regards, ULFL
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
> I think you forgot to add some Makefile.am/Makefile.common
> files here :)
>
Oh, you are right. Thanks!
I was not good start of this day. :(
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wires
46 matches
Mail list logo
