Re: [Wireshark-dev] Npcap 0.03 call for test

2015-08-05 Thread Yang Luo 
Hello Jim,

On Tue, Aug 4, 2015 at 12:23 PM, Jim Young  wrote:

> 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 follows:
>
> ping -t -l 65500 127.0.0.1
>
> The first several ping requests and responses are seen and captured but
> after
> several seconds I started seeing "[Malformed Packets]" of length 14.  A
> pair of
> Malformed packets were seen each second.  When I stopped the ping, the
> Malformed
> Packets stopped.  I stopped and restarted Wireshark but the same thing
> happened.
>

Thanks for test. I have confirmed and fixed this "Malformed Packets" issue,
this is because the packet read function *NPF_TapExForEachOpen* didn't copy
the 2nd MDL data if the data has crossed the buffer boundary. Latest
installer that has this bug fixed is:
https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-0.03-r4.exe



> I then wanted to reboot the system to see if I could still replicate this
> Malformed
> Packet issue.
>
> After the system rebooted I double-clicked on the Wireshark icon but it
> did not
> immediately start.  I thought that I had not double-clicked on it properly
> so I
> double-clicked on the Wireshark icon a second time and then the system
> crashed
> with the following Bug Check Message:
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL
>

This is still the *NdisFOidRequest* BSoD issue we talked about on this list
before, IMO this BSoD has nothing to do with the "Malformed Packets" issue.
The last way to fix it is to just disable the GetDeviceMTU call and
directly returns 1514 for MTU, so this issue should be got rid of, however
this is never a good way to fix a problem.


Cheers,
Yang
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] Error when compiling extcap/androiddump.c with (released) MSVC 2015

2015-08-05 Thread Anders Broman 
Hi,
I get:

androiddump.c
extcap/androiddump.c(736): error C2220: warning treated as error - no 'object' f
ile generated
extcap/androiddump.c(736): warning C4477: 'fprintf' : format string '%I64i' requ
ires an argument of type '__int64', but variadic argument 3 has type 'ssize_t'
extcap/androiddump.c(736): note: to simplify migration, consider the temporary u
se of /Wv:18 flag with the version of the compiler with which you used to build
without warnings
extcap/androiddump.c(736): note: consider using '%i' in the format string
extcap/androiddump.c(736): note: consider using '%I32i' in the format string
extcap/androiddump.c(786): warning C4477: 'fprintf' : format string '%I64i' requ
ires an argument of type '__int64', but variadic argument 3 has type 'ssize_t'
extcap/androiddump.c(786): note: to simplify migration, consider the temporary u
se of /Wv:18 flag with the version of the compiler with which you used to build
without warnings
extcap/androiddump.c(786): note: consider using '%i' in the format string
extcap/androiddump.c(786): note: consider using '%I32i' in the format string
extcap/androiddump.c(866): warning C4477: 'fprintf' : format string '%I64i' requ
ires an argument of type '__int64', but variadic argument 3 has type 'ssize_t'
extcap/androiddump.c(866): note: to simplify migration, consider the temporary u
se of /Wv:18 flag with the version of the compiler with which you used to build
without warnings
extcap/androiddump.c(866): note: consider using '%i' in the format string
extcap/androiddump.c(866): note: consider using '%I32i' in the format string
extcap/androiddump.c(1565): warning C4477: 'printf' : format string '%I64i' requ
ires an argument of type '__int64', but variadic argument 1 has type 'ssize_t'
extcap/androiddump.c(1565): note: to simplify migration, consider the temporary
use of /Wv:18 flag with the version of the compiler with which you used to build
without warnings
extcap/androiddump.c(1565): note: consider using '%i' in the format string
extcap/androiddump.c(1565): note: consider using '%I32i' in the format string
extcap/androiddump.c(1624): warning C4477: 'printf' : format string '%I64i' requ
ires an argument of type '__int64', but variadic argument 2 has type 'ssize_t'
extcap/androiddump.c(1624): note: to simplify migration, consider the temporary
use of /Wv:18 flag with the version of the compiler with which you used to build
without warnings
extcap/androiddump.c(1624): note: consider using '%i' in the format string
extcap/androiddump.c(1624): note: consider using '%I32i' in the format string
extcap/androiddump.c(1624): warning C4477: 'printf' : format string '%I64i' requ
ires an argument of type '__int64', but variadic argument 3 has type 'ssize_t'
extcap/androiddump.c(1624): note: to simplify migration, consider the temporary
use of /Wv:18 flag with the version of the compiler with which you used to build
without warnings
extcap/androiddump.c(1624): note: consider using '%i' in the format string
extcap/androiddump.c(1624): note: consider using '%I32i' in the format string
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0
\VC\BIN\amd64\cl.EXE"' : return code '0x2'
Stop.

