BSNL FTTH IPv6 Issue: Some Websites Not Loading and YouTube Videos Not Playing

  • Thread starter Thread starter Akg09
  • Start date Start date
  • Replies Replies 9
  • Views Views 1,242
A

Akg09

Messages
3
Location
Idukki
ISP
BSNL
Hi everyone,

I'm experiencing some significant issues with my BSNL FTTH connection when IPv6 is enabled. Here are the details:

  • Router Model: Genexis Platinum 4410
  • Websites Affected: Certain websites, such as my.1password.com, do not load at all. The YouTube site loads, including the home feed and search results, but videos do not play.
  • Temporary Fix: Disabling IPv6 on my router resolves the issue, and all websites and YouTube videos work fine.
Troubleshooting Steps Taken:

  1. Ping Test: Running ping -6 google.com shows that IPv6 connectivity is generally working.
  2. Traceroute Test: Running tracert my.1password.com reveals multiple timeouts and delays at various hops.
  3. Router Settings: IPv6 settings on my router are verified and correctly configured. The router firmware is up to date.
  4. Network Testing: The problem occurs across different devices, including PCs and mobile devices.
Has anyone else faced similar issues? Any suggestions on additional steps I can take to resolve this problem permanently?

Thanks in advance for your help!

Amal
 
Last edited:
@Akg09 This could be more of a hardware and software issue. I tried loading my.1password.com (loads fine with IPv6 enabled) and it is only IPv4, so either browser doesn't switch between v4 and v6 properly or the ONT/router. If you can, test with a different router by bridging to confirm it's not the ONT that is causing issue.
 
For anyone using hardware that follows proper linux/bsd networking, IPv6 ain't gonna work until "experts" at BSNL learn how MTU work. Anyone using cheap ONTs, your IPv6 will work fine.
 
On 18th July evening BSNL change some routing and now IPv6 is completely broken.

CF routing is good now at the cost of IPv6

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

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     2 ms     1 ms     1 ms  117.214.8.1
  3     5 ms     9 ms     3 ms  10.219.12.38
  4    19 ms    19 ms    18 ms  218.248.255.1
  5    19 ms     *       18 ms  218.248.255.2
  6     *       62 ms    71 ms  117.216.207.122
  7    73 ms    64 ms    63 ms  162.158.52.4
  8    65 ms    86 ms    66 ms  162.158.52.19
  9    63 ms    63 ms    63 ms  one.one.one.one [1.1.1.1]
 
No issue on my end.

Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                  2001:4490:4005:7e60::1 -    0 |   20 |   20 |    0 |    0 |    1 |    0 |
|                      Request timed out. -  100 |    5 |    0 |    0 |    0 |    0 |    0 |
|                      2001:4490:33fc::8f -    0 |   20 |   20 |    2 |    2 |    3 |    2 |
|                      Request timed out. -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                      Request timed out. -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   2001:4490:effe:1::4:0 -    0 |   20 |   20 |   14 |   15 |   16 |   15 |
|                   2001:4490:effe:1::4:1 -    0 |   20 |   20 |   14 |   14 |   15 |   15 |
|                   2001:4490:effd:1::4:1 -    0 |   20 |   20 |   50 |   50 |   52 |   51 |
|                      2401:7500:fff6::48 -   38 |    8 |    5 |    0 |   51 |   56 |   50 |
|                       2400:cb00:202:3:: -    0 |   20 |   20 |   49 |   52 |   68 |   49 |
|                    2606:4700:4700::1111 -    0 |   20 |   20 |   48 |   48 |   49 |   49 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)

Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                               10.15.9.1 -    0 |   11 |   11 |    0 |    0 |    0 |    0 |
|                              10.0.196.1 -    0 |   11 |   11 |    0 |    0 |    1 |    0 |
|                             10.219.41.2 -    0 |   11 |   11 |    2 |    2 |    2 |    2 |
|                      Request timed out. -  100 |    3 |    0 |    0 |    0 |    0 |    0 |
|                            10.200.99.33 -    0 |   11 |   11 |    9 |    9 |    9 |    9 |
|                         117.216.207.122 -   13 |    8 |    7 |   56 |   56 |   56 |   56 |
|                            162.158.52.4 -    0 |   11 |   11 |   52 |   55 |   72 |   72 |
|                           162.158.52.35 -    0 |   11 |   11 |   52 |   59 |  111 |   53 |
|                                 1.1.1.1 -    0 |   11 |   11 |   53 |   53 |   55 |   53 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v1.00 GPLv2 (original by Appnor MSP - Fully Managed Hosting & Cloud Provider)
 
There is no issue on ping/trace route but test-ipv6.com and ipv6-test.com failed.
 
ipv6-test.com, 42.be, bgp.tools, bgp.he.net aren't loading with v6, it might simply be a routing issue. Google v6 test detects it just fine. It's like the issue I had early Friday morning when some sites weren't loading at all, possibly because there was no route to reach them but just for v6 now.

xD5OXEN.png
 
Last edited:
You must log in or register to reply here.
Back