On Sat, Aug 04, 2007 at 03:27:19AM +, [EMAIL PROTECTED] wrote:
> Directory: /trunk/tools/
> ChangesPath Action
> +1 -1 runlex.sh Modified
>
> Directory: /trunk/wiretap/
> ChangesPath Action
> +1 -1 runlex.sh Modified
Why are there two (curre
On Sat, Aug 04, 2007 at 02:13:57AM +, [EMAIL PROTECTED] wrote:
> Add a script
or maybe not :)
Ciao
Joerg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should r
Whenever I try to build Wireshark on my iMac G5 running Mac OSX
10.4.10 I get a large number of errors.
The configure script works and prints this:
The Wireshark package has been configured with the following options.
Build wireshark : yes
Build tshark
Hi to all,
>From the latest sources (I've checked out the revision 22443), I see that
the decoding of MPEG2TS packets arrives only till header + adaptation field
while the payload is dumped, but the payload still includes other useful
info: PSI table info (ISO/IEC 13818-1 par. 2.4.4) and PES packe
Luis EG Ontanon schrieb:
> SQL clients are blocking. (There may be some non-blocking, but I'm not
> aware of any GPL compatible non-blocking SQL client). That means that
> wireshark should wait for the write to be acked before capturing the
> next packet and that would probably cause many packets t
SQL clients are blocking. (There may be some non-blocking, but I'm not
aware of any GPL compatible non-blocking SQL client). That means that
wireshark should wait for the write to be acked before capturing the
next packet and that would probably cause many packets to be dropped,
thus rendering the
Is there any news regarding this topic in the Wishlist?
Data I/O (e.g. Files)
1.
The ability to dump packet data/info into an SQL database. (How
would the schema for the database be specified, and how would the
information to be dumped to the database be specified
[EMAIL PROTECTED] wrote:
> I've seen that the pcap packet header contains a field "Interface ID"
The pcap packet header, as defined by libpcap from tcpdump.org (which is
the closest thing to an official pcap header definition that exists), has:
a time stamp, with seconds and microsecond
>
> Lars Ruoff wrote:
> > Sorry, but I think they look quite dull.
> > I prefer the actual ones.
>
> Can you please elaborate as to how you think they are dull?
> Does the blue version linked above alleviate this thought?
It does.
But I still prefer the current one.
I basically go with the opi
My humble opinion:
> Making the fin blue is an option though, and the result would look
like so:
>
>http://wayofthemonkey.com/wireshark-blue.png
That's better than the other one.
>The TM'd image, and the current icon, I think are a bit over-simplified
for an application icon/logo on modern oper
Hi,
I'm also very interested in displaying Interface IDs in an additional column
(like e.g. timestamps).
I've seen that the pcap packet header contains a field "Interface ID" which
seems to be currently unused in Wireshark?
Would it be possible to add this Interface ID to the packet info, so it
11 matches
Mail list logo
