|
One way could be to disable ICQ protocol
if you are not interested in ICQ-protocol at all and/or if you think that those
packets are not ICQ-packets.
In Ethereal you can do this from memu item
Analyze/Enabled Protocols ...
The protocol will be disabled permanently until you
enable it again (even in Tethereal) if you do Save after you have unchecked
ICQ in the list of enabled protocols.
Another alternative is to edit the
diabled_protos file manually. Mine disabled_protos file is in C:/Documents and
Settings/Martin/Application Data/Ethereal.
The file should list the shortnames for the
protocols that you want to disable, e.g.:
dlsw
icq rx From what I understand there is probably another
protocol that uses the same port number as the ICQ-dissector is registering (UDP
port 4000)
either as source port or destination port.
Maybe Ethereal will dissect the packet with another dissector (based on the other source port or destination port) or based on heuristics if you disable ICQ protocol.
If you know the protocol of the packet and it is
implemented in Ethereal it may be possible to use "Analyze/Decode As..." in
Ethereal, or to use
the -d option with Tethereal.
I normally disable several protocols that I'm not
interested in right after installing Ethereal: Protocols that I know
that
are normally not used in the networks
I'm analyzing, especially when I know
the dissector is registering with a port number
that are used by several different
protocols.
It may also be possible to improve the ICQ
dissector in a way so that it will only accept packets
that really looks like ICQ-packets, if there
is some specific things that always should
be valid for ICQ packets. I don't know so much about ICQ - so I don't know
if that would be good
to do.
Best regards,
Martin
Niklas Abrahamsson (KI/EAB) wrote:
|
Powered by MHonArc 2.6.10