Hi Bryant,
Specifically regarding this point...
> Thanks for clarification on releases. I was confused because of the jump
> between 1.0.8 and 1.2.0, with a (yet unreleased) 1.1.x.
>
>
> In case you haven't already read these two pages, you might get some useful
information on how the releases a
On Fri, Jun 19, 2009 at 4:08 PM, Guy Harris wrote:
>
> On Jun 18, 2009, at 4:43 PM, Joshua (Shiwei) Zhao wrote:
>
> > With Wireshark, I'm trying to modify it to send NDIS requests to a
> > wifi card driver on windows OS.
>
> Ideally, Wireshark shouldn't do that; all operations on capture
> device
Using tshark from svn (today) with ath5k from wireless-testing (today)
I'm noticing some reporting of a signal value which is completely off
when using the statistics feature (io,stat). At first I though it was
ath5k so I went to verify we don't report huge signal values and we
don't. Right before
I was thinking mainly in terms of SCCP.
There are protocols on top of SCCP where the receiver/sender is
important.
Currently the SCCP code is setting the direction to SENT for which ever
point code originates the SCCP Connection Request.
Which is logical if you are trying to indicate who initated
This isn't critical for us, and I haven't been able to reproduce it by
running tshark standalone, and its an old tshark version... but I
thought I'd report this in case anybody knows what's going on.
We run tshark from inside a python/twisted exe, that's running as
root. If I run from the command
On Jun 18, 2009, at 4:43 PM, Joshua (Shiwei) Zhao wrote:
> With Wireshark, I'm trying to modify it to send NDIS requests to a
> wifi card driver on windows OS.
Ideally, Wireshark shouldn't do that; all operations on capture
devices should be done through libpcap/WinPcap.
However, as not all
The issue is solved.
I was trying to build plugin without building the wireshark from source. That
might be a reason, but not sure.
Though wireshark build failed, I was able to build the plugin. I guess the
wireshark build would have generated proper config.h file.
Thanks for you help in advance
On Jun 19, 2009, at 3:13 PM, kahou lei wrote:
> My fibre channel captured is in pcap format.
To use pcap format for a capture, either
1) your capture must be able to use an existing DLT_ value - which
isn't the case for Fibre Channel;
2) you use one of the DLT_USERn link-laye
Hi Guy,
My fibre channel captured is in pcap format. What I want to do is to dissect
this file with fibre channel dissector. In this case, do I still need to
write code to read/write the file? Or just create a new DLT value for Fibre
Channel and then register the existing fibre channel dissector w
Guy Harris wrote:
> On Jun 19, 2009, at 11:01 AM, kahou lei wrote:
>
>> Is there an existing DLT value that I can dissect raw fibre channel
>> packet?
>
> No.
>
>> I saw there is a fibre channel dissector (packet-fc.c) but I cannot
>> find a DLT value corresponse to it.
>
> It's used to d
On Jun 19, 2009, at 9:25 AM, Jeff Morriss wrote:
> Well, I don't know if it's the same for all protocols, but it's
> usually
> set to one of these defines:
>
> epan/packet_info.h:#define P2P_DIR_UNKNOWN -1
...which means "there's not enough information in the file to
determine the direc
On Jun 19, 2009, at 11:01 AM, kahou lei wrote:
> Is there an existing DLT value that I can dissect raw fibre channel
> packet?
No.
> I saw there is a fibre channel dissector (packet-fc.c) but I cannot
> find a DLT value corresponse to it.
It's used to dissect FC encapsulated in various low
shreejith bl wrote:
> I copied config.h.win32 to config.h in c:\wireshark.
> Now I am getting the below error.
>
> I can see in config.h declarations which the compiler is not
> understanding like,
> @HAVE_LIBPCAP@
> @HAVE_PCAP_BREAKLOOP@
> @HAVE_PCAP_FINDALLDEVS@
> @HAVE_PCAP_DATALINK_NAME_TO_VAL
I copied config.h.win32 to config.h in c:\wireshark.
Now I am getting the below error.
I can see in config.h declarations which the compiler is not understanding like,
@HAVE_LIBPCAP@
@HAVE_PCAP_BREAKLOOP@
@HAVE_PCAP_FINDALLDEVS@
@HAVE_PCAP_DATALINK_NAME_TO_VAL@
@HAVE_PCAP_DATALINK_VAL_TO_NAME@
@WP
shreejith bl wrote:
> Hello all,
>
> I am trying to build a plugin.dll. I am using the wireshark sources from the
> revision HEAD (latest source).
> I am using VC++ 2008 Express Edition. Same was the case with VS .NET 2003.
>
> I am getting the following error. Can someone please help me in this
Sorry for the top post (Outlook).
I would argue that it ain't released until it is "released". One could
further argue that the official release should be built from the
location, but I know there are issues related to that.
As for using SVN in this case, it is part of our automated build
process
Hi,
Is there an existing DLT value that I can dissect raw fibre channel packet?
I saw there is a fibre channel dissector (packet-fc.c) but I cannot find a
DLT value corresponse to it.
If there is no such DLT value, can you give me some direction on how to
extend my local wireshark build so that t
Hello all,
I am trying to build a plugin.dll. I am using the wireshark sources from the
revision HEAD (latest source).
I am using VC++ 2008 Express Edition. Same was the case with VS .NET 2003.
I am getting the following error. Can someone please help me in this regard?
Thanks,
Shreejith
Error
Michael Lum wrote:
> Hello,
>
> is there a fixed meaning of packet_info.p2p_dir for all protocols?
>
> What is that value supposed to mean?
Well, I don't know if it's the same for all protocols, but it's usually
set to one of these defines:
epan/packet_info.h:#define P2P_DIR_UNKNOWN -1
Bryant Eastham wrote:
> All-
>
> This is going to sound more harsh than I mean it to. I appreciate that
> people have differing opinions on this subject.
>
> To the core developers: please use Subversion in a more standard way.
>
> Yes, Subversion can be used in many different ways. However, j
All-
This is going to sound more harsh than I mean it to. I appreciate that
people have differing opinions on this subject.
To the core developers: please use Subversion in a more standard way.
Yes, Subversion can be used in many different ways. However, just
because it can doesn't mean
Yeah, the program just crashed. It said it was a runtime error and was forced
to close unexpectedly or something.
And yes, those examples are very similar to what I had and the only change I
made was what you changed, changing the array into a pointer and allocating
memory to it with calloc( )
Hello Dave,
I am doing this at the moment, nearly finished.
Patch is attached for your reference.
Please feel free to comment on it.
I am going to submit implementation to Bugzilla today or on Monday.
Regards,
Artem Tamazov
TELLABS
From: wireshark-dev-boun...@
23 matches
Mail list logo
