Netduma Fraser

Thanks for that, looks like they're mostly trying to replace the Sky hub which I think is what we'll have to do. I've heard from the team and there is a fix on the way for VLAN which should be ready for tomorrow if you're able to wait until then? Then I can provide the firmware to you and you should be able to bypass the Sky hub entirely.

Ahh that's good to hear, do keep us updated on that. If you have Geo-Latency enabled there shouldn't be any issues connecting to friends, otherwise have you added them to your allow list on the Geo-Filter?

I've heard back from the team and they have confirmed this is a bug and they are looking into fixing it, thank you for the report!

Thanks a lot, we've definitely made some improvements!

I've sent you a PM, please see if that helps

Possono essere inattivi fino a quando non sei effettivamente in gioco. 80/443 sono improbabili da attivare in quanto sono per la navigazione web, non per giocare.

The router receiving internet should always have the internet source connected to the WAN, like the R3 WAN is connecting to the internet source via the WAN port

We don't give out dates for firmware but when it's available we'll give people access

What are the SmartBOOST priorities you have enabled? If you disable those rather than disabling SmartBOOST entirely what do you get?

It will be pushed to your router so you can upgrade from the interface it contains 3 bug fixes so is quite small, nothing new. I can send it to you manually if you prefer not to wait

I sent you a PM for this and you said it worked, did you factory reset and stuck in the wizard again or is it an issue on a different page?

If you disable SmartBOOST entirely do you still see that problem?

Ah that's great to hear, thanks for the update!

We haven't specifically tested any mobile games as far as I am aware so I will pass this on for the team to take a look into

That's great to hear, thanks for posting the solution!

Yes that's exactly how it would work if they all have filtering enabled, you can click each device and disable them from there if you don't want it to apply to one

You may have needed to reboot the devices after the IP reservation change so they pick up the IP properly. If you still get disconnects could you enable remote support in Settings > Troubleshooting and post back here from a device connected to the R3 please?

We are looking at it not being as reliable as it should be currently. Make your settings on the Geo-Filter, then reboot the console completely then check again, does it seem more consistent then?

I have PMd you

Nunca damos fechas para actualizaciones, ya que siempre están sujetas a cambios. La mejor aproximación que puedo dar en este momento es que podría ser este año o a principios del próximo año.

Could you disable DHCPv6 as well please if that didn't disable when you disabled IPv6 and try again? It's very strange devices can connect directly to it without issues which indicates there aren't any settings you need to enter into the R3 specifically, it should just work

Glad to hear you like it and are enjoying it overall! We're looking into the issues you mentioned currently. For Destiny 2 you'll have to use Geo-Latency to get filter it properly

Thank you for the kind words, we're glad you're excited and happy you liked the note!

Quando si crea una regola di inoltro porta, selezionare l'intervallo di porte invece della singola porta.

DHCP should be active on the R3 as it gives IP addresses to devices connected to the router. No just the WAN IP of the R3 (from Settings > WAN) in the DMZ on the other router and you're good to go.