Yes, some users observed similar behaviour and we made some investigations. The problem is due to the fact that VPN connections (and some other NdisWan-based connections) invoke the NPF_Tap() function with a list of arguments that is different from the one that the function expects. This produces a stack corruption and a consequent blue screen. We have not found simple workarounds at the moment, so we plan to disable the capture on the adapters that have NdisWan as supported media. This will prevent winpcap to open (and show) any kind of PPP connection.
Loris ----- Original Message ----- From: "Gavin Morris" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, February 03, 2003 6:54 AM Subject: [WinPcap-users] Version 3.0a4 and VPN Hi all, Have been testing 3.0a4 and come across an issue - if a machine makes a PPTP VPN connection while the driver is active, a BSOD occurs ... Error from our Sentinel application: STOP error 0xD1 (0xDBD, 0x2, 0x1, 0xEB752021) Address EB752021, Base EB750000 in npf.sys Error from windump: STOP error 0xD1 (0xDBD, 0x2, 0x1, 0xEB742021) Address EB742021, Base EB740000 in npf.sys Windump prints about 10 packets before the stop occurs. Client: 2K Pro SP3, WinPCap 3.0a4 Server: 2K Server SP3 (has WinPCap 2.3 installed, as well as MS ISA Server) VPN configured through Windows 2000 Routing & RAS. Has anyone else observed similar behaviour or derived a workaround? Cheers, -G --- Gavin Morris, BSc [EMAIL PROTECTED] Mobile: +61 0403 508 862 ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[email protected]/ To unsubscribe use mailto: [EMAIL PROTECTED]?body=unsubscribe ==================================================================
