|
|
Awesome - works like a charm.
I was wrong in my suspicion - it does look like there's some sort of
DHCP communication going on, but it takes a while for the W2K box to
even send the request. It then takes a long time to assign the address
(usually assigns it after an ARP) and even times out in some cases.
It's bizarre that the first DHCP request comes 20 seconds after the
media state was set to attached. I'm not certain, but it might be a
problem with my W2K setup (network card perhaps), interaction with
another piece of VPN software installed (I'll try uninstalling it to see
if it helps) or just the fact that the computer is very slow (PII-300).
It's very likely the two pieces of VPN software are conflicting - I'll
confirm this one. I've attached the logfile, but it looks like
everything is working, just really slow.
Matt.
On Fri, 2004-04-02 at 07:35, James Yonan wrote:
> For those of you wishing to get driver debugging info out of the Windows beta
> 2.0 version, I've made a checked build. Run at --verb 6 or higher to get
> TAP-Win32 debugging messages, including DHCP requests and replies.
>
> http://openvpn.sourceforge.net/beta/openvpn-2.0_test19-CHK-install.exe
>
> James
>
> Matthew Mastracci <matt@xxxxxxxxxx> said:
>
> > I've got a failure with DHCP on one of my clients in 2.0 beta 18 that I
> > can't seem to resolve.
> >
> > The server manages to grab a DHCP address correctly but the client takes
> > more than a minute to successfully obtain an address. By this time, the
> > routes have failed to set (the IP address is stated as 0.0.0.0).
> >
> > I used windump to see what's happening but it appears as if the windows
> > box is correctly sending the DHCP request, but the TUN/TAP driver is
> > just ignoring it (or the message is otherwise lost). No interesting
> > information appeared with "verb 8".
> >
> > Is it possible for me to get some debugging messages out of the driver,
> > or will I need to recompile? I'd like to see if the driver is dropping
> > the DHCP message because of a MAC address mismatch, invalid format or
> > some other error.
> >
> > I would like to diagnose this issue and I might be able to help fixing
> > it, but I'm a newbie at windows driver development.
> >
> > Matt.
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux Tutorials
> > Free Linux tutorial presented by Daniel Robbins, President and CEO of
> > GenToo technologies. Learn everything from fundamentals to system
> > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > _______________________________________________
> > Openvpn-users mailing list
> > Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/openvpn-users
> >
--
Matthew Mastracci <matt@xxxxxxxxxx>
Event log:
8:26:06 Your computer has automatically configured the IP address for the Network Card with network address 00FF06338655. The IP address being used is 169.254.218.194.
8:28:12 Your computer has automatically configured the IP address for the Network Card with network address 00FF06338655. The IP address being used is 169.254.218.194.
OpenVPN:
Fri Apr 02 08:26:43 2004 61: PUSH: Received control message: 'PUSH_REPLY,route 1
92.168.2.1 255.255.255.255,route 192.168.1.0 255.255.255.0,ifconfig 192.168.2.10
192.168.2.9'
Fri Apr 02 08:26:43 2004 62: PULL: --ifconfig/up options modified
Fri Apr 02 08:26:43 2004 63: PULL: route options modified
Fri Apr 02 08:26:44 2004 64: Attempting to lock Win32 semaphore 'openvpn_netcmd'
prior to net shell command (timeout = 600 sec)
Fri Apr 02 08:26:44 2004 65: TAP-WIN32 device [Local Area Connection 8] opened:
\\.\Global\{06338655-9D53-4B53-B1C7-A204F765F47D}.tap
Fri Apr 02 08:26:44 2004 66: TAP-Win32 Driver Version 6.7 (DEBUG)
Fri Apr 02 08:26:44 2004 67: TAP-Win32 MTU=1500Fri Apr 02 08:26:44 2004 68: Notified TAP-Win32 driver to set a DHCP IP/netmask
of 192.168.2.10/255.255.255.252 on interface {06338655-9D53-4B53-B1C7-A204F765F4
7D} [DHCP-serv: 192.168.2.9, lease-time: 31536000]
Fri Apr 02 08:26:44 2004 69: Successful ARP Flush on interface [33554435] {06338
655-9D53-4B53-B1C7-A204F765F47D}
Fri Apr 02 08:26:44 2004 70: UDPv4 WRITE [22] to xx.xx.xx.xx:52212: P_ACK_V1 k
id=0 [ 36 ]
Fri Apr 02 08:26:44 2004 71: TAP-Win32: [\DEVICE\{06338655-9D53-4B53-B1C7-A204F7
65F47D}] [TAP] release [6.7] close/cleanup request
Fri Apr 02 08:26:44 2004 72: TAP-Win32: [\Device\{06338655-9D53-4B53-B1C7-A204F7
65F47D}.tap] [TAP] FlushQueues n_IRP=[0,1,16] n_Packet=[0,0,64]
Fri Apr 02 08:26:44 2004 73: TAP-Win32: [\DEVICE\{06338655-9D53-4B53-B1C7-A204F7
65F47D}] [TAP] release [6.7] open request (m_TapOpens=0)
Fri Apr 02 08:26:54 2004 74: Attempting to lock Win32 semaphore 'openvpn_netcmd'
prior to net shell command (timeout = 600 sec)
Fri Apr 02 08:26:54 2004 75: route ADD 192.168.2.1 MASK 255.255.255.255 192.168.
2.9
The route addition failed: Either the interface index is wrong or the gateway do
es not lie on the same network as the interface. Check the IP Address Table for
the machine.
Fri Apr 02 08:26:54 2004 76: ERROR: Windows route add command failed: system() r
eturned error code 176
Fri Apr 02 08:26:54 2004 77: Attempting to lock Win32 semaphore 'openvpn_netcmd'
prior to net shell command (timeout = 600 sec)
Fri Apr 02 08:26:54 2004 78: route ADD 192.168.1.0 MASK 255.255.255.0 192.168.2.
9
The route addition failed: Either the interface index is wrong or the gateway do
es not lie on the same network as the interface. Check the IP Address Table for
the machine.
Fri Apr 02 08:26:54 2004 79: ERROR: Windows route add command failed: system() r
eturned error code 176
Fri Apr 02 08:26:54 2004 80: UDPv4 WRITE [53] to xx.xx.xx.xx:52212: P_DATA_V1
kid=0 DATA len=52
Fri Apr 02 08:26:54 2004 81: UDPv4 READ [53] from xx.xx.xx.xx:52212: P_DATA_V1
kid=0 DATA len=52
Fri Apr 02 08:27:05 2004 82: UDPv4 READ [53] from xx.xx.xx.xx:52212: P_DATA_V1
kid=0 DATA len=52
Fri Apr 02 08:27:05 2004 83: UDPv4 WRITE [53] to xx.xx.xx.xx:52212: P_DATA_V1
kid=0 DATA len=52
Fri Apr 02 08:27:10 2004 84: TAP-Win32: AdapterTransmit IPv4 UDP[342] BOOTREQUES
T DHCPDISCOVER 0.0.0.0:BOOTPC[0:ff:6:33:86:55] -> 255.255.255.255:BOOTPS[ff:ff:f
f:ff:ff:ff] ch=0:ff:6:33:86:55 xid=0x9d5d5224 id=0xfd7f ttl=128 ic=0x3c26 [0x000
0] uc=0xba39 [0x0000/60] OPT.53.1.1.251.1.1.61.7.1.0.255.6.51.134.85.50.4.169.25
4.218.194.12.3.111.108.100.60.8.77.83.70.84.32.53.46.48.55.10.1.15.3.6.44.46.47.
31.33.43.255.0.0.0.0.0.0.0.0.0.0.0
Fri Apr 02 08:27:10 2004 85: TAP-Win32: DHCPMsg IPv4 UDP[304] BOOTREPLY DHCPOFFE
R 192.168.2.9:BOOTPS[0:ff:7:33:86:55] -> 255.255.255.255:BOOTPC[ff:ff:ff:ff:ff:f
f] yi=192.168.2.10 si=192.168.2.9 ch=0:ff:6:33:86:55 xid=0x9d5d5224 ttl=16 ic=0x
e71a [0x0000] uc=0x24e3 [0x0000/22] OPT.53.1.2.54.4.192.168.2.9.51.4.1.225.51.12
8.1.4.255.255.255.252.255
Fri Apr 02 08:27:14 2004 86: TAP-Win32: AdapterTransmit IPv4 UDP[342] BOOTREQUES
T DHCPDISCOVER 0.0.0.0:BOOTPC[0:ff:6:33:86:55] -> 255.255.255.255:BOOTPS[ff:ff:f
f:ff:ff:ff] ch=0:ff:6:33:86:55 xid=0x9d5d5224 secs=1280 id=0xfd8e ttl=128 ic=0x3
c17 [0x0000] uc=0xb539 [0x0000/60] OPT.53.1.1.251.1.1.61.7.1.0.255.6.51.134.85.5
0.4.169.254.218.194.12.3.111.108.100.60.8.77.83.70.84.32.53.46.48.55.10.1.15.3.6
.44.46.47.31.33.43.255.0.0.0.0.0.0.0.0.0.0.0
Fri Apr 02 08:27:14 2004 87: TAP-Win32: DHCPMsg IPv4 UDP[304] BOOTREPLY DHCPOFFE
R 192.168.2.9:BOOTPS[0:ff:7:33:86:55] -> 255.255.255.255:BOOTPC[ff:ff:ff:ff:ff:f
f] yi=192.168.2.10 si=192.168.2.9 ch=0:ff:6:33:86:55 xid=0x9d5d5224 ttl=16 ic=0x
e71a [0x0000] uc=0x24e3 [0x0000/22] OPT.53.1.2.54.4.192.168.2.9.51.4.1.225.51.12
8.1.4.255.255.255.252.255
Fri Apr 02 08:27:15 2004 88: UDPv4 WRITE [53] to xx.xx.xx.xx:52212: P_DATA_V1
kid=0 DATA len=52
Fri Apr 02 08:27:15 2004 89: UDPv4 READ [53] from xx.xx.xx.xx:52212: P_DATA_V1
kid=0 DATA len=52
|