Any ideas on how to fix?

Regards
Anders
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] unicode replacement character in online docs

2015-08-05 Thread Hadriel Kaplan 
Anyone else seeing the unicode replacement character all over the
online auto-generated docs? (user guide and developer guide)

I don't recall having seen them there before, though maybe they've
always been there.

https://www.wireshark.org/docs/wsdg_html_chunked/index.html
https://www.wireshark.org/docs/wsug_html_chunked/index.html

-hadriel
___
Sent via:Wireshark-dev mailing list 
Archives:https://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] unicode replacement character in online docs

2015-08-05 Thread Evan Huus 
On Wed, Aug 5, 2015 at 9:49 AM, Hadriel Kaplan
 wrote:
> Anyone else seeing the unicode replacement character all over the
> online auto-generated docs? (user guide and developer guide)

Yup, and that's new AFAIK. Anybody know if something's change on the
server or on the build bot with respect to character encoding?

Based on the byte-values of something I expect should be a copyright
symbol, it looks like it's using ISO8859-1 and/or Windows-1252.

> I don't recall having seen them there before, though maybe they've
> always been there.
>
> https://www.wireshark.org/docs/wsdg_html_chunked/index.html
> https://www.wireshark.org/docs/wsug_html_chunked/index.html
>
> -hadriel
> ___
> Sent via:Wireshark-dev mailing list 
> 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 
Archives:https://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] Error when compiling extcap/androiddump.c with (released) MSVC 2015

2015-08-05 Thread Michal Labedzki 
Hello,

Try this one: https://code.wireshark.org/review/#/c/9876/

On 5 August 2015 at 11:16, Anders Broman  wrote:

