Route: Waiting for TUN/TAP interface to come up...

This forum is for admins who are looking to build or expand their OpenVPN setup.
Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
khakkinen
OpenVpn Newbie
Posts: 8
Joined: Tue Jan 04, 2011 12:37 pm

Route: Waiting for TUN/TAP interface to come up...

Post by khakkinen » Tue Jan 04, 2011 12:45 pm

Hey All,

I have been having a problem for quite a while on my OpenVPN setup. OpenVPN is running on a FreeBSD 8.0 Server and my client is running Windows 7 Ultimate. This setup was working fine for me for ages on Windows XP. When I switched to Windows 7, it worked fine for a few months then suddenly started erroring out saying "Route: Waiting for TUN/TAP interface to come up...".

Now this is the really irritating thing. Sometimes, for no apparent reason, it will work! It will work wonderfully for a few connections, then it will just die with the same error message.

Any ideas why this may be happening? I have been searching google for weeks now trying to figure it out. I have disabled UAC, Set OpenVPN to compat mode, disabled the firewall, alot of things. I even tried it on another Windows 7 computer with the same result. I have a vague feeling it may be something to do with Windows 7 but I don't have a Windows XP machine to test with.

Thanks,
Karl

User avatar
gladiatr72
Forum Team
Posts: 194
Joined: Mon Dec 13, 2010 3:51 pm
Location: Lawrence, KS

Re: Route: Waiting for TUN/TAP interface to come up...

Post by gladiatr72 » Wed Jan 05, 2011 11:48 am

Karl,

What version of openvpn are you using on your client system?

-Stephen
[..]I used to think it was awful that life was so unfair. [...]Wouldn't it be much worse if life were fair, and all the terrible things that happen to us come because we actually deserve them? -Marcus Cole

khakkinen
OpenVpn Newbie
Posts: 8
Joined: Tue Jan 04, 2011 12:37 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by khakkinen » Wed Jan 05, 2011 10:42 pm

Hey gladiatr72,

Im running: OpenVPN 2.1.3 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Aug 20 2010

Edit:

I just upgraded to 2.1.4 but there was no change, it still errored out.

Thanks,
Karl

User avatar
gladiatr72
Forum Team
Posts: 194
Joined: Mon Dec 13, 2010 3:51 pm
Location: Lawrence, KS

Re: Route: Waiting for TUN/TAP interface to come up...

Post by gladiatr72 » Thu Jan 06, 2011 7:31 pm

Hrm. Ok. If you can, please post your client configuration.

-S
[..]I used to think it was awful that life was so unfair. [...]Wouldn't it be much worse if life were fair, and all the terrible things that happen to us come because we actually deserve them? -Marcus Cole

khakkinen
OpenVpn Newbie
Posts: 8
Joined: Tue Jan 04, 2011 12:37 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by khakkinen » Fri Jan 07, 2011 2:39 am

Client.ovpn:

Code: Select all

client
dev tun
proto udp
remote theta 28058
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt
cert karlh.crt
key karlh.key
ns-cert-type server
comp-lzo
verb 3
I should also note I am running 64bit Windows.

User avatar
krzee
Forum Team
Posts: 729
Joined: Fri Aug 29, 2008 5:42 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by krzee » Fri Jan 07, 2011 3:17 am

try this in the client config

Code: Select all

route-delay

khakkinen
OpenVpn Newbie
Posts: 8
Joined: Tue Jan 04, 2011 12:37 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by khakkinen » Fri Jan 07, 2011 3:32 am

By the great lords of cobol.... I think that may have done it. Put it in, tried it and it connected first go! That's the first time that has happened in ages :D I'll do some more testing but hopefully, that got it :D

Thanks Heaps Guys!

khakkinen
OpenVpn Newbie
Posts: 8
Joined: Tue Jan 04, 2011 12:37 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by khakkinen » Fri Jan 07, 2011 10:27 am

Hey Guys,

Just tested it again... It's stopped working :( Any other ideas?

Thanks,
Karl

User avatar
gladiatr72
Forum Team
Posts: 194
Joined: Mon Dec 13, 2010 3:51 pm
Location: Lawrence, KS

