10.03.2013 Views

Sniffer® Portable Professional User's Guide - NetScout

Sniffer® Portable Professional User's Guide - NetScout

Sniffer® Portable Professional User's Guide - NetScout

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 8<br />

Using Protocol Forcing<br />

You can define up to four<br />

rules. Checked rules are<br />

enabled and applied to<br />

decoded data.<br />

198 Sniffer <strong>Portable</strong> <strong>Professional</strong><br />

Protocol forcing is useful when capturing frames that use a mixture of<br />

standard and non-standard (for example, proprietary) protocols that the<br />

Sniffer <strong>Portable</strong> <strong>Professional</strong> might not otherwise be able to decode. For<br />

example, in some situations, networks may include standard IP data<br />

within a proprietary lower layer packet format unknown to the analyzer.<br />

Protocol forcing essentially lets you tell the analyzer “if you see this<br />

condition, skip this many bytes (to where the standard data is), then<br />

apply this protocol interpreter.”<br />

You specify protocol forcing rules in the Protocol Forcing tab of the<br />

Options dialog box, displayed by selecting the Options command from<br />

the analyzer's Tools menu (sample shown in Figure 8-17).<br />

Use the drop-down list to specify the protocol that should<br />

be used as the “force from” protocol. When the analyzer<br />

encounters the condition specified here, it will skip the<br />

number of bytes specified in the Skip x bytes field and<br />

apply the protocol interpreter specified in the Then field.<br />

Figure 8-17. Defining Protocol Forcing Rules<br />

Specify the number of<br />

bytes to skip once the “If”<br />

condition is detected.<br />

Use the drop-down list to<br />

specify the protocol that<br />

should be used as the<br />

“force to” protocol (that is,<br />

the protocol to be<br />

expected at the offset you<br />

specified in the Skip x<br />

bytes field).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!