Netduma Fraser

Provide a screenshot of the DHCP page on the linksys and I can guide you from there

It should just be assign a static/reserved IP to the R3 and then pop that in the DMZ and you're good to go. You could try assigning the IP outside the DHCP range and then disable DHCP (make sure you give those nodes and any other devices IPs outside the range first) and that way if there is an issue with the DHCP implementation it may stay working.

In theory both options should work unless there is an issue assigning an address to the router. I'm confident it would be exactly the same as I don't think it's on the R3 side.

If you're putting the ISP modem back in router mode then yes you still need to assign the local IP address. With bridge mode that's not applicable.

Access using the IP http://192.168.77.1 and see if that works

That's great thank you, I'll pass it onto the team to have a look at. Do whatever you need to to get internet/access again.

Ahh I see, yes it does say only to their equipment, I'd keep it that way at least for a few days to see if that has fixed the NAT issue

There are many servers clustered in a location, so you're not denying every server located that. You exclude a location by having it outside your radius.

If the ISP modem is in bridge mode it won't affect any devices connected to the R3.

Try accessing the logs using this link http://192.168.77.1/cgi-bin/logs.txt it should work even without normal access

The allow/deny doesn't mean it will only force you onto those servers, it just means you can connect to it if your Geo-Filter settings would normally exclude it. If you want to force specific servers then cover them specifically with the radius and enable strict mode.

Change the console to use automatic network settings, then check the IP on the console, then check the Device Manager for the device you think it is, do the IPs match? If so please provide a screenshot of your Geo-Filter page.

What firmware version are you on currently? I know there was an issue with Sonos on earlier firmware's but we did fix it, are you on .236?

For the Sonos I suspect it's not liking the automatic band switching for the WiFi so split the bands, connect it to 2.4GHz and assuming that works then run the bridge mode and see if it works better.

What did it say when you tried to connect to it? If that happens again please try to grab the logs from router via ethernet prior to rebooting - any helpful information is lost upon a reboot.

Just replied to your email and seen you've received that and have the tracking now

We're aware of this issue and looking into it, in the meantime, remove the device from the Geo-Filter, then in the Device Manager give the PC the Xbox device type, then re-add it to the Geo-Filter and it should work then.

Good advise above, in addition: Experiment with the widths to see what gives better results Ensure it's in an elevated position - not on a metal surface Ensure there aren't any electrical / wireless devices e.g headphones etc within close proximity ~3 feet if possible

I live on a full ground floor, between the router and the furthest point there are 3 fairly thick walls in the way and I still get full bars of signal just to give you an idea.

It's very hard to do that because everyone's setup/home environment will be different, there may be more obstacles which might limit the range. I'd say the hardware on the R3 for WiFi is better than the XR500 and more akin to the XR1000.

When that happens grab the log from the System Information page using a wired device and post it here please

Tray is essentially the leading person on Apex and the R3 working together and from what he's shown before that will work. It looks to be a port issue, either the game not requesting the right port or us not opening it properly with UPnP.

The WiFi stops working in what sense? I'd say they're probably comparable but let me know your issue and we can probably resolve it.

The server that's hardcoded for use isn't working properly, as we don't own the server there isn't anything we can do about that and as development is in full force for DumaOS 4 for the R2 it'd take more time to push out an update to change the server. It will be working properly in the DumaOS 4 update.

Same as before, utilizing Congestion Control and priorities - CC will ensure devices can't make each other lag and priority will put you ahead of everyone else