Re: Route: Waiting for TUN/TAP interface to come up...

Post by gladiatr72 » Fri Jan 07, 2011 2:55 pm

Stopped working: as in

A: "you start the client, it works for a while but then stops working at some point"
or
B: "It doesn't work at all now"?

-S
[..]I used to think it was awful that life was so unfair. [...]Wouldn't it be much worse if life were fair, and all the terrible things that happen to us come because we actually deserve them? -Marcus Cole

khakkinen
OpenVpn Newbie
Posts: 8
Joined: Tue Jan 04, 2011 12:37 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by khakkinen » Fri Jan 07, 2011 11:45 pm

Sorry, I should have been more clear.

When I go to connect to my OpenVPN server, it will connect 2 times out of 10. The rest of the time it just keeps cycling that same error message.

When it does connect, it works great. But then I may disconnect it for some reason (Like computer reboot) and then it wont connect again. I have to keep trying to connect until it works (As I said, usually around 10 tries).

When I put in the route-delay option, it seemed to work fine. I'd connect every time I tried (I tried 3 times). I turned off my computer, restarted it and it wouldn't connect (Saying the same error message).

khakkinen
OpenVpn Newbie
Posts: 8
Joined: Tue Jan 04, 2011 12:37 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by khakkinen » Sun Jan 09, 2011 11:13 am

I just managed to test on a friend of mines computer which is running Windows XP. I tried to connect using Windows XP and it worked fine. Tried a second later (After disconnecting the Windows XP connection) with my Windows 7 laptop and it didn't work.

I just re-read over my original post, I forgot to add something that may be relevant. The times which it doesn't work is strange because it looks like it's connected (It gets a valid IP, the same IP it gets when it is working) but there is no data flow at all (Can't access anything via the connection like SMB or Proxy whereas when it connects fine, it works perfectly). When it doesnt work it shows this error message at the end:

Code: Select all

un Jan 09 22:24:55 2011 Warning: route gateway is not reachable on any active network adapters: 10.8.0.5
Sun Jan 09 22:24:55 2011 Route addition via IPAPI failed [adaptive]
Sun Jan 09 22:24:55 2011 Route addition fallback to route.exe
 OK!
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 10.0.0.138 p=0 i=13 t=4 pr=3 a=30698 h=0 m=25/0/0/0/0
10.0.0.0 255.255.255.0 10.0.0.6 p=0 i=13 t=3 pr=3 a=30698 h=0 m=281/0/0/0/0
10.0.0.6 255.255.255.255 10.0.0.6 p=0 i=13 t=3 pr=3 a=30698 h=0 m=281/0/0/0/0
10.0.0.255 255.255.255.255 10.0.0.6 p=0 i=13 t=3 pr=3 a=30698 h=0 m=281/0/0/0/0
10.8.0.0 255.255.255.0 10.8.0.5 p=0 i=13 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
10.8.0.1 255.255.255.255 10.8.0.5 p=0 i=13 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=30800 h=0 m=306/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=30800 h=0 m=306/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=30800 h=0 m=306/0/0/0/0
169.254.0.0 255.255.0.0 169.254.181.152 p=0 i=22 t=3 pr=3 a=30772 h=0 m=286/0/0/0/0
169.254.181.152 255.255.255.255 169.254.181.152 p=0 i=22 t=3 pr=3 a=30772 h=0 m=286/0/0/0/0
169.254.255.255 255.255.255.255 169.254.181.152 p=0 i=22 t=3 pr=3 a=30772 h=0 m=286/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=30800 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 169.254.181.152 p=0 i=22 t=3 pr=3 a=30782 h=0 m=286/0/0/0/0
224.0.0.0 240.0.0.0 10.0.0.6 p=0 i=13 t=3 pr=3 a=30758 h=0 m=281/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=30800 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 169.254.181.152 p=0 i=22 t=3 pr=3 a=30782 h=0 m=286/0/0/0/0
255.255.255.255 255.255.255.255 10.0.0.6 p=0 i=13 t=3 pr=3 a=30758 h=0 m=281/0/0/0/0
SYSTEM ADAPTER LIST
TAP-Win32 Adapter V9
  Index = 22
  GUID = {239556A4-7E56-4030-A7B6-4D6B3D3F315C}
  IP = 169.254.181.152/255.255.0.0 
  MAC = 00:ff:23:95:56:a4
  GATEWAY = 0.0.0.0/255.255.255.255 
  DHCP SERV = 0.0.0.0/255.255.255.255 
  DHCP LEASE OBTAINED = Sun Jan 09 22:24:55 2011
  DHCP LEASE EXPIRES  = Sun Jan 09 22:24:55 2011
  DNS SERV =  
Intel(R) PRO/Wireless 2915ABG Network Connection
  Index = 13
  GUID = {F7760217-38CF-49D8-AC87-76233893D075}
  IP = 10.0.0.6/255.255.255.0 
  MAC = 00:16:6f:09:4e:f4
  GATEWAY = 10.0.0.138/255.255.255.255 
  DHCP SERV = 10.0.0.138/255.255.255.255 
  DHCP LEASE OBTAINED = Sat Jan 08 10:54:01 2011
  DHCP LEASE EXPIRES  = Sat Jan 15 10:54:01 2011
  DNS SERV = 10.0.0.138/255.255.255.255 
Sun Jan 09 22:24:55 2011 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
When I look at the link, I can't find anything about "dhcpclientserv" and when I search the source code for the anchor "dhcpclientserv" I don't find anything.

I have a copy of my error log. It can be found here: http://www.khakkinen.com/error.txt (I can't find a place to attach it here :()

User avatar
krzee
Forum Team
Posts: 729
Joined: Fri Aug 29, 2008 5:42 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by krzee » Mon Jan 10, 2011 8:38 pm

are you sure you are starting openvpn as ADMIN?

User avatar
krzee
Forum Team
Posts: 729
Joined: Fri Aug 29, 2008 5:42 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by krzee » Mon Jan 10, 2011 9:06 pm

http://openvpn.net/index.php/open-sourc ... rorsq.html

that is where the anchor should have taken you, i forwarded this post to someone who should be able to fix the anchors on the faq

khakkinen
OpenVpn Newbie
Posts: 8
Joined: Tue Jan 04, 2011 12:37 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by khakkinen » Sun Jan 16, 2011 9:59 am

I tried those links but nothing worked but my laptop has decided to give up the ghost so I have decided to reinstall Windows XP on it. Thanks for all the help :)

