BolehVPN Support
Sales Queries => Product Enquiries => Topic started by: ErasmusMundus on February 19, 2014, 08:30:36 AM
-
Hi ! I subscribed yesterday to BolehVPN, and have been trying using the different FullyRouted servers in conjunction with uTorrent. Sadly on the latest Ubuntu version on any server I get only up to 1 MB/s download (I have 175 Mbps up/down without the VPN, and while I don't expect the servers to give me 20 MB/s, I did hope to get at least 5 or 6 MB/s). I'm in Canada and it appears that the Canadian BolehVPN IP is very close to mine, so I hoped I would get better results with it, but funnily enough Netherlands proved to be the best choice (it's the one with which I achieve 1.0 MB/s). Truth be told I'm a bit disappointed as from the different threads and reviews, I got reports of people getting 45 Mbps out of their 50 Mbps connection (yes, I know, there's a difference with Mbps and MBps; the different speed tests give at best around 7 Mbps with the different FullyRouted IPs so anyway it's not a torrent problem). Please tell me that I'm doing something wrong :-(.
(By the way, if I want to torrent on fully routed, I just have to connect to a fully routed IP and then I can use utorrent without any specific configuration without it leaking in case of VPN disconnection, right ? I know, Norton's bad, but I don't want to replace it with Commodore...)
Edit : Maybe I should mention that in the BolehVPN program itself I cannot run speedtests as it gives after a second "Canceled".
-
Try the French, Swiss or Luxembourg servers and see if those give better speeds. Just to double check, you're using the 13.10 Ubuntu torrent, correct?
Post your logs from the BolehVPN client here as well please.
For your fully routed question: Yes that's correct. A firewall solution is just for security in the event that your connection to the VPN server is lost unexpectedly. You can setup a solution using Windows firewall, we have a guide to doing this here http://bolehvpn.net/blocking-non-vpn-traffic.php (http://bolehvpn.net/blocking-non-vpn-traffic.php)
-
Yes, 13.10. So I retried, it seems better today, got speeds up to nearly 3 MB/s (only 1 MB/s for Switzerland/Lux as before, so the very first time I most probably just had forgotten to test the French servers). Logs on the French server :
SUCCESS: download 794 bytes update information to local.
Version Server: 2.4.1
Version Current: 2.4.1
Run script: 0
Checking installed tap driver...
ROOT\NET\0000 : TAP-Windows Adapter V9
1 matching device(s) found.
Use port 44358 as management port
Wed Feb 19 20:50:18 2014 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Jul 31 2013
Wed Feb 19 20:50:18 2014 Control Channel Authentication: using 'C:/Users/XXX/AppData/Local/BolehVPN/cfg/OpenVPN/ta.key' as a OpenVPN static key file
Wed Feb 19 20:50:18 2014 UDPv4 link local: [undef]
Wed Feb 19 20:50:18 2014 UDPv4 link remote: [AF_INET]Some French IP
Wed Feb 19 20:50:26 2014 [server] Peer Connection Initiated with [AF_INET]Some French IP
Wed Feb 19 20:50:29 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Wed Feb 19 20:50:29 2014 open_tun, tt->ipv6=0
Wed Feb 19 20:50:29 2014 TAP-WIN32 device [Local Area Connection] opened: \\.\Global\{BE2BF354-CCB6-4DD1-AD04-93CD70930293}.tap
Wed Feb 19 20:50:29 2014 Set TAP-Windows TUN subnet mode network/local/netmask = 172.16.0.0/172.16.0.95/255.255.255.0 [SUCCEEDED]
Wed Feb 19 20:50:29 2014 Notified TAP-Windows driver to set a DHCP IP/netmask of 172.16.0.95/255.255.255.0 on interface {BE2BF354-CCB6-4DD1-AD04-93CD70930293} [DHCP-serv: 172.16.0.254, lease-time: 31536000]
Wed Feb 19 20:50:29 2014 Successful ARP Flush on interface [6] {BE2BF354-CCB6-4DD1-AD04-93CD70930293}
Wed Feb 19 20:50:39 2014 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Feb 19 20:50:39 2014 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Feb 19 20:50:39 2014 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Feb 19 20:50:39 2014 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Feb 19 20:50:39 2014 Initialization Sequence Completed
Run script: 1
Wed Feb 19 20:55:32 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #19156 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:34 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25176 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:34 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25177 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:34 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25179 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:34 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25182 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:34 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25183 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:35 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25424 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:35 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25426 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:35 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25427 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:35 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25428 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:35 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25430 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:35 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25432 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:35 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #25435 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:36 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #28734 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:36 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #28735 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:36 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #28736 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:36 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #28737 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:36 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #28738 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:36 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #28739 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:36 2014 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #28740 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Wed Feb 19 20:55:36 2014 NOTE: --mute triggered...
-
Are you on wifi? Looks like bad packets to the server, could be your routing. Try the TCP servers and see if this helps
-
No, I'm wired. I cap at about the same values as usual using the TCP servers (in the logs the only things I have are env_blocks adding paths to System32\Wbem).
-
192.99.13.226
46.19.137.130
62.210.162.7
Can you perform ping tests and traceroutes to these IPs? Ping -n 100
-
• 192.99.13.226 ping = 13 ms, 0% loss, and the traceroute gives
Tracing route to ns4010906.ip-192-99-13.net [192.99.13.226]
over a maximum of 30 hops:
1 3 ms 3 ms 5 ms monreseau.home [192.168.2.1]
2 15 ms 5 ms 5 ms 10.11.17.129
3 * 6 ms 4 ms 10.178.206.132
4 5 ms 4 ms 5 ms 10.178.206.133
5 12 ms 12 ms 12 ms bx6-newyork83_xe3-0-0.net.bell.ca [64.230.187.8]
6 * * * Request timed out.
7 * * * Request timed out.
8 15 ms 14 ms 16 ms bhs-g1-6k.qc.ca [198.27.73.205]
9 13 ms * 14 ms bhs-4b-6k.qc.ca [198.27.73.226]
10 14 ms 13 ms 13 ms ns4010906.ip-192-99-13.net [192.99.13.226]
• 46.19.137.130 => 112ms, 0% loss, and traceroute (this one took like a dozen seconds to progress at some point) :
Tracing route to 46.19.137.130 over a maximum of 30 hops
1 3 ms 3 ms 3 ms monreseau.home [192.168.2.1]
2 5 ms 5 ms 5 ms 10.11.17.129
3 * 5 ms 4 ms 10.178.206.132
4 5 ms 5 ms 5 ms 10.178.206.133
5 12 ms 12 ms 12 ms bx6-newyork83_xe2-0-0.net.bell.ca [64.230.187.16
2]
6 12 ms 18 ms 24 ms core1.nyc4.he.net [198.32.118.57]
7 19 ms 20 ms 51 ms 100ge5-1.core1.ash1.he.net [184.105.223.165]
8 98 ms 98 ms 98 ms 10ge9-2.core1.par2.he.net [184.105.213.94]
9 111 ms 113 ms 112 ms 10ge3-2.core1.zrh1.he.net [184.105.222.50]
10 115 ms 115 ms 124 ms private-layer-inc.10gigabitethernet1-4.core1.zrh
1.he.net [216.66.87.10]
11 112 ms 112 ms 112 ms 46.19.137.130
• 62.210.162.7 => 100 ms, 0% loss, traceroute :
Tracing route to sd-57032.webserver.eu.com [62.210.162.7]
over a maximum of 30 hops:
1 3 ms 5 ms 3 ms monreseau.home [192.168.2.1]
2 11 ms 5 ms 11 ms 10.11.17.129
3 * 5 ms 4 ms 10.178.206.132
4 5 ms 4 ms 4 ms 10.178.206.133
5 5 ms 4 ms 5 ms bx4-montrealak_xe2-0-0_0.net.bell.ca [64.230.32.
145]
6 202 ms * * level3_bx4-montrealak.net.bell.ca [67.69.246.110
]
7 96 ms 98 ms 95 ms ae-11-11.car1.Montreal2.Level3.net [4.69.141.2]
8 100 ms 99 ms 100 ms ae-5-5.ebr2.NewYork1.Level3.net [4.69.141.6]
9 97 ms 97 ms 97 ms ae-47-47.ebr2.NewYork2.Level3.net [4.69.201.34]
10 98 ms 98 ms 98 ms ae-1-100.ebr1.NewYork2.Level3.net [4.69.135.253]
11 98 ms 98 ms 98 ms ae-37-37.ebr2.Washington1.Level3.net [4.69.132.8
9]
12 97 ms 97 ms 97 ms ae-43-43.ebr2.Paris1.Level3.net [4.69.137.57]
13 98 ms 98 ms 98 ms ae-62-62.csw1.Paris1.Level3.net [4.69.161.94]
14 99 ms 105 ms 99 ms ae-1-60.edge5.Paris1.Level3.net [4.69.168.8]
15 97 ms 98 ms 98 ms 213.242.121.42
16 101 ms 99 ms * 45x-s31-1-4090.dc3.poneytelecom.eu [195.154.1.35
]
17 100 ms 99 ms 100 ms sd-57032.webserver.eu.com [62.210.162.7]
Edit : maybe you should move the thread to General Support ?
-
I see. Could you try the XCloak Routed servers as well? Will escalate your case to my superior.
-
I get roughly the full speed of my connection on the xCloakProxy Canada. On the xCloakRouted Canada though I get back to the same slow speeds as the fully routed connection.
-
XCloak-Proxy, is this with proxy settings configured in your torrent client?
-
ErasmusMundus,
I am also in montreal using a VL cable reseller as an ISP and am experiencing the exact same issue.
Speeds are maxed when not connected to boleh. When connected to any Fully Routed server, the speeds cap at 1Mbit (~160KB/s).
I know you are new to Boleh. In my case I have been a subscriber for more than 2 years and it JUST started doing this last week.
I have asked the ISP if they throttle VPN, and they swear up and down they do not:
http://www.dslreports.com/forum/r29057694-Cable-Ebox-Videotron-throttling-VPN. (http://www.dslreports.com/forum/r29057694-Cable-Ebox-Videotron-throttling-VPN.)
Here's my thread:
http://www.bolehvpn.net/forum/index.php?topic=7677.0 (http://www.bolehvpn.net/forum/index.php?topic=7677.0)
Hopefully we can get some resolution.
Chris has suggested I tru a canada or US fully routed server, and then try xcloak fully routed. I will experiment some more tonight and post results.
-
XCloak-Proxy, is this with proxy settings configured in your torrent client?
I speedtest'd this one to my max speed. Indeed though, I might be missing the configuration of the proxy in my browser ? (when I speedtested the fully routed connections both close to me and the VPN geo location, I got ~15 Mbps)
Speeds are maxed when not connected to boleh. When connected to any Fully Routed server, the speeds cap at 1Mbit (~160KB/s).
I get between 1 and 2 MB/s at best, not Mb/s luckily. I am with Bell, but I really do not think the ISP would (could?) throttle VPN traffic.
-
Could we stick with the Ubuntu torrent test for speed test? You can also use www.testmy.net (http://www.testmy.net) instead, make sure you choose a server closest to the VPN location first before running the test.
Also just double check that you haven't inadvertently set a limit on uTorrents download speed as well.
-
The results of the speedtest should not really vary from those of Ubuntu or testmynet. Anyway it seems that, as of today, I can't connect to any xCloak server.
-
We did some maintenance on our XCloak servers, you'll have to update your configurations. Go to the Settings tab, hit Update configurations and you should be good to go after that.
-
OP out of curiosity what kind of router do you have installed?
-
The default Sagemcom (not really)f@st 2864. Btw updated the config files for the vpn client, still getting the same speeds.
-
do you have access to any other routers? still testing but i think my router is the culprit
-
I don't know much about routers, so I may be wrong, but I don't think there is any reason why the router would prefer non-VPN traffic to VPN traffic, as I have no trouble maxing my dl speed no matter where a server is, as long as their upload speeds are sufficiently higher than my bandwidth; and anyway my router doesn't even have QoS to discriminate my internet traffic. Also I the speeds on different devices, but I still get a disappointing 1-2 MB/s depending on the server.
-
There has been discussion that some unix or linux-based routers can benefit from what is called TCP fast forwarding.
https://forum.pfsense.org/index.php?topic=47567.0
I will try the setting as soon as I can
-
Your router might not support the setting, but internally, the routing code might be affected by it.
-
I had the best results on french servers