Wireshark-dev: Re: [Wireshark-dev] How does the wireshark identify the corresponding protocol a
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: "Yuming fang" <fangyuming.leo@xxxxxxxxx>
Date: Tue, 23 Dec 2008 17:09:42 +0800


2008/12/23 Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx>


On Tue, Dec 23, 2008 at 8:11 AM, Yuming fang <fangyuming.leo@xxxxxxxxx> wrote:

<snipped>

 
 
Yeah, I register the dissector for the LTE data with the "tcp.port" dissector table with the value 9999. And now I could get the LTE data from the 9999 port. Do I just add  my LTE code into the corresponding functions, such as the function of dissect_LET to parse the LTE date?  Could you give me some information about the APIs(in wireshark) which could display the LTE data headers as layers in wireshark?(I want to display these headers like layers)
 
Thank you very much!
 
Best wishes,
Yuming
 
 

Hi Yuming,

Which LTE data headers are you referring to?  I'm planning to check in my LTE MAC dissector tonight.  RLC is almost ready (hopefully early next year) and I have a PDCP dissector that I need to tidy up a little and add a couple more ROHC profiles to.
 
 
At present, I want to check the LTE MAC dissector. Could you give me some information about your solution of checking the code through wireshark?
 
 

Note that Wireshark already has support for several LTE signalling protocols (S1AP, X2AP, RRC, NAS), and and although they're not normally carried over TCP I'm sure we could allow them to be decoded over a configured TCP port.
 
 
I see some code about the RRC in wireshark. It seems we could not decode the LTE data directly because there is no LTE card. So I want to decode the LTE data through a configured TCP port(At present we use the port 9999 as a test.). But how could my LTE code be added into this dissector(tcp.port=9999) perfectly? Could you give me some suggestions?
 
Thank you!
 
Best wishes,
Yuming
 
 

Martin
 
 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe