Ryan Lovett wrote:
What does this mean?
It means that there needs to be some way in a Wireshark protocol tree to
distinguish XXX is a protocol inside YYY from XXX is the next
instance of a protocol after the YYY instance of that protocol.
Currently, there isn't, so the protocol statistics
Here is OpenBSD 4.0 Wireshark 0.99.5 port:
http://secure.lv/~nikns/stuff/ports/wireshark-0.99.5.tar
SECURITY MEASURES:
If run with root privileges, wireshark, tshark and dumpcap will drop
privileges to unprivileged user _wireshark after opening live capture
device or dump file.
On Thu, Mar 01, 2007 at 12:38:01PM -, McGlinchy, Alistair wrote:
While you are there, could you cast your eyes over this extension to
your fix to allow for the files:value criteria too. This works but
requires multiple uses of the -b flag (rather than the -b and -a
flags).
But MLPPP can definitely be a source of out of order delivery!
Mike
On Mar 12, 2007, at 5:29 PM, Stephen Fisher wrote:
On Fri, Mar 02, 2007 at 05:01:09PM -0500, Small, James wrote:
I believe the 3 T1 are multiplexed using multilink PPP using an
Adtran
router if I remember correctly.
Is
