Author Topic: Boleh on YES  (Read 7686 times)

sgchan

  • Guest
Boleh on YES
« on: April 02, 2012, 08:10:21 AM »
Can't seem to get Boleh working on YES network. It connects to the Boleh server via Fully Routed... no prob. Then I open the browser and try Google using Firefox (or Chrome). It says connected but the wheel keeps spinning and it doesn't seem to download the page. Any clues?

The only Boleh service that works on YES is US-SurfingStreaming. The rest doesn't work (I configured the app to go via Proxy as instructed too).

I am on Mac using TunnelBlick. Help please?

Offline Reuben

  • Chief Doraemon
  • Administrator
  • Admiral
  • *****
  • Posts: 6878
Re: Boleh on YES
« Reply #1 on: April 02, 2012, 10:40:52 AM »
If you're using Fully Routed, there's no need to configure the app to use the proxy. Can you try without the proxy?
*If you like my service/support, please consider posting a positive feedback here*<3



Co-Founder/Administrator

sgchan

  • Guest
Re: Boleh on YES
« Reply #2 on: April 02, 2012, 01:49:57 PM »
Hello Reuben,
Thanks for the reply. I do not configure Proxy in Fully Routed and it still does not work. I know this configuration is necessary for Proxied and TCP443. The weird thing is the browser does indicate that it reached the server but cannot download the content or webpage. It just freezes there.

Any advice? Thanks in advance. 

Offline Reuben

  • Chief Doraemon
  • Administrator
  • Admiral
  • *****
  • Posts: 6878
Re: Boleh on YES
« Reply #3 on: April 02, 2012, 01:58:37 PM »
You confirm it works with US-SurfingStreaming and you get a new US IP?
*If you like my service/support, please consider posting a positive feedback here*<3



Co-Founder/Administrator

sgchan

  • Guest
Re: Boleh on YES
« Reply #4 on: April 02, 2012, 02:05:36 PM »
Yes, I went to Hulu and played Glee.

Offline Reuben

  • Chief Doraemon
  • Administrator
  • Admiral
  • *****
  • Posts: 6878
Re: Boleh on YES
« Reply #5 on: April 03, 2012, 11:16:49 AM »
Hey could you enclose your logs for both US SurfingStreaming and also the failed ones so that we can take a look? Maybe something to do with the internal IP assignment.
*If you like my service/support, please consider posting a positive feedback here*<3



Co-Founder/Administrator

sgchan

  • Guest
Re: Boleh on YES
« Reply #6 on: April 03, 2012, 12:15:27 PM »
Below is the log for FullyRouted-All:

2012-04-03 12:03:01 *Tunnelblick: OS X 10.7.3; Tunnelblick 3.2.3 (build 2891.2932) Unsigned
2012-04-03 12:03:01 *Tunnelblick: Attempting connection with FullyRouted-All; Set nameserver = 1; monitoring connection
2012-04-03 12:03:01 *Tunnelblick: /Applications/Tunnelblick.app/Contents/Resources/openvpnstart start FullyRouted-All.ovpn 1337 1 0 0 0 49 -atDASNGWrdasngw
2012-04-03 12:03:01 OpenVPN 2.2.1 i386-apple-darwin10.8.0 [SSL] [LZO2] [PKCS11] [eurephia] built on Jan  8 2012
2012-04-03 12:03:01 *Tunnelblick: openvpnstart: /Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.2.1/openvpn --cd /Users/chanshionggau/Library/Application Support/Tunnelblick/Configurations --daemon --management 127.0.0.1 1337 --config /Users/chanshionggau/Library/Application Support/Tunnelblick/Configurations/FullyRouted-All.ovpn --log /Library/Application Support/Tunnelblick/Logs/-SUsers-Schanshionggau-SLibrary-SApplication Support-STunnelblick-SConfigurations-SFullyRouted--All.ovpn.1_0_0_0_49.1337.openvpn.log --management-query-passwords --management-hold --script-security 2 --up /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -m -w -d -atDASNGWrdasngw --down /Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -m -w -d -atDASNGWrdasngw --up-restart
2012-04-03 12:03:02 *Tunnelblick: openvpnstart message: Loading tun.kext
2012-04-03 12:03:02 *Tunnelblick: Established communication with OpenVPN
2012-04-03 12:03:02 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2012-04-03 12:03:02 WARNING: file 'sgchan.key' is group or others accessible
2012-04-03 12:03:02 WARNING: file 'ta.key' is group or others accessible
2012-04-03 12:03:02 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
2012-04-03 12:03:02 LZO compression initialized
2012-04-03 12:03:02 UDPv4 link local: [undef]
2012-04-03 12:03:02 UDPv4 link remote: 94.242.213.5:443
2012-04-03 12:03:10 [server] Peer Connection Initiated with 94.242.213.5:443
2012-04-03 12:03:12 TUN/TAP device /dev/tun0 opened
2012-04-03 12:03:12 /sbin/ifconfig tun0 delete
                                        ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address
