Package: pptpd Version: 1.3.0-1 Severity: wishlist Tags: patch Hi!
There is a bug in Microsoft Windows VPN client: even if the default route is set to use the VPN connection, the DNS server used for name resolution may be not the VPN one... (See KB311218 for more information) Users should be warned about this but, so that they don't spend hours trying to fix it (as I did)! I wrote a patch with a comment added in pptpd-options, right before the ms-dns options. Tell me if you have comments about it. Cheers, -- Steph -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (970, 'unstable'), (930, 'experimental'), (870, 'dapper'), (500, 'edgy-updates'), (500, 'edgy-security'), (500, 'edgy-backports'), (500, 'edgy'), (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper-backports') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-beyond1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
--- pptpd-options.old 2006-08-24 21:34:00.000000000 +0200 +++ pptpd-options 2006-08-24 22:02:02.000000000 +0200 @@ -50,6 +50,8 @@ # addresses to the clients. The first instance of this option # specifies the primary DNS address; the second instance (if given) # specifies the secondary DNS address. +# Attention! This information may not be taken into account by a Windows +# client. See KB311218 in Microsoft's knowledge base for more information. #ms-dns 10.0.0.1 #ms-dns 10.0.0.2
