craiga79 Posted February 5 Share Posted February 5 I thought I'd feedback how the R3 has been for me. After getting frustrated waiting for the XR1000 to receive its long awaited update and having to constantly re-boot it to get it to respond, I bit the bullet and bought the R3. I read about the CPU issue and decided to wait until that was resolved before taking it out of the box. I set it up last week on the .40 firmware and it ran beautifully. I've seen the issues being discussed, but my wifi performance was good, gaming felt improved compared to the XR1000, most importantly for me, it didnt drop Voice over Wifi calls that the XR1000 did. Fast forward to .41 this weekend and it has been a nightmare. Firstly I updated without a factory reset and nothing would connect via wifi. So it was factory reset via a browser and it wouldnt respond at all. Then it took about 3 or 4 attempts via the reset pin and I found out I have to disconnect the LAN devices (I have extensive Cat 6 in the house) and configure it with only one device connected. My devices are looking for a 192.168.1.254 address pool and the R3 wont respond to a webpage calling for 192.168.77.1 unless all of the legacy devices are disconnected. There are just too many devices in the house that its easier to change the router IP range than all the devices. Then I realised the wifi performance isnt great in the far end of the house, so I change wifi channels as I'd forgottent to select channel 44 after the reset, the router decides everything on wifi can connect but not access the internet, only cabled devices can get that. So, another factory reset to get wifi working and this time remember to goto channel 44 immediately. Then after a few hours, I realise I forgot to change my dns server to use my adguard raspberry pi. This causes the router to disconnect from the WAN and yep, another factory reset ahead. In between that, Ive had to do a factory reset by trying a wifi repeater. Then my son's PC was randomly refused an internet connection, queue the factory reset. So I went back to .40 in frustration and still found difficulties with wifi connections and had to quickly get the XR1000 running for my sons online class. After that, I revisited the R3 via a fresh .41 install. I have realised that I need a 10min powerdown after a factory reset, so perhaps errors were remaining in memory all along? In summary, I have to get the router setup first time, almost via a checklist to get it working stable. Any wifi, dns or a simple reboot after about 12 hours means I need a factory reset. I know you will ask, so I connect via a PPPoE Openreach ONT device. It feels, to me, that Im trying beta firmware at the moment and I really want something more stable. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 5 Administrators Share Posted February 5 Thank you for the feedback, definitely some weird behavior going on there, best thing you can do in that situation if possible is to grab the log from troubleshooting and we can see what might be happening. Does all appear okay now? Link to comment Share on other sites More sharing options...
craiga79 Posted February 5 Author Share Posted February 5 Last reset was this morning and so far its stable. Next time it behaves unexpectadly I'll grab the logs, unfortunately it was factory reset since then. At the moment, the logs show hundreds of "possible DNS-rebind attack detected". I assume this is blocking using the raspberry pi adguard as my dns server? Looks like its falling back on the second DNS server. Could this be causing the instability? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 5 Administrators Share Posted February 5 That probably is the cause yes, potentially, if it's constantly trying to block something the whole time Link to comment Share on other sites More sharing options...
craiga79 Posted February 19 Author Share Posted February 19 So now my R3 has joined the club of refusing to allow access via a browser and needs switched off and on. Once it reboots, access works for less and less between reboots. This started off at maybe 3 days working, but its now down to around 3 hours rather than a daily reboot. I'd send the logs if I could access the thing. Fraser, I have to say, this is pretty painful. I'm faced with using one firmware that runs the cpu too hard or another that works for a few hours between reboots. If I do another factory reset, it's pot luck which fault will develop. Having to reboot a couple of times a day is the lesser of the problems compared to what I highlighted in my opening post 2 weeks ago when wifi wouldn't allow devices to connect. So Im not even attempting another factory reset until a better firmware is available for fear of it losing wifi connected devices again. Not everyone is affected it seems, but for those that are, these routers don't do the job they were bought for. I think most of us posting here are behind Netduma and want it to work well, but there is a point where we have to question if this product is fit for sale at the moment. I know you won't give eta's on firmware, but it needs to be soon as the goodwill is beginning to run out. If you want to replicate these issues, swap my R3 with a return slip for mine and you can explore it? Im in the UK so can't be too hard to organise? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 19 Administrators Share Posted February 19 The team are doubling down on these issues so I'm sure they will get it sorted very soon. Disabling IPv6 in LAN/WAN has been reported as a potential workaround as well as disabling priorities on SmartBOOST. Once these issues are sorted it'll be much more solid for those of you experiencing them. Link to comment Share on other sites More sharing options...
craiga79 Posted February 23 Author Share Posted February 23 Disabling smartboost worked for a few days. Now the router doesnt allow access after a few hours even with IPv6 disabled in LAN/WAN and Smartboost switched off. When it doesn't provide access it also is bypassing all of the gaming features. Obviously can't even access the logs to share. As I mentioned above, goodwill is running out. My router was ordered Jan 16th and delivered on Jan 18th so over 30 days ago. That said, I opened this post well within 30 days. I'm not going to keep banging the drum for a firmware release, but its time for me to state that, in my opinion, the router does not deliver the advertised features and I am leaning towards requesting a refund (including postage costs) for the router. My XR1000 is getting put back into action this weekend. Fraser, I'm willing to hold out for a few more days but I'm using this post to document the troubles leading up to a return. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted February 23 Administrators Share Posted February 23 Could you email us [email protected] with a link to this topic please and we can help you further there Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now