hi,

i've tried a few different vpns on debian 7 and ubuntu 12.04 but keep coming up with the same problem.

p2p runs at it's full 500kb/s (i live in a village, crap internet!) but even when deluge isn't running, my browser doesn't have enough bandwidth to load facebook, or go past the first page of a google search.

speed test gives 3mb/s, is normal-ish.

why do i have internet in deluge but not in chrome, firefox or iceweasel?

currently running btguard from terminal.

i'm guessing here, but i've also had that recently where my browser didn't get past the google page and in my case it had to do with the DNS servers of my ISP..

after i changed them to google's DNS servers ( or open DNS )everything was running smooth again..

i have no idea how to do that! could you help? i get this error message when connecting,

WARNING: potential route subnet conflict between local LAN [10.10.10.0/255.255.255.0] and remote VPN [10.10.10.1/255.255.255.255]
Sun Apr 13 21:36:51 2014 /sbin/route add -net 10.10.10.1 netmask 255.255.255.255 gw 10.10.10.161

it still connects though, with full speed on p2p. the speed test website also detects it as full speed.

you were able to connect to that website using your vpn now ?

that error message is a different problem i know nothing about, but that DNS server change can be done in /etc/resolv.conf if you look in that file now you'll probably see 2 name servers assigned by your ISP...just to do a quick check i would just use either google's or opendns' servers..all you have to do is edit that file and place 1 of these on top


nameserver 8.8.8.8
nameserver 8.8.4.4

nameserver 208.67.222.222
nameserver 208.67.220.220



i'm not familiar with the distros you are using and when you reboot your system will probably change it back but that would show you if your problem has anything to do with this.. afterwards you could have a look how to do it in such a way that it stays that way

if changing them doesn't help then then i'd start looking into that error message..

this is my file:

# Generated by NetworkManager
domain dlink.com
search dlink.com
nameserver 192.168.1.1

what exactly should i do with it? i don't want to risk losing my internet!

thanks

i'm looking at resolvconf to deal with the nameservers for me, to potentially remove the conflict that the error message is putting out. Reading about it, it says that programs can conflict when rewriting resolv.conf. It seems like a good idea until it says you can't get rid of it.

I'm in over my head, any ideas as to whether this is system suicide?

i don;t have a clue if changing DNS servers will even work..so no need to worry about making things permanent yet..to test it all you have to is copy 1 of those i posted and paste them above the ones you have in your file right now..fire up your VPN and see if it worked..if not, you can just change it back to what it was and you'll know you need to find another solution..you seem to be a little scared ? probably had some bad experiences in the past ?

..i only started my linux career 3 months ago and already had to resurrect myself like 5 times aha..trial and error / falling and getting up is a good way to learn things though

i tried all of the above nameservers to no avail. this forum and imdb still work while facebook and twitter don't.

i have a healthy respect for conf files and their unique ability to completely bugger up my system. while i am now proficient in reversing changes from rescue terminal, i am wary of edits suggested outside of how-to's. it's no offence to you at all, i just wanted to make exactly sure what I was to do.

i totally understand what you mean about being careful with altering conf files, so no offence taken..the fact that you are able to access this site means the DNS servers aren't the problem, if they were you wouldn't have access at all..


..think it has to do with that error message then..lol i just did a quick google and the first result i saw was your's on debian's user formum..so i guess you're already getting help fixing that..i saw they already offered a solution also, so let's hope that's gonna fix it..good luck