IPv6 setup on your router behind JIO router

  • Thread starter Thread starter bhojv74
  • Start date Start date
  • Replies Replies 48
  • Views Views 18,352
Could someone please help me configure JioFiber with pfsense as an OPT interface?

I would really like to have this working during the trial period.
 
upal said:
Even the IPv6 subnet is dynamic and changes with every ONT reboot or more like after expiring the DHCP lease time.
As I’m using Pi-Hole for my network what I had to do was disable DHCPv4 as Pi-Hole is managing it otherwise the DNS does not change for some reason. And for IPv6 it is automatically assigned from the router itself (stateful). But I have to keep running a script even though it’s on a crontab in order to update the Public IPv6.
So my guess is that even the IPv6 ranges has a lease time and after it expires then it changes the IPv6 addresses for the clients too.
Click to expand...
are you using openwrt?
 
I don't have a Jio Fiber connection, and this is what I could infer with the limited digging I could do with a JioFi :

JioFi Status Page :
image.png

Windows Client IPv6 :
image.png

Traceroute :

image.png


Ping to 2409:4063:4215:294d:1020:f0ff:fe0c:c33e :

image.png


As we can see the JioFi gets assigned an IPv6 address, most likely via IPv6 DHCP, since it doesn't match the subnet from which the downstream clients are assigned IPv6 addresses.

Also via DHCPv6 the JioFi requests a /64 delegated prefix : 2409:4063:4215:294d::/64 which is used to assign public IPv6 addresses to downstream clients.

On pinging 2409:4063:4215:294d:1020:f0ff:fe0c:c33e I receive a reply time of <1ms (if this was DHCP relay, then the response time on LTE would never be <1ms even if I was sitting right below the towers) which means this is the IPv6 address that the JioFi is using to advertise itself through SLAAC to downstream devices (NO DHCPv6, hence no possibility of getting delegated prefixes further downstream).

varkey said:
Mobile connections doesn't seem to support IPv6 prefix delegation which is necessary for your LAN devices to get IPv6 addresses.
Click to expand...

On tracing route to the public IPv6 address assigned to my computer (2409:4063:4215:294d:f7:3497:4552:23f4), we get the following result :
image.png

Which further confirms that the JioFi is in fact acting as a proper IPv6 router, not just relaying IP addresses.


[/QUOTE]
ShihabSoft said:
All I did was create a new bridge between LAN and WAN. After applying the changes.. voila! my LAN clients got IPv6 directly from the ISP via the JioFi router in bridged mode..
Click to expand...
If you go by this approach you lose all the firewall features (+ other layer 3 features) of the pfSense firewall. That's equal to removing pfSense from the middle.


Now, if you want to use pfSense as an IPv6 router, there's no other way than to use IPv6 NAT. Here are steps to do so :

TL;DR : This must be used only and only if you absolutely need IPv6 connectivity (torrents, VPS, etc.). This method does not provides publicly routable IPv6 addresses to end hosts :

Step 1 : Change WAN Interface to obtain IPv6 address via SLAAC :
image.png


Step 2 : Assign a private IPv6 Address to your LAN Adapter ( Any range from fc00::/7). I chose mine to be fd00::1/64
image.png

Step 3 : Go to Firewall > NAT > Outbound

Choose Hybrid Outbound NAT Rules Generation and add the following mapping : (Leave all other settings at default)

image.png


Step 4 : Go to Services > DHCPv6 Server and RA > LAN > Router Advertisements : (Leave other settings at default, be sure to match the advertised subnets with that you chose under LAN)

image.png


Save and restart pfSense.

Go to ipv6.google.com and you should see the page load.

image.png
 
Last edited:

Top