Hi,
"TCP ports vary from a
capture to another" is this comunicated by some
other protocol or are the ports configured
manually?
Brg
Anders
Hi,
the capture is from Ethereal. The octets contain the length of the
rest of the packet (i don't need decode this info, only next layers). TCP ports
vary from a capture to another. Do you suggest write a dissector? isn't there a
more direct (easy) solution?
Thanks,
Alonso.
"Anders Broman (AL/EAB)"
<anders.broman@xxxxxxxxxxxx> escribió:
Hi,
If
the output is from some sort of trace tool you could write a dissector which
could strip off those octets. Do they contain some meaningful information
?
Packet length?
Which TCP port(s) are used ?
Brg
Anders
Hi, i have captures of messages following next stack: Phy / Eth / IP /
Tcp / 2 octets / SCCP / RANAP ..., the problem is layer between TCP and SCCP,
consisting of two octets, an unrecognized format that makes impossible
decoding upper layers, which are known for Ethereal.
Is there any way to configure an : ignore these two octets an continue
decoding from there', or something similar to avoid this 'layer'?
Maybe some kind of output manipulation to overwrite these octets with
some dummy, but known, header like M3UA...?
I would thank any idea, i'm new in Ethereal.
Alonso
LLama Gratis a cualquier PC del
Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
_______________________________________________
Ethereal-users mailing
list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
LLama Gratis a cualquier PC del
Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users