yaun
OpenVpn Newbie
Posts: 1
Joined: Mon Apr 11, 2011 6:15 am

Re: Route: Waiting for TUN/TAP interface to come up...

Post by yaun » Mon Apr 11, 2011 6:25 am

Hi guys,

I have the exact same problem wih windows7!
Everytime I'm trying to connect to OPENVPN servers with client on Windows 7, the first time the client keep logging:
Route: Waiting for TUN/TAP interface to come up...
Then it established connection with errors. I can't go anywhere.

After disconnecting, the second time goes well.

maschwar77
OpenVpn Newbie
Posts: 5
Joined: Wed May 04, 2011 3:35 am

Re: Route: Waiting for TUN/TAP interface to come up...

Post by maschwar77 » Fri May 06, 2011 3:48 pm

Has there been any resolution to this? I am getting the following:

Fri May 06 08:45:08 2011 TEST ROUTES: 2/3 succeeded len=2 ret=0 a=0 u/d=up
Fri May 06 08:45:08 2011 Route: Waiting for TUN/TAP interface to come up...

It will eventually work but it started mysteriously for me too. I am using OpenBSD.

User avatar
krzee
Forum Team
Posts: 729
Joined: Fri Aug 29, 2008 5:42 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by krzee » Thu May 12, 2011 10:01 am

yaun wrote:Hi guys,

I have the exact same problem wih windows7!
Everytime I'm trying to connect to OPENVPN servers with client on Windows 7, the first time the client keep logging:
Route: Waiting for TUN/TAP interface to come up...
Then it established connection with errors. I can't go anywhere.

After disconnecting, the second time goes well.
try adding

Code: Select all

route-delay
to your config

