Hello Yang,
I have attempted to test Npcap 0.04 on my primary Windows 8.1 machine.
After uninstalling any previous WinPCap or Npcap I rebooted and then
successfully installed Npcap 0.04.
The Npcap Loopback Adapter shows up in the list from the Device Manager's
Network adapter.
The good ne
Hello Yang,
With Npcap 0.04-r3 the Npcap Loopback Adapter is again visible and usable as a
sniffable interface to Wireshark. [😊]
I hope to do more extensive testing later today or tomorrow (especially
regarding throughput and packet drops).
I have a question regarding the encapsulation type
Hello Michael,
Absolutely amazing how much effort you must have put into your "Journey of a
thousand miles". But it looks like we have a regression with regards to
commit 38b6f306: Refactor NCP Python data so that INFO column can be generated
on the fly.
Not all of info_string_t objects def
> On Wednesday, December 2, 2015 14:09
> On Dec 2, 2015, at 8:11 AM, Evan Huus wrote:
> > My current hypothesis is commit 74541a9596eead6647c592de9aa46797c2dffa84
> > but I don't have any files to test with locally.
>
> So that one looks as if it might affect *startup* time but not *file loading
My tests point to v2.1.0rc0-228-g4f39c60 on master as the big one in terms of
capture file load performance hit, but there is an earlier commit that appears
to consistently added one second to the load of my test file versus head on
master-2.0. I'll start bisect for this smaller one shortly.
On Wednesday, March 16, 2016 20:55 Gerald Combs wrote:
> The uploads were getting truncated. The issue should be fixed now.
Thanks sir.
Verified as fixed. Newest package "Wireshark 2.1.0-2369-ge37275b
Intel 64.dmg" opened and installed fine.
Best regards.
Jim Y.
Hello,
Anybody else having any issues installing the latest OS X buildbot images?
This morning I downloaded the latest development package "Wireshark
2.1.0-2365-g597b227 Intel 64.dmg" to install on a few Mac-minis. After
double-clicking on the dmg file I was presented with a Warning dialog th
>> Buildslave for this Build: osx-10.6-x64
>>
>> Build Reason: The SingleBranchScheduler scheduler named 'Gerrit' triggered
>> this build
>> Build Source Stamp: [branch master] b84637b4f6a1f3f910b97c21264ff6132a9c19c4
>> Blamelist: Jörg Mayer
>>
>> BUILD FAILED: failed compile_1
>
>Not me :-)
>
On Tue, Feb 13, 2018 at 11:52:56AM +0530, Aditya Tyagi wrote:
> Please find attached screenshot when i trying to configure wireshark on
> rhel 7..even when it is configured it gives error while that this qt
> function is protected or something...
The error looks to be ...
> Checking whether Qt
Trying to chase down some intermittent crashes on Windows 8.1 when running
with recent automated build packages.
Could someone confirm the actual Windows.pdb installed in
the wireshark-pdb-win64-2.9.0-*.zip files available from the automated dev
build site ( https://www.wireshark.org/download/auto
Hello Ben,
Similar to the way that IDBs must be preceded by any EPBs that reference
it, Apple's tcpdump can augment pcpang files with proprietary process
information blocks. EPBs are augmented with proprietary options that can
reference any preceding process information blocks.
Unfortunately App
On Wed, Jun 13, 2018 at 6:06 PM, Gerald Combs wrote:
>
> Does anyone know what we did between July 2012 and 2013 that would affect
> SLOCCount?
>
Using git bisect and defining "bad" as lower SLOC and "good" as higher SLOC
this is what I came up with:
$ git bisect start 6d7a3a8ceef0fbcf3fc0ced1b
Hello,
I almost exclusively run development versions of Wireshark when doing my
day to day troubleshooting tasks and I typically (but not always) do the
analysis on a macOS system.
I've stumbled into some weird UI glitches when running with very recent
buildbot development releases on my macOS sy
a., 29. Juni 2019 um 07:47 Uhr schrieb Jaap Keuter <
> jaap.keu...@xs4all.nl>:
>
>> Hi Jim,
>>
>> Any dark mode stuff going on?
>>
>> Thanks,
>> Jaap
>>
>> On 28 Jun 2019, at 18:11, Jim Young wrote:
>>
>> Hello,
>>
>> I a
On Sat, Jun 29, 2019 at 10:44 AM Jim Young wrote:
>
> This transparent context menu issue can be triggered in the file list on
> the Wireshark UI Welcom page.
>
> Looks like might be something specific to Qt 5.12.4.
>
Building the macOS UI against the latest Qt 5.13.0 and pr
Submitted https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15888 for the
context menu issue.
On Sun, Jun 30, 2019 at 10:08 PM Jim Young wrote:
>
> Building the macOS UI against the latest Qt 5.13.0 and prior Qt 5.12.3
> does not expose the transparent context menu issue. The macO
The macOS buildbot has been down since Nov 04 17:31.
https://buildbot.wireshark.org/wireshark-master/builders/macOS%2010.14%20x64
Is this intentional?
Thanks,
Jim Y.
___
Sent via:Wireshark-dev mailing list
Archives:
eshark's console whenever the
RTP Stream Analysis dialog is opened. These are two of several messages that
first appeared as a result of the refactoring introduced with
d5d815189d. All but
these two messages were subsequently resolved with
We've had failing macOS builds since the commit set from
https://gitlab.com/wireshark/wireshark/-/merge_requests/2136 was
applied.
First failing build:
https://buildbot.wireshark.org/wireshark-master/builders/macOS%2010.14%20x64/builds/1753
The last successful automated build for macOS was with
Hello Martin,
On Wed, May 19, 2021 at 7:09 AM Martin Mathieson via Wireshark-dev
wrote:
> ... when I try to clone it starts to go through the stages (i.e.
> counting/compressing/ receiving objects/resolving objects) I am told
> 'Connection to gitlab.com closed by remote host' ...
>
> Any ideas?
Hello Gerald,
On Thu, May 27, 2021 at 4:20 PM Martin Mathieson via Wireshark-dev
wrote:
>
> I am using VirtualBox..
After discussing the conditions with Martin, I tried unsuccessfully to
replicate the issue with a macOS VM running on Vmware Fusion with NAT.
I had initially tried using an https
Looking at a few of the undefined references with `git grep` it looks
like they are defined in epan/dissectors/packet-ncp.inc.
> % git grep ncp_echo_server
> epan/dissectors/packet-ncp-int.h:extern gboolean ncp_echo_server;
> epan/dissectors/packet-ncp.c:
> &
Hello Ateeth,
Are you sure you are not picking up a wireshark found in your $PATH as opposed
to the one in the development directory?
If you are trying to launch it while from your development folder then you
would launch it as ./wireshark (or sudo ./wireshark)
You also didn't mention which sp
Hey Michael,
Are there are any mnemonic option letters available?
Would use of long options be the appropriate solution in this case?
A few years ago I had a need for some additional options for a hacked up
version of tshark. Because there were not enough sensible option letters
available I e
From: Yang Luo Hi list,
>
>In order not to diverge with WinPcap interfaces, I have made a "WinPcap
>Mode" for Npcap, it uses the same system32 directory to put DLLs and has
>the same "npf" service and driver name. So it can be directly used in
>Wireshark without any patch.
Hello Yang,
I've been t
Hello Yang,
From: Yang Luo Date: Thursday, July 16, 2015 8:44 PM
>When your Cisco AnyConnect VPN Client stops working, how about your other
>Internect connections? There seems to be a bug in Npcap that will lead to
>the whole network failure.
>
In my case the (Wifi) network interface was stil
Hello Yang,
Two comments on all for 2nd test.
1 - Should the name of the newer package reflect that this is a different Npcap
package from the 1st one? The 2nd package is named identical to the 1st one of
npcap-nmap-0.01.exe. The newly downloaded one was saved by the browser as
npcap-nmap-0.
Hello Yang,
Similar to Tyson I had quite a bit of difficulty in getting Npcap 0.01.r02
installed and running.
Looking back at a Device Manager Screen Shot I took PRIOR to attempting to
install the 2nd version of Npcap yesterday I realized that I had an orphaned
"Microsoft LM-TEST Loopback Adap
Hello Yang,
From: Yang Luo , Date: Wednesday, July 22, 2015 11:12
PM
>I tested it against Win10 10240 x64 (French and Chinese), try installer
>at:
>https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-0.02-r2.exe
I've continued to test the various Npcap versions in WinPcap API mode on
Wind
From: wireshark-dev-boun...@wireshark.org
on behalf of Pascal Quantin
Sent: Monday, August 3, 2015 12:48
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Npcap 0.03 call for test
Hello Yang,
Since my last comments I've been (quietly) tes
Hello Yang,
While testing Npcap 0.03-r3 I stumbled into one reproducible issue but I
also triggered a crash (which I am currently unable to reproduce).
The reproducible issue involves capturing on the Npcap loopback interface and
then starting a cmd shell and pinging the loopback address as follo
Hello Yang,
I've been doing some testing with Npcap 0.03-r4.
Current observations:
I can confirm the ping -t -l 65500 127.0.0.1 command is now working as expected.
Also I have been unable to trigger any BSODs.
On my primary Windows 8.1 system I can easily reproduce the installation stall
Hello Yang,
After installing 0.03-r5 on my Windows 8.1 system I too am see a BSOD when
starting Wireshark, tshark or dumpcap.
Like Pascal's Bugcheck Analysis my crashes are also reporting bug check string:
IRQL_NOT_LESS_OR_EQUAL (a)
2: kd> .symfix C:\Symbols
2: kd> .reload
Loading Kernel S
Hello Yang,
I installed npcap-nmap-0.03-r6.exe but am still getting the
IRQL_NOT_LESS_OR_EQUAL (a) BSoD on my Windows 8.1. system immediately when I
start Wireshark.
I went back retested 0.03-r3, 0.03-r4 and 0.03-r5 to confirm that its only r5
and r6 that trigger the immediate BSoD on my sys
will need to submit a bug report? I can if
someone else doesn't beat me to it.
Regards,
Jim Young
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
ing only 8-bit ones. Can anyone
who's
> having problems see if this helps?
It looks like Version 0.99.6-SVN-20687 (SVN Rev 20687) fixed the
problem
with "invisable" Wireshark icons with *.pcap email attachments in
Novell
Groupwise.
Thanks,
Jim Young
__
gger" packets would be
recoverable if dumpcap simply forwarded the pcap data
stream onto tshark and/or wireshark using a pipeline.
FWIW:
I really like dumpcap's lean and mean design. When I
really need to fetch the most data with as little packet
drops as possible I use dumpcap (o
s in advance for any help in this matter.
Jim Young
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Hello Steve,
>>> Stephen Fisher <[EMAIL PROTECTED]> 11/24/07 2:28 AM >>>
> On Sat, Nov 24, 2007 at 01:09:47AM -0500, Jim Young wrote:
>> Can a bug report that is initially created as public be later marked
>> as private (by the bug submitter)?
>
>
>>> Stephen Fisher <[EMAIL PROTECTED]> 11/24/07 3:16 AM >>>
> Done. Now anything you put in the bug, including files, cannot be seen
> outside of the core developers. In fact, if they list bugs it won't
> show up and if they type in that bug number, it will give an access
> denied message. Now l
be reviewed and/or modified by clicking on the "Details" link for the
patch under the "Actions" column within the table of Attachment(s).
I hope you find this useful.
Jim Young
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
ocol?
> Can someone suggest something ?
> Regards,
> Sameer
Use "bootp". DHCP is (more or less) a superset of BOOTP.
The parsing of the dhcp components is done within the bootp
dissector.
Hope this helps.
Jim Young
___
Wireshark-d
play filter "macros".
The "macro" could be used by the user to augment the filter
rules with new (preferred) names for complex filters pieces.
That way instead of cutting and pasting snippets of complex
filters, one could reference them via their simple "macro"
na
he last packet"
toolbar buttons to accomplish same.
Best regards,
Jim Young
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Hello,
Windows Buildbot Build #3732 failed to complete due to a problem apparently
while building the "portableapps package".
Subsequent attempts by the Windows buildbot to build now fails svn checkout
with:
> exceptions.OSError: [Errno 13] Permission denied:
> 'C:\\buildbot\\wireshark\\tru
standard cli tools (sed?) that something similar could be put together.
Perhaps something like this be worth pursuing? (Or perhaps a simple
compiler flag exists for accomplishing same!)
Jim Young
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Hello Ulf,
>>> Ulf Lamping <[EMAIL PROTECTED]> 2008-04-05 16:16 >>>
> Having less messages at higher severity levels is a lot easier to work
> with the expert infos, compared to dumped with all kinds of stuff.
>
> As I wouldn't call myself a real TCP expert, what do others think?
The logic/reas
Hello Ulf,
> Ulf Lamping <[EMAIL PROTECTED]> 2008-04-05 18:05 >>>
>>> Jim Young schrieb:
>>> I started thinking about the need for an expert info configuration
>>> framework to allow the Wireshark user to tune the expert system to
>>> t
Hello Sake,
>>> Sake Blok <[EMAIL PROTECTED]> 2008-04-06 15:13 >>>
> I have no intention to create a war... now that we have met in person ;-)
I wish to second that sentiment. It was truly a pleasure and an honor
to meet you all!
> Regarding the enhancement request for a configurable severit
Hello Ulf,
>>> Ulf Lamping <[EMAIL PROTECTED]> 2008-04-17 04:35 >>>
>> Guy Harris schrieb:
>> Stig Bjørlykke wrote:
>>
>>> On startup I get this warning:
>>> (wireshark:26750): Gtk-CRITICAL **: gtk_container_foreach:
assertion
>>> `GTK_IS_CONTAINER (container)' failed
>>>
>> That appears t
Hello Ulf,
>>> Ulf Lamping <[EMAIL PROTECTED]> 2008-04-19 10:08 >>>
> Stig Bjørlykke schrieb:
>> (wireshark:19088): GLib-GObject-CRITICAL **: g_object_get_data:
>> assertion `G_IS_OBJECT (object)' failed
>
> I just don't see those errors on XP!
>
> ...and again that lovely little beast called G
Hello,
>>> Jaap Keuter <[EMAIL PROTECTED]> 10/08/08 12:55 PM >>>
> Hi,
>
> A clear comment line explaining the hack may help here...
>
> Thanx,
> Jaap
>
>>Greg Morris wrote:
>> Stig,
>>
>> Well that white space was there on purpose...
>>
>> { 15, "Read Class Definition " },
Years ago I
Hello,
It looks like the Windows-XP-x86 buildbot might be stalled.
The last successful build available from the buildbot
download site is listed as:
wireshark-win32-1.1.2-SVN-26897.exe, 01-Dec-2008 15:43
It looks as through the buildbot's waterfall view for the
"Windows-XP-x86" implies that
Hello,
The Windows buildbot, after successful compile and
packaging, is currently unable to complete all the tasks.
It's generally (but not always) failing in step 13 the 'rsync'
task.
See:
http://buildbot.wireshark.org/trunk/builders/Windows-XP-x86
Thanks,
Jim Y.
_
>>> 01/08/09 9:23 AM >>>
> The Buildbot has detected a new failure of OSX-10.5-ppc on Wireshark
> (development).
> Full details are available at:
> http://buildbot.wireshark.org/trunk/builders/OSX-10.5-ppc/builds/309
>
> Buildbot URL: http://buildbot.wireshark.org/trunk/
>
> Buildslave for t
>>> Stig Bjørlykke 02/15/09 7:01 PM >>>
>> 2009/2/16 Guy Harris :
>> That was probably in the code to copy ipmap.html; it wasn't
checking
>> whether the open of the source or destination ipmap.html file
succeeded.
>
> Yes. It works as expected with your latest commit.
With Windows Buildbot Vers
Hello Beth,
>>> Beth 09/18/09 10:58 AM >>>
> As I try to debug my Lua issues, it would be really helpful if I could view
> stdout while running the wireshark GUI. Then I can print debug info with a
> simple printf instead of having to add gratuitous items to the display tree.
>
> I thought all
Hello,
Since SVN 30390 [1] the Windows buildbot has failed to compile.
If one reverts that change (which itself was a reversion of a patch
to get the windows buildbot working again ), it will be found
that the changes submitted with SVN 30392 [2] will also fail to
compile under windows.
[1] - h
Hello Jeff,
>> [2] - http://anonsvn.wireshark.org/viewvc?view=rev&revision=30392
>
> Oops. I haven't been able to build Windows in a while. Can you send me
> the errors you get?
I'm sorry. I must have misread my error output when I first tried
to compile after doing an "svn update" earlie
Hello Lars/Anders,
>> [] On Behalf Of RUOFF LARS
>> Sent: den 14 oktober 2009 15:48
>>
>> I have attached a patch for dlg-utils.c which removes the transient
>> thing for WIN32 only.
> "Anders Broman" <> 10/14/2009 11:03 AM >>>
> Hi,
> I've done some quick tests with your patch closing wireshark
> Guy Harris 3/22/2010 4:48 PM >>>
>> On Mar 22, 2010, at 1:40 PM, Maynard, Chris wrote:
>>
>> It’s particularly annoying if you’ve got a large capture file
>> opened and only wanted to check the capture options
>> used, not actually start a new capture.
>In any case, that seems pretty bogus, so
>Stephen Fisher 02/16/11 11:57 AM >>>
>> . On Tue, Feb 15, 2011 at 07:57:09PM +0100, Andreas wrote:
>> This might be easy. If all .obj files that are linked in the directory
>> epan you can do
>>
>>cd epan
>>dumpbin /symbols *.obj | find /v "UNDEF" | find "External"
> sfisher@shadow:/us
>Chris Maynard <> 5/20/2011 10:25 AM
> To me, if it doesn't work without -n and -t, then it makes it that much more
> user-friendly to automatically use pcapng and threads whenever multiple
> interfaces are specified.
+1 to automagically do -n -t when more than one
interface is specified.
Here's
Hello Japp,
>> This problem is now addressed through bug 7744. A fix was committed with
>> revision 45058, although this could not be tested on OS X. Anyone
>> willing to drop some pcap files onto an Wireshark main window on OS X?
>
>I compiled a GTK2/X11 Wireshark from trunk on OsX, but DnD is no
Hello,
The most recent OSX built version is SVN 45082
according to the buildbot builders' page at:
http://buildbot.wireshark.org/trunk/builders
But the OSX buildbot images are NOT getting copied
over to the OSX automated download page at:
http://www.wireshark.org/download/automated/osx/
The O
Hello Martin,
On 11/20/12 9:12 AM, "Martin Mathieson"
wrote:
>Alex, do you still see crashes when switching graph type?
>Martin
I'm not trying to answer for Alex, but I also saw the
crashes in the tcp graphs before your most recent patches.
I haven't crashed since your last patches. ;-)
But I
Hello Edwin,
On 3/8/13 7:49 AM, "Edwin Groothuis" wrote:
>Recently I submitted a patch to perform rectangular zooms into the
>tcpgraph windows (Statistics -> TCP Stream Graph -> tcpgraph). It got
>committed to trunk for release into 1.10 and I myself backported it to
>1.8 for our internal Wiresha
Hello Japp,
On 3/21/13 2:57 AM, "Jaap Keuter" wrote:
>Hi all,
>
>As a side note, the bug is still 'in progress' because we haven't heard
>of an OS
>X test yet. If someone could confirm, in the bug comments, that the
>current
>Interface List dialog works properly on OS X we can close the matter.
I click on the
toolbar icon for "List the available capture interfaces..." the
"Please tell Microsoft about this problem" dialog is presented.
I can still successfully "Start" a capture via the interface stored
in my preferences.
FWIW I do NOT see the problem with build
't directly resolve bug
#1181
it can help suppress bug #1181 in certain scenarios. I'd vote for
applying
your patch.
I hope someone finds this info helpful.
Jim Young
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
70 matches
Mail list logo