2012-04-03 12:03:12 NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
2012-04-03 12:03:12 /sbin/ifconfig tun0 10.10.11.126 10.10.11.125 mtu 1500 netmask 255.255.255.255 up
2012-04-03 12:03:12 /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -m -w -d -atDASNGWrdasngw tun0 1500 1542 10.10.11.126 10.10.11.125 init
                                          No such key
                                        add net 94.242.213.5: gateway 192.168.60.1
                                        add net 0.0.0.0: gateway 10.10.11.125
                                        add net 128.0.0.0: gateway 10.10.11.125
2012-04-03 12:03:14 *Tunnelblick client.up.tunnelblick.sh: Retrieved name server(s) [ 195.24.72.6 83.243.8.6 ] and WINS server(s) [ ] and using default domain name [ openvpn ]
2012-04-03 12:03:14 *Tunnelblick client.up.tunnelblick.sh: Up to two 'No such key' warnings are normal and may be ignored
2012-04-03 12:03:14 *Tunnelblick client.up.tunnelblick.sh: Saved the DNS and WINS configurations for later use
2012-04-03 12:03:14 *Tunnelblick client.up.tunnelblick.sh: Set up to monitor system configuration with process-network-changes
2012-04-03 12:03:18 *Tunnelblick: Flushed the DNS cache
2012-04-03 12:03:18 Initialization Sequence Completed
2012-04-03 12:03:20 *Tunnelblick process-network-changes: A system configuration change was ignored because it was not relevant


This is from US-Stream/Surfing:
2012-04-03 12:10:56 *Tunnelblick: OS X 10.7.3; Tunnelblick 3.2.3 (build 2891.2932) Unsigned
2012-04-03 12:10:56 *Tunnelblick: Attempting connection with US-SurfingStreamingTCP; Set nameserver = 1; monitoring connection
2012-04-03 12:10:56 *Tunnelblick: /Applications/Tunnelblick.app/Contents/Resources/openvpnstart start US-SurfingStreamingTCP.ovpn 1337 1 0 0 0 49 -atDASNGWrdasngw
2012-04-03 12:10:56 OpenVPN 2.2.1 i386-apple-darwin10.8.0 [SSL] [LZO2] [PKCS11] [eurephia] built on Jan  8 2012
2012-04-03 12:10:56 *Tunnelblick: openvpnstart: /Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.2.1/openvpn --cd /Users/chanshionggau/Library/Application Support/Tunnelblick/Configurations --daemon --management 127.0.0.1 1337 --config /Users/chanshionggau/Library/Application Support/Tunnelblick/Configurations/US-SurfingStreamingTCP.ovpn --log /Library/Application Support/Tunnelblick/Logs/-SUsers-Schanshionggau-SLibrary-SApplication Support-STunnelblick-SConfigurations-SUS--SurfingStreamingTCP.ovpn.1_0_0_0_49.1337.openvpn.log --management-query-passwords --management-hold --script-security 2 --up /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -m -w -d -atDASNGWrdasngw --down /Applications/Tunnelblick.app/Contents/Resources/client.down.tunnelblick.sh -m -w -d -atDASNGWrdasngw --up-restart
2012-04-03 12:10:57 *Tunnelblick: openvpnstart message: Loading tun.kext
2012-04-03 12:10:57 *Tunnelblick: Established communication with OpenVPN
2012-04-03 12:10:57 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2012-04-03 12:10:57 WARNING: file 'sgchan.key' is group or others accessible
2012-04-03 12:10:57 WARNING: file 'ta.key' is group or others accessible
2012-04-03 12:10:57 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
2012-04-03 12:10:57 LZO compression initialized
2012-04-03 12:10:57 Attempting to establish TCP connection with 68.68.105.234:443 [nonblock]
2012-04-03 12:10:58 TCP connection established with 68.68.105.234:443
2012-04-03 12:10:58 TCPv4_CLIENT link local: [undef]
2012-04-03 12:10:58 TCPv4_CLIENT link remote: 68.68.105.234:443
2012-04-03 12:11:10 [server] Peer Connection Initiated with 68.68.105.234:443
2012-04-03 12:11:13 TUN/TAP device /dev/tun0 opened
2012-04-03 12:11:13 /sbin/ifconfig tun0 delete
                                        ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address
