[vpn-help] New 2.2.0 Alpha Build Available ( PLEASE TEST !!! )

Wed Dec 15 23:10:26 CST 2010

Okay, I tested on 2 more computers (all are Windows 7 but 2 were 32 bit and
1 is 64). The results are reproducible... I am connecting to a Fortigate
unit and have tried connecting to 2 different Fortigate units with the same
results. I can ping things on the remote side if I know the IP, I can do an
nslookup since I know the IP of the DNS server but all in all things are
pretty bleak. I am also getting disconnected from the key daemon regularly
and it doesn't work again without restarting my computer (probably I could
just restart some services I admit).

Okay indeed if I restart the Shrew IKE Daemon things work again (the service
was no longer running BTW). I pulled this out of the event log.

Faulting application name: iked.exe, version: 0.0.0.0, time stamp:
0x4d01dd9a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x784
Faulting application start time: 0x01cb9cdd7392aba1
Faulting application path: C:\Program Files\ShrewSoft\VPN Client\iked.exe
Faulting module path: unknown
Report Id: 1fe750e4-08d2-11e0-bf5f-00188bc87b37

Here is what I get in ipconfig.

2.1.7
Ethernet adapter Local Area Connection* 11:

   Connection-specific DNS Suffix  . : nbn.lan
   Description . . . . . . . . . . . : Shrew Soft Virtual Adapter
   Physical Address. . . . . . . . . : AA-AA-AA-96-F2-00
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . :
fe80::19b9:ea96:e658:a2d9%31(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.48.8(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 531278506
   DHCPv6 Client DUID. . . . . . . . :
00-01-00-01-14-96-84-94-00-18-8B-C8-7B-37

   DNS Servers . . . . . . . . . . . : 172.16.10.11
   NetBIOS over Tcpip. . . . . . . . : Disabled

2.2.0
Ethernet adapter Local Area Connection* 11:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Shrew Soft Virtual Adapter
   Physical Address. . . . . . . . . : AA-AA-AA-B2-87-00
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . :
fe80::7155:a796:93d8:909%17(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.48.9(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Disabled

Matthew should I wait a couple days for a new version or fall back to 2.1.7?

On Mon, Dec 13, 2010 at 10:42 PM, Noach Sumner <nss at compu-skill.com> wrote:

> I upgraded a computer (Windows 7 x64) to from 2.1.7 to 2.2.0 and I
> immediate noticed that it now gave me DNS as an IPv6 address which is not
> what my DHCP should be handing out and I didn't have this with 2.1.7. I also
> noticed that after I disconnected I wasn't able to reconnect until I
> rebooted the computer but I didn't have a chance to see if this was once off
> or repeatable.
>
> On Sun, Dec 12, 2010 at 11:56 PM, Matthew Grooms <mgrooms at shrew.net>wrote:
>
>> All,
>>
>> So its been quite some time since we have released a new build from the
>> head branch which will become the 2.2.0 release version. I'm pleased to be
>> moving beyond the 2.1.7 series as there are many enhancements and changes in
>> the head branch that have yet to make it into a stable VPN client release. I
>> really need everyone's help to test this release as it contains a few
>> critical bug fixes in the kernel drivers which will take some time to pass
>> through WinQual certification. This was a major bottleneck for the 2.1.7
>> release so we hope to get this completed much quicker this time around. All
>> the kernel driver related items on the 2.2.0 todo list have been completed.
>> Unless regressions are reported ( and I don't expect any ), we should be
>> able to qualify this version of the driver.
>>
>> What's new in this release? I'll start with the major bug fixes ...
>>
>> 1) A myriad of tools were used to test user binaries to shake out any
>> memory leaks that were present. Embarrassingly, there were at least a dozen
>> problems found and corrected, none of them kernel driver related. If you
>> noticed a memory leak related to the VPN client on any platform, please test
>> this build.
>>
>> 2) The WLAN related problem that could be avoided by disabling the
>> Microsoft Virtual WiFi Miniport Adapter problem has now been worked around
>> at the driver level. As long as you are connected to an AP, the VPN client
>> should operate normally. Using adhoc networks are currently unsupported. If
>> you currently have the Virtual WiFi adapter disabled, please re-enable it
>> and test this build.
>>
>> 3) The problem related to slow TCP performance when direct adapter mode
>> was in use has been corrected. This was due to the miniport TCP Large
>> Segment Offload feature not being emulated in the LWF driver send path. If
>> you currently have LSO disabled on your adapter, please re-enable it and
>> test this build.
>>
>> 4) The daemons no longer wake up every 500ms to check for an exit status.
>> It's quite possible that this caused unnecessary CPU activity while in a low
>> power state. This may cause a laptop battery to drain faster even with the
>> VPN client disconnected. To accomplish this on Windows platforms, we now use
>> asynchronous communication functions in all driver interface library calls.
>> This has also increased throughput on low latency connections by a factor of
>> 3. Less objective tests show that this change also has a positive impact on
>> high latency connections such as mobile broadband adapters. If you have a
>> native Windows 7 mobile broadband connection, please test this build.
>>
>> A huge number of other minor bug fixes are included in this release when
>> compared to the last 2.2.0 alpha. In many ways, this release is likely more
>> polished than even the 2.1.7 release. The reason its still marked as alpha
>> is that we still have more feature work and the driver certification to
>> complete before calling it a beta. If you have time, please help test this
>> build! We really need as many eyeballs on it as possible to help us located
>> driver bugs or regressions before we spend the time and funds to re-certify
>> the drivers.
>>
>> Thanks to everyone in advance,
>>
>> -Matthew
>> _______________________________________________
>> vpn-help mailing list
>> vpn-help at lists.shrew.net
>> http://lists.shrew.net/mailman/listinfo/vpn-help
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.shrew.net/pipermail/vpn-help/attachments/20101216/02320237/attachment-0001.html>