Jump to content

Killhippie

Members
  • Content Count

    718
  • Joined

  • Days Won

    18

Killhippie last won the day on September 3

Killhippie had the most liked content!

About Killhippie

  • Rank
    Senior Member

Profile Information

  • Gender
    Male
  • Location
    UK
  • Interests
    Making Soylent Green

Recent Profile Visitors

1,380 profile views
  1. FF does not tell you the password is not good or long enough unless you are talking about Firefoxes master password which is not the same as logging into your router. In the update 2.3.2.56 it does say 'Support GUI login weak password protection' So if you are talking about the login for your router then if its weak Netgears code will ask you to change it and for good reason as its to protect you.
  2. And I have and as I mentioned it just all goes around in circles, you know what Netgear is like. Also you get no real support after 90 days, just vitriol from some very rancid users quite a lot of the time. Its not a good environment to deal with bugs, some people don't even realise its a Netgear router! On this forum people can talk without anger and that's a good thing and the forum does feel friendly, also the staff are great. Id rather voice my concerns to Fraser or Alex or Jack than deal with the bowels of hell, sorry I meant the Netgear forum.
  3. They have been fielded at Netgear believe me. Netduma are responsible for fixing bugs in DumaOS and passing them on to Netgear and it seems many which arrived with Milestone 1.3 point to DumaOS for which they acknowledged some, and others are Netgears, but they all have just have just vanished into a black hole of promises, with each side seemingly passing the blame to the other. No matter what, it does not take 8 months to release a patch which virtually no fixes in it for major bugs like VLAN tagging, or DumaOS's QoS issues or port mapping GUI bugs or actual port mapping bugs. Netgear say talk to Netduma, and vice versa and the users are none the wiser and this process of going in ever decreasing circles just continues. You of all people know how fast Voxel can turn around an update, so there really is no excuse for the lack of fixes from Netduma to pass to Netgear as I see it apart from red tape at Netgears end, but even then Netgear used to kick out quarterly updates. Most of the bugs seem to be relying on milestone 1.4 to fix and that's in my view not a good way to patch a router. I really think this side of the Netgears router business is not being prioritised at this time with AX being pushed so hard now, but that's just a theory I'm well aware you can't just release fixes "willy nilly" too but with promises of fixes for bugs almost a year old still not fixed after Netduma said they would be fixed or at least if its not one of their they would communicate with Netgear who do we hold responsible? As to "Be patient and show some understanding" I have for 8 months and look where that landed us <sigh> I think the Netgear ,Netduma sandwich is not working well at this time as far as fixing issues. I also can't see it improving when Netduma don't appear to have a timescale for bug fixes. The issue is when you get answers like " Of course we plan to continue to fix issues and keep improving the firmware but no specific news on fix timelines" it does not give you renewed confidence that things will improve.
  4. So you didn't learn that people need regular bug fixes in those 8 months? Not new milestones? New features are great but fix the bugs at a regular intervals, new features can come later when we have had old bugs that have been around for 9 months squashed. Seeing Netduma being proactive in bug hunting and fixing those issues inspires confidence, rhetoric about new features and zero talk about fixing issues does not. Right now I have no faith in Milestone 1.4 because there are so many bugs from almost a year ago that are still not fixed in DumaOS. Why is that? I really want to know why in those 8 months no major bug fixes were pushed to users with issues with QoS and VLAN tagging and Geo filter issues, and the mess that's the device manager that is still being back to front in table view compared with Netgears own port map? All these issues came with Milestone 1.3 in December 2018, almost 9 months ago now, Its a simple question, that really deserves an answer I believe. Why cant You guys just release regular fixes rather than making a new milestone with zero fixes in between or just add new features along the way instead of lumping it all together in what will always be a buggy update, not because you are bad devs but because that's the nature of big software re-writes, they all have bugs, hence patches to fix these bugs after release. Patching only by milestone seems an insanely bad way of dealing with these issues in my view and a very easy way to lose your customer base. More transparency about what's going on would really help too, If the updates are DumaOS related why do you have to get permission from Netgear when DumaOS is your code?
  5. So the XR500 is ageing hardware now and cant handle QoS? 🤫
  6. So we have had no real fixes in almost a year, a update that really fixed a few game issues but was mainly a kernel security patch and you have no idea when you will fix bugs? Also no posts about Milestone 1.4 as promised either, in fact that's all gone silent. It seems nothing has changed or has been taken on board from the community, no lessons learned from the 8 month gap between milestone 1.3 and this last patch. So many users have said we need fixes between milestones not fixes in new milestones! Not the best statement for Netduma or DumaOS tbh from my point of view, let alone in keeping those who stayed on board invested with seeing regular patching of bugs and a timeline laid down for doing that. Some users have had their patience pushed pretty much to the limit already by the lack of structure in regular bug patching and also the lack of any meaningful dialogue going forward about how to change this apparent stagnation, it feels like nothing is going to change. 😒
  7. Firmware updates put a lot of strain on routers or any equipment and that’s most likely when will fail, how many times have you seen computers and phones go down when there is a firmware update on forums. I’m not saying it’s hardware but the only way to check would be to go back to the previous version and test using that then update without doing a factory reset maybe. For the small amount of time you’ll be online with the previous firmware you will be fine just to see if it is a firmware issue then have the latest firmware version downloaded ready so after testing you can update straightaway. If you are still having issues I would contact netgear too as they are in charge of the hardware side of things.
  8. Not buy much and TX wise all routers are at thier limit, the so called active antenna don't do that much and you cant transmit any more powerfully than a XR500 or a XR300 as their are legal limits that all powerful Netgear routers tend to reach they just add things like 'active antennas as part of the price justification. If the small gains are worth the price go ahead. I would say you wont really notice that much tbh. (R7800 compared with the R9000 (XR500 vs XR700) nothing has changed hardware wise apart from the XR500 gained a as yet unused extra 128MB flash NAND to bring it to 256MB vs the R7800's 128MB. Below are some tables showing wireless performance for the R9000 (XR700) and the R7800 (XR500) and a complete review of the R9000. Nothing has been done to the XR700 to make the Wi-Fi better than the R9000 its just in a new shell with a new paint job, and is still buggy for its price as was the R9000 which is no surprise as they are identical hardware as I mentioned. https://www.smallnetbuilder.com/wireless/wireless-reviews/33046-netgear-r9000-nighthawk-x10-smart-wifi-router-reviewed
  9. Netgeasr cant predict when Netgear is releasing a firmware update
  10. yo m8 how come when I set it all up the servers pop up on my geofilter then dissapear

    1. stef

      stef

      I have it on filtering mode nothing happens

       

  11. Weird how these bugs work on different set ups, I'm not dropping anything out on Ethernet at all, streaming etc is flawless. This why Netgear should really do more controlled public beta testing as there are so many permutations to check out. Also it could be hardware, you could downgrade briefly and see if things work okay and then update again, but I understand you not wanting to.
  12. Delays seem to be the one thing we can guarantee will happen it seems. I know this stuff happens but surely this was something that really didn't need any delays and should have been gotten in front of ready to be posted, otherwise it's just another case of rinse and repeat.
  13. Thought you said you used Ethernet? (which is what I meant by cable)
  14. Don't you also need DHCP option 61 with SKY which I think the XR500 got with 2.3.2.40 as well?
×
×
  • Create New...