Jump to content

MotFPS

Members
  • Content Count

    31
  • Joined

  • Last visited

About MotFPS

  • Rank
    Apprentice

Basic Info

  • DumaOS Routers Owned
    XR1000

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Still broken with new firmware. Terribly slow. Here's a video taken with incognito mode (no cache) https://youtu.be/NHb3ekAxxF4
  2. Negative. I was tracking the .58 was only security updates.
  3. I think you're alone on that one. Just casually opening the interface right now took over 40 seconds to present the GUI. The interface issues are still present and very much a problem. I can take videos if needed to show how bad it is for a 'daily driver'
  4. https://kb.netgear.com/000063915/XR1000-Firmware-Version-1-0-0-58 Last Updated:08/12/2021 Why has this been out since 12th of Aug and we haven't heard anything?
  5. Negative. They figured out a work-around not a solution. They're disabling DHCP on the XR1000 and using pihole as a the DHCP server. I'm doing that now as a temp work around. We'd like an actual solution implemented. Other brands of routers allow the user to manually specify the LAN DHCP DNS options (dlink, linksys, etc) but not this $300 router? This is something that should be in the new firmware.
  6. The above thread goes into more detail but basically, the firmware as it is does not support pihole since you cannot modify the DHCP option for DNS servers. You can only do so on the internet side which is not compatible with pihole. Please see the discussion on this thread.
  7. Admins, In the new firmware coming out, will I be able to use my Pihole with the XR1000?
  8. My video was based on FF, a browser that I only use to view my cameras. I used incognito mode too just in case it wanted to save cookies, etc. Essentially, it's a fresh install of Firefox I never use.
  9. I'd like to chime in here. I feel like the interface on the XR1000 is incredibly slow. I made a short video about my experience rather than explain how to replicate the problem. Video of the XR1000 taking minutes to load the web interface: I did a full factory reset a week ago when I was troubleshooting the DHCP bugs the XR1000 has. It's a very fresh config of the XR1000 and most likely represents the optimal conditions of the XR1000's web interface's performance.
  10. Thank you Fraser. Entirely, my use of pihole is what complicates these issues (DNS, guest wifi, etc). Using an external DNS server removes these problems however with pihole becoming more mainstream I'd like to see the use of pihole considered from the Netgear/Netduma family. Pihole (and similar services) offer features that many people have become reliant on. Netduma/Netgear with pihole support is a perfect scenario that a huge community would be ecstatic over. Again, thank you for being active on this forum.
  11. @Netduma Fraser I know you're busy I see you're active on here a lot which I'm very thankful for. Any update on this bug?
  12. That's correct. "allow guests to see each other" gives Guest Wifi clients access to the custom DNS server. However that negates the entire point of having a guest wifi network. Reasons for having an isolated guest wifi network include having untrusted IOT devices in your home (Wemo, nest thermostats, etc). As well as actual guests that you don't want on your LAN. The entire point of the guest network is isolation. Giving those devices LAN access to enable DNS functionality is what I'm trying to avoid. I'd like to see an option to allow guest wifi clients access to a single IP for homes with a pihole. The problems stems from the unfixed DHCP bugs and custom DNS servers hosted on the LAN (Pihole installs)
  13. I disabled the DHCP sever on the XR1000 due to DHCP server bugs (unable to use pihole/it's on a separate topic/Still unfixed bug). This also is repeated when using a pihole on the network. Running a pihole as a custom DNS server works for LAN (wired/wireless) clients but breaks when using the guest wifi feature. In my case the XR1000 isn't the DHCP and DNS server, guest wifi connections cannot resolve DNS queries. The guest wifi can contact internet IPs without DNS but this effectively breaks most devices connected to the guest wifi especially IOT devices where you cannot specify a DNS server. The root cause is because my DNS server is a pihole device on the LAN segment that the guest wifi is unable to communicate with. So while this is related to my DHCP issue, it is really caused because my custom DNS server is blocked by the guest wifi firewall. In essence, the guest wifi works perfectly since it still gets a DHCP IP address from the LAN but because I'm using a custom DHCP server and DNS server, the guest wifi doesn't know to give guest wifi devices access to that custom DNS server. Fix: Give an option to allow traffic between the guest wifi and a specific LAN IP address. Essentially, the guest wifi would still be segmented but a user specific IP would be allowed to be connected to the guest wifi giving people that want a working pihole with this netgear to continue to use it.
  14. When you added your new router, your PC would have detected another connection. Is it set to private under network settings? If it's "Public" your windows firewall isn't going to allow any games to connect. Also make sure you're seeing a UPNP connection, while your game is running. That will narrow down if you're problem is at your PC or the router.
×
×
  • Create New...