Netduma Fraser

That open does seem a bit sus, we can come back to that if needed but ideally it should be off. So your DHCP range starts at .10 so change the R3 IP to be between .2 - .9, if you have any other devices connected to it then reserve IPs for them within this range also. Then see how it is, if the issue happens again then disable DHCP on the Linksys.

PPPoE is the cause of that issue, we're aware of it and it should be fixed for the upcoming 3.3 beta, in the meantime you'd need to have the hub handle PPPoE for now. Yes I'd still recommend utilizing traffic prio.

If you want to force specific servers then cover them specifically with the radius and enable strict mode.

What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g. R3 in its DMZ, modem/bridge mode. Are ALL devices connected to the R3? Where are you testing the speeds? Is speed test bypass enabled?

You have to be connected via ethernet to the router to get internet and access to the interface

We tried to get into the playtest but we weren't able to, otherwise we definitely would have tested it. Whenever there is another playtest or upon release we'll test it and try to get it supported.

Ah good to hear, thanks for the update!

Well previously you had strict mode off so yes it would have got you local servers.

If it's saying DumaOS not loaded then it's not bricked. You should be able to access settings via http://routerlogin.net/adv_index.htm and you can re-install the firmware from there or initiate a reset from the interface

Yeah it's fine, it's local information

While connected to the router via a wired Windows PC, open command prompt, type ipconfig press enter and then post a screenshot of the results here please.

You should be able to connect to the interface using: http://192.168.1.1 or http://10.0.0.1 or http://routerlogin.net do any of those work? Is it the XR1000 you have? Did you connect the internet port on the XR to your modem and then one of the LAN ports to your PC?

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?