it works in pclinuxos on another machine and it works on this machine in windows but when i start it here in linux mint i loose my internet , although it doesnt give any errors

i asked around in irc and someone told me to add this line to my config file>
up /etc/openvpn/update-resolv-conf

i had to add extra arguments so it would accept that line , no errors but no internet, so i left it as it was

this is the log to the default command>

http://pastebin.com/bJhUnEGU

thanx

(i tested it with a bodhi livecd too with almost the same result except that i noticed that google partially worked, very partially)

Isn't the point of a VPN to secure the connection?

something like that, so?

when you bring the VPN up can you ping the other end of it?
the command will likely be like 'ping -i tap0 178.73.206.129' (ping the remote end of the tunnel out the tunnel interface.
If that works, then most likely it is a routing issue. Otherwise your VPN is not up.

rastiazul@rastiazul ~ $ ping -i tap0 178.73.206.129
ping: bad timing interval.

rastiazul@rastiazul ~ $ ping 178.73.206.129
PING 178.73.206.129 (178.73.206.129) 56(84) bytes of data.
64 bytes from 178.73.206.129: icmp_seq=1 ttl=62 time=210 ms
64 bytes from 178.73.206.129: icmp_seq=2 ttl=62 time=211 ms
64 bytes from 178.73.206.129: icmp_seq=3 ttl=62 time=213 ms
^C

Do the ping test after you have enabled the VPN. If you have enabled it and the ping succeeds without the -i tap0 option then you have internet access from your box with the VPN up, just not through the VPN. Unless the interface name is not correct, check with 'ip addr' or ifconfig. Is tap0 the interface with the .223 address?

As far as I can tell, you have the .223 address locally and the .129 at the remote end of the tunnel.
The routes that are being set up above as part of the VPN make the remote end of the tunnel the default gateway. So if you VPN is not up you will not have internet access.

I partially understand you, anyway if config doesnt show any .223 address, this is the tap0:

tap0 Link encap:Ethernet direcciónHW 4a:5f:d8:b1:6f:33
Direc. inet:188.126.74.171 Difus.:188.126.74.255 Másc:255.255.255.128
Dirección inet6: fe80::485f:d8ff:feb1:6f33/64 Alcance:Enlace
ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST MTU:1500 Métrica:1
Paquetes RX:24 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:21 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:100
Bytes RX:3150 (3.1 KB) TX bytes:4243 (4.2 KB)

and all the output if you need>
http://pastebin.com/TysXWSPT

I thought tap0 is your vpn tunnel interface when it actually is just another ethernet interface.

Can you post the contents of /etc/openvpn/vpnname.conf? Obviously replace vpnname with whatever you have and mask any sensitive information.

there is no tap0 when the vpn is off

/etc/openvpn/update-resolv-conf:
http://pastebin.com/SyvCyAM4 (i dont know which info is sensitive....)

did you meant that file of the vpn conf file provided by the vpn company?

Yes.

If this is a commercial product, do they not support it? If your linux distro is not supported by them, then it is likely the setup scripts will need to be modified to get this to work, or it might not be possible at all.

in their guide they have instructions for ubuntu and debian so there shouldnt be problems

http://pastebin.com/B1ME6KUt

Hi rastiazul,

I think this is your "problem":
When you connect to the server, openvpn pushes back the default gateway to the client machine. (route add net)

You can change this behaviour here: /etc/openvpn/server.conf
Just put ; (rem) to the front of that line and only the 10.8.0.0(default openvnp server) network will be routed to the server.
The rest will be routed to the local gateway.

Like that:
Or if you want to add private networks you could do that with this command:
Then it will add this private network to the routing table on the client machine.

Take a look for more explanation here:
http://openvpn.net/index.php/open-so....html#redirect

I hope it helps.

Laz

hi laz.

the only file in /etc/openvpn/ is update-resolv-conf and it doesnt have the line you mentioned (i posted the contents of that file here previously)

and the vpn conf file doesnt contain that line eather, i posted it in my previous post

Hi rastiazul,

I had a look again your config and the reason you didn't find this because this one is at the server side.
You can't change this behaviour on the client side only at the server side.
When the client logging in to the server the config will run the route add command which is adding the remote gateway into the local routing table. (obviously it depends on the config how this behaves)

I had routing problem on my config when I installed openvpn and this was the issue in my config too.
When the redirect-gateway was in my config and I tried to reach a local PC on the LAN the whole traffic went through on the vpn.
I had checked it with tcpdump and I was really surprised about this behaviour. For example I pinged a local pc and the traffic went through on the server/vpn.

So check the server side instead of client side.

i dont have access to the server but if it works on other machines, it should work on here