[Wireshark-dev] please help
dear developers, I am new to Open source coding.I have a fair grip on c,libpcap library and some packet capturing and I am very interested in network analysis and I would love to contribute to Wireshark. Can anyone please tell me about where to start. Thanks in advance.And pardon me if the question is naive. sincerely, Kaushik ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] qtshark startup time ~1 minute just printing messages
On Tue, Sep 10, 2013 at 05:25:25PM -0700, Gerald Combs wrote: > I don't recall a lot of controversy when the splash screen + progress > bar was added in 2004. Why all the fuss now? Because this is the first time that I had time to conciously look at and think about it ;-> I've been hit by the bug for quite a while and only recently asked about the problem. Ciao Jörg -- Joerg Mayer We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] please help
Hello Kaushik, On Wed, Sep 11, 2013 at 01:00:35PM +0530, Ned Stark wrote: > I am new to Open source coding.I have a fair grip on c,libpcap library and > some packet capturing and I am very interested in network analysis and I > would love to contribute to Wireshark. Can anyone please tell me about > where to start. It really depends on that you want to do, the only common thing is to look at the WSDG (Wireshark Developers Guide) and the READMEs in doc/ and of course to compile Wireshark yourself. Once you are there you need to decide where to go next - enhance an existing protocol, add a new protocol, work on one of the GUIs etc. In case you you have only a rough idea of what you want to do, just ask again. > Thanks in advance.And pardon me if the question is naive. Don't worry, it isn't - feel free to continue asking! Ciao Jörg -- Joerg Mayer We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] please help
Ned Stark writes: > Can anyone please tell me about where to start. Once you've got a development environment set up (which the documentation that Joerg pointed to you should help you with), you're able to compile Wireshark and think you're ready to try making some changes, you might want to peruse the open bug list to see if there's something in there you might want to work on. https://bugs.wireshark.org/bugzilla/ ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] TCP/HTTP reassembly problems with IPv6?
Do we have reassembly problems with IPv6? I tried "wget http://ftp.uni-kl.de/CCC/29C3/ogg-audio-only/29c3-5077-en-ethics_in_security_research_ogg.ogg"; and there was no "200 OK" response, only "tcp segments". After I repeated the command as "wget -4 http://ftp.uni-kl.de/CCC/29C3/ogg-audio-only/29c3-5077-en-ethics_in_security_research_ogg.ogg"; I got a reassembled answer. Ciao Jörg PS: And I've reported to the webadmin that the content-type needs fixing :-/ -- Joerg Mayer We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] please help
Thank you Joerg and Christopher. As you have advised I have gone through the wireshark developer's guide and the Read-me. I got a basic idea about the functionality of wireshark and how dissectors are coded. I would like to first start by developing the existing dissectors.But I am confused about where to go.I would like to know more about working of the source code. I would be grateful if anyone suggests me some simple bugs to work on(even solved ones) so that I can learn more about the working of source code. thank you in advance. sincerely, kaushik On Wed, Sep 11, 2013 at 8:07 PM, Christopher Maynard < christopher.mayn...@gtech.com> wrote: > Ned Stark writes: > > > Can anyone please tell me about where to start. > > Once you've got a development environment set up (which the documentation > that Joerg pointed to you should help you with), you're able to compile > Wireshark and think you're ready to try making some changes, you might want > to peruse the open bug list to see if there's something in there you might > want to work on. > > https://bugs.wireshark.org/bugzilla/ > > > ___ > Sent via:Wireshark-dev mailing list > Archives:http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe > ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] patch development questions
I've used Wireshark for years but I'm brand new to Wireshark development. I have a few patches to dissector packet-afs that were given to me by a customer to submit on their behalf. I have the current Wireshark source and have my toolchain set up on a Centos6 box to build 1.6, 1.8, or 1.10 successfully. The patches were originally written against 1.6. I'm currently forward-porting them to master, but I have no way to build and test master patches in my current environment because the Centos repos do not in general have the latest preregs (for gtk3, pango, glib, etc) required to configure and build the current tip/master/trunk (whatever you all call the development branch). I do not want to get into downloading toolchain sources and maintaining dependencies manually; I'd much rather stick with packages if possible. My understanding from reading the developer docs is that I should open bug reports and attach my patches to the tickets. These patches should apply to the tip, not to a particular release. Do you ever make exceptions to this policy? That is, would you accept patches against 1.10? If not, I'll make a new vm with a Linux distro that's not so conservative in its repo policies. Is there a particular distro you would recommend for Wireshark development, or doesn't it matter much? My only requirements are the need to use a package manager (yum/apt/whatever) to automate my dependency checking, and that its repos be current enough to configure and build the latest Wireshark. Thanks, -- Mark Vitale mvit...@sinenomine.net signature.asc Description: Message signed with OpenPGP using GPGMail ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] patch development questions
On Wed, Sep 11, 2013 at 3:42 PM, Mark Vitale wrote: > I've used Wireshark for years but I'm brand new to Wireshark development. > Welcome :) My understanding from reading the developer docs is that I should open bug > reports and attach my patches > to the tickets. These patches should apply to the tip, not to a > particular release. Do you ever > make exceptions to this policy? That is, would you accept patches against > 1.10? > Only bug-fixes and security patches go into the stable branches, so patches that fall in those categories are welcome. Most of the time in those cases people provide a patch against trunk and then we backport it, though sometimes a backport is not possible for whatever reason. If not, I'll make a new vm with a Linux distro that's not so conservative > in its repo policies. > Is there a particular distro you would recommend for Wireshark > development, or doesn't it matter much? > My only requirements are the need to use a package manager > (yum/apt/whatever) to automate my > dependency checking, and that its repos be current enough to configure and > build the latest Wireshark. > Ubuntu seems to be a popular choice. Our buildbot runs 12.04 (the latest LTS release) to build trunk, so you shouldn't have any issues with that or any more recent version. As Anders says though, this is probably a moot point. Cheers, Evan ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] patch development questions
Mark Vitale skrev 2013-09-11 21:42: I've used Wireshark for years but I'm brand new to Wireshark development. I have a few patches to dissector packet-afs that were given to me by a customer to submit on their behalf. I have the current Wireshark source and have my toolchain set up on a Centos6 box to build 1.6, 1.8, or 1.10 successfully. The patches were originally written against 1.6. I'm currently forward-porting them to master, but I have no way to build and test master patches in my current environment because the Centos repos do not in general have the latest preregs (for gtk3, pango, glib, etc) required to configure and build the current tip/master/trunk (whatever you all call the development branch). I do not want to get into downloading toolchain sources and maintaining dependencies manually; I'd much rather stick with packages if possible. My understanding from reading the developer docs is that I should open bug reports and attach my patches to the tickets. These patches should apply to the tip, not to a particular release. Do you ever make exceptions to this policy? That is, would you accept patches against 1.10? If not, I'll make a new vm with a Linux distro that's not so conservative in its repo policies. Is there a particular distro you would recommend for Wireshark development, or doesn't it matter much? My only requirements are the need to use a package manager (yum/apt/whatever) to automate my dependency checking, and that its repos be current enough to configure and build the latest Wireshark. Thanks, -- Mark Vitale mvit...@sinenomine.net You should be able to build trunk on CentOS 6 ( unless GTK2 is to old) ./configure --with-gtk2 Otherwise you could attach patches for 1.10 in a bug report they might apply to trunk. Regards Anders ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] patch development questions
On Sep 11, 2013, at 3:52 PM, Anders Broman wrote: > You should be able to build trunk on CentOS 6 ( unless GTK2 is to old) > ./configure --with-gtk2 Thank you, that worked well for me. -- Mark Vitale mvit...@sinenomine.net signature.asc Description: Message signed with OpenPGP using GPGMail ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
