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 1504] RUDP plugin doesn't work in Wireshark >= 0.99.3

Date: Mon, 2 Apr 2007 06:38:59 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1504


jeff.morriss@xxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME




------- Comment #3 from jeff.morriss@xxxxxxxxxxx  2007-04-02 06:38 GMT -------
Thanks for providing a dump file, that helps.  :-)

Unfortunately, RUDP does not have IANA-assigned UDP port numbers.  The RUDP
plugin used to listen on port 7000 (which is what is used by Cisco, apparently)
but this caused problems for other dissectors (AFS is mentioned in the code
change) so this was disabled:

http://anonsvn.wireshark.org/viewvc/viewvc.py/trunk/plugins/rudp/packet-rudp.c?r1=18197&r2=18861

Now RUDP has a preference as to what port it listens on and it defaults to 0
(no port).  So, to dissect RUDP traffic, you must set a UDP port number in the
RUDP plugin by going to Edit->Preferences->Protocols->RUDP and adding a port
number there (probably 7000).

The Right Way to fix this would be to make the RUDP plugin a real dissector and
make it heuristic (meaning it would check for RUDP on all UDP ports so it
"should" automatically detect RUDP).  But that's a project unto itself.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.