BolehVPN Support
Sales Queries => Product Enquiries => Topic started by: ian on May 23, 2010, 05:09:45 AM
-
hi i signed up earlier for the 3 day trial but not recieved any details as yet ?
just the email from paypal saying that ive paid
can someone contact me please
cheers
-
Can you check your spambox/junk mail if you are using hotmail or yahoo? If not, please give an alternate email than we can send it to.
-
found it just working out how to use it now :S got all the certficates and stuff now just need to get the software
thanks
-
http://www.speedtest.net/result/823118242.png
not good at all is there any other ips i can try ?
-
You could try reconnecting your own internet to get an IP with better routing to the US. What's the purpose of you using our service, speedier surfing?
-
http://www.speedtest.net/result/823337335.png < using ur vpn
http://www.speedtest.net/result/823338308.png < without vpn
http://www.speedtest.net/result/823343842.png < with my other vpn provider
u can see the difference from urs and theres
and i use it for surfing and watching hulu and other usa tv networks
i also will be using it for p2p traffic thats why i thought id try ur service out but looking at the speeds its pretty dismall
unless u can offer me some other ips so i can try
-
There is no problem from the US server, its from streamyx having issues.
[root@SeattleVPN ~]# ping 218.111.7.189 - to streamyx 4mbit
PING 218.111.7.189 (218.111.7.189) 56(84) bytes of data.
64 bytes from 218.111.7.189: icmp_seq=1 ttl=53 time=358 ms
64 bytes from 218.111.7.189: icmp_seq=2 ttl=53 time=344 ms
64 bytes from 218.111.7.189: icmp_seq=3 ttl=53 time=365 ms
64 bytes from 218.111.7.189: icmp_seq=4 ttl=53 time=364 ms
64 bytes from 218.111.7.189: icmp_seq=5 ttl=53 time=363 ms
64 bytes from 218.111.7.189: icmp_seq=7 ttl=53 time=336 ms
64 bytes from 218.111.7.189: icmp_seq=9 ttl=53 time=366 ms
64 bytes from 218.111.7.189: icmp_seq=10 ttl=53 time=343 ms
64 bytes from 218.111.7.189: icmp_seq=11 ttl=53 time=365 ms
64 bytes from 218.111.7.189: icmp_seq=12 ttl=53 time=358 ms
Now, this ping to Streamyx Corp Fix-IP
[root@SeattleVPN ~]# ping 219.95.177.174
PING 219.95.177.174 (219.95.177.174) 56(84) bytes of data.
64 bytes from 219.95.177.174: icmp_seq=1 ttl=51 time=300 ms
64 bytes from 219.95.177.174: icmp_seq=2 ttl=51 time=300 ms
64 bytes from 219.95.177.174: icmp_seq=3 ttl=51 time=301 ms
64 bytes from 219.95.177.174: icmp_seq=4 ttl=51 time=296 ms
64 bytes from 219.95.177.174: icmp_seq=5 ttl=51 time=301 ms
64 bytes from 219.95.177.174: icmp_seq=6 ttl=51 time=324 ms
64 bytes from 219.95.177.174: icmp_seq=7 ttl=51 time=321 ms
64 bytes from 219.95.177.174: icmp_seq=8 ttl=51 time=299 ms
64 bytes from 219.95.177.174: icmp_seq=9 ttl=51 time=301 ms
64 bytes from 219.95.177.174: icmp_seq=10 ttl=51 time=323 ms
And now, to the tmnet datacenter,
[root@SeattleVPN ~]# ping 202.71.104.165
PING 202.71.104.165 (202.71.104.165) 56(84) bytes of data.
64 bytes from 202.71.104.165: icmp_seq=1 ttl=52 time=280 ms
64 bytes from 202.71.104.165: icmp_seq=2 ttl=52 time=302 ms
64 bytes from 202.71.104.165: icmp_seq=3 ttl=52 time=280 ms
64 bytes from 202.71.104.165: icmp_seq=4 ttl=52 time=302 ms
64 bytes from 202.71.104.165: icmp_seq=5 ttl=52 time=286 ms
64 bytes from 202.71.104.165: icmp_seq=6 ttl=52 time=302 ms
64 bytes from 202.71.104.165: icmp_seq=7 ttl=52 time=302 ms
64 bytes from 202.71.104.165: icmp_seq=8 ttl=52 time=286 ms
64 bytes from 202.71.104.165: icmp_seq=9 ttl=52 time=286 ms
64 bytes from 202.71.104.165: icmp_seq=10 ttl=52 time=302 ms
64 bytes from 202.71.104.165: icmp_seq=11 ttl=52 time=279 ms
64 bytes from 202.71.104.165: icmp_seq=12 ttl=52 time=280 ms
64 bytes from 202.71.104.165: icmp_seq=13 ttl=52 time=280 ms
Now this is the result for the various site to US,
[root@SeattleVPN ~]# ping www.youtube.com
PING youtube-ui.l.google.com (72.14.213.138) 56(84) bytes of data.
64 bytes from pv-in-f138.1e100.net (72.14.213.138): icmp_seq=1 ttl=54 time=7.06 ms
64 bytes from pv-in-f138.1e100.net (72.14.213.138): icmp_seq=2 ttl=54 time=7.48 ms
64 bytes from pv-in-f138.1e100.net (72.14.213.138): icmp_seq=3 ttl=54 time=7.51 ms
64 bytes from pv-in-f138.1e100.net (72.14.213.138): icmp_seq=4 ttl=54 time=7.20 ms
64 bytes from pv-in-f138.1e100.net (72.14.213.138): icmp_seq=5 ttl=54 time=7.44 ms
64 bytes from pv-in-f138.1e100.net (72.14.213.138): icmp_seq=6 ttl=54 time=7.53 ms
[root@SeattleVPN ~]# ping www.veoh.com
PING www.veoh.com (69.167.127.59) 56(84) bytes of data.
64 bytes from 69-167-127-59.veoh.com (69.167.127.59): icmp_seq=1 ttl=57 time=27.6 ms
64 bytes from 69-167-127-59.veoh.com (69.167.127.59): icmp_seq=2 ttl=57 time=27.6 ms
64 bytes from 69-167-127-59.veoh.com (69.167.127.59): icmp_seq=3 ttl=57 time=27.7 ms
64 bytes from 69-167-127-59.veoh.com (69.167.127.59): icmp_seq=4 ttl=57 time=27.7 ms
64 bytes from 69-167-127-59.veoh.com (69.167.127.59): icmp_seq=5 ttl=57 time=28.3 ms
[root@SeattleVPN ~]# ping www.hulu.com
PING a1700.g.akamai.net (96.17.8.163) 56(84) bytes of data.
64 bytes from a96-17-8-163.deploy.akamaitechnologies.com (96.17.8.163): icmp_seq=1 ttl=59 time=0.517 ms
64 bytes from a96-17-8-163.deploy.akamaitechnologies.com (96.17.8.163): icmp_seq=2 ttl=59 time=0.559 ms
64 bytes from a96-17-8-163.deploy.akamaitechnologies.com (96.17.8.163): icmp_seq=3 ttl=59 time=0.511 ms
64 bytes from a96-17-8-163.deploy.akamaitechnologies.com (96.17.8.163): icmp_seq=4 ttl=59 time=0.518 ms
64 bytes from a96-17-8-163.deploy.akamaitechnologies.com (96.17.8.163): icmp_seq=5 ttl=59 time=0.598 ms
64 bytes from a96-17-8-163.deploy.akamaitechnologies.com (96.17.8.163): icmp_seq=6 ttl=59 time=0.505 ms
64 bytes from a96-17-8-163.deploy.akamaitechnologies.com (96.17.8.163): icmp_seq=7 ttl=59 time=0.495 ms
I think our server routing is exceptionally good to reach US based servers but as usual streamyx / local ISP depends on upstream providers which seem to be giving a lot of failures lately (thats what TM said).
So, you can see its the routing to streamyx routing is having issues with TM at the moment. It has nothing to do with our VPN servers.
-
Ian where you from?
-
Pit Boss if I'm not mistaken, Ian is from London so Streamyx routing should not be an issue.
Will look into this.
ian can you provide your OpenVPN log?
-
yep will do
give me a few minutes in middle of a poker game please
thanks
-
ok it's about 11.00 pm where we are so just provide as many details as you can including any firewalls, etc etc, your openvpn log so that we can troubleshoot it tomorrow when wewake up
-
Sun May 23 16:03:36 2010 OpenVPN 2.1.1 i686-pc-mingw32 [SSL] [LZO2] [PKCS11] built on Dec 11 2009
Sun May 23 16:03:36 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Sun May 23 16:03:37 2010 UDPv4 link local: [undef]
Sun May 23 16:03:37 2010 UDPv4 link remote: 67.228.199.190:1194
Sun May 23 16:03:43 2010 [server] Peer Connection Initiated with 67.228.199.190:1194
Sun May 23 16:03:45 2010 TAP-WIN32 device [Local Area Connection 2] opened: \\.\Global\{A37AE200-2951-410F-ACB5-E8B28DE1DE38}.tap
Sun May 23 16:03:45 2010 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.8.3.242/255.255.255.252 on interface {A37AE200-2951-410F-ACB5-E8B28DE1DE38} [DHCP-serv: 10.8.3.241, lease-time: 31536000]
Sun May 23 16:03:45 2010 Successful ARP Flush on interface [22] {A37AE200-2951-410F-ACB5-E8B28DE1DE38}
Sun May 23 16:03:50 2010 Initialization Sequence Completed
windows firewall
-
Give this test dl a try with VPN and without VPN and tell us your results:
http://67.228.199.187/testfile.bin
-
I have also sent you new keys to extend your trial to give us more time to troubleshoot.
-
without vpn = 456 kb/s and with vpn starts off at 2MB/s then rapidly drops to 100 kb/s
thanks for the help btw
-
hrm interesting. will look into this further. thanks for your patience.
Can u double confirm this so we can be sure it's not an isolated incident?
-
out of interest, can you pm me what type of VPN is your other VPN using? Is it also based off OpenVPN?
-
Here is another test result downloading from our server is US to bluesqure datacenter in London.
[root@crysis-92-48-100-10 ~]# wget http://67.228.199.187/testfile.bin
--2010-05-24 12:21:52-- http://67.228.199.187/testfile.bin
Connecting to 67.228.199.187:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1048576000 (1000M) [application/octet-stream]
Saving to: `testfile.bin.1'
32% [===========> ] 340,633,031 5.40M/s eta 2m 52s
Which is 50mbit...
Ian, can your run a tracert to our server is US. 67.228.199.190?
And download this file: http://92.48.100.10/testfile.bin and see what are the speed you are getting?
Thank you