qupfer
OpenVpn Newbie
Posts: 8
Joined: Sat Feb 05, 2011 9:24 am

Re: Route: Waiting for TUN/TAP interface to come up...

Post by qupfer » Fri Nov 25, 2011 11:28 pm

if you have this problem after "playing" with openvpn..check server an client are both in tun (or tap) mode. After testing some openvpn modes, i get this error and yes, server use tun device and client tap :roll:

michaltadeas
OpenVpn Newbie
Posts: 1
Joined: Tue Jan 15, 2013 1:48 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by michaltadeas » Tue Jan 15, 2013 1:51 pm

Hi guys,
I found the solution helped me on another forum ;)

1.Restart the DHCP client service
a.Go to Start > Run, type services.msc , and Click OK. The service manager appears.
b.In the list of services, find and double-click DHCP Client.
c.Set the Startup type to Automatic.
d.If the Service status is Started, click Stop.
e.Click Start.
f.Click OK, and close the service manager.
g.Restart ExpressVPN and try connecting again.

2.If that didn't resolve the problem, reset winsock:
a.Go to Start > All Programs > Accessories, and do one of the following:
■On Windows Vista or Windows 7, right-click Command Prompt and select Run as administrator.
■On Windows XP, click Command Prompt.

b.Run the following commands:
netsh int ip reset logfile.txt
netsh winsock reset catalog

c.Restart the computer.
d.Start ExpressVPN and try connecting again.

Then the Waiting for TUN/TAP interface to come up stopped to loop.
Good luck,
michaltadeas

dbakercalfrac@hotmail.com
OpenVpn Newbie
Posts: 1
Joined: Thu Jun 20, 2013 8:18 pm

Re: Route: Waiting for TUN/TAP interface to come up...

Post by dbakercalfrac@hotmail.com » Thu Jun 20, 2013 8:26 pm

OK i could use some help. i am trying to connect to 2 different servers. i have the additional TAP adapters installed. my client configs reflect the adapter it should use under devnode! this is the log i get with not connection.

i can connect to either server one at a time but not both. the error below is the second client trying to connect. the first is up and running just fine.



