Ethereal-dev: [Ethereal-dev] tethereal tree expansion

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

From: PC Drew <drewpc@xxxxxxxxxxxxxxx>
Date: Sat, 28 Sep 2002 21:51:51 -0600
Okay, so I finally took a stab at fixing a problem that has annoyed me for quite some time. It seems I'm not the only one too (task number 33 on the wish list)!! I've attached part 1 of my solution to allow people to specify which protocols they want expanded when using tethereal, instead the "all or none" option which is there currently. Here's the syntax as I've implemented it now:

$ tethereal -e "[+]proto[+]"

Where "proto" is the name of the protocol you want expanded. The combination of options work like this:

-e "proto" -> expand only that protocol
-e "+proto" -> expand all protocols up to and including that protocol
-e "proto+" -> expand all protocols including and after that protocol

So, if you say "+ip", this is an example of how it would look for an HTTP packet:

Frame 1 (680 on wire, 680 captured)
   Arrival Time: Sep 28, 2002 21:46:17.587007000
   Time delta from previous packet: 0.000000000 seconds
   Time relative to first packet: 0.000000000 seconds
   Frame Number: 1
   Packet Length: 680 bytes
   Capture Length: 680 bytes
Ethernet II
   Destination: 00:04:5a:23:27:37 (00:04:5a:23:27:37)
   Source: 00:02:3f:34:3e:f6 (00:02:3f:34:3e:f6)
   Type: IP (0x0800)
Internet Protocol, Src Addr: 10.0.0.102 (10.0.0.102), Dst Addr: 63.238.77.237 (63.238.77.237)
   Version: 4
   Header length: 20 bytes
   Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
   Total Length: 666
   Identification: 0xc630
   Flags: 0x04
   Fragment offset: 0
   Time to live: 64
   Protocol: TCP (0x06)
   Header checksum: 0xd9ec (correct)
   Source: 10.0.0.102 (10.0.0.102)
   Destination: 63.238.77.237 (63.238.77.237)
Transmission Control Protocol, Src Port: 38338 (38338), Dst Port: 80 (80), Seq: 993942208, Ack: 1554448627, Len: 614
Hypertext Transfer Protocol

Right now, you can only specify one protocol at a time. Depending on what kind of reaction I get from the list, I may or may not implement a multi-protocol version, where you could specify a comma seperated list of protocols in the same manner as above.

I've attached a patch for people to check it out...lemme know what ya think.

--
PC Drew
Manager, Client Services

IBSN
12600 W. Cedar Drive, Suite 100
Lakewood, CO 80228

Email: drewpc@xxxxxxxxxxxxxxx
Phone: 303-984-4727
Cell: 720-841-4543
Fax: 303-984-4730

Attachment: expand_tree.patch
Description: Binary data