[Ns-bugs] [Bug 443] Net device pcap traces arent consistent with what tcpdump would display

[code@nsnam.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=443





--- Comment #5 from Craig Dowell <craigdo at ee.washington.edu>  2009-03-11 03:02:11 EDT ---
>From list mail, suggesting a policy

1) There is a set of suggested trace sources for net devices.  These are
currently found in the repo I mentioned and should be documented in the
manual.

2) Implementing the complete set of suggested trace sources in a net device
is not a requirement.  A device author may pick a subset of these sources to
implement.

3) The net device author should document what trace sources are implemented
and the state the packets are in when they come out of the trace source.
For example, raw IP, ethernet header, llc/snap, dix, p2p, wifi, etc.

4) A net device author should implement a PromiscSniffer trace source to
allow tcpdump-like functionality in helpers to be called a "standard" net
device; but you are always allowed to do whatever you think is right on your
own time.

In furtherance of this policy I did the following:

1) Remove the objectionable Sniffer (Ethernet frame) and tx complete trace
sources from the wifi device;

2) Remove the unused rx start trace sources from the csma and point-to-point
devices;

3) Remove the non-promiscuous sniffer helper code from the wifi-helper and
leave yans-wifi-phy hooked to the promisc sniffer;

4) Adding PromiscSniffer (tcpdump) functionality to the various net devices.

5) Changing the documented examples to use promiscuous sniffers as if someone
were doing tcpdump on a real net.

Changes queued for review/push in craigdo/ns-3-tracing


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.