Hathway Broadband is now using Reliance Jio gateway which means all Jio blocked services are now blocked on it

I would like to request this forum's mod/admin to kindly tag this post to both Jio's and Hathway's threads, as it kind of relates to both of them.

Okay, so here it is. I'll tell you exactly how it all started...

Till yesterday, I was able to access all the torrent sites (link-removed, link-removed, etc) and some really good sites (hub and all that....) without any problem. I was having a jolly good time too. Everything was going fine, I was happy with my life (or so I've been telling myself).

What I didn't knew was that my happiness was predestined to be short and limited. Thanks to motabhai.

I had my semester exams today, and because of how boring and dry my exam was, I decided to download the recently released Captain Marvel from link-removed on coming home. But on opening the site, instead of seeing the good stuff, here's what I was greeted with:


CWr0MHa.png


Feeling disappointed, I tried some more sites. What I noticed is that, basically all those sites that are blocked in Jio, are now also blocked in Hathway. Nothing works anymore. Even changing the DNS also doesn't help, which wasn't the case earlier.

So, I performed a trace route on the most common site - google.com. And here's the result:


PJwtdri.png


Here's what I found after after a detailed inspection:
Traceroute IP list :
1. My router
2. Hathway's Kolkata Node
3. Hathway's Mumbai Node
4. Jio's Mumbai Node
5-8. Some Internal IPs
9. Google's Gateway
10. The Final Destination

This means that, from now on, whatever blocking that we have on Jio, all Hathway's customers are going to face the same too.
 
I would also like to say that on realizing that my traffic is going through Jio's nodes, I contacted the regional office of Hathway (Kolkata). But they said that they'll see if they can do anything regarding unblocking of some of those "private sites" (that's exactly how they named it, private sites). I highly doubt anything's ever going to happen about this as the traffic is routed from Hathway's Mumbai Headend NOC. And we all know one already, if anything is blocked by Jio, it's going to stay like that. There's no unblocking it.
 
Try using encrypted DNS (firefox only)


How-To Manually Configure DoH


Do you want to use (or not use) DoH all the time? Use the configuration editor to configure DoH if you want to test DoH outside of a shield study. DoH support works best in Firefox 62 or newer. Shield studies will not override your manual configuration.

1] Type about:config in the location bar

2] Search for network.trr (TRR stands for Trusted Recursive Resolver – it is the DoH Endpoint used by Firefox.)

3] Change network.trr.mode to 2 to enable DoH. This will try and use DoH but will fallback to insecure DNS under some circumstances like captive portals. (Use mode 5 to disable DoH under all circumstances.)

4] Set network.trr.uri to your DoH server. Cloudflare’s is https://mozilla.cloudflare-dns.com/dns-query but you can use any DoH compliant endpoint.

The DNS tab on the about:networking page indicates which names were resolved using the Trusted Recursive Resolver (TRR) via DoH.
 
@Sushubh Exactly. Jio uses some really really strong firewall, which, no matter how strong your encryption is, as long as traffic is through Jio, it's blocked.

I read this that Jio achieves this by implementing deep packet inspection and other such techniques.
 
I'll have to do that from now on.
Just feeling sad about the fact that things won't be the same like they used to be earlier on Hathway. I could easily access any torrent site through chrome only. Not only that, my Hathway connection was something that my friends used to envy. They were all like, dude you're so lucky, open ports, no blocking....now, they're all gonna laugh at me. 🙁
 
personally i am just waiting for the launch of cloudflare warp for desktop. though it might not solve the problem as they would also end up using indian data centers which would be using jio or airtel backbone.
 

Okay, so I tried it, just like you said.
To avoid any funny misconfigurations, the DNS IP address of my router is set to Cloudflare's too.
And I followed this guide: Reddit post
And it worked like a charm:


yaB4EkT.png


But, torrents sites are still not accessible. This time, the error is different. Instead of resetting my connection as I've mentioned before, I'm getting this new error on firefox while trying to access a torrent site (that worked till yesterday):


0Ywvup7.png


This IP address that you see, 49.44.18.34 , is nothing but another Jio's IP.

As mentioned earlier, only VPN is the solution now (or so I think).
 

Top