[Guide] How to host webservers on Jio Fiber, accessible to IPv4 clients

As you might know, Jio does not offer static IPv4, and it is not easy to apply for port forwarding (for Camera etc. purposes). However, they do provide IPv6 and this can be used for hosting web servers.

To allow IPv6 incoming connections to your device (e.g. a PC running nginx), you need to disable all firewall rules in Jio Router. (At least initially for ease of setup / troubleshooting - once you get it working you can slowly tighten it up).

Your device on which you want to host must be connected to your Jio router directly (Wifi or LAN) and must have IPv6 assigned from the Jio router's DHCP.
On your device running webserver (nginx, plex, whatever), make sure it is bound to localhost or the IPv6 equivalent (NOT 127.0.0.1 - this wont allow IPv6 connectivity). Usually apps bind to all network interfaces so you should be fine.

From command prompt (or equivalent), Type ipconfig all (if you're on linux you probably know the commands - but it should be ifconfig), and view your IPv6 address. This is indeed your "Public IPv6". Let us assume it is 2001:0db8:85a3:0000:0000:8a2e:0370:7334

If your server is running on port 80, for example, you can now, from another client, access it by specifying a URL [2001:0db8:85a3:0000:0000:8a2e:0370:7334]:80. But this is limited to IPv6 clients only.

For IPv4, you need a domain name. Freenom offers free '.tk', but I'd recommend spend $1 and get a .xyz or something from namecheap. With a domain name, you can setup a cloudflare website, and have the DNS AAAA record point to your IPv6 (no A record).

E.g. AAAA record for 'randomdomain.xyz' -> 2001:0db8:85a3:0000:0000:8a2e:0370:7334

Set cloudflare proxy for the domain to "On". Now cloudflare will act as an automatic gateway, and IPv4 only clients can go to randomdomain.xyz, and access cloudflare over IPv4, which itself will connect to you over IPv6.

Using this method I was able to run a webserver, and had a friend in U.S. download from me at ~90Mbps (My Jio Speed is 100Mbps). This was probably helped by routing over Cloudflares network.

One caveat is - you cannot run services like FTP, SSH etc over Cloudflare, only web servers (on port 80 and 443 only, too). But for hosting Plex or something it works great.

Have fun!
 
Messages
407
Location
Jharkhand
ISP
Jio Fiber 150Mbps
Airtel 4G, Jio4g
(Railwire 100Mbps)
Yes from Mumbai. I get around 60 ms if I go via airtel. Which ISP are you using?
just fyi its hosted on a macmini , in case that makes a slight difference in response time’s
Bro I'm also using JioFiber. Ping is very high in my area(Jharkhand) for every server because the ping on the gateway(Asansol/Kolkata) itself is 30-40ms. Still it's surprising to see 60ms ping if you're in Mumbai. I'm guessing that some of their routes are IPv6 only due to which my IPv4 traffic has to take some other route to reach Mumbai.
 
Messages
67
Location
Mumbai
ISP
Jiofibre
Yes Its possible. Are you hosting gaming servers that you need low ms ?
 
Messages
49
Location
Kolkata, India
ISP
Jio Fiber
Bro I'm also using JioFiber. Ping is very high in my area(Jharkhand) for every server because the ping on the gateway(Asansol/Kolkata) itself is 30-40ms. Still it's surprising to see 60ms ping if you're in Mumbai. I'm guessing that some of their routes are IPv6 only due to which my IPv4 traffic has to take some other route to reach Mumbai.

30-40 ms to your gateway? That is very stupid of Jio given that I am getting 1-2ms compared to mine from Kolkata.
This reminds me of the time when ADSL connections existed where Airtel's gateway itself was 40ms so pinging any IP would add 40-50ms because of the idiotic routing from the gateway to the destination address but that had also got fixed (stable at 3-4ms) as soon as it changed to a VDSL from an ADSL.

Here is an example of a traceroute to 1.1.1.1 (IPv6)

Tracing route to one.one.one.one [2606:4700:4700::1111]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 2405:201:800a:xxx:xxx:xxx:xxx:xxx
2 * * * Request timed out.
3 3 ms 3 ms 2 ms 2405:200:801:500::1d
4 3 ms 4 ms 3 ms 2405:200:1606:600:49:44:187:2d
5 3 ms 2 ms 3 ms one.one.one.one [2606:4700:4700::1111]

Trace complete.

Can you share your traceroute/tracert result here to [2606:4700:4700::1111] which is the IPv6 address of one.one.one.one
 
Messages
407
Location
Jharkhand
ISP
Jio Fiber 150Mbps
Airtel 4G, Jio4g
(Railwire 100Mbps)
Tracing route to one.one.one.one [2606:4700:4700::1001]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms ROUTER_IP
2 * * * Request timed out.
3 29 ms 29 ms 29 ms 2405:200:801:500::1d
4 26 ms 24 ms 25 ms 2405:200:1606:600:49:44:187:2d
5 24 ms 26 ms 24 ms one.one.one.one [2606:4700:4700::1001]

Trace complete.
This is the IPv6 traceroute and the IPv4 one is:
1 1 ms 1 ms 1 ms reliance.reliance [192.168.29.1]
2 5 ms 4 ms 5 ms 10.27.208.1
3 27 ms 27 ms 27 ms 172.16.89.153
4 30 ms 31 ms 31 ms 172.26.66.54
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 76 ms 106 ms 74 ms 103.198.140.164
13 117 ms 116 ms 117 ms 49.45.4.82
14 118 ms 119 ms 119 ms 103.198.140.49
15 111 ms 112 ms 130 ms 162.158.160.241
16 117 ms 117 ms 116 ms one.one.one.one [1.1.1.1]
I'm ignoring 10.27.208.1 and considering 172.16.89.153 as the gateway for IPv4 as one of my friends in a nearby city has the same traceroute beyond the 2nd node. Surprisingly 8.8.8.8 and dns.google(IPv6) also has a difference in ping.
 
Messages
49
Location
Kolkata, India
ISP
Jio Fiber
This is the IPv6 traceroute and the IPv4 one is:

I'm ignoring 10.27.208.1 and considering 172.16.89.153 as the gateway for IPv4 as one of my friends in a nearby city has the same traceroute beyond the 2nd node. Surprisingly 8.8.8.8 and dns.google(IPv6) also has a difference in ping.
Holy shit. 30 ms to your gateway? How do you expect any ping result to be lower than the gateway ping.
It will always add +30ms to your base IP ping results. Throw this piece of garbage outside your building.
This is exactly taking an ethernet cable, connecting it to a switch and throwing the other side at you and then telling you to ping me - it shows 30ms. I would take the cable and hang the provide upside down probably. This is so stupid

Here is my IPv4 traceroute to 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms reliance.reliance [192.168.29.1]
2 2 ms 2 ms 1 ms 10.10.120.1
3 3 ms 3 ms 2 ms 172.16.19.29
4 4 ms 1 ms 1 ms 172.17.117.70
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 40 ms 39 ms 40 ms 103.198.140.60
11 97 ms 149 ms 98 ms 49.45.4.86
12 79 ms 79 ms 82 ms 103.198.140.51
13 * * * Request timed out.
14 75 ms 75 ms 74 ms one.one.one.one [1.1.1.1]

Trace complete.
 


Messages
49
Location
Kolkata, India
ISP
Jio Fiber
Plus compared to Airtel Xtream in Calcutta - the pings are exactly the same on Jio Fiber. No wonder it hit it off in this city as playing CS 1.6 is a higher priority to the public here than eating food.
 
Messages
407
Location
Jharkhand
ISP
Jio Fiber 150Mbps
Airtel 4G, Jio4g
(Railwire 100Mbps)
Holy shit. 30 ms to your gateway? How do you expect any ping result to be lower than the gateway ping.
It will always add +30ms to your base IP ping results.
Yeah that should be the case but not sure why there's so much variation in IPv4 and IPv6 pings. It is quite possible that some of their routes are IPv6 only, due to which my IPv4 traffic has to take some other route resulting in higher pings.
image.png
 
Messages
49
Location
Kolkata, India
ISP
Jio Fiber
Jio should do something about this. As your entire city must be facing this issue but at the end of the day this country does not give a shit about latency or better routing tables.

You can use their looking glass and compare it with other cities which can help their idiotic so called "engineers" understand what the exact problem is:
 
Messages
49
Location
Kolkata, India
ISP
Jio Fiber
Hahah an entire ISP that completely relies on an IPv6 network does not have IPv6 lookup and features connected to your looking glass.
-from Jio with Love

My guess is because the site is hosted on an IPv4 address:

Hence, no IPv6 lookup support and their script is very shit. My kid can develop something better than this.
 
Messages
49
Location
Kolkata, India
ISP
Jio Fiber
Anyway your gateway related issues are on IPv4 addresses as well,
Just compare it with your location with another.

For an example, here is my traceroute to the looking glass of Jio:

1 <1 ms <1 ms <1 ms reliance.reliance [192.168.29.1]
2 3 ms 1 ms 2 ms 10.10.120.1
3 3 ms 2 ms 3 ms 172.16.19.29
4 2 ms 3 ms 3 ms 172.17.117.70
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 33 ms 33 ms 33 ms 49.40.2.164

Tell them how can my local GATEWAY itself be of such high pings.
My best guess is that they do not have an exchange in your city and gets rerouted through one of these exchanges listed on their LG.
 
Messages
164
Location
Ranaghat
ISP
Jio Fiber
This is the IPv6 traceroute and the IPv4 one is:

I'm ignoring 10.27.208.1 and considering 172.16.89.153 as the gateway for IPv4 as one of my friends in a nearby city has the same traceroute beyond the 2nd node. Surprisingly 8.8.8.8 and dns.google(IPv6) also has a difference in ping.
ipv6 tracert jiofiber . my location 80km from kolkata
C:\Users\srinj>tracert 2606:4700:4700::1111

Tracing route to one.one.one.one [2606:4700:4700::1111]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 2405:201:9004:2096:16ae:85ff:fee1:da79
2 * * * Request timed out.
3 7 ms 6 ms 6 ms 2405:200:100::1:0:434
4 6 ms 6 ms 5 ms 2405:200:1606:600:49:44:187:2d
5 6 ms 6 ms 5 ms one.one.one.one [2606:4700:4700::1111]

Trace complete.

ipv4 tracert jiofiber
C:\Users\srinj>tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms reliance.reliance [192.168.29.1]
2 3 ms 3 ms 3 ms 10.15.136.1
3 5 ms 5 ms 5 ms 172.16.19.29
4 5 ms 6 ms 5 ms 172.17.117.70
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 38 ms 38 ms 38 ms 103.198.140.60
11 77 ms 76 ms 79 ms 103.198.140.15
12 77 ms 75 ms 75 ms 103.198.140.51
13 * * * Request timed out.
14 75 ms 76 ms 77 ms one.one.one.one [1.1.1.1]

Trace complete.