Jump to content

Killhippie

DumaOS Insiders
  • Content Count

    815
  • Joined

  • Days Won

    18

Reputation Activity

  1. Like
    Killhippie reacted to Netduma Alex in High Priority Traffic possible bug with Indicator light?   
    Going to do tests to isolate this issue.
  2. Like
    Killhippie got a reaction from Netduma Alex in High Priority Traffic possible bug with Indicator light?   
    Was not graphical on mine as my antibufferbloat settings stayed applied with the light on, no rules added, Jack. Just DumaOS classified games ticked and unticking them , turning off antibufferbloat and even QoS didn't stop the issue it was just in a frozen state thinking something was high priorty traffic I even had a friend pull the plug on my TV etc and I turned off all the wifi devices and it still stayed on, always had to be a reboot and since I'm in a wheelchair and my router is high up that was really hard work if in the end a reset (using the reset button on the back always seemed to give a cleaner reset oddly enough) was needed as it seemed to do it more and more often until a factory reset was performed and then it would be okay for a while, until a long gaming session on Destiny 2
  3. Like
    Killhippie reacted to kymadn in High Priority Traffic possible bug with Indicator light?   
    Thanks Jack. You might be right about it being graphical. I am going to get my router back to the stuck High Priority Detected indicator and confirm if bufferbloat is actually applying the whole time after game is closed. I will let you know what i find.

    The High Priority Traffic indicator light 100% stays on with F5 refresh. I also tried multiple browsers and clearing the cache. It just stays on until reboot when its stuck.  
    I have the problem with Apex Legends and Battlefield V on PC which are the only 2 games i play right now. I have no rules added to Traffic Prioritization. I have my PC added as a Console using DumaOs Classfield Games enabled. 
  4. Like
    Killhippie got a reaction from Zippy in High Priority Traffic possible bug with Indicator light?   
    Was not graphical on mine as my antibufferbloat settings stayed applied with the light on, no rules added, Jack. Just DumaOS classified games ticked and unticking them , turning off antibufferbloat and even QoS didn't stop the issue it was just in a frozen state thinking something was high priorty traffic I even had a friend pull the plug on my TV etc and I turned off all the wifi devices and it still stayed on, always had to be a reboot and since I'm in a wheelchair and my router is high up that was really hard work if in the end a reset (using the reset button on the back always seemed to give a cleaner reset oddly enough) was needed as it seemed to do it more and more often until a factory reset was performed and then it would be okay for a while, until a long gaming session on Destiny 2
  5. Like
    Killhippie reacted to Netduma Jack in High Priority Traffic possible bug with Indicator light?   
    I'm going to see if we can investigate this issue with High Priority getting stuck - we'll test it with Apex and Destiny 2 for good measure. It's possible that the issue is graphical but I can't really speculate until we take a look.
    Could you guys confirm whether this persists when you hard refresh the page (F5)? Also @Zippy, could you let us know which game this happened to you on? If anyone has experienced this while playing another game let us know.
    If any of you guys have added your own rules to Traffic Prio, please let us know that as well. The more information we have, the faster we'll be able to get to the bottom of it!
  6. Like
    Killhippie reacted to Netduma Fraser in XR500 Can't connect to internet   
    Hey, welcome to the forum!
    Good advice above. In System Information does the router show that it's getting a WAN IP at all? Also in Settings > Internet Setup have you tried switching it from auto and putting in the details manually?
  7. Like
    Killhippie got a reaction from UK_Wildcats_Fans in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    I appreciate the more transparent side of things here now, Fraser. I still think your devs have patching backwards, I know of no other company that releases new operating systems without patches for their software in between major releases. Its just seems to me a retrograde way of doing things. Apple have just released macOS Catalina and its buggy, now imagine if no point releases came until next year with macOS 10.16 Users would go mad and Apple would never sell another computer probably, same for iOS, Android, Windows, Linux etc.  That is just not how you do things in my view and no matter what the new version hopes and expectations are it will have bugs, you cant make bug free software, its impossible.

     I'm just hoping DumaOS 4.0 or another incarnation of DumaOS wont be the fix for DumaOS 3.0's bugs.  Until I can see a point release path rather than 8-12 month gaps between updates to fix issues with DumaOS software pushed to Netgear hardware, I've had to remove the XR500 as my daily driver for now and box it up. I'm aware this may not be all your fault believe me, and I know you guys work really hard and I will continue to help where I can, but the XR development cycle in my view is unacceptable as it stands. I look forward though to seeing what your plans are with DumaOS nevertheless. Right time for more more coffee  
  8. Like
    Killhippie got a reaction from crawlgsx in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    I appreciate the more transparent side of things here now, Fraser. I still think your devs have patching backwards, I know of no other company that releases new operating systems without patches for their software in between major releases. Its just seems to me a retrograde way of doing things. Apple have just released macOS Catalina and its buggy, now imagine if no point releases came until next year with macOS 10.16 Users would go mad and Apple would never sell another computer probably, same for iOS, Android, Windows, Linux etc.  That is just not how you do things in my view and no matter what the new version hopes and expectations are it will have bugs, you cant make bug free software, its impossible.

     I'm just hoping DumaOS 4.0 or another incarnation of DumaOS wont be the fix for DumaOS 3.0's bugs.  Until I can see a point release path rather than 8-12 month gaps between updates to fix issues with DumaOS software pushed to Netgear hardware, I've had to remove the XR500 as my daily driver for now and box it up. I'm aware this may not be all your fault believe me, and I know you guys work really hard and I will continue to help where I can, but the XR development cycle in my view is unacceptable as it stands. I look forward though to seeing what your plans are with DumaOS nevertheless. Right time for more more coffee  
  9. Like
    Killhippie got a reaction from crawlgsx in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    Sadly that's something I may not be able to do any more. With no guarantees as to updates for releases in the future, let alone no DumaOS updates for months to come and no promise of XR compatibility (because of company NDA's)  let alone no guarantees this wont happen again, its time to find another router as my daily driver instead of the XR500 I think. Just imagine if Microsoft/Apple/Google etc released a new operating system then left it for over a year with no updates for bugs until the next version and then no guarantees your hardware would get it. Its almost back to front in my view. Companies patch so that if there is no new OS for your hardware you have the best version you can have on the hardware you own and to just fix bugs too as a matter of course. The whole create a new version of DumaOS instead of patching the old one will always be my sticking point.  
  10. Like
    Killhippie got a reaction from crawlgsx in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    Thanks Alex, unfortunately that’s what I kind of feared. Basically bugs that came out in milestone 1.3 in what is rapidly going to become a year soon aren’t going to get patched in other words. Anything DumaOS related will be left until version 3.0. Also no one has a real clue how much Netgear will be interested in any of these new features. Also Current bugs with VLAN tagging, QoS getting slow, port mapping in table view and antibufferbloat  getting stuck on and and the leaky hybrid VPN won’t be fixed until this new version is ready and that probably won’t be this year and once again may not come to the XR routers. Is that a fair assumption of the current situation?
      I appreciate you coming up with a new operating system and it takes great effort to create one, but I am a little taken aback by the lack of patching in milestone 1.3 considering it’s almost a year old and virtually nothing has been done to fix the issues with it on the XR routers, as I can’t speak for the R1. I really wish you had focused on bug fixing Milestone 1.3 first before creating yet another new OS rather than leaving things unfixed and with an air of uncertainty as to whether they ever will be patched , because this all rides on Netgear. I think this could be a problem possibly especially since obviously you can’t promise how long this will take, and I have noted the words ‘early days’ which doesn’t bode well for further fixes in the pipeline for DumaOS as it stands on current Netgear hardware with your firmware. So we could be waiting possibly until next year with no fixes at all on the DumaOs side at all. Also a lot depends on Netgear wanting the new version as well, is that correct?  I’m not trying to be negative, I’m just trying to understand where Netgear users stand. 
     
      I hope you understand my concerns, router stability is created hopefully by fixing issues in current firmware no matter how welcome new features are. However the continued lack of support for patching  your own firmware on Netgear hardware I find to be a bit odd. Personally I would need fixes and stability not long  gaps where nothing is happening visibly for DumaOS software thats on existing XR routers, because you are busy creating another new version.Fixing the issues first before moving on seems the more logical approach but that’s just from my point of view.  Are you going to focus on patching rather than creating new versions of DumaOS, because all new operating systems inevitably are buggy. So Will you patch 3.0 or move onto the next version? I hope you can see my concerns. Good luck with version 3.0 nevertheless.
  11. Like
    Killhippie got a reaction from Bat 'n' Ball in High priority traffic stuck on   
    Yes but it seemed everything was high priority traffic tbh. Sorry for the long title, now edited. Pain, Morphine and sleep deprivation isn’t a good mix. 
  12. Like
    Killhippie reacted to Netduma Alex in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    I've replied to you in this thread: 
     
    That IS the plan, the reason we've not been so good at bug patching so far is because we've not had the staff. We've got enough people now that we can have one group working on features and one group working on fixes. Once 3.0 is out, the pressure for features is off, and the pressure for fixes is on.
  13. Like
    Killhippie got a reaction from Delta in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    I appreciate the more transparent side of things here now, Fraser. I still think your devs have patching backwards, I know of no other company that releases new operating systems without patches for their software in between major releases. Its just seems to me a retrograde way of doing things. Apple have just released macOS Catalina and its buggy, now imagine if no point releases came until next year with macOS 10.16 Users would go mad and Apple would never sell another computer probably, same for iOS, Android, Windows, Linux etc.  That is just not how you do things in my view and no matter what the new version hopes and expectations are it will have bugs, you cant make bug free software, its impossible.

     I'm just hoping DumaOS 4.0 or another incarnation of DumaOS wont be the fix for DumaOS 3.0's bugs.  Until I can see a point release path rather than 8-12 month gaps between updates to fix issues with DumaOS software pushed to Netgear hardware, I've had to remove the XR500 as my daily driver for now and box it up. I'm aware this may not be all your fault believe me, and I know you guys work really hard and I will continue to help where I can, but the XR development cycle in my view is unacceptable as it stands. I look forward though to seeing what your plans are with DumaOS nevertheless. Right time for more more coffee  
  14. Thanks
    Killhippie got a reaction from migueltaveras6 in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    I appreciate the more transparent side of things here now, Fraser. I still think your devs have patching backwards, I know of no other company that releases new operating systems without patches for their software in between major releases. Its just seems to me a retrograde way of doing things. Apple have just released macOS Catalina and its buggy, now imagine if no point releases came until next year with macOS 10.16 Users would go mad and Apple would never sell another computer probably, same for iOS, Android, Windows, Linux etc.  That is just not how you do things in my view and no matter what the new version hopes and expectations are it will have bugs, you cant make bug free software, its impossible.

     I'm just hoping DumaOS 4.0 or another incarnation of DumaOS wont be the fix for DumaOS 3.0's bugs.  Until I can see a point release path rather than 8-12 month gaps between updates to fix issues with DumaOS software pushed to Netgear hardware, I've had to remove the XR500 as my daily driver for now and box it up. I'm aware this may not be all your fault believe me, and I know you guys work really hard and I will continue to help where I can, but the XR development cycle in my view is unacceptable as it stands. I look forward though to seeing what your plans are with DumaOS nevertheless. Right time for more more coffee  
  15. Thanks
    Killhippie got a reaction from migueltaveras6 in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    So why couldn't you just patch Milestone 1.3 then, if you have not got enough staff you fix what you have already made surely before starting a new project? Anyway I wish you luck with it and look forward to seeing what's coming. 
  16. Like
    Killhippie got a reaction from joaso in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    I appreciate the more transparent side of things here now, Fraser. I still think your devs have patching backwards, I know of no other company that releases new operating systems without patches for their software in between major releases. Its just seems to me a retrograde way of doing things. Apple have just released macOS Catalina and its buggy, now imagine if no point releases came until next year with macOS 10.16 Users would go mad and Apple would never sell another computer probably, same for iOS, Android, Windows, Linux etc.  That is just not how you do things in my view and no matter what the new version hopes and expectations are it will have bugs, you cant make bug free software, its impossible.

     I'm just hoping DumaOS 4.0 or another incarnation of DumaOS wont be the fix for DumaOS 3.0's bugs.  Until I can see a point release path rather than 8-12 month gaps between updates to fix issues with DumaOS software pushed to Netgear hardware, I've had to remove the XR500 as my daily driver for now and box it up. I'm aware this may not be all your fault believe me, and I know you guys work really hard and I will continue to help where I can, but the XR development cycle in my view is unacceptable as it stands. I look forward though to seeing what your plans are with DumaOS nevertheless. Right time for more more coffee  
  17. Like
    Killhippie reacted to Netduma Fraser in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    I would say the refinements will fix most of the issues, whether or not Netgear decide to take on all of the features but lets face it - why wouldn't they?!  So although it's the longer method of patching bugs it should be more sustainable in the future and produce less bugs hopefully. Totally understand if you're too fedup by it, that why we brought out the insider program to try and be more transparent with what we're up to.
  18. Like
    Killhippie got a reaction from raf1212 in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    Thanks Alex, unfortunately that’s what I kind of feared. Basically bugs that came out in milestone 1.3 in what is rapidly going to become a year soon aren’t going to get patched in other words. Anything DumaOS related will be left until version 3.0. Also no one has a real clue how much Netgear will be interested in any of these new features. Also Current bugs with VLAN tagging, QoS getting slow, port mapping in table view and antibufferbloat  getting stuck on and and the leaky hybrid VPN won’t be fixed until this new version is ready and that probably won’t be this year and once again may not come to the XR routers. Is that a fair assumption of the current situation?
      I appreciate you coming up with a new operating system and it takes great effort to create one, but I am a little taken aback by the lack of patching in milestone 1.3 considering it’s almost a year old and virtually nothing has been done to fix the issues with it on the XR routers, as I can’t speak for the R1. I really wish you had focused on bug fixing Milestone 1.3 first before creating yet another new OS rather than leaving things unfixed and with an air of uncertainty as to whether they ever will be patched , because this all rides on Netgear. I think this could be a problem possibly especially since obviously you can’t promise how long this will take, and I have noted the words ‘early days’ which doesn’t bode well for further fixes in the pipeline for DumaOS as it stands on current Netgear hardware with your firmware. So we could be waiting possibly until next year with no fixes at all on the DumaOs side at all. Also a lot depends on Netgear wanting the new version as well, is that correct?  I’m not trying to be negative, I’m just trying to understand where Netgear users stand. 
     
      I hope you understand my concerns, router stability is created hopefully by fixing issues in current firmware no matter how welcome new features are. However the continued lack of support for patching  your own firmware on Netgear hardware I find to be a bit odd. Personally I would need fixes and stability not long  gaps where nothing is happening visibly for DumaOS software thats on existing XR routers, because you are busy creating another new version.Fixing the issues first before moving on seems the more logical approach but that’s just from my point of view.  Are you going to focus on patching rather than creating new versions of DumaOS, because all new operating systems inevitably are buggy. So Will you patch 3.0 or move onto the next version? I hope you can see my concerns. Good luck with version 3.0 nevertheless.
  19. Like
    Killhippie got a reaction from sharpz44 in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    Thanks Alex, unfortunately that’s what I kind of feared. Basically bugs that came out in milestone 1.3 in what is rapidly going to become a year soon aren’t going to get patched in other words. Anything DumaOS related will be left until version 3.0. Also no one has a real clue how much Netgear will be interested in any of these new features. Also Current bugs with VLAN tagging, QoS getting slow, port mapping in table view and antibufferbloat  getting stuck on and and the leaky hybrid VPN won’t be fixed until this new version is ready and that probably won’t be this year and once again may not come to the XR routers. Is that a fair assumption of the current situation?
      I appreciate you coming up with a new operating system and it takes great effort to create one, but I am a little taken aback by the lack of patching in milestone 1.3 considering it’s almost a year old and virtually nothing has been done to fix the issues with it on the XR routers, as I can’t speak for the R1. I really wish you had focused on bug fixing Milestone 1.3 first before creating yet another new OS rather than leaving things unfixed and with an air of uncertainty as to whether they ever will be patched , because this all rides on Netgear. I think this could be a problem possibly especially since obviously you can’t promise how long this will take, and I have noted the words ‘early days’ which doesn’t bode well for further fixes in the pipeline for DumaOS as it stands on current Netgear hardware with your firmware. So we could be waiting possibly until next year with no fixes at all on the DumaOs side at all. Also a lot depends on Netgear wanting the new version as well, is that correct?  I’m not trying to be negative, I’m just trying to understand where Netgear users stand. 
     
      I hope you understand my concerns, router stability is created hopefully by fixing issues in current firmware no matter how welcome new features are. However the continued lack of support for patching  your own firmware on Netgear hardware I find to be a bit odd. Personally I would need fixes and stability not long  gaps where nothing is happening visibly for DumaOS software thats on existing XR routers, because you are busy creating another new version.Fixing the issues first before moving on seems the more logical approach but that’s just from my point of view.  Are you going to focus on patching rather than creating new versions of DumaOS, because all new operating systems inevitably are buggy. So Will you patch 3.0 or move onto the next version? I hope you can see my concerns. Good luck with version 3.0 nevertheless.
  20. Like
    Killhippie got a reaction from WalkedDave in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    Thanks Alex, unfortunately that’s what I kind of feared. Basically bugs that came out in milestone 1.3 in what is rapidly going to become a year soon aren’t going to get patched in other words. Anything DumaOS related will be left until version 3.0. Also no one has a real clue how much Netgear will be interested in any of these new features. Also Current bugs with VLAN tagging, QoS getting slow, port mapping in table view and antibufferbloat  getting stuck on and and the leaky hybrid VPN won’t be fixed until this new version is ready and that probably won’t be this year and once again may not come to the XR routers. Is that a fair assumption of the current situation?
      I appreciate you coming up with a new operating system and it takes great effort to create one, but I am a little taken aback by the lack of patching in milestone 1.3 considering it’s almost a year old and virtually nothing has been done to fix the issues with it on the XR routers, as I can’t speak for the R1. I really wish you had focused on bug fixing Milestone 1.3 first before creating yet another new OS rather than leaving things unfixed and with an air of uncertainty as to whether they ever will be patched , because this all rides on Netgear. I think this could be a problem possibly especially since obviously you can’t promise how long this will take, and I have noted the words ‘early days’ which doesn’t bode well for further fixes in the pipeline for DumaOS as it stands on current Netgear hardware with your firmware. So we could be waiting possibly until next year with no fixes at all on the DumaOs side at all. Also a lot depends on Netgear wanting the new version as well, is that correct?  I’m not trying to be negative, I’m just trying to understand where Netgear users stand. 
     
      I hope you understand my concerns, router stability is created hopefully by fixing issues in current firmware no matter how welcome new features are. However the continued lack of support for patching  your own firmware on Netgear hardware I find to be a bit odd. Personally I would need fixes and stability not long  gaps where nothing is happening visibly for DumaOS software thats on existing XR routers, because you are busy creating another new version.Fixing the issues first before moving on seems the more logical approach but that’s just from my point of view.  Are you going to focus on patching rather than creating new versions of DumaOS, because all new operating systems inevitably are buggy. So Will you patch 3.0 or move onto the next version? I hope you can see my concerns. Good luck with version 3.0 nevertheless.
  21. Like
    Killhippie got a reaction from CrossFitKila717 in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    Thanks Alex, unfortunately that’s what I kind of feared. Basically bugs that came out in milestone 1.3 in what is rapidly going to become a year soon aren’t going to get patched in other words. Anything DumaOS related will be left until version 3.0. Also no one has a real clue how much Netgear will be interested in any of these new features. Also Current bugs with VLAN tagging, QoS getting slow, port mapping in table view and antibufferbloat  getting stuck on and and the leaky hybrid VPN won’t be fixed until this new version is ready and that probably won’t be this year and once again may not come to the XR routers. Is that a fair assumption of the current situation?
      I appreciate you coming up with a new operating system and it takes great effort to create one, but I am a little taken aback by the lack of patching in milestone 1.3 considering it’s almost a year old and virtually nothing has been done to fix the issues with it on the XR routers, as I can’t speak for the R1. I really wish you had focused on bug fixing Milestone 1.3 first before creating yet another new OS rather than leaving things unfixed and with an air of uncertainty as to whether they ever will be patched , because this all rides on Netgear. I think this could be a problem possibly especially since obviously you can’t promise how long this will take, and I have noted the words ‘early days’ which doesn’t bode well for further fixes in the pipeline for DumaOS as it stands on current Netgear hardware with your firmware. So we could be waiting possibly until next year with no fixes at all on the DumaOs side at all. Also a lot depends on Netgear wanting the new version as well, is that correct?  I’m not trying to be negative, I’m just trying to understand where Netgear users stand. 
     
      I hope you understand my concerns, router stability is created hopefully by fixing issues in current firmware no matter how welcome new features are. However the continued lack of support for patching  your own firmware on Netgear hardware I find to be a bit odd. Personally I would need fixes and stability not long  gaps where nothing is happening visibly for DumaOS software thats on existing XR routers, because you are busy creating another new version.Fixing the issues first before moving on seems the more logical approach but that’s just from my point of view.  Are you going to focus on patching rather than creating new versions of DumaOS, because all new operating systems inevitably are buggy. So Will you patch 3.0 or move onto the next version? I hope you can see my concerns. Good luck with version 3.0 nevertheless.
  22. Like
    Killhippie got a reaction from ArcaPulse in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    Will patching continues on Milestone 1.3 issues on DumaOS or is  any further development now for Netgears firmware side only? I assume you and Netgear have some agreement over patching issues and if DumaOS 3.0 will make it to current hardware (I know NDA's are all over the place these days) but some words of support to Netgear XR users would go down well as Milestone 1.3 issues are still ongoing. DumaOS 3.0 looks good though from the glimpse above. Really liking the Data history.
  23. Like
    Killhippie got a reaction from kamoj in XR500 Firmware version 2.3.2.56 released.   
    With a need for IPv6 and WPA3 being the new standard in town soon (unless that's not a priority for Netgear on older kit as it can be updated), also Wi-Fi 6 is replacing Wi-Fi 5 quite fast and I will be looking at hardware that keeps up with new clients and my networking needs. I love the GUI of DumaOS but not the failed promises and the never ending bugs that Netgear and Netduma don't get fixed, I'm guessing more Netgear than you guys, but still Ive seen to many promises  just fade away on these forums. Also this XR hardware is getting old. SoC's and Wi-Fi chipsets from 2016 are hardly cutting edge any more. Basically buying a R9000 or the gaming equivalent, the XR700 means people are buying 3 year old hardware, the XR500's CPU hits 4 years old in January 2020 as that's when the IPQ8065 landed on the shelves in home routers like Netgears R7800, which the XR500 basically is just in a new body shell and a bit more flash NAND that seems to not even be used.
  24. Like
    Killhippie got a reaction from Zippy in XR500 Firmware version 2.3.2.56 released.   
    With a need for IPv6 and WPA3 being the new standard in town soon (unless that's not a priority for Netgear on older kit as it can be updated), also Wi-Fi 6 is replacing Wi-Fi 5 quite fast and I will be looking at hardware that keeps up with new clients and my networking needs. I love the GUI of DumaOS but not the failed promises and the never ending bugs that Netgear and Netduma don't get fixed, I'm guessing more Netgear than you guys, but still Ive seen to many promises  just fade away on these forums. Also this XR hardware is getting old. SoC's and Wi-Fi chipsets from 2016 are hardly cutting edge any more. Basically buying a R9000 or the gaming equivalent, the XR700 means people are buying 3 year old hardware, the XR500's CPU hits 4 years old in January 2020 as that's when the IPQ8065 landed on the shelves in home routers like Netgears R7800, which the XR500 basically is just in a new body shell and a bit more flash NAND that seems to not even be used.
  25. Like
    Killhippie reacted to Zippy in XR500 Firmware version 2.3.2.56 released.   
    I totally agree. Merlins and Voxels firmware's are very good with good support. Sounds like you know what direction your going. And no worries we all are annoyed past what anyone should have to put up with. Lets just say we learned our lesson here.. Ha Ha I still got my ROG spider! When my friends first seen it they were like what the hell is that!! LOL..    Good luck with whatever router you go with my friend! 👍 If your not already on SNB forums join it. Theres a lot of good folks there and also Merlin and Voxel hangout there as well. killhippie is also on that site. Good info on both Netgear and ASUS routers not to mention everything in between..
    Zippy.
×
×
  • Create New...