Hi folks, I've some strange behaviour (at least in my opinion ;) ). First of all my config: (source: [url]http://wiki.openvpn.eu/index.php/Config_ServerNET_ClientNET[/url], german) Windows 10 PC, acting as server (192.168.35.23) behind a avm fritzbox router (192.168.35.1) Config file: [code]port 1194 proto udp dev tap server 10.10.35.0 255.255.255.0 dh dh1024.pem pkcs12 cert.p12 client-config-dir "c:\\program files\openvpn\config" keepalive 10 60 route 192.168.10.0 255.255.255.0 push "route 192.168.35.0 255.255.255.0"[/code] Client config file "DEFAULT.": [code]iroute 192.168.10.0 255.255.255.0 [/code] Windows 7 PC, acting as client (192.168.10.222) behind a whatevernamed-router (192.168.10.1): [code]port 1194 proto udp dev tap client remote serverurl.domain pkcs12 clientcert.p12[/code] --- Now the tunnel is working properly, so the dial in works and also the vpn-ips (10.10.35.1 & 10.10.35.2) can be pinged from client and server. But the routing does not work. From the windows 7 computer I can ping 192.168.35.23, from the windows 10 pc the 192.168.10.222 is not reachable. Here are some things I tried: * Of course all firewalls are completly disabled * Added the route 192.168.10.0/24 via 10.10.35.1 to the server pc manually * Routing and RAS service is started on both computers (for routing) If I use [url]tracert 192.168.10.222[/url] on the windows 10 machine, I can see that all the traffic is send to the router 192.168.35.1 and not to the vpn adapter ALTHOUGH there is a route entry to do so. Does anybody have an answer for that behaviour? Is that a windows 10 issue?

No logs and no routing tables ... :roll: However ..[quote="dpt"][code]client-config-dir "c:\\program files\openvpn\config"[/code][/quote]to be honest, I am surprised openvpn even starts with this config line .. Try:[code]client-config-dir "c:\\program files\\openvpn\\config"[/code]or[code]client-config-dir "c:/program files/openvpn/config"[/code]Yes "/" is compatible with windows. Please see this: [url=http://openvpn.net/index.php/open-source/documentation/howto.html#scope]HOWTO: Expanding the scope of the VPN to include additional machines[/url]

Your server log at --[b]verb 4[/b] would be most useful .. (as per the [color=#A40000]Forum Rules[/color]) It [i]looks like[/i] your CCD file DEFAULT is not being parsed ..

Sorry guys for answering so late, I've found my mistake. [quote="dpt"]* Added the route 192.168.10.0/24 via 10.10.35.1 to the server pc manually[/quote] This was the mistake, of course I have to add this route via 10.10.35.2 (Client IP) and not the Server-IP! [quote="Traffic"]It [i]looks like[/i] your CCD file DEFAULT is not being parsed ..[/quote] Yes, you are also right, I saw that the IROUTE command only works with TUN devices. But setting the route manually worked fine (of course THEN I have to use fixed IPs for the client ;) ) Thanks for your suggestions!!

Windows 10 routing behaviour

dpt

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

Traffic

No logs and no routing tables ... :roll:

However ..

dpt wrote

client-config-dir "c:\\program files\openvpn\config"

to be honest, I am surprised openvpn even starts with this config line ..

Try:

client-config-dir "c:\\program files\\openvpn\\config"

client-config-dir "c:/program files/openvpn/config"

Yes "/" is compatible with windows.

Please see this:
HOWTO: Expanding the scope of the VPN to include additional machines

dpt

Sorry, typo: of course there are two backslashes...

client-config-dir "c:\\program files\\openvpn\\config"

I don't have routing tables available at the moment because I'm not at that office. Next week I can post them, I thought perhaps I have something wrong in my thoughts or so...

thanks!

Traffic

Your server log at --verb 4 would be most useful .. (as per the Forum Rules)

It looks like your CCD file DEFAULT is not being parsed ..

dpt

Sorry guys for answering so late, I've found my mistake.

dpt wrote* Added the route 192.168.10.0/24 via 10.10.35.1 to the server pc manually

This was the mistake, of course I have to add this route via 10.10.35.2 (Client IP) and not the Server-IP!

Traffic wroteIt looks like your CCD file DEFAULT is not being parsed ..

Yes, you are also right, I saw that the IROUTE command only works with TUN devices. But setting the route manually worked fine (of course THEN I have to use fixed IPs for the client 😉 )

Thanks for your suggestions!!