RE: [Openvpn-users] TUN/TAP doesn't get an IP address

[Andreas Iwanowski <namezero@xxxxxxxxx>]

-----Original Message-----
From: James Yonan [mailto:jim@xxxxxxxxx] 
Sent: Wednesday, March 02, 2005 1:17 AM
To: Andreas Iwanowski
Cc: Openvpn Users (openvpn-users@xxxxxxxxxxxxxxxxxxxxx)
Subject: Re: [Openvpn-users] TUN/TAP doesn't get an IP address


On Tue, 1 Mar 2005, Andreas Iwanowski wrote:

> Hello List,
> 
> I have some trouble with OpenVPN 2.0rc6 on a Windows 2003 SBS server, SP1.
> 
> Occasionally (once or twice a week), after the connection with the peer is re-established,
> the TAP device fails to obtain the IP address set by OpenVPN.
> The log file says the following:
> 
> ---------------
> Fri Feb 25 15:18:34 2005 us=173685 NOTE: FlushIpNetTable failed on interface
> [2] {5A4DE833-7293-4544-98EF-3CE949D78158} (status=1413) : Invalid index.
> ---------------
> followd by a _lot_ of these:
> ---------------
> Fri Feb 25 15:18:53 2005 us=687643 TEST ROUTES: 0/0 succeeded len=1 ret=0
> a=0 u/d=down
> Fri Feb 25 15:18:53 2005 us=687764 Route: Waiting for TUN/TAP interface to
> come up...
> ---------------

Do you have "persist-tun" and "persist-key" in the client config file?

Have you tried other "ip-win32" methods?

Make sure the DHCP client service is always running.

You might try adding "show-net-up" to the Windows config.  It will show 
OpenVPN's view of the interface and routing table at the point of failure.

James

Thank you for your reply!

I have the following Tunnel/IP config directives in my config file:
 
----------
# Server configuration file xxxxxxx -> xxxxxxx
# Connection
mode p2p
remote xxxxxxxxxxxxx
port xxxx
proto udp
resolv-retry infinite
float
up-delay

# Connection parameters
dev tun
dev-node tap0

#Interface configuration
ip-win32 dynamic
ifconfig 192.168.102.2 192.168.102.1
route-delay 20 20
route-method exe
route 192.168.0.0 255.255.0.0 192.168.102.1
----------

The DHCP client service is running, too.
Funny thing is, that it works for a couple times before the error occurs, and then you can either restart the server or reinstall OpenVPN to solve the problem.

Currently, I'm circumventing the problem by setting the IP in Windows and telling OpenVPN  that I set it manually (ip-win32 manual). However, I would like to go back to normal operation if possible.

The problem does not occur on Windows 2000 Advanced Server, SP4.

-andy

____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users