On Fri, 9 Feb 2001 puimak@xxxxxxxxxxxxxx wrote: > However, when I try to read some wsp/wtp snoop file, it just show the > protocol as UDP. When > I use other utility, it can decode the data as wtp-Invoke, wtp-ack, etc. Ethereal won't naturally detect these packets as WAP as neither the source nor destination ports are in the 9200-9203 range. However, if you right-click on packet 6 and select "Decode as..." from the pop-up menu, then click the transport tab and select "destination (49200)". Finally select WTP as the protocol in the right-hand list of possible dissectors. This will apply the WTP dissector to the remaining packets in the capture. I'll need to have a look at this one though - I haven't seen this port being used for WAP traffic before... Thanks for the capture though, there's some new headers in there I haven't implemented the decoding for yet so I'll work on those :) Cheers, Neil ------------------------------------------------------------------------------- Neil Hunter Tel: +44 (0)113 207 6073 Internet Systems Developer Fax: +44 (0)113 234 6065 Energis Squared Mobile: +44 (0)7787 100 649 http://www.energis-squared.com/ --------------------------------------- This email is confidential and may be privileged. If you are not the named recipient please notify the sender immediately and do not disclose to another person or use it and take copies. If you receive this message in error please call the switchboard on + 44 (0)113 234 5100. -------------------------------------------------------------------------------
Powered by MHonArc 2.6.10