| This is just a list of things I did to see if I could enable it... And I could. There's really no guarantee that any of this will actually work, and moreso it could break at any point and you're very much on your own at that point. Most importantly, the reset button on the device does not switch back to Router Mode... so if it's broken you may not be able to fix it. |
After a conversation with a friend about VM's Hub 2.0 and it's inability to do Modem Mode when IPv6 is enabled I got that drive to explore. Figuring that DSLite is a standard protocol (RFC6333) I figured it wasn't going to be impossible to get running... So that begged the question, can I get the unit into Modem Mode to experiment?
After a great deal of scanning through JS, yes. So once I was logged in I managed to navigate to the Modem page at http://192.168.0.1/?modem_settings&mid=Modem. Not one to be put off by a blank page I had an explore and discovered the display: none tag on #mainpage. An easy mistake to make, I suppose... But once visible I saw the following:
Being as curious as I am... I couldn't help myself. But first a quick pit stop on the Info page. I vaguely remembered that there was some info about the AFTR host there, so before committing to Modem Mode I decided to jot down some settings:
I also took a second to resolve aftr01.upc.ie for good measure. Once I had all that noted down I took the leap of faith that was enabling Modem Mode. Once enabled, everything stopped working as expected, but then stayed that way... I decided to wait. This bit took an inordinately long time, maybe 15 minutes. My OPNSense box was picking up nothing from the Hub. A bit panicky at this point I power cycled the Hub (using the switch) and boom everything came back to life.
And it worked... and everyone lived happily ever after. Except GitHub, Twitch, Amazon, and anyone else who requires IPv4... because who needs IPv6 right?
Despite the fact I could be living my best IPv6 only life, I figured that I might not fare so well with Revenue's ROS and My Account not being IPv6 enabled. So I got down to business with DSLite, and to my surprise it was pretty straight forward. On OPNSense it was just a case of creating a new GIF which was helpfully signposted by this blog post.
It's worth noting that 192.0.0.1 (for the AFTR side) and 192.0.0.2 (for the "B4 element"... basically CPE) are fixed addresses and shouldn't ever change. See RFC6333 Sec 5.7.
Once that was created, and assigned as one has to do in OPNSense, I set the gateway for IPv4 traffic to be the new GIF that I created and everything magically worked. With some further tinkering that I won't go into here my LAN interfaces could also use /64's subnetted off the /57 that I was getting off VM, meaning all my networks could have un NAT'd IPv6.