OpenVPN connects, stays connected, but can't access network resources

[polaris20]

Hello,

Untangle 6.2 user here. I've got the OpenVPN system configured for the defaults (172.16.0.0, default network).

It didn't want to connect before, but that turned out to be the DSL combo router/modem crap my ISP gave me (they refuse to give me a straight modem). I did a port forward of 1194 UDP to the internal static IP address of the Untangle server, and bingo: connects great, assigns an IP of 172.16.0.5. At this point it stays connected, however I cannot ping or access anything in the internal network; PC's, NAS, etc. I actually cannot even ping the Untangle server itself.

Any ideas? This is so smooth in how it works for configuration, but obviously a bummer that I cannot connect to anything.

FYI the network behind the Untangle box that I'm attempting to access is a class C 192.168.0.0 network.

[dmorris]

make sure that your network is in the 'exported hosts' list.

does untangle show that the client is connected?
what does the routing table on the host?
is the remote host on a different ip network than your network?

welcome to the forums

[polaris20]

Originally Posted by dmorris

make sure that your network is in the 'exported hosts' list.

does untangle show that the client is connected?
what does the routing table on the host?
is the remote host on a different ip network than your network?

welcome to the forums

1. Yes, that network is exported.
2. Yes, it shows as being connected
3. Remote client is on different IP range than local
4. Need to get the routing table

I just thought of something that could be potentially boneheaded of me; do I need a class B, with say a local 192.168.0.0 on the local side with untangle assigning something like a 192.168.2.0 on the remote client?

I think I made a fundamental networking blunder.

[WebFooL]

Hi,

From a client on the Internel interface tracert the VPN Ip (172.16.0.5)
Post Output.

From the VPN client tracert a internal IP.
Post Output.

On the Untangle go to Config>Networking> Advanced then Route.
Post a Screenshot.

[polaris20]

Here's the route table from the UT box. Need to still get the tracert outputs.

[polaris20]

I think I know what the problem is......stupidly high latency. See attached tracert from outside VPN client.

I got access to my NAS on the inside of my network; however it showed the two available shares (in Windows explorer) but when I actually tried to access it, it says it was inaccessible. The tracert leads me to believe the latency is really what's causing the problems.

[dbrine]

Are you able to access your resources now? I'm having the same problem

[polaris20]

No, still having the same issue. It connects just fine, immediately. But everything times out. Very disappointing, because I'm so close!!

[sky-knight]

Polaris...

You are running NAT off the DSL router then forwarding to an Untangle Bridge?

If this is the case, you need a static route in the DSL router to redirect local traffic bound for the VPN segment to the Untangle.

Then, I must ask what you are using for a VPN client, and what OS it is installed on.

[polaris20]

Originally Posted by sky-knight

Polaris...

You are running NAT off the DSL router then forwarding to an Untangle Bridge?

If this is the case, you need a static route in the DSL router to redirect local traffic bound for the VPN segment to the Untangle.

Then, I must ask what you are using for a VPN client, and what OS it is installed on.

1. Yes, port forwarded from DSL router/modem to UT box via port 1194, as noted in Wiki. Have not done the static route from DSL to UT though.
2. Prepackaged OpenVPN software downloaded from the UT box; I wanted to get that running before I muck with it on Ubuntu and OS X (w/ Viscosity)