Great News - Bsnl enabled IPv6.

  • Thread starter Thread starter Ejaz
  • Start date Start date
  • Replies Replies 66
  • Views Views 8,315
Although my router gets an IPv6 address on the WAN it isn't able to assign an IPv6 to my devices guess RA is off. Ok, so they had to screw up somewhere!
 
@Trex Try DHCPv6 on WAN and SLAAC or DHCPv6 on LAN and assign DNS manually.
 
headshot GIF by funk
 
Also, they disabled boost speed. Now it is hard-capped(previously shoots up to 400Mbps). Increased loaded latency for download.
The good thing is getting a constant 160Mbps on the 150 plan.

also noticed strange routing.
Code:
IPv4 Upstream
Protocol: PPPoE
Address: 117.2**.1*.1**/32
Gateway: 117.2**.13.1
DNS 1: 10.0.0.20
Connected: 10h 48m 58s

this is the config on pppoe tunnel but traceroute tells me something else.
Code:
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  10.0.0.1 (10.0.0.1)  3.823 ms  3.757 ms  3.723 ms
 2  61.2.28.1 (61.2.28.1)  57.158 ms  58.493 ms  58.465 ms
 3  10.219.14.166 (10.219.14.166)  59.183 ms  59.153 ms  59.123 ms
 4  * * *
 5  * * *
 6  * * *
 7  172.69.202.2 (172.69.202.2)  69.760 ms  60.911 ms 172.68.39.7 (172.68.39.7)  60.815 ms
 8  one.one.one.one (1.1.1.1)  61.997 ms  62.049 ms  62.004 ms
 
Is it same for other traceroutes too?
 


One more discovery. They have increased MTU size from 1460 to 1492.
Code:
trex@hpdebian:~$ ping -M do -s 1464 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 1464(1492) bytes of data.
1472 bytes from 1.1.1.1: icmp_seq=1 ttl=53 time=12.4 ms
1472 bytes from 1.1.1.1: icmp_seq=2 ttl=53 time=12.7 ms
1472 bytes from 1.1.1.1: icmp_seq=3 ttl=53 time=18.1 ms
 
Same here,

I did complain about it and its been a month. Don't think they'll fix it anytime soon. Btw are you from Maharashtra as well? I'm from Maharashtra and facing the same issue. Do let me know if it gets fixed for you.
 

Top