Wireshark-dev 发自网易邮箱手机版 On 2015-09-02 14:38 ,
wireshark-dev-requ...@wireshark.org Wrote: Send Wireshark-dev mailing list
submissions to wireshark-dev@wireshark.org To subscribe or unsubscribe via the
World Wide Web, visit https://wireshark.org/mailman/listinfo/wireshark-dev or,
via email, send a message with subject or body 'help' to
wireshark-dev-requ...@wireshark.org You can reach the person managing the list
at wireshark-dev-ow...@wireshark.org When replying, please edit your Subject
line so it is more specific than "Re: Contents of Wireshark-dev digest..."
Today's Topics: 1. Re: Npcap 0.04 call for test (Pascal Quantin) 2. Re: Npcap
0.04 call for test (Yang Luo)
---------------------------------------------------------------------- Message:
1 Date: Tue, 1 Sep 2015 19:57:17 +0200 From: Pascal Quantin
<pascal.quan...@gmail.com> To: Developer support list for Wireshark
<wireshark-dev@wireshark.org> Subject: Re: [Wireshark-dev] Npcap 0.04 call for
test Message-ID:
<CAGka-80WOuxySPqWLQoFDMSX=glj3pdw1ff_rmnyjuuzyqe...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8" 2015-09-01 17:23 GMT+02:00 Pascal
Quantin <pascal.quan...@gmail.com>: > > > 2015-09-01 3:19 GMT+02:00 Yang Luo
<hslu...@gmail.com>: > >> Hi Pascal, >> >> Thanks for this bug. This bug is
because loopback flag in Npcap driver >> isn't set when the driver is paused
and restarted (occurs when system >> resumes from sleep). I have fixed it. >>
Try lastest installer at: >>
https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-0.04-r9.exe >> > > Hi
Yang, > > thanks for the updated driver. I just tested it on the Windows 7 x64
> laptop that was having BSoD beginning of August and I can happily tell you >
that: > - it does not crash anymore and WiFi is working fine with Npcap
installed > - loopback interface is still working after a suspend / resume > >
Thanks for your work and congratulation for your GSoC. I guess (hope?) it > was
considered as being successful :) > Hi Yang, a small glitch I just noticed: you
forgot to update the string used by Wireshark to get Ncap version (as seen in
About Wireshark dialog box:). It reports "Npcap version 0.04 (packet.dll
version 1.00), based on WinPcap version 4.1.3 (packet.dll version 4.1.0.3001),
based on libpcap version 1.0 branch 1_0_rel0b (20091008)". Pascal. > Pascal. >
> >> >> >> Cheers, >> Yang >> >> >> On Fri, Aug 28, 2015 at 4:17 AM, Pascal
Quantin <pascal.quan...@gmail.com >> > wrote: >> >>> >>> 2015-08-25 12:00
GMT+02:00 Yang Luo <hslu...@gmail.com>: >>> >>>> Hi Guy, >>>> >>>> Now
PCAP_IF_LOOPBACK flag in pcap_if_t struct will be set for "Npcap >>>> Loopback
Adapter" both for DLT_NULL mode and Fake Ethernet mode. >>>> See Npcap 0.04 r8
at: >>>> https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-0.04-r8.exe
>>>> >>>> Cheers, >>>> Yang >>>> >>> >>> Hi Yang, >>> >>> I noticed an issue
when running Npcap 0.4r8 with DLT_NULL option on my >>> Windows 10 x64 host.
After putting my laptop in standby mode and resuming >>> my session, when
launching Wireshark the Npcap loopback interface is no >>> more working as
expected: >>> - the capture is no more done with Null/Loopback encapsulation
type, but >>> with Ethernet type using a MAC address 02:00:4c:4f:4f:50 >>> -
pinging loopback address is no more captured >>> - when checking the interface
characteristics with Wireshark GTK UI, the >>> media supported is Ethernet
instead of Null/Loopback >>> Rebooting the PC solves the issue. Any idea on how
to investigate this? >>> >>> You will find attached th corresponding DebugView
log when launching >>> Wireshark. >>> >>> Cheers, >>> Pascal. >>> >>> >>> >>>
___________________________________________________________________________ >>>
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> >>>
Archives: https://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 <wireshark-dev@wireshark.org> >>
Archives: https://www.wireshark.org/lists/wireshark-dev >> Unsubscribe:
https://wireshark.org/mailman/options/wireshark-dev >>
mailto:wireshark-dev-requ...@wireshark.org >> ?subject=unsubscribe >> > >
-------------- next part -------------- An HTML attachment was scrubbed... URL:
<https://www.wireshark.org/lists/wireshark-dev/attachments/20150901/49c0ea9a/attachment.html>;
------------------------------ Message: 2 Date: Wed, 2 Sep 2015 14:38:19 +0800
From: Yang Luo <hslu...@gmail.com> To: Developer support list for Wireshark
<wireshark-dev@wireshark.org> Subject: Re: [Wireshark-dev] Npcap 0.04 call for
test Message-ID:
<cam_tfozpla0vmqtdjus8obtysnscxxh1icnusg2chdfjgvu...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8" Hi Pascal, On Wed, Sep 2, 2015 at
1:57 AM, Pascal Quantin <pascal.quan...@gmail.com> wrote: > > > 2015-09-01
17:23 GMT+02:00 Pascal Quantin <pascal.quan...@gmail.com>: > >> >> >>
2015-09-01 3:19 GMT+02:00 Yang Luo <hslu...@gmail.com>: >> >>> Hi Pascal, >>>
>>> Thanks for this bug. This bug is because loopback flag in Npcap driver >>>
isn't set when the driver is paused and restarted (occurs when system >>>
resumes from sleep). I have fixed it. >>> Try lastest installer at: >>>
https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-0.04-r9.exe >>> >> >>
Hi Yang, >> >> thanks for the updated driver. I just tested it on the Windows 7
x64 >> laptop that was having BSoD beginning of August and I can happily tell
you >> that: >> - it does not crash anymore and WiFi is working fine with Npcap
installed >> - loopback interface is still working after a suspend / resume >>
>> Thanks for your work and congratulation for your GSoC. I guess (hope?) it >>
was considered as being successful :) >> > Yes, I have completed the project
successfully, and lots of test work from Wireshark has helped me so much,
thanks for all your work too:) > >> > Hi Yang, > > a small glitch I just
noticed: you forgot to update the string used by > Wireshark to get Ncap
version (as seen in About Wireshark dialog box:). It > reports "Npcap version
0.04 (packet.dll version 1.00), based on WinPcap > version 4.1.3 (packet.dll
version 4.1.0.3001), based on libpcap version 1.0 > branch 1_0_rel0b
(20091008)". > This is because that wpcap.dll version string is not updated to
1.00, I have fixed it and improved the appearance of the installer. Try
installer at: https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-1.00.exe
<https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-1.00.exe>; > > >
Pascal. > > >> Pascal. >> >> >>> >>> >>> Cheers, >>> Yang >>> >>> >>> On Fri,
Aug 28, 2015 at 4:17 AM, Pascal Quantin < >>> pascal.quan...@gmail.com> wrote:
>>> >>>> >>>> 2015-08-25 12:00 GMT+02:00 Yang Luo <hslu...@gmail.com>: >>>>
>>>>> Hi Guy, >>>>> >>>>> Now PCAP_IF_LOOPBACK flag in pcap_if_t struct will be
set for "Npcap >>>>> Loopback Adapter" both for DLT_NULL mode and Fake Ethernet
mode. >>>>> See Npcap 0.04 r8 at: >>>>>
https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-0.04-r8.exe >>>>> >>>>>
Cheers, >>>>> Yang >>>>> >>>> >>>> Hi Yang, >>>> >>>> I noticed an issue when
running Npcap 0.4r8 with DLT_NULL option on my >>>> Windows 10 x64 host. After
putting my laptop in standby mode and resuming >>>> my session, when launching
Wireshark the Npcap loopback interface is no >>>> more working as expected:
>>>> - the capture is no more done with Null/Loopback encapsulation type, >>>>
but with Ethernet type using a MAC address 02:00:4c:4f:4f:50 >>>> - pinging
loopback address is no more captured >>>> - when checking the interface
characteristics with Wireshark GTK UI, >>>> the media supported is Ethernet
instead of Null/Loopback >>>> Rebooting the PC solves the issue. Any idea on
how to investigate this? >>>> >>>> You will find attached th corresponding
DebugView log when launching >>>> Wireshark. >>>> >>>> Cheers, >>>> Pascal.
>>>> >>>> >>>> >>>>
___________________________________________________________________________
>>>> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> >>>>
Archives: https://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 <wireshark-dev@wireshark.org> >>>
Archives: https://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 <wireshark-dev@wireshark.org> >
Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe:
https://wireshark.org/mailman/options/wireshark-dev >
mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe > Cheers,
Yang -------------- next part -------------- An HTML attachment was scrubbed...
URL:
<https://www.wireshark.org/lists/wireshark-dev/attachments/20150902/2dc2875c/attachment.html>;
------------------------------ _______________________________________________
Wireshark-dev mailing list Wireshark-dev@wireshark.org
https://wireshark.org/mailman/listinfo/wireshark-dev End of Wireshark-dev
Digest, Vol 112, Issue 3 *********************************************
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
