[Scott Fringer <fringsm@xxxxxxxxxxxxxxxxx>]

Brian,
  Have you tried selecting the packet in question and choosing Decode
As... and selecting WSP there?  That should do what you're aksing.

Scott

Scott Fringer                              Shands Healthcare @ U.F.
Network Systems Analyst                        Gainesville, FL

On Fri, 12 Apr 2002, Rosenbaum, Brian wrote:

> I've noticed that when a WAP WSP Msg is sent on port 9201 that Ethereal
> decodes it, yet if the msg is sent on a different port, say 49200 that
> Ethereal does not go beyond the UDP layer.  Is there a way to get Ethereal
> to recognize this WAP msg even though it is not on port 9201 without
> modifying any source code?  I am running version 0.9.2.
>
> I've attached two files below.  sim_connect7.cap shows a WSP Connect msg
> being sent to a dest port 49200.  This msg is not decoded beyond the UDP
> layer.  sim_connect4.cap shows a WSP Connect being sent to port 9201 that is
> properly decoded up to the WSP layer.
>
> Thx
> Brian
>
>  <<sim_connect7.cap>>
>  <<sim_connect4.cap>>
>
>
>