fatal0Efx Posted December 21, 2022 Posted December 21, 2022 On latest build, yet this is still an issue. Cannot get into Geofilter due to some dumb RPC/LSON error. Why is this still a thing? I've had this many versions
Administrators Netduma Fraser Posted December 22, 2022 Administrators Posted December 22, 2022 I'd recommend signing up to Early Access: https://forum.netduma.com/topic/39415-introducing-early-access/ and once approved you can try any firmware there and see if that resolves the issue for you.
fatal0Efx Posted December 31, 2022 Author Posted December 31, 2022 Do you have firmwares that actually target this issue or am I just to randomly test different firmwares in hopes one of them will just work as expected? I have no clue when the problem actually starts to occur. I'm never in my router's interface. I just leave it open in a chrome tab, that stays up for days/weeks. The moment I need to get in there to play with something, is when I notice it's no longer working. Do you not have any way to troubleshoot this while it's happening? You've connected to my router remotely to troubleshoot something before. Is that not possible here?
Administrators Netduma Fraser Posted December 31, 2022 Administrators Posted December 31, 2022 The firmware in Early Access has a lot of fixes/improvements, it's always best to try what is available to see if that helps, if it does then that reduces troubleshooting, if it doesn't then it gives a better place to start for troubleshooting. What you have just said however is most likely the reason why you're getting that error, the interface isn't meant to be open 24/7, it will be timing out and that will cause errors. Close the tab when you're not using it and open when you need it and I suspect it will work a lot better.
fatal0Efx Posted January 2, 2023 Author Posted January 2, 2023 How does leaving the tab open in the background cause the R2 to completely go bonkers? I understand if the browser did, but closing/reopening the browser has no effect. Plus it's not technically "open". It's in the background behind other tabs.
Administrators Netduma Fraser Posted January 2, 2023 Administrators Posted January 2, 2023 12 hours ago, fatal0Efx said: How does leaving the tab open in the background cause the R2 to completely go bonkers? I understand if the browser did, but closing/reopening the browser has no effect. Plus it's not technically "open". It's in the background behind other tabs. The interface times out, when that happens it breaks the Remote Procedure Calls (RPC) that usually take place and shows the error. Once you've changed an option on the browser close the tab completely, when you want to use it again open it again and you shouldn't have an error.
fatal0Efx Posted January 4, 2023 Author Posted January 4, 2023 When it times out, there's no other way to get it back than to restart the router? I've never seen a browser session tank the service it was accessing before. Usually the page just times out.
Administrators Netduma Fraser Posted January 5, 2023 Administrators Posted January 5, 2023 It should be okay if you refresh the page but the error may still appear, if you click ok it should go away
fatal0Efx Posted January 26, 2023 Author Posted January 26, 2023 On 1/5/2023 at 9:28 AM, Netduma Fraser said: It should be okay if you refresh the page but the error may still appear, if you click ok it should go away If this were true I wouldn't be worried about it as it would just be a nuisance. The problem is, when this error starts to occur, my ability to use the geo fence page completely goes away until the router is rebooted. This is not OK.
Netduma Liam Posted January 26, 2023 Posted January 26, 2023 9 hours ago, fatal0Efx said: If this were true I wouldn't be worried about it as it would just be a nuisance. The problem is, when this error starts to occur, my ability to use the geo fence page completely goes away until the router is rebooted. This is not OK. Can you not click OK to get it to go away? Out of interest, when was the last time you factory reset the R2?
fatal0Efx Posted February 1, 2023 Author Posted February 1, 2023 On 1/26/2023 at 10:00 AM, Netduma Liam said: Can you not click OK to get it to go away? Out of interest, when was the last time you factory reset the R2? When I click OK, it comes back immediately in an endless loop. I factory reset the last time I had this issue, as well as when I got this latest firmware which was hopeful to fix it.
Netduma Liam Posted February 1, 2023 Posted February 1, 2023 7 hours ago, fatal0Efx said: When I click OK, it comes back immediately in an endless loop. I factory reset the last time I had this issue, as well as when I got this latest firmware which was hopeful to fix it. OK, thanks. What device(s) do you have added to Geo-filter? Could you try reserving these devices IP addresses from Network Settings -> LAN -> DHCP and also make sure they've got a name in Device Manager. Then remove and re-add them from Geo-filter if they're already added. Let me know if that helps.
fatal0Efx Posted February 2, 2023 Author Posted February 2, 2023 14 hours ago, Netduma Liam said: OK, thanks. What device(s) do you have added to Geo-filter? Could you try reserving these devices IP addresses from Network Settings -> LAN -> DHCP and also make sure they've got a name in Device Manager. Then remove and re-add them from Geo-filter if they're already added. Let me know if that helps. Just a single device, my Xbox. Has been DHCP reserved since the router was installed (I don't like IPs changing) and has had a name in device manager for just about as long. FYI.
Netduma Liam Posted February 2, 2023 Posted February 2, 2023 How bizarre. Do you know if your ISP uses IPv6? Can you try disabling this from the WAN and LAN settings and check if the problem persists?
fatal0Efx Posted February 10, 2023 Author Posted February 10, 2023 Bizarre, indeed. I do not think my ISP uses ipv6 but I went ahead and disabled it on both wan and lan. The issue isn't currently happening so I guess it'll take me a few weeks to know for sure.
fatal0Efx Posted February 10, 2023 Author Posted February 10, 2023 OK, well changing those settings has triggered all sorts of issues. Lost network connectivity, but finally came back, but now my PC cannot resolve DNS through the router AGAIN. This is an old issue that has plagued me for the longest time but has not reoccurred in months, but now it's back! I mean seriously?!?! Note: In the images below you'll see that the router is pointing at the DNS servers that work if I directly use them, but the router is "refusing" the DNS queries. This router is a nightmare.
fatal0Efx Posted February 10, 2023 Author Posted February 10, 2023 Had to reboot the router again to get the DNS to come back. Ugh.
Netduma Liam Posted February 10, 2023 Posted February 10, 2023 The DNS issue should be fixed in the next firmware. Can you set DNS manually on the client machine and check if it occurs again? Krush 1
fatal0Efx Posted February 11, 2023 Author Posted February 11, 2023 Well that's good news. I don't understand your ask. If I'm using static DNS on the client and not the router then it would for sure not happen again. While I'm thinking about DNS, it would be nice if we had an option to set DHCP options, e.g. pushing specific DNS servers down to the clients.
Administrators Netduma Fraser Posted February 11, 2023 Administrators Posted February 11, 2023 I think Liam means if you can use that method in the meantime without the issue occurring then please do until the next version resolves the issue for you. Thanks for the suggestion!
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