Sorry I'm replying to this so late. The main problem here is that the
packets are coming from the default RADIUS port, which also happens to be
the default Diameter port until IANA assigns a new one.
Once Diameter has it's own port, this should only happen when RPC again
tries to squat a well known port.
But, at least the dissector was smart enough to barf on the packet w/o core
dumping :)
-Dave
On Tuesday, 24 Sep 2002, Ulf Lamping wrote:
> Hi List!
>
> A minor problem I have noticed:
>
> Displaying a trace I have made, with some DCE-RPC packets, but displayed as diameter packets.
>
> Some messages on the console:
>
> Diameter: Unable to find name for command code 0x00000000, Vendor "1207959552"!
> Diameter: Bad packet: Bad Flags(0x10) or Version(5)
> Diameter: Unable to find name for command code 0x00000000, Vendor "1207959552"!
> Diameter: Bad packet: Bad Flags(0x10) or Version(5)
> Diameter: Unable to find name for command code 0x00000000, Vendor "671088640"!
> Diameter: Bad packet: Bad Flags(0x10) or Version(5)
> Diameter: Unable to find name for command code 0x00000000, Vendor "671088640"!
> Diameter: Bad packet: Bad Flags(0x10) or Version(5)
>
> -The diameter dissector should not decode the corresponding packets as diameter packets, as they are using the ports 1812 (diameter) and 135 (rpc), and are really DCE-RPC packets.
> I have fixed this by setting the diameter port in the preferences to a different value (I'm not using diameter).
>
> -In the console comes a lot of messages like the ones above, which shouldn't be there I think.
>
> Regards ULFL
> ______________________________________________________________________________
> WEB.DE MyPage - Ohne Computerkenntnisse in nur 5 Minuten online! Alles
> inklusive! Kinderleicht! http://www.das.ist.aber.ne.lustige.sache.ms/
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
--
David Frascone
Falls don't kill people. It's the deceleration trauma.