search

xingplus / tunnelblick

Automatically exported from code.google.com/p/tunnelblick
0 stars 0 forks source link

In version 3.0b10, connection initializes, but routes are not set properly. #59

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
Using my config file, i connect to server. Connection initializes properly.
I try to connect to servers behind VPN, but I can't -- routes are not set.
traceroute shows my long way rather than short way through tunneled gateway. 

What is the expected output? What do you see instead?

These messages might be related to what's going on:
...
Fri 11/28/08 07:55 AM: [vpn.worldnews.com] Peer Connection Initiated with 
195.149.84.230:6601
Fri 11/28/08 07:55 AM: Options error: route parameter gateway 'default' must be 
a valid address
Fri 11/28/08 07:55 AM: Options error: route parameter gateway 'default' must be 
a valid address
Fri 11/28/08 07:55 AM: Options error: route parameter gateway 'default' must be 
a valid address
Fri 11/28/08 07:55 AM: Options error: route parameter gateway 'default' must be 
a valid address
Fri 11/28/08 07:55 AM: TUN/TAP device /dev/tun0 opened
...
(other messages)

These messages didn't appear on previous version.

What version of Tunnelblick are you using? On what version of OS X? PPC or 
Intel?
OS X 10.5.5 Intel

Please provide any additional information below.
Providing correct log of 3.0b9 and wrong log of 3.0b10.
This issue might be related to openvpn library update.

Original issue reported on code.google.com by burc...@gmail.com on 28 Nov 2008 at 2:20

Attachments:

GoogleCodeExporter commented 9 years ago 
can you post your openvpn config file as well? Maybe an option needs to be 
updated to work with openvpn 2.1.

Original comment by angelol...@gmail.com on 28 Nov 2008 at 9:14

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Resolved. It was because of old 2.0 TLS certificate, that was not accepted by 
2.1. 
After replacing it with newer certificate, it worked. With server version 2.0.9.

Original comment by burc...@gmail.com on 16 Dec 2008 at 5:35

GoogleCodeExporter commented 9 years ago 
I'm still having the problem. New to VPN and Tunnelblick. I got all 
configuration files from the provider. Any 
advice on what I need to do/change?

Original comment by franz1...@gmail.com on 10 Jan 2009 at 5:17

GoogleCodeExporter commented 9 years ago 
I also have the same problem, what info do you need from me in order to resolve 
this
issue?
Below is my config-file:

client
dev tap
proto tcp
remote XXX.XXX.XXX.XXX 1314
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt
cert client-XXX-XXX.crt
key client-XXX-XXX.key
comp-lzo

Original comment by thomas.n...@gmail.com on 2 Mar 2009 at 8:32

GoogleCodeExporter commented 9 years ago 
@franz1234 and @thomas.nikitin:

What do you mean by the same problem? Are you getting the "Options error: route 
parameter gateway 'default' must be a valid address" message?

@franz1234:
Are you using tap also?

Original comment by jkbull...@gmail.com on 1 Aug 2010 at 1:43

GoogleCodeExporter commented 9 years ago 
Abandoned because of no response from reporter

Original comment by jkbull...@gmail.com on 9 Sep 2010 at 12:14