Hi,

I'll clean up the dissector source somewhat and add two port mappings.
They'll be on the IANA registered ports though, and I suggest you'll do 
the same, if possible. To convenience you I'll make them configurable 
through the preferences.
Hopefully I'll get it done later tonight.

Thanx,
Jaap

Filippo Margiotta wrote:
> Hi Jaap,
> now the mikey dissector is working as I was looking for.
> 
> I suggest you to add the two lines :
> 
>     dissector_add("udp.port", 4359, mikey_handle);
>     dissector_add("tcp.port", 4359, mikey_handle);
> 
> after the line
>     dissector_add_string("key_mgmt", "mikey", mikey_handle);
> 
> in the proto_reg_handoff_mikey() function as you suggested.
> 
> The port 4359 are ufficially assigned by IANA.
> 
> I cannot commit the changes because I haven't the right.
> Thanks again.
> Filippo
> 
> 
> 
> 2007/9/18, Filippo Margiotta < [EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>>:
> 
>     Hi Jaap,
>     tomorrow I will test your suggestion.
> 
>     Thank you very much!
>     Filippo
> 
> 
> 
>     2007/9/18, Jaap Keuter < [EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>>:
> 
>         Hi,
> 
>         Add this line to proto_reg_handoff_mikey() in
>         epan/dissectors/packet- mikey.c:
> 
>            dissector_add("udp.port", 2269, mikey_handle);
> 
>         as I assume you're using the IANA registered UDP port.
> 
>         Thanx,
>         Jaap
> 
>         Filippo Margiotta wrote:
>         >  Hi All,
>         >  I would like to use the mikey dissector in a different way it
>         is used now.
>         >  At the moment, a mikey packet is captured only as key-mgmt session
>         >  attributes in the SDP protocol.
>         >
>         >  Could somebody give me, please, some information about what to
>         modify in
>         >  the current implementation to have a mikey capture dissector
>         that can
>         >  directly parse an UDP datagram containing directly a mikey
>         message?
>         >
>         >  Thanks in advance,
>         >  Filippo
>         >
> 

_______________________________________________
Wireshark-dev mailing list
[email protected]
http://www.wireshark.org/mailman/listinfo/wireshark-dev

Reply via email to