What Is ProtocolWorks? |
-
ProtocolWorks works in conjunction with ViewComm Async and ViewComm Ethernet analyzers to provide interactive design and test capabilities
for new protocols or modifications to existing protocols. ProtocolWorks was an add-on in Version 2.5x and 3.3 but is standard
at no additional cost in ViewComm Async II and Async Ethernet II protocol analyzers.
-
Having said that, if you are a user of version 3.3 (only), and want to leave your installation intact but add the functionality of
ProtocolWorks, you may order it as an add-on. To do this you will need to furnish us with your serial number (you will be getting a
new one once your software is upgraded).
If you wish to add ProtocolWorks functionality to more than one version 3.3 analyzer, you must purchase
one copy of ProtocolWorks for each. We no longer offer the Pro versions of the analyzers.
|
|
Who Needs It? |
- ProtocolWorks is ideal for protocol developers, RFC and Internet standards writers and reviewers who want to
"play in the sand" with new protocols.
- It is perfect for data communications hardware and software developers, product designers, application developers.
- ProtocolWorks is great for network and datacomm troubleshooters, and field service engineers and technicians who work
with proprietary protocols and want to upgrade their skillset.
- ProtocolWorks makes it easy to customize the columns and views presented by VCS Frame View displays. You can change
just about anything about the way the information about packets is displayed. This capability alone can save untold hours in
wading through information that you may not need or want, or that you simply want displayed a bit differently so you can find what
you want. Sometimes it's the trees you need to see instead of or in addition to the forest.
- Drastically reduce the amount of time you would otherwise spend sifting through raw data, looking up
control code values and hex data. In a word, change the way you work.
- You can organize data the way you want it. If an existing VCS decode doesn't suit you, change it. If you want
pieces of a packet presented in Frame View differently than VCS provides, change it.
- Are you a trainer, teaching protocols? First, you need VCS, and then you can definetly simplify the way protocols are
displayed for beginning students, then add detail for more advanced classes. You can change it.
- Do you know the protocol but spend too much time diagnosing "gotcha" cases? Change it. Add cases, detect
additional fields or interpret header fields differently.
|
|
How Does It Work? |
How is this possible?
Greenleaf ViewComm comes with a variety of decode (script language) files that tells VCS how to
decode and present in Frame View the details of protocols on the line. In the case of ViewComm Ethernet, the decoders
work on the Ethernet family of protocols and include TCP/IP, IPX/SPX, Frame Relay, and other common protocols. Typically
there is a top level decode file, e.g. IP.DEC, which then loads and branches to recurse all of the various protocols encountered.
|
|
At the right is one column in the Summary pane of VCS Frame View. The decode for the protocol (it happens to be Async PPP) shows whether Address Control information is present in each packet. A decode file tells VCS to show this as the word "Present." Let's imagine that we want to change it to read "Here." |
 |
|
At the right is a segment of a decode page open in a text editor showing the word "Present" |
 |
|
Change it to "Here" and save the decode file. |
 |
|
In Frame View, ProtocolWorks adds the button shown at the right. Click it to reload the decoders in use -- while the decoder is still open in the text editor. |
 |
|
...And voila! The Summary view changes to match your change. |
 |
|
Let's shift our focus to the Decode Pane in Frame View. This shows an Async PPP packet in which the protocol we're interested in is the Link Control Protocol that negotiates options between a dial-up station and an ISP or other system. Let's change "Configure Request" to "Request for Configuration." |
 |
|
The decode script for PPP contains the line highlighted below. If the value of a certain portion of the frame header is a 1, the LCP packet type is "Configure Request." |
|
 |
|
Change it. |
|
 |
|
Click the Reload Decoders button.. |
|
|
Now the type is displayed according to your change. The possibilities are endless. Suppose there is "one more"
type of LCP packet you want to add for a client and test. Just add a line beneath those in this table, specify the Value
and what you want displayed. Now you've changed a protocol! Neat, huh? |
 |
