Ethereal-dev: Re: [ethereal-dev] Captures of the loop-back driver causes all sorts of problem

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Richard Sharpe <sharpe@xxxxxxxxxx>
Date: Tue, 12 Sep 2000 13:28:52 +0900
At 11:32 PM 9/10/00 -0700, Guy Harris wrote:
>On Mon, Sep 11, 2000 at 12:51:56AM +0900, Richard Sharpe wrote:
>> Damn captures on the loopback driver, which gives me two copies of each
>> packet, causes real problems with my latest BXXP code ...

[some deletia]

>In a capture program such as Ethereal, one could, I guess, check for
>duplicate IP packet retransmissions (same source and destination IP
>addresses, same IP ID, same length, same fragment offset) and just
>display them as duplicates rather than handing them to the next
>protocol; this might be useful in any case (when we do fragment
>reassembly we'll have to keep track of that information for IP
>fragments, at least), and would, at least, make the display of Linux
>loopback traffic less confusing (you'd only see bogus duplicate IP
>packets, not other bogosity).

As I am finding, this is relatively hard to do. We will have to keep
per-frame state and per-conversation state, and will have to syncronize
between them.




Regards
-------
Richard Sharpe, sharpe@xxxxxxxxxx
Samba (Team member, www.samba.org), Ethereal (Team member, www.zing.org)
Contributing author, SAMS Teach Yourself Samba in 24 Hours
Author, Special Edition, Using Samba