We are pleased to announce that Router Firmware 8.6.0 RC 4 is now available.
This firmware is expected to become GA in about two weeks.
The Direct Access Mode support for the SF Connect App is currently available through beta testing. Please join the test and share your feedback.
Great news and so many fixes! Highly appreciated 
I noticed the new IPv6 SLAAC/DHCPv6 WAN configuration in RC4. Does this update also add a stateful IPv6 firewall (default deny for inbound traffic), or does the B One still simply route globally routable IPv6 addresses to LAN clients without inbound filtering?
Does the B One fully support DHCPv6 Prefix Delegation (PD) together with SLAAC, including proper prefix delegation to multiple VLANs?
The software stack is still – for all practical purposes – oblivious to IPv6.
The key difference appears to be that you can use SLAAC/DHCPv6 instead of raw IPv6 passthrough for one-and-only-one WAN. And you still cannot assign this traffic to a VLAN.
Baby steps I guess! 
But progress is progress. 
I’d still be the most happy if they’d just support IPv6 on the WAN side so SpeedFusion (etc) could easily negotiate more point-to-point links by avoiding CGNAT.
Yes you are right. But be aware, that as soon as you activate IPVv6 on WAN settings, you expose all your clients behind the Peplink router to the WAN. So better have a e.g. a Fritz!Box with IPv6 firewall (at least deny all inbound rule) before the router.
See: Post
Has this behavior changed in firmware 8.6.0 RC4? Does the B One now provide a stateful IPv6 firewall for routed traffic, or does it still rely entirely on the upstream router’s IPv6 firewall?
For me it would be helpful, if the PL router could create a /62 or /64 IPv6 network for every VLAN based on a /56 IPv6 network received by Prefix Delegation from the provider router.
I believe there is a bug related to FIPS mode with a Max BR1Pro 5G. When FIPS mode is enabled I’m unable to connect using Remote Web Admin from IC2. Turning on Remote Assistance on the device resolves the problem. Returning to 8.5.4 or disabling FIPS mode resolves the issue as does turning on Remote Assistance. I’ve raised ticket 26070041 as this issue might be masked for most people as RA is normally activated when using beta firmware.