Hello,
> The pseudo-header is 16 bytes long; the 2 bytes at an offset of 14 from
> the beginning of the header are a big-endian number which must have the
> value 0x0030, the first 2 bytes of the header are a big-endian number
> that gives an indication of the direction on which the packet is goin
Hello,
I got a new DLT_ value for raw LAPD from tcpdump.org i.e 203;
I was advised earlier by the WireShark Dev as below
__
> If you can't use the Linux LAPD DLT (even by faking the headers?)
___
derful support you all have rendered to us till now.
Thanks in advance
Varuna De Silva
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
es and they are raw LAPD messages.
How can we proceed from here onwards to decode LAPD messages.
Is it possible for us to use the same LAPD dissectors of wireshark.
Thank you
Varuna De Silva
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://w
ig on Wireshark.
Are there any other things that I should take precautions in
handling QSig other than changing the linktype in the pcap_t
structure.
Thanks
Varuna De Silva
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/ma
Hello,
Thanks for the reply,
> The function is implemented in Packet.dll, the sources are in
\winpcap\Packetntx\dll\packet32.cpp
It's my understanding that you implemented support for your card directly in
wpcap.dll. If so, the p->adapter field is a NULL/bogus pointer, so there
Packet API will rec
stop the live capture when we need. What could be the problem
for this? It keeps on capturing data at some speed around 128kbps.
Kind regards
Varuna De Silva
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listi
On 10/6/07, Varuna De Silva <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> We have had several problems when trying to integrate our device
> with wireshark. But as its our original effort there are certain problems
> we came across.
>
> When we run wireshark with our ow
Hello,
We have had several problems when trying to integrate our device
with wireshark. But as its our original effort there are certain problems
we came across.
When we run wireshark with our own wpcap.dll when our device is
attached to the USB port, and when we try to start our capture,
through
Hello,
It is with utmost thankfulness we write this to you regarding the approval
from Gerald to host our project on wireshark site.
We thank Gerald, Guy and all the wireshark community for this support.
Gerald Combs wrote:
> Guy Harris wrote:
> > On Sep 30, 2007, at 9:47 PM, Varuna
Hello,
> > dp = &dispbuff[0]; /*pointer to the data*/
> >
> > /* Call the user supplied callback function */
> > callback(user, &pcap_header, dp);
> >
> > processed++;
> >
> > }while(processed For your testing, you probably want to add a packet count variable,
Hello,
I further did some change like below,
(*ps).ps_recv = p->md.stat.ps_recv;
instead of
*ps = p->md.stat;
Now I cant see any unusual values for packets or packets/s
But when I started the normal network packet capturing other
than my device I still get the packets of my device.
But still
Hello,
> > And when I press the start button, the program, Hangs up.
> Perhaps your xxx_read routine is blocked waiting for a 3968-byte buffer
> full of data to arrive, even though some
> data has arrived? See my mail to tcpdump-workers on that.
I have not implemented it yet, before doing it I t
Hello,
> > This is what we hope to do, we will use the filter driver, of
> > snifferusb2.0, and hope to get the raw usb packets, then I will write
the porting
> > file ( the
> > famous pcap-xxx.c file), similar to one which we are doing
> > to integrate our hw, and integrate it with pcap-win32.
>
Hello,
with regard to one of my previous mails, I modified libpcap and compiled it
to support my device and replaced the wpcap.dll with the new one.
When this is done and when wireshark is opened,
In capture->interfaces list displays my device along with the others,
but in the "packets" and "pack
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
Hello,
I want to get the name of my device in capture->interfaces
> As long as you've modified libpcap/WinPcap so that pcap_findalldevs() adds
your device to the list of available > devices, it should be displayed in
Capture -> Interfaces and in the drop-down list in Capture -> Options.
I also
Hello,
Thanks for the reply,
>If you've modified libpcap/WinPcap to read from your capture device, and
>it supplies a link-layer type that Wireshark can handle (DLT_MTP2, for
>example), all you have to do to interface your device with Wireshark is to
>build and install your modified version of Wi
Hi friends,
I started on this forum, on developing a Hardware platform to capture SS7
traffic.
What We did so far:
I modified libpcap (in fact winpcap since I am at the moment on windows) to
open my
device to read packets in as instructed by the forum. But I have certain
things to get
cleared up
Hi all,
I have got it wrong thanks for showing it,
It works fine
sorry for the trouble
Xavier
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Hi Michael,
Thanks for the reply, heres the text file attached
Xavier
00 5c 5e 18 85 1a e2 45 70
08 83 56 13 77 70 10 83 08
18 0a 02 03 0a 00 60 00 a3
20 90 90 03 1d 09 13 50 82
28 11 13 83 07 0a 0f 00
Hi,
The lowest level of my SS7 frame is MTP2 and the highest is ISUP.
I was able to run text2pcap - l 140 to get it with a MTP2 header. But I
Still have the
problem of text2pcap truncating my capture file size to 16 bytes starting at
zero.
C:\Program Files\Wireshark>text2pcap -l 140 isup.txt is
Hi,
I have a problem with running text2pcap on windows, when I try to run it, it
truncates in 16 bytes. For example in the following part of script i tried
to convert
a file isup.txt to a pcap format with a pseudo SCTP header the file is
larger than
16 bytes (36 bytes) but it truncates at 16 byt
Hi,
Thanks for the quick reply,
1. Can we use/modify PCAP to access the contents of the memory, since the
data transfer is through USB and we dont have low level access to the IC (
i.e. before that being sent to the memory)? (I am new to pcap as well)
2. If we use raw SS7 frames how does WireShark
Hi All,
Dear friends I am new to the Wireshark community as a developer. As our
final year project
we will be developing a SS7 protocol Analyzer. Here we will be developing
the Hardware
Circuitry to tap a physical E1 line. We have used Dallas Maxim E1/DS1 ICs
are being used to
capture the raw data
Hi All,
Dear friends I am new to the Wireshark community as a developer. As our
final year project
we will be developing a SS7 protocol Analyzer. Here we will be developing
the Hardware
Circuitry to tap a physical E1 line. We have used Dallas Maxim E1/DS1 ICs
are being used to
capture the raw data
26 matches
Mail list logo