2012-04-03 12:11:13 NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
2012-04-03 12:11:13 /sbin/ifconfig tun0 10.11.10.22 10.11.10.21 mtu 1500 netmask 255.255.255.255 up
2012-04-03 12:11:13 /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -m -w -d -atDASNGWrdasngw tun0 1500 1544 10.11.10.22 10.11.10.21 init
                                          No such key
                                        add net 68.68.105.234: gateway 192.168.60.1
                                        add net 0.0.0.0: gateway 10.11.10.21
                                        add net 128.0.0.0: gateway 10.11.10.21
                                        add net 10.11.10.1: gateway 10.11.10.21
2012-04-03 12:11:15 *Tunnelblick client.up.tunnelblick.sh: Retrieved name server(s) [ 8.8.8.8 ] and WINS server(s) [ ] and using default domain name [ openvpn ]
2012-04-03 12:11:15 *Tunnelblick client.up.tunnelblick.sh: Up to two 'No such key' warnings are normal and may be ignored
2012-04-03 12:11:15 *Tunnelblick client.up.tunnelblick.sh: Saved the DNS and WINS configurations for later use
2012-04-03 12:11:15 *Tunnelblick client.up.tunnelblick.sh: Set up to monitor system configuration with process-network-changes
2012-04-03 12:11:18 *Tunnelblick: Flushed the DNS cache
2012-04-03 12:11:18 Initialization Sequence Completed
2012-04-03 12:11:20 *Tunnelblick process-network-changes: A system configuration change was ignored because it was not relevant

Offline PitBoss

  • Administrator
  • Admiral
  • *****
  • Posts: 1250
Re: Boleh on YES
« Reply #7 on: April 03, 2012, 02:05:22 PM »
Hi,
Can you try Proxy TCP443 server?
The US server was successful on the TCP streaming.  Can you try on the US Stream UDP?

Thank you.

Co-Founder / Administrator

sgchan

  • Guest
Re: Boleh on YES
« Reply #8 on: April 03, 2012, 11:00:34 PM »
TCP443 does not work. Tried it already. I will try the US Stream UDP tomorrow morning. Will let you know then.

What do you suspect it may be?

Offline Reuben

  • Chief Doraemon
  • Administrator
  • Admiral
  • *****
  • Posts: 6878
Re: Boleh on YES
« Reply #9 on: April 04, 2012, 09:49:38 AM »
We were suspecting they may be blocking UDP traffic or an internal IP conflict.
*If you like my service/support, please consider posting a positive feedback here*<3



Co-Founder/Administrator

sgchan

  • Guest
Re: Boleh on YES
« Reply #10 on: April 04, 2012, 11:21:00 AM »
Reuben, you are absolutely correct. the US Stream UDP does not work. So what could be a solution for this? Would it be possible to get FullyRouted working?

Offline PitBoss

  • Administrator
  • Admiral
  • *****
  • Posts: 1250
Re: Boleh on YES
« Reply #11 on: April 05, 2012, 03:56:18 PM »
I will update you on this. Probably will setup uk server to accept connection on top 443 on top of the existing Udp.

Will update you once it's done.

Co-Founder / Administrator

sgchan

  • Guest
Re: Boleh on YES
« Reply #12 on: April 09, 2012, 03:25:49 PM »
Thanks

carnithuranis

  • Guest
Re: Boleh on YES
« Reply #13 on: April 10, 2012, 01:06:51 AM »
I have had a similar problem with my Isp and may have a solution to your problem.  Some Isp's like to throttle there connections by setting a lower MTU allowance.  The average package size is set to 1500 MTU.  Your Isp may have assigned a lower package size on the udp.  To get around this problem you have to set the MTU size to 1300 on the tap adapter. On windows you would do the following:

 Go to your tap-32 adapter, open properties,open configure,open advanced, highlight MTU and put in a value of 1300.
 Press okay and try connection.

On Mac, you go to system preference, select the network interface you use to connect to the Internet, press the advanced button, then click on the hardware tab.  There you will see the Mtu and put in the value of 1300.

I hope this solves your problem, if not it may be useful to others.