ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 9138] Malformed NORM packet

Date: Wed, 18 Sep 2013 15:04:04 +0000

changed bug 9138

What Removed Added
Status UNCONFIRMED RESOLVED
Resolution --- FIXED

Comment # 12 on bug 9138 from
(In reply to comment #11)
> I applied the patch to packet-rmt-norm.c and it got rid of the CMD CC
> malformed packet error, although the packet size is still huge (2074 bytes)
> and filled primarily with zeros, once again making hundreds of Congestion
> Control subtrees.  Is that a problem with Wireshark or is that just a
> problem with the packet itself?

I'm not familiar with this protocol and I don't have any capture files
containing NORM traffic to look at, so it's hard to say for certain, but it
sounds to me like the packet itself is the problem and Wireshark is only doing
its best to interpret the data that's there.

If you can provide a small capture file, then someone can take a look.  You can
mark the capture file private if you want to limit viewers to Wireshark core
developers only.

In any case, I've committed the patch to the trunk in r52139 and scheduled it
to be back-ported to 1.10.3 and 1.8.11, so I'm closing this bug as fixed.


You are receiving this mail because:
  • You are watching all bug changes.