Home Network Monitor · Guide 12 of 12

ISP router guide: Airtel, Tata Play Fiber and JioFiber

How to test what your provider router allows, what users commonly report for Airtel, Tata Play Fiber and JioFiber, and workarounds when it is locked.

Sections
9
Code samples
1
Time
~5 min
Visits
…

Home fibre providers in India supply their own router or ONT (optical network terminal), and what you are allowed to change on it varies a lot. This guide helps you find out what your unit allows, and gives a ranked set of workarounds when it is locked down.

How reliable is this guide? There is no official provider documentation for most of these settings. What follows combines general networking knowledge with reports from users on public forums (linked at the end). Router models, firmware versions and provider policies differ by city and change over time, and providers can update routers remotely. Treat every provider-specific statement as "commonly reported, verify on your unit". The test procedure in section 12.2 tells you the truth about your own router in about ten minutes.

#12.1 Identify your router

  1. Read the label on the router or ONT: model name, admin address and (usually) the admin username and password. Do not assume defaults; many units have a unique password printed on the label.
  2. Find the address from a connected computer: ip route | grep default (Linux), route -n get default (macOS) or ipconfig (Windows). It is often 192.168.1.1, but check.
  3. Log in from a browser at that address. Note the model and firmware version; they decide what is possible.
  4. Take a screenshot of each page you change, so you can undo it.

Some providers also manage the router remotely (the standard mechanism is called TR-069). Where that is the case, a setting you change can be reset later by the provider.

Do not factory-reset a provider router unless the provider told you to. A reset can remove provisioning that your connection depends on and may need a technician visit to restore.

#12.2 Test what your router allows

Go through this list on your router's admin pages. The answers decide which setup in guide 4 you can use.

# Test Where to look Why it matters
1 Can you set a DHCP DNS server (the DNS that the router hands to devices)? LAN, DHCP, or DNS settings If yes: Pi-hole works with the simplest setup
2 Is the DHCP section editable, or greyed out? LAN, DHCP Greyed out means you cannot change DNS there or turn DHCP off
3 Can you reserve an address for a device (static lease)? DHCP, address reservation Gives the monitor box a fixed IP
4 Is there a bridge mode / "ONT only" option? WAN, Advanced, Network Lets your own router take over
5 Can you turn off IPv6 DNS advertisement, or IPv6 entirely? IPv6, LAN Stops devices skipping Pi-hole through IPv6
6 What is the WAN IP shown, and is it the same as https://ifconfig.me? Status or WAN page If they differ, you are behind carrier-grade NAT (CGNAT): nothing from the internet can reach you

Record the results; the next section uses them.

#12.3 What users commonly report, by provider

These are reports, not guarantees. Use them to know what to try first.

#Airtel (Xstream Fiber)

#Tata Play Fiber

#JioFiber

#Other providers (ACT, BSNL, regional ISPs, and so on)

Behaviour varies by model. Apply the test in 12.2 and use the same workarounds. If you confirm exact steps for your provider and model, please contribute them (section 12.8).

#12.4 Pick your path

Based on your test results:

Your router... Choose
Lets you set DHCP DNS (tests 1 and 3 pass) Setup A in guide 4 plus Pi-hole. Simplest.
Locks DHCP/DNS (tests 1 or 2 fail) and you want web activity Setup A2 below (your own router behind the provider's), or Setup B (box as gateway)
Locks DHCP/DNS and you only want device alerts Setup A works unchanged: new-device and connectivity alerts need no DNS change
You want data usage per device Setup B or C in guide 4
Bridge mode is available and supported by the provider Use your own router in router mode; optional

A locked provider router does not stop device discovery. The built-in scanner reads the LAN directly, so Stage 1 of the install works with any router.

#12.5 Setup A2: monitor behind your own router

When the provider router will not let you change DNS or DHCP, put your own consumer router behind it and make that the router your devices use.

Internet ── provider router (Wi-Fi OFF) ──WAN── YOUR ROUTER ──┬── Wi-Fi devices
                                                              ├── wired devices
                                                              └── monitor box

What you need: a basic router that lets you set DHCP DNS and address reservations (most retail routers do), and an Ethernet cable.

Steps

  1. Connect a LAN port on the provider router to the WAN/Internet port of your router.
  2. On your router, use router mode (the default) with a LAN subnet different from the provider's: if the provider uses 192.168.1.0/24, use 192.168.50.0/24 for yours. (Two routers on the same subnet cause conflicts.)
  3. Set your router's DHCP DNS to the monitor box's IP (once Pi-hole is installed; until then leave defaults).
  4. Reserve a fixed address for the monitor box on your router, for example 192.168.50.2.
  5. Move your devices to your router's Wi-Fi and LAN ports, using the Wi-Fi name and password they already know.
  6. Switch off the provider router's Wi-Fi (or keep it only for guests or devices you do not need to monitor).
  7. Plug the monitor box into your router, then follow guide 5. In the app set the subnet to 192.168.50.0/24 and the gateway to your router's LAN address, e.g. 192.168.50.1.

What you get: everything from Setup A (devices, alerts, and Pi-hole web activity, since you control DHCP DNS). Only devices on your router are monitored; anything left on the provider's network is invisible to the scanner.

Trade-offs: double NAT (provider router and yours). This is fine for browsing and streaming but can affect game consoles, voice calls and port forwarding. If your provider uses CGNAT these were already limited. Your router's firmware becomes the network's weak point, so keep it updated.

#12.6 Other workarounds when the router is locked

Option How Notes
Per-device DNS Set the DNS server to the box's IP in each device's network settings Works for the few devices you care about; each device must be done by hand
Pi-hole as DHCP server Turn off the provider's DHCP and enable DHCP in Pi-hole Only possible if the provider's DHCP is not greyed out. Makes the box critical: if it is off, new devices get no address.
Box as gateway (Setup B) Build it behind the provider router; guide 4, section 4.4 Works whatever the provider locks, because the provider router is not reconfigured. Brings the biggest visibility, and the biggest risk.
Ask the provider Request DNS/DHCP changes or bridge mode via support Outcomes vary; changes may be reverted by remote management

#12.7 IPv6, extenders and mesh

#12.8 Help improve this guide

Provider firmware changes, so confirmed details from real units are valuable. When you have tested your router, record it in this format and send it as an issue or pull request to the project:

Field Example
Provider and plan (name)
Router/ONT model and firmware (from the label and status page)
Date tested 2026-10-22
Test 1: DHCP DNS editable yes / no / greyed out
Test 3: address reservation yes / no
Test 4: bridge mode yes / no / needs support
Test 6: CGNAT yes / no
What worked (steps)
What did not (what happened)

Do not include passwords, serial numbers, MAC addresses or your public IP.

#12.9 Sources

Community reports used for the provider notes above (retrieved October 2026). They are user discussions, not official documentation, and may be out of date:

Next: back to Placing the monitor in your network or on to Install and configure.

Questions or feedback?

Stuck on a step, found a bug, or have an idea? Leave a note — 60 words max.

0 / 60 words