Wireshark 1.1.1 is now available. This is a development release,
intended to be used for testing new features. The latest stable release
of Wireshark is 1.0.3. Installers for Windows, OS X, and source code can
be downloaded immediately from
http://www.wireshark.org/download/win32/wireshark-win32-1
On 9. okt.. 2008, at 19.33, Gerald Combs wrote:
> I've added a script to update it every Sunday.
Great!
I was thinking about a "make-a-new-release" script where we update the
manuf and services files, bump versions in configure.in, config.nmake,
debian/changelog, docbook/user-guide.xml, docb
What's the take on using exception handling in a dissector?
I'd like to do a transfer syntax detection in packet-dcm, and the most
appealing way would be to try the three options in a try {} clause.
Apart from the TCP dissector, I've seen exception handling in other
places. So it it o.k to use
> > Hmm, did I miss a commit or did you just update the (normally
> > generated)
> > manuf file directly?
>
>
> Do we update the manuf file any other way than running the make-manuf
> and commit the new generated file? I haven't seen this file
> automatically updated when we make a release
I noticed on Google's main page today that Google is celebrating their
10th birthday. From their page, they provide a link to "try a search
from our early days". ... so I did. Of course the Wireshark project was
called Ethereal back then so that's what I searched for. A few clicks
later and I en
Stig Bjørlykke wrote:
> Do we update the manuf file any other way than running the make-manuf
> and commit the new generated file? I haven't seen this file
> automatically updated when we make a release. Maybe we should? It
> has been some months since it has been updated...
I've added a
Hi,
Wow, 36 monitor ports. All connected on one platform? Impressive.
I'm not sure what insight I can give you on the dropped packets statitics. What
I can do is advice you to capture with dumpcap i.s.o. tshark. The thing is
tshark spawns dumpcap to do the capture, but then does the dissection.
Jaap,
Thanks for looking into this.
> When 36 ethernet ports can cause packet drops on the capture
> interface then probably the monitor port will be dropping
> packets too. How are you going to account for that?
There is no single monitor port. The 36 ports are the monitor ports with 36
instan
Hi Didier,
Good advice! Thanks.
Comment inline,
David
* -Message d'origine-
* De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de didier
* Envoyé : mercredi 8 octobre 2008 19:26
* À : Developer support list for Wireshark
* Objet : Re: [Wireshark-