> Hi,
>
> I get:
>
>
>
> androiddump.c
>
> extcap/androiddump.c(736): error C2220: warning treated as error - no
> 'object' f
>
> ile generated
>
> extcap/androiddump.c(736): warning C4477: 'fprintf' : format string
> '%I64i' requ
>
> ires an argument of type '__int64', but variadic argument 3 has type
> 'ssize_t'
>
> extcap/androiddump.c(736): note: to simplify migration, consider the
> temporary u
>
> se of /Wv:18 flag with the version of the compiler with which you used to
> build
>
> without warnings
>
> extcap/androiddump.c(736): note: consider using '%i' in the format string
>
> extcap/androiddump.c(736): note: consider using '%I32i' in the format
> string
>
> extcap/androiddump.c(786): warning C4477: 'fprintf' : format string
> '%I64i' requ
>
> ires an argument of type '__int64', but variadic argument 3 has type
> 'ssize_t'
>
> extcap/androiddump.c(786): note: to simplify migration, consider the
> temporary u
>
> se of /Wv:18 flag with the version of the compiler with which you used to
> build
>
> without warnings
>
> extcap/androiddump.c(786): note: consider using '%i' in the format string
>
> extcap/androiddump.c(786): note: consider using '%I32i' in the format
> string
>
> extcap/androiddump.c(866): warning C4477: 'fprintf' : format string
> '%I64i' requ
>
> ires an argument of type '__int64', but variadic argument 3 has type
> 'ssize_t'
>
> extcap/androiddump.c(866): note: to simplify migration, consider the
> temporary u
>
> se of /Wv:18 flag with the version of the compiler with which you used to
> build
>
> without warnings
>
> extcap/androiddump.c(866): note: consider using '%i' in the format string
>
> extcap/androiddump.c(866): note: consider using '%I32i' in the format
> string
>
> extcap/androiddump.c(1565): warning C4477: 'printf' : format string
> '%I64i' requ
>
> ires an argument of type '__int64', but variadic argument 1 has type
> 'ssize_t'
>
> extcap/androiddump.c(1565): note: to simplify migration, consider the
> temporary
>
> use of /Wv:18 flag with the version of the compiler with which you used to
> build
>
> without warnings
>
> extcap/androiddump.c(1565): note: consider using '%i' in the format string
>
> extcap/androiddump.c(1565): note: consider using '%I32i' in the format
> string
>
> extcap/androiddump.c(1624): warning C4477: 'printf' : format string
> '%I64i' requ
>
> ires an argument of type '__int64', but variadic argument 2 has type
> 'ssize_t'
>
> extcap/androiddump.c(1624): note: to simplify migration, consider the
> temporary
>
> use of /Wv:18 flag with the version of the compiler with which you used to
> build
>
> without warnings
>
> extcap/androiddump.c(1624): note: consider using '%i' in the format string
>
> extcap/androiddump.c(1624): note: consider using '%I32i' in the format
> string
>
> extcap/androiddump.c(1624): warning C4477: 'printf' : format string
> '%I64i' requ
>
> ires an argument of type '__int64', but variadic argument 3 has type
> 'ssize_t'
>
> extcap/androiddump.c(1624): note: to simplify migration, consider the
> temporary
>
> use of /Wv:18 flag with the version of the compiler with which you used to
> build
>
> without warnings
>
> extcap/androiddump.c(1624): note: consider using '%i' in the format string
>
> extcap/androiddump.c(1624): note: consider using '%I32i' in the format
> string
>
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
> Studio 14.0
>
> \VC\BIN\amd64\cl.EXE"' : return code '0x2'
>
> Stop.
>
>
>
> Any ideas on how to fix?
>
>
>
> Regards
>
> Anders
>
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org
> ?subject=unsubscribe
>



-- 

Pozdrawiam / Best regards
-
Michał Łabędzki, Software Engineer
Tieto Corporation

Product Development Services
http://www.tieto.com / http://www.tieto.pl
---
ASCII: Michal Labedzki
location: Swobodna 1 Street, 50-088 Wrocław, Poland
room: 5.01 (desk next to 5.08)
---
Please note: The information contained in this message may be legally
privileged and confidential and protected from disclosure. If the reader of
this message is not the intended recipient, you are hereby notified that
any unauthorised use, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and deleting it
from your computer. Thank You.
---
Please consider the environment before printing this e-mail.
---
Tieto Poland spółka z ograniczoną odpowiedzialnością z siedzibą w
Szczecinie, ul. Malczewskiego 26. Zarejestrowana

Re: [Wireshark-dev] unicode replacement character in online docs

2015-08-05 Thread Gerald Combs 
On 8/5/15 6:57 AM, Evan Huus wrote:
> On Wed, Aug 5, 2015 at 9:49 AM, Hadriel Kaplan
>  wrote:
>> Anyone else seeing the unicode replacement character all over the
>> online auto-generated docs? (user guide and developer guide)
> 
> Yup, and that's new AFAIK. Anybody know if something's change on the
> server or on the build bot with respect to character encoding?

It was a server misconfiguration. It should be fixed.

> Based on the byte-values of something I expect should be a copyright
> symbol, it looks like it's using ISO8859-1 and/or Windows-1252.

The fixed version shows non-breaking space, at least for the first page of
the Developer's Guide.

What's odd is that we're managing to generate documentation encoded as
ISO-8859-1.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe