Re: [Wireshark-dev] overriding dissector for port 8080

2014-04-04 Thread John Dill
Message: 4 Date: Thu, 03 Apr 2014 16:14:53 -0400 From: Jeff Morriss jeff.morriss...@gmail.com To: Developer support list for Wireshark wireshark-dev@wireshark.org Subject: Re: [Wireshark-dev] overriding dissector for port 8080 Message-ID: 533dc13d.8010...@gmail.com Content-Type: text/plain

Re: [Wireshark-dev] overriding dissector for port 8080

2014-04-04 Thread Hadriel Kaplan
On Apr 4, 2014, at 9:56 AM, John Dill john.d...@greenfieldeng.com wrote: I also noticed a disabled_protos.[ch], so maybe there is a feature to disable other protocols. Is there a feature that could be used to hide protocols I don't need in the Filter Expression (to reduce the list to

Re: [Wireshark-dev] overriding dissector for port 8080

2014-04-04 Thread John Dill
Message: 2 Date: Fri, 4 Apr 2014 10:19:52 -0400 From: Hadriel Kaplan hadriel.kap...@oracle.com To: Developer support list for Wireshark wireshark-dev@wireshark.org Subject: Re: [Wireshark-dev] overriding dissector for port 8080 Message-ID: d1433e77-410e-44ed-9cb6-2cd341618...@oracle.com Content

Re: [Wireshark-dev] overriding dissector for port 8080

2014-04-04 Thread Hadriel Kaplan
On Apr 4, 2014, at 10:43 AM, John Dill john.d...@greenfieldeng.com wrote: The Filter Expression dialog is the best place in Wireshark to locate the data elements they are looking for, so it was mentioned as a nice to have”. Oh well if it’s just the dialog, why not just disable the other

Re: [Wireshark-dev] overriding dissector for port 8080

2014-04-04 Thread John Dill
Message: 2 Date: Fri, 4 Apr 2014 10:59:18 -0400 From: Hadriel Kaplan hadriel.kap...@oracle.com To: Developer support list for Wireshark wireshark-dev@wireshark.org Subject: Re: [Wireshark-dev] overriding dissector for port 8080 Message-ID: 225ee544-6929-4484-a8c2-2260be860...@oracle.com Content

[Wireshark-dev] overriding dissector for port 8080

2014-04-03 Thread John Dill
I have network traffic that uses TCP port 8080 for sending non-http data (on a private network with its own custom application layer on top of TCP an UDP). Is there a recommendation for how to override or remove this dissector? I still have port 80 for http traffic. I can remove port 8080

Re: [Wireshark-dev] overriding dissector for port 8080

2014-04-03 Thread Alexis La Goutte
On Thu, Apr 3, 2014 at 4:26 PM, John Dill john.d...@greenfieldeng.com wrote: I have network traffic that uses TCP port 8080 for sending non-http data (on a private network with its own custom application layer on top of TCP an UDP). Is there a recommendation for how to override or remove this

Re: [Wireshark-dev] overriding dissector for port 8080

2014-04-03 Thread Jeff Morriss
On 04/03/14 10:26, John Dill wrote: I have network traffic that uses TCP port 8080 for sending non-http data (on a private network with its own custom application layer on top of TCP an UDP). Is there a recommendation for how to override or remove this dissector? I still have port 80 for http