For anyone interested in enabling ICMPv6 traffic on JioFiber, I stumbled across something rather interesting: the ICMPv6 filtering appears to happen upstream at Jio itself, rather than simply being a firewall rule on the customer’s ONT.
I was able to verify this directly on a JioFiber ONT. Even after accessing the router through Telnet and manually changing the ip6tables rules to permit ICMPv6 echo requests, externally initiated pings still resulted in complete packet loss. The giveaway was tracing the traffic from an IPv6 host on the public internet. An MTR/traceroute showed the packets making it as far as Jio’s regional edge infrastructure with addresses in the 2405:200:10a:... range (in my case) appearing along the path before the traffic was discarded. The packets never made it as far as the subscriber’s fiber router =)
Just tells us that Jio is filtering ICMPv6 echo requests at the BNG/edge level for subscriber IPv6 prefixes. And of course this does not appear to apply universally to inbound IPv6 traffic. No wonder a basic ping6 from outside the network gets absolutely nowhere.
I was able to verify this directly on a JioFiber ONT. Even after accessing the router through Telnet and manually changing the ip6tables rules to permit ICMPv6 echo requests, externally initiated pings still resulted in complete packet loss. The giveaway was tracing the traffic from an IPv6 host on the public internet. An MTR/traceroute showed the packets making it as far as Jio’s regional edge infrastructure with addresses in the 2405:200:10a:... range (in my case) appearing along the path before the traffic was discarded. The packets never made it as far as the subscriber’s fiber router =)
Just tells us that Jio is filtering ICMPv6 echo requests at the BNG/edge level for subscriber IPv6 prefixes. And of course this does not appear to apply universally to inbound IPv6 traffic. No wonder a basic ping6 from outside the network gets absolutely nowhere.
