> Yes I am doing live capturing, but all what I interested about is the 16
> byte "Source Name" field (Name to Add). I want to include the tcpdump
> command in my perl program so that I can make further processing on the data
> of that field.
i would suggest you write a program using libp
Yes I am doing live capturing, but all what I interested about is the 16
byte "Source Name" field (Name to Add). I want to include the tcpdump
command in my perl program so that I can make further processing on the data
of that field.
I need your help in this matter
Regards
Bassam A. Al-Khaffa
> Hi,
>I am capturing the NetBeui (NBF) packets by using the following command:
>
> tcpdump -X netbuie
>
> I am getting a range of data, but, is there a way to determine which part of
> the packet to extract? I am interested in the 16 byte "Source Name" field
> (Name to add) as shown below. I
Hi,
I am capturing the NetBeui (NBF) packets by using the following command:
tcpdump -X netbuie
I am getting a range of data, but, is there a way to determine which part of
the packet to extract? I am interested in the 16 byte "Source Name" field
(Name to add) as shown below. I want to extrac
On May 27, 2004, at 5:22 AM, Gisle Vanem wrote:
Since pcap_dump_close() doesn't have a pcap_t argument, where should
the oldmode come from? Can we have two module globals; oldmode_stdin,
oldmode_stdout, assuming stdin/stdout won't be opened for capture more
than once?
If it's opened for capture or
On May 27, 2004, at 11:04 AM, [EMAIL PROTECTED] wrote:
Below are patches to perform significantly more complete LDP decoding.
Checked in, with an unused variable removed, and with declarations of
"decode_prefix{4,6}()" put into a "decode_prefix.h" header included by
"print-bgp.c" and "print-ldp.c
Below are patches to perform significantly more complete LDP decoding.
Synposis:
- Minor diff to print-tcp.c (actually call the LDP decoder)
- Minor diff to print-bgp.c (unstaticize routines used by print-ldp.c)
- Major diff to print-ldp.c
Hannes: I'd be happy to decode even more if you can get m
> Since pcap_dump_close() doesn't have a pcap_t argument, where should
> the oldmode come from? Can we have two module globals; oldmode_stdin,
> oldmode_stdout, assuming stdin/stdout won't be opened for capture more
> than once?
I've added a 'long filemode' to 'struct pcap' (long since O_BINARY
"Guy Harris" <[EMAIL PROTECTED]> said:
> Also, should we save the mode returned by "setmode()" and restore it
> when we close a "pcap_t" or "pcap_dumper_t" that refers to the standard
> input or output?
Since pcap_dump_close() doesn't have a pcap_t argument, where should
the oldmode come from?
CVS log entries from 26.05.2004 (Wed) 09:04:04 - 27.05.2004 (Thu) 09:04:04 GMT
=
Summary by authors
=
Author: guy
File: tcpdump/CREDITS; Revisions: 1.94
File: tcpdump/print-ipx.c;
10 matches
Mail list logo