Thu Jun 20 15:02:02 2013 TAP-Win32 MTU=1500
Thu Jun 20 15:02:02 2013 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {F0B9D79A-4773-404B-A682-807D23F66FFB} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
Thu Jun 20 15:02:02 2013 Successful ARP Flush on interface [4] {F0B9D79A-4773-404B-A682-807D23F66FFB}
Thu Jun 20 15:02:07 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:07 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:12 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:12 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:13 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:13 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:14 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:14 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:15 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:15 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:16 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:16 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:17 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:17 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:18 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:18 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:19 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:19 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:20 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:20 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:21 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:21 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:22 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:22 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:23 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:23 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:24 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:24 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:25 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:25 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:26 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:26 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:27 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:27 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:29 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:29 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:30 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:30 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:31 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:31 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:32 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:32 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:34 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:34 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:35 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:35 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:36 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:36 2013 Route: Waiting for TUN/TAP interface to come up...
Thu Jun 20 15:02:37 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Thu Jun 20 15:02:37 2013 C:\WINDOWS\system32\route.exe ADD 192.168.1.0 MASK 255.255.255.0 10.8.0.5
Thu Jun 20 15:02:37 2013 Route addition via IPAPI succeeded [adaptive]
Thu Jun 20 15:02:37 2013 C:\WINDOWS\system32\route.exe ADD 10.8.0.1 MASK 255.255.255.255 10.8.0.5
Thu Jun 20 15:02:37 2013 Route addition via IPAPI succeeded [adaptive]
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 10.25.51.1 p=0 i=2 t=4 pr=3 a=287296 h=0 m=20/-1/-1/-1/-1
10.8.0.1 255.255.255.255 10.8.0.5 p=0 i=5 t=4 pr=3 a=0 h=0 m=1/-1/-1/-1/-1
10.8.0.4 255.255.255.252 10.8.0.6 p=0 i=5 t=3 pr=2 a=567 h=0 m=30/-1/-1/-1/-1
10.8.0.6 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=567 h=0 m=30/-1/-1/-1/-1
10.25.51.0 255.255.255.0 10.25.51.51 p=0 i=2 t=3 pr=2 a=287299 h=0 m=20/-1/-1/-1/-1
10.25.51.51 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=287299 h=0 m=20/-1/-1/-1/-1
10.255.255.255 255.255.255.255 10.8.0.6 p=0 i=5 t=3 pr=2 a=567 h=0 m=30/-1/-1/-1/-1
10.255.255.255 255.255.255.255 10.25.51.51 p=0 i=2 t=3 pr=2 a=287299 h=0 m=20/-1/-1/-1/-1
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=287534 h=0 m=1/-1/-1/-1/-1
192.168.0.0 255.255.255.0 10.8.0.5 p=0 i=5 t=4 pr=3 a=567 h=0 m=1/-1/-1/-1/-1
192.168.1.0 255.255.255.0 10.8.0.5 p=0 i=5 t=4 pr=3 a=0 h=0 m=1/-1/-1/-1/-1
224.0.0.0 240.0.0.0 10.8.0.6 p=0 i=5 t=3 pr=2 a=567 h=0 m=30/-1/-1/-1/-1
224.0.0.0 240.0.0.0 10.25.51.51 p=0 i=2 t=3 pr=2 a=287299 h=0 m=20/-1/-1/-1/-1
255.255.255.255 255.255.255.255 10.8.0.6 p=0 i=5 t=3 pr=2 a=287534 h=0 m=1/-1/-1/-1/-1
255.255.255.255 255.255.255.255 10.8.0.6 p=0 i=3 t=3 pr=2 a=287534 h=0 m=1/-1/-1/-1/-1
255.255.255.255 255.255.255.255 10.8.0.6 p=0 i=4 t=3 pr=2 a=287534 h=0 m=1/-1/-1/-1/-1
255.255.255.255 255.255.255.255 10.25.51.51 p=0 i=2 t=3 pr=2 a=287534 h=0 m=1/-1/-1/-1/-1
SYSTEM ADAPTER LIST
TAP-Win32 Adapter V9 #2 - Packet Scheduler Miniport
Index = 4
GUID = {F0B9D79A-4773-404B-A682-807D23F66FFB}
IP = 0.0.0.0/0.0.0.0
MAC = 00:ff:f0:b9:d7:9a
GATEWAY =
DHCP SERV = 255.255.255.255
DHCP LEASE OBTAINED = Thu Jun 20 15:02:24 2013
DHCP LEASE EXPIRES = Sun May 31 10:02:28 1970
DNS SERV =
TAP-Win32 Adapter V9 - Packet Scheduler Miniport
Index = 5
GUID = {08610DA6-8537-4890-AB5A-5688B4D3C587}
IP = 10.8.0.6/255.255.255.252
MAC = 00:ff:08:61:0d:a6
GATEWAY =
DHCP SERV = 10.8.0.5
DHCP LEASE OBTAINED = Thu Jun 20 14:53:01 2013
DHCP LEASE EXPIRES = Sun May 31 10:13:08 1970
DNS SERV =
Intel(R) Centrino(R) Advanced-N 6205 - Packet Scheduler Miniport
Index = 2
GUID = {ECE54DCB-2BAB-417D-ABB5-9F386CE901BF}
IP = 10.25.51.51/255.255.255.0
MAC = a0:88:b4:a8:ae:c0
GATEWAY = 10.25.51.1/0.0.0.0
DHCP SERV = 10.25.4.3
DHCP LEASE OBTAINED = Thu Jun 20 14:53:00 2013
DHCP LEASE EXPIRES = Wed Dec 31 18:00:00 1969
DNS SERV = 10.25.4.3 10.100.4.3
Intel(R) 82579LM Gigabit Network Connection - Packet Scheduler Miniport
Index = 3
GUID = {80C64B9A-F834-4F7A-AE17-D725C1F9A40E}
IP = 0.0.0.0/0.0.0.0 0.0.0.0/0.0.0.0
MAC = 5c:26:0a:6d:e8:fa
GATEWAY =
DNS SERV =
Thu Jun 20 15:02:37 2013 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

Post Reply