Hello, Im running into an issue where the LAN subnet where the OpenVPN server resides cannot reach devices/networks that are connected via OpenVPN. The OpenVPN server is standalone (not the same device as the gateway) Details: LAN: 192.168.0.0/24 OpenVPN Server: 192.168.0.109 Other devices on the same LAN can reach 192.168.0.109 but cannot go further reach devices that are connected to VPN (the 192.168.3.X and 192.168.4.x networks). Devices that are connected via OpenVPN can reach each other fine and the other networks without issue. I suspected it's a missing static route on the LAN gateway, I added 10.8.0.0/24 into my ASUS router but no change. Server Config: server 10.8.0.0 255.255.255.0 proto udp port 1194 dev tun cipher BF-CBC comp-lzo adaptive keepalive 15 60 verb 3 push "route 192.168.0.0 255.255.255.0" client-config-dir ccd client-to-client #duplicate-cn route 192.168.3.0 255.255.255.0 push "route 192.168.3.0 255.255.255.0" route 192.168.4.0 255.255.255.0 push "route 192.168.4.0 255.255.255.0" tls-auth static.key 0 ca ca.crt dh dh.pem cert server.crt key server.key status-version 2 status status route-delay 5 route-method exe Any ideas? Windows firewall is disabled, I also performed the registry edit to enable routing on Windows 7 as well as right clicking the LAN network and sharing it with the TAP adapter. Thanks

if you use your openvpn server as default gateway , do you access vpn clients? if not check win7 firewall (if any) Michael.

Thanks for the reply - my gateway (192.168.0.254) is a different device on the network. I also have the Windows 7 firewall disabled. Any other suggestions I could try? Thanks

[quote]my gateway (192.168.0.254) is a different device on the network[/quote] ok, can you for testing switch your default gateway to point to your openvpns servers lan ip? Michael.

Sure Michael - I changed the default gateway on one of the workstations and pointed it towards the OpenVPN server. Once that was performed, I could then access the other networks and devices without issue (the 192.168.3.x and 192.168.4.x networks) Once I reverted the workstation back to its normal gateway (192.168.0.254) I could no longer ping or access those networks. Seems like a routing issue between the default gateway - but a static route doesn't seem to resolve it either. Network: 10.8.0.0 Subnet: 255.255.255.0 Metric: 1 Gateway: 192.168.0.109 (VPN Server) Thats the static route I tried, but no change.

[quote]but a static route doesn't seem to resolve it either.[/quote] your static route looks ok,where exactly did you add it? Michael.

It was added via the GUI of the Asus router (192.168.0.254) Thanks

try adding it to a pc on your lan. also disable any firewall running on your router while testing. Michael.

Adding the static route directly on the workstation? I've also cobbled together a diagram which may help explain the issue. Thanks again [img]http://i62.tinypic.com/14dhl5u.png[/img] Larger Image: [url]http://i58.tinypic.com/2ebwns0.png[/url]

FYI - I did add a static route directly on the workstation (192.168.0.1) and now it works :D : C:\Users\test>route add 192.168.4.0 mask 255.255.255.0 192.168.0.109 metric 1 Can you help me understand why that worked and how I can work to have it resolved without adding manual routes to all the other devices which are currently disconnected from the switch? Thanks

@ jprez1980 [list]NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create [b]routing conflicts[/b] if you connect to the VPN server from public locations such as internet cafes that use the same subnet.[/list]

[Solved]Windows 7 OpenVPN Server - LAN Issue

Traffic

jprez1980 wroteI would have thought a more upscale Asus would have handled static routes better...

hehe .. would have . been there .. [expletive deleted] .. upgraded !

FYI:

$500 Juniper device which does not redirect
Netgear DSL Router for 10c from a boot sale which does ...

Security .. apparently !

maikcat

watchguard IS one of the best firewall appliances and is based on linux since i
first saw them back in 2003....

Michael.

« Previous Page