filipovics
It's in the bridge. The bridge contains the eth and the tap interfaces. I don't now, why it doesn't show in ipconfig ...
I rechecked the birdge properties and lan1 - tap are checked. TAP's description:
TAP-Windows Provider V9
Traffic
My apologies ..
Infact when the bridge is created ipconfig does not show the interfaces which are included ..
I am getting too used to Linux :roll:
A suitable alternative is: (Command prompt) > netsh bridge show adapter
filipovics
It says this:
C:\Windows\system32>netsh bridge show adapter
----------------------------------------------------------------------
ID AdapterFriendlyName ForceCompatibilityMode
----------------------------------------------------------------------
1 TAP disabled
2 LAN1 disabled
----------------------------------------------------------------------
C:\Windows\system32>
It's interesting, why is it like this. In console it shows, the bridge is OK. How can it be?
filipovics
I enabled them:
C:\Windows\system32>netsh bridge set adapter 1 forcecompatmode=enable
C:\Windows\system32>netsh bridge set adapter 2 forcecompatmode=enable
C:\Windows\system32>netsh bridge show adapter
----------------------------------------------------------------------
ID AdapterFriendlyName ForceCompatibilityMode
----------------------------------------------------------------------
1 TAP enabled
2 LAN1 enabled
----------------------------------------------------------------------
But now openvpn doesn't start up:
Fri Apr 17 22:19:17 2015 Warning: cannot open --log file: openvpn.log: A folyama
t nem fér hozzá a fájlhoz, mert azt egy másik folyamat használja. (errno=32)
Fri Apr 17 22:19:17 2015 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO]
[PKCS11] [eurephia] [IPv6] built on Aug 7 2014
Fri Apr 17 22:19:17 2015 NOTE: when bridging your LAN adapter with the TAP adapt
er, note that the new bridge adapter will often take on its own IP address that
is different from what the LAN adapter was previously set to
Fri Apr 17 22:19:17 2015 NOTE: your local LAN uses the extremely common subnet a
ddress 192.168.0.x or 192.168.1.x. Be aware that this might create routing conf
licts if you connect to the VPN server from public locations such as internet ca
fes that use the same subnet.
Fri Apr 17 22:19:17 2015 Diffie-Hellman initialized with 1024 bit key
Fri Apr 17 22:19:17 2015 Socket Buffers: R=[65536->65536] S=[65536->65536]
Fri Apr 17 22:19:17 2015 TCP/UDP: Socket bind failed on local address [undef]: A
ddress already in use (WSAEADDRINUSE)
Fri Apr 17 22:19:17 2015 Exiting due to fatal error
Press any key to continue...
Traffic
Before you get carried away .. I doubt that you need compatibility mode on the server bridge.
The problem is most likely the client as your logs show that the ip address is pushed to the client
and the client log shows that openvpn tries to set the ip address.
But for some reason fails ?
Traffic
First:
- On client try: (Command prompt) > net start dhcp
post result ..
Second:
- Your client log:
Fri Apr 17 10:28:34 2015 OpenVPN 2.3.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Dec 1 2014
This can be updated ..
You are using the NDIS-6 openvpn version:
- Installer (64-bit), Windows Vista and later :: openvpn-install-2.3.6-I603-x86_64.exe
TAP-Windows Driver Version 9.21
You could try the NDIS-5 openvpn version:
- Installer (64-bit), Windows XP and later :: openvpn-install-2.3.6-I003-x86_64.exe
TAP-Windows Driver Version 9.9 (I believe)
http://openvpn.net/index.php/download/community-downloads.html
Finally:
