Connection hangs

Got a problem with Viscosity or need help? Ask here!

4jeg

Posts: 1
Joined: Sun Jun 28, 2009 2:45 pm

Post by 4jeg » Sun Jun 28, 2009 2:49 pm
So I recently set up an OpenVPN server via dd-wrt. I was able to connect just fine when using that network, but having moved to another network I cannot connect. Here's my log:

Sun Jun 28 00:41:33 2009: IMPORTANT: OpenVPN's default port number is now 1194
Sun Jun 28 00:41:33 2009: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Sun Jun 28 00:41:33 2009: LZO compression initialized
Sun Jun 28 00:41:33 2009: TUN/TAP device /dev/tap0 opened
Sun Jun 28 00:41:33 2009: /Applications/Viscosity.app/Contents/Resources/dnsup.py tap0 1500 1577 init
Sun Jun 28 00:41:34 2009: UDPv4 link local (bound): [undef]:1194
Sun Jun 28 00:41:34 2009: UDPv4 link remote: 69.157.64.249:1194

...and it just stays at that last part. I am 'assigned' a client IP, but it seems locally generated (i.e. 168.254.164.133).

Now, the network I'm on uses the same addressing scheme (192.168.1.1), so perhaps that's part of it?

Any help would be great!

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Mon Jul 06, 2009 7:14 pm
Now, the network I'm on uses the same addressing scheme (192.168.1.1), so perhaps that's part of it?
If both the VPN network and your local network use the same IP range, then yes, this is most likely the problem. At any rate, even if it wasn't you'd probably run into routing issues once you are assigned an IP address. I'd recommend changing the IP range of either your local network, or your remote VPN network if possible.

I'd also recommend checking that your DHCP server is fully functioning, and that the bridge on the server (as it appears to be a bridged TAP connection) is still working. One of the most command reasons for a self-assigned IP address when using a TAP connection is that the bridge has gone down.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
2 posts Page 1 of 1