Reliance Wimax Broadband: Reliance WiMAX Youtube Routing issue

  • Thread starter Thread starter rel_user
  • Start date Start date
  • Replies Replies 20
  • Views Views 12,961
Status
Not open for further replies.
I have RelianceWimax Connection I have Shared the Connection all other machine internet is workin fine but file sharing or other system is not showing in the workgroup
 
well may be im entering this conversation very late..its day 2 with relaince wimax 600 kbps plan, and youtube is just not buffering. rel user1 what did you exactly tell the reliance customer care to make them under stand about routing youtube...and it is the same with watching videos on megavideo too...i did a speed check with speedtest.net and i get speeds varying from 300 kbps to 550 kbps.everytime i open youtube and also run the speed check parallel the speed drops down to a pathetic 140 kbps...soo basically helllppppppppppppppp..thanks,vik
 
well may be im entering this conversation very late..its day 2 with relaince wimax 600 kbps plan, and youtube is just not buffering.

rel user1 what did you exactly tell the reliance customer care to make them under stand about routing youtube...and it is the same with watching videos on megavideo too...i did a speed check with speedtest.net and i get speeds varying from 300 kbps to 550 kbps.

everytime i open youtube and also run the speed check parallel the speed drops down to a pathetic 140 kbps...soo basically helllppppppppppppppp..

thanks,
vik

Firstly, when you're downloading from youtube AND running speedtest.net at the same time, the speed it reports is bound to drop. You don't get 600kbit/s per website that you visit, you get 600kbit/s in total, so when you're visiting youtube, it looks like it's eating about 350-400kbit/s which leaves a mere 150kbit/s or so for speedtest.net to play with which is why it reports such shitty speeds.

Secondly, Youtube and other sites seem to be problematic no matter which ISP you're on in India. This is in part due to the general consideration that ISP DNS servers in India are widely considered to be slow and/or unreliable, and thus many people find themselves using Google DNS or OpenDNS.

However, there is a phenomenon that causes things to go a little haywire for sites like Youtube.com (which use CDNs), as the route to youtube.com does depend on your DNS settings - the theory here being that if you use your ISPs DNS you should get better performance than using OpenDNS or GoogleDNS, due to caching and geolocation.

There have been similar problems with people on US ISPs downloading from Netflix - abysmal speeds if they use OpenDNS or GoogleDNS but great speeds if they use their ISPs DNS, and I was experiencing some problems recently myself on my connection here in NZ.

As it turns out, the requests when using the ISP DNS can go to the server farm which is located geographically closest (or in some cases, is less busy), because it will pick the correct location based on where the request comes from - but when using GoogleDNS or OpenDNS the request will always go to the same server farm no matter where you are in the country/world.

While this isn't necessarily the problem which users on this thread are experiencing, the situation is similar - even compounded to be worse - in India. To illustrate the point, try pinging Youtube.com from your normal DNS, then changing your DNS to OpenDNS and then pinging Youtube.com again. My result is this:

ISP DNS:
Code:
ping www.youtube.comPinging youtube-ui.l.google.com [66.102.11.91] with 32 bytes of data:Reply from 66.102.11.91: bytes=32 time=60ms TTL=53Reply from 66.102.11.91: bytes=32 time=57ms TTL=53Reply from 66.102.11.91: bytes=32 time=57ms TTL=53Reply from 66.102.11.91: bytes=32 time=58ms TTL=53Ping statistics for 66.102.11.91:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 57ms, Maximum = 60ms, Average = 58ms
Open DNS:
Code:
ping www.youtube.comPinging youtube-ui.l.google.com [74.125.224.12] with 32 bytes of data:Reply from 74.125.224.12: bytes=32 time=263ms TTL=50Reply from 74.125.224.12: bytes=32 time=263ms TTL=50Reply from 74.125.224.12: bytes=32 time=265ms TTL=50Reply from 74.125.224.12: bytes=32 time=264ms TTL=50Ping statistics for 74.125.224.12:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 263ms, Maximum = 265ms, Average = 263ms
Google DNS in my case gave me the same results as my ISP DNS but maybe I got lucky. The suggestion here is this: based on my knowledge of routing and ping-times from where I am now, the physical Youtube.com server I'm hitting when I use Google or my ISP DNS is located either in Auckland or perhaps Sydney. When I use OpenDNS, I end up pinging the USA directly - probably LA, San Francisco or San Jose.

And no, you often can't tell where these servers are physically located based on WHOIS information from ARIN/APNIC/whoever because they are usually registered to the company who owns them, in this case, Google, which means both of these IPs are registered as being in the US.

Clearly, however, the closest server with the IP of 66.102.11.91 for me is NOT in the US - it has been used for the server on this side of the Pacific as well, and probably people in other parts of the world will see this IP as their "local" Youtube server, thanks to something called IP Anycasting.

So what's the moral of the story? Well unfortunately, you're damned if you do and damned if you don't.

Because ISPs DNS servers are considered by many to be unreliable and slower than using Google or OpenDNS for general browsing, but when it comes to visiting sites like Youtube, it messes up the geolocation stuff and you end up trying to pull content from the USA at greatly reduced speeds, instead of taking advantage of all the caching that goes on behind the scenes at Reliance (or any other ISP, for that matter).

---------- Post added at 04:56 AM ---------- Previous post was at 04:45 AM ----------

Why using Google DNS / OpenDNS is a bad idea Why using Google DNS / OpenDNS is a bad idea (see at the bottom about ISP quotas: for the record, this will be VERY important for Hayai!!)
 
I use Airtel DNS and YouTube still lags a lot frequently. Can't even buffer a 360p video on a 2Mbps line. I don't think most if their stuff is cached locally. The bastards charge you for it even if it is cached like PSN content.
 
I use Airtel DNS and YouTube still lags a lot frequently. Can't even buffer a 360p video on a 2Mbps line. I don't think most if their stuff is cached locally. The bastards charge you for it even if it is cached like PSN content.

As I mentioned, I'm not suggesting that this is the entire reason for these kinds of problems but they don't help. Perhaps Airtel doesn't have very good caching of Youtube and whatnot. As for cached content, yeah, this is normal. It's up to the ISP to decide what is included in their own free-zones - iiNet in Australia has PSN and iTunes, several NZ ISPs now have Sky - Airtel has things of it's own.

Either way, it would be interesting to see the results for these Reliance customers. Whether it actually helps or solves the problem is another story altogether.
 
yeah Reliance much better then any other ISP with low latency and good download and upload speed. If anyone go for multiuser plan he will get static IP in which routing and pings are very nice. So you can play online games without any probs...
 


Status
Not open for further replies.
Top