Jump to content

lilstone87

Clubhouse Member
  • Content Count

    282
  • Joined


Reputation Activity

  1. Like
    lilstone87 got a reaction from Alex49H in ANNOUNCEMENT: DUMAOS 3.0 IS HERE   
    Hello Ruxomar,
    Trust me I understand some of your frustrations, in regards to netgear, and their past history of slow firmware updates. Which is still something they need to be better at. Also I understand concerns in regard's to security on their routers. As it seems every couple/few months, there's a security exploit found. However Netgear hasn't always been fast to patch the issue.
    As for the Asus routers, and the AX88U overall. Asus does have a history of pushing out updates every couple months. However with their more often updates, they also bring more bugs within their software, to customers. Which luckily Merlin does a hell of a job fixing some of their messes, and if he can't fix certain things, he tells them about the problems. To be honest.. over the last few month's, a lot of the firmwares they have been releasing, for a lot of their routers, have been pretty buggy, with customers rolling back to older builds.
    Finally there's one part of ASUS software I want to talk about, and for a lot of people who own the R1, or one of the XR routers. It's something they care about, and want to use, that's QoS. ASUS QoS from the outside looks very nice, and it sounds great for gamers, and people who want to use it. The bad part.. their QoS isn't set up well, and if you look at another forum. Where Merlin post his build's and such. You will see a thread about their QoS, and how it doesn't work all that good. There's a 200+ page thread about people wanting improvements on the current QoS, that Asus uses on their routers.
    Ultimately I'm mentioning this, as there isn't one router company, in terms of software, better than the other currently. I have owned many Netgear, and Asus routers, over the last ten years. So the things I'm saying, is from using their products on my home network, over the last several years. Both companies need to do things better, and when I say that.. I'm talking about them working with their customers more, and listening to their feedback, on certain things. Instead of their current yearly push for 3-4 new routers, with all these new shiny features, that either don't work at launch, or are buggy as shit for 6-12 months, after they release.
    Anyways to the mods, and other people reading this thread. I'm sorry for going a bit off topic with my post. However I felt this needed to be said, and I feel I was respectful in what I typed in this post. To end this post of mine,  I look forward to running the newer build, with some of these newer/improved features. I will for sure give feedback on any issues I run into, which hopefully is zero for me. However I know everyone's setups are different. So I'm sure even if it runs great for me, someone else will find a bug, or two. Still that's why it's great netgear/netduma guys are starting out slow, with a beta build first. As you never want to push an official build, without a good amount of testing, with a smaller scale of people.
  2. Like
    lilstone87 got a reaction from raf1212 in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    Well I see a lot of people are upset, with how long/delayed updates have taken for their XR routers. I owned the R1 from the very early days, and I bought the XR500 early on as well. To be honest, I haven't used either of them very much. They have collected a lot more dust, than uptime. Overall most will say I wasted my money, and I can understand them saying that, and I won't argue that.
    Also I have known a couple of the original ND guys since they started up as a company. They do WANT to make things better for US as GAMERS. At the same time, they were a startup company, and I'm sure they're still a pretty small company overall. Still they have made it this far, and I'm happy for them. I know some are likely angry with them partnering with Netgear. Which I can understand that as well. But for them as a company, it was their best decision, to help grow themselves as a company, going forward.
    As for these XR routers, it was a hard decision for me to buy the XR500. For me at the time, I had the money to buy it, so I did. However before buying the router, I knew "Netgear's" history, when it came to their routers. Which is, they're very slow with pushing firmware updates for their routers. I have owned close to 15 routers in the last 10-12 years, several netgear routers. As of right now, I won't buy another netgear router, due to how slow they're with updates. As they don't post beta build's, and such, unless you're a beta tester for a select router, and you only get updates for it.
    As of right now, with the main routers you can buy in many stores, and such. The brand I feel is best for routers at the moment is ASUS. As they actually push firmware updates pretty often, as of the last couple months, I feel some of their build's are buggy, for me at least, the wireless drivers they're using, causes me random short disconnects to my Galaxy S9+ phone. Still even with some of their bugs, with faster updates being pushed. There's a guy named RMerlin, who makes build's for a lot of their newer routers, fixes some of the smaller bugs, and add some other features as well. Plus he pushes newer build's pretty often as well.
    Finally I want to say, if Netgear truly wants to help gamers with routers, with gaming type features. They have to learn to work much faster with updates. Averaging 6+ months for every firmware update, at this point in time, is piss poor, and not good enough. My phone gets updates so much faster, and more often. There's zero reason, for a router company to not be faster, and more steady with firmware updates. As for the XR line of routers, I won't place blame on ND. As I'm sure they only work on/handle a certain part of the firmware for these routers. Even with that said, as people on these forums repeatedly have mentioned. With the current firmware for these routers, there are minor annoying type bugs, which should of been worked on, and fixed, in a timely manner. That's not happening, and NG should be ashamed of themselves for being so slow with updates. As I type this, if someone asked me about buying a Netgear branded router, I would tell them to stay away. This isn't a me HATING them as a company. It's just me calling things out like I see them, nothing I said in this post is a lie.
  3. Like
    lilstone87 got a reaction from patoche2520 in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    Well I see a lot of people are upset, with how long/delayed updates have taken for their XR routers. I owned the R1 from the very early days, and I bought the XR500 early on as well. To be honest, I haven't used either of them very much. They have collected a lot more dust, than uptime. Overall most will say I wasted my money, and I can understand them saying that, and I won't argue that.
    Also I have known a couple of the original ND guys since they started up as a company. They do WANT to make things better for US as GAMERS. At the same time, they were a startup company, and I'm sure they're still a pretty small company overall. Still they have made it this far, and I'm happy for them. I know some are likely angry with them partnering with Netgear. Which I can understand that as well. But for them as a company, it was their best decision, to help grow themselves as a company, going forward.
    As for these XR routers, it was a hard decision for me to buy the XR500. For me at the time, I had the money to buy it, so I did. However before buying the router, I knew "Netgear's" history, when it came to their routers. Which is, they're very slow with pushing firmware updates for their routers. I have owned close to 15 routers in the last 10-12 years, several netgear routers. As of right now, I won't buy another netgear router, due to how slow they're with updates. As they don't post beta build's, and such, unless you're a beta tester for a select router, and you only get updates for it.
    As of right now, with the main routers you can buy in many stores, and such. The brand I feel is best for routers at the moment is ASUS. As they actually push firmware updates pretty often, as of the last couple months, I feel some of their build's are buggy, for me at least, the wireless drivers they're using, causes me random short disconnects to my Galaxy S9+ phone. Still even with some of their bugs, with faster updates being pushed. There's a guy named RMerlin, who makes build's for a lot of their newer routers, fixes some of the smaller bugs, and add some other features as well. Plus he pushes newer build's pretty often as well.
    Finally I want to say, if Netgear truly wants to help gamers with routers, with gaming type features. They have to learn to work much faster with updates. Averaging 6+ months for every firmware update, at this point in time, is piss poor, and not good enough. My phone gets updates so much faster, and more often. There's zero reason, for a router company to not be faster, and more steady with firmware updates. As for the XR line of routers, I won't place blame on ND. As I'm sure they only work on/handle a certain part of the firmware for these routers. Even with that said, as people on these forums repeatedly have mentioned. With the current firmware for these routers, there are minor annoying type bugs, which should of been worked on, and fixed, in a timely manner. That's not happening, and NG should be ashamed of themselves for being so slow with updates. As I type this, if someone asked me about buying a Netgear branded router, I would tell them to stay away. This isn't a me HATING them as a company. It's just me calling things out like I see them, nothing I said in this post is a lie.
  4. Like
    lilstone87 got a reaction from Sunaikinti in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    Well I see a lot of people are upset, with how long/delayed updates have taken for their XR routers. I owned the R1 from the very early days, and I bought the XR500 early on as well. To be honest, I haven't used either of them very much. They have collected a lot more dust, than uptime. Overall most will say I wasted my money, and I can understand them saying that, and I won't argue that.
    Also I have known a couple of the original ND guys since they started up as a company. They do WANT to make things better for US as GAMERS. At the same time, they were a startup company, and I'm sure they're still a pretty small company overall. Still they have made it this far, and I'm happy for them. I know some are likely angry with them partnering with Netgear. Which I can understand that as well. But for them as a company, it was their best decision, to help grow themselves as a company, going forward.
    As for these XR routers, it was a hard decision for me to buy the XR500. For me at the time, I had the money to buy it, so I did. However before buying the router, I knew "Netgear's" history, when it came to their routers. Which is, they're very slow with pushing firmware updates for their routers. I have owned close to 15 routers in the last 10-12 years, several netgear routers. As of right now, I won't buy another netgear router, due to how slow they're with updates. As they don't post beta build's, and such, unless you're a beta tester for a select router, and you only get updates for it.
    As of right now, with the main routers you can buy in many stores, and such. The brand I feel is best for routers at the moment is ASUS. As they actually push firmware updates pretty often, as of the last couple months, I feel some of their build's are buggy, for me at least, the wireless drivers they're using, causes me random short disconnects to my Galaxy S9+ phone. Still even with some of their bugs, with faster updates being pushed. There's a guy named RMerlin, who makes build's for a lot of their newer routers, fixes some of the smaller bugs, and add some other features as well. Plus he pushes newer build's pretty often as well.
    Finally I want to say, if Netgear truly wants to help gamers with routers, with gaming type features. They have to learn to work much faster with updates. Averaging 6+ months for every firmware update, at this point in time, is piss poor, and not good enough. My phone gets updates so much faster, and more often. There's zero reason, for a router company to not be faster, and more steady with firmware updates. As for the XR line of routers, I won't place blame on ND. As I'm sure they only work on/handle a certain part of the firmware for these routers. Even with that said, as people on these forums repeatedly have mentioned. With the current firmware for these routers, there are minor annoying type bugs, which should of been worked on, and fixed, in a timely manner. That's not happening, and NG should be ashamed of themselves for being so slow with updates. As I type this, if someone asked me about buying a Netgear branded router, I would tell them to stay away. This isn't a me HATING them as a company. It's just me calling things out like I see them, nothing I said in this post is a lie.
  5. Like
    lilstone87 reacted to RamGuy in XR500 Firmware V2.3.2.32 released   
    I'm sorry but this is incorrect. The major benefit, at least for gaming with IPv6 is the fact that your ISP will provide you with a huge subnet of public IP-addresses so unless you configure IPv6 the wrong way all your clients should have their very own public IP-address avoiding the need for doing NAT.
    Luckily you are able to avoid most issues with gaming and NAT on the XR450 and XR500 due to the fact at Netgear allows for selecting Open NAT filtering which means applying Full Cone NAT on the NAT-rules instead of more modern symmetric or port restricted NAT. With Full Cone NAT and UPNP you will probably get away without doing any manual port forwarding and should hopefully never run into a situation where you have multiple clients in the need for having the very same port for inbound traffic as games supporting UPNP will allow for UPNP to handle the traffic and as Full Cone NAT won't restrict the flow of incoming connections you will be good to go.
    But this is far from common. Most home routers use port restricted NAT or symmetric NAT which means there is no free flow of incoming connections when the port is being handled by UPNP. So a lot of services will start having issues as they expect UPNP to behave like a port forward, meaning it allows for traffic from any external IP address to be able to access your gaming system / console using the inbound port but port restricted NAT and symmetric NAT will only allow for returning traffic from the external IP's that your client initiated traffic towards. Which is why Xbox One and Teredo/Xbox Networking in Windows 10 will give you Moderate NAT when you are behind a router running UPNP if its doing symmetric or port restricted NAT as your dynamically created NAT rules won't allow for all the incoming traffic as you will get getting traffic for other external addresses than just the ones your system/consoles is using for outbound connections and these will be dropped as that's a part of the stricter nature of port restricted and symmetric NAT.
     
    IPv6 would have a huge benefit here as you avoid NAT altogether as long as the gaming service is fully supporting IPv6 of course.
  6. Like
    lilstone87 got a reaction from Uzumaki619 in upgraded internet speeds an ping is super high now   
    Exactly the reason we need Ping Assist. Servers being mislocated is a far to common issue.
  7. Like
    lilstone87 got a reaction from Locosano in upgraded internet speeds an ping is super high now   
    Exactly the reason we need Ping Assist. Servers being mislocated is a far to common issue.
  8. Like
    lilstone87 got a reaction from Jlman3705 in Why is my Anti-Bufferbloat not working?   
    Well I have did more testing, and digging on this, the last couple days. I noticed a couple things, and I'm gonna share my findings below.
     
     
    1. Oddly at times I noticed my result's were not the best while using google chrome. I used firefox, and things seemed more steady. I have been able to get some good result's with chrome as well though. So I wouldn't say not use it. I tried using windows 10 built in IE browser, however I tried a couple test's, all failed when trying to do the upload side of the test. So I say stay away from IE for testing.
     
    2. When running this test, I strongly suggest cutting all bandwidth usage on the device you're testing on. So if you're on your pc, which you shouldn't be testing over a wifi device anyways. So testing while on a PC/Laptop. Close any apps/browser tabs that are using active bandwidth till testing is over. Also I highly recommend when testing on dslreports.com, try to only have it open within the browser you're using. I feel that will minimize any other tabs within the browser somehow causing the test an issue.
     
    3. Do yourselves a favor, and create an account on dslreports.com, will only take a short time to do so. Reason being, you can configure your "Preferences" settings for the speedtest, once saved, they will stay linked to your account. I feel configuring the preference settings is VERY important with this speedtest. I will explain more below.
     
    4. Reason to setup preference settings. First you can select the servers you want to use, for the test. At the top you have a option to let it pick some servers for you based off of either Latency, or Bandwidth. I suggest using the "Latency" option. After that's done running, it will have the servers it picked with a check on them. After that, you can look at the one's it picked, and unselect some of them if you want. I did a couple for myself, pick the ones closest to me. After this, make sure to hit the save button at the bottom.
     
    However I'm not done with the preference settings yet... After getting a small number of servers picked based off latency by it's own testing, and also checking over them yourself. I wouldn't have no more then 8-10 servers selected.
     
    Now scroll down a little, and you will see "No. download streams" with a box beside it. You can pick between 1-32. I honestly think for most of us "4" will be enough. That will be the amount of servers it will use while testing. Do the same for the upload side, which is right below it.
     
    For awhile I was using 16+ for each test I done, and I now don't recommend using that high of a number of servers for each test. Reason being, your overall result's will depend on all the servers used during that test. For me, I'm on the east coast of the US, and when I'm doing one of these test using 16+ servers. I'm likely using several servers on the west coast of the US. With a mixature of servers all over, there's so many things that can affect your routing from one minute to the next.
     
    So my final opinion on this, keep the number of servers used for the test low, and use servers close to you. Because this to me will give you more accurate result's, when it comes to the bufferbloat part of this test. Finally make sure after any preference setting changes, you make sure to click the "save" button at the bottom.
     
     
     
    5. After doing the stuff above, I have been seeing more steady result's with the dslreports.com speedtest, in terms of bufferbloat, and my overall results. I don't feel the current default settings used for their speedtest, is optimized very well for testing, and getting the most accurate results. Ultimately I think by default they're running the test using to many servers, which can be from far away. With that, comes a lot of possible routing issue's. Some of them you have no control over, and isn't an issue with your connection. However whatever each server is reporting back, ultimately is included at the end of the test, and will factor into your final result.
  9. Like
    lilstone87 got a reaction from Netduma Fraser in Looking for PUBG & Fortnite Players with XR500   
    I'm here, and no you can't take over my computer LUL kidding...
  10. Like
    lilstone87 got a reaction from Soloflyerz in Why is my Anti-Bufferbloat not working?   
    Well I have did more testing, and digging on this, the last couple days. I noticed a couple things, and I'm gonna share my findings below.
     
     
    1. Oddly at times I noticed my result's were not the best while using google chrome. I used firefox, and things seemed more steady. I have been able to get some good result's with chrome as well though. So I wouldn't say not use it. I tried using windows 10 built in IE browser, however I tried a couple test's, all failed when trying to do the upload side of the test. So I say stay away from IE for testing.
     
    2. When running this test, I strongly suggest cutting all bandwidth usage on the device you're testing on. So if you're on your pc, which you shouldn't be testing over a wifi device anyways. So testing while on a PC/Laptop. Close any apps/browser tabs that are using active bandwidth till testing is over. Also I highly recommend when testing on dslreports.com, try to only have it open within the browser you're using. I feel that will minimize any other tabs within the browser somehow causing the test an issue.
     
    3. Do yourselves a favor, and create an account on dslreports.com, will only take a short time to do so. Reason being, you can configure your "Preferences" settings for the speedtest, once saved, they will stay linked to your account. I feel configuring the preference settings is VERY important with this speedtest. I will explain more below.
     
    4. Reason to setup preference settings. First you can select the servers you want to use, for the test. At the top you have a option to let it pick some servers for you based off of either Latency, or Bandwidth. I suggest using the "Latency" option. After that's done running, it will have the servers it picked with a check on them. After that, you can look at the one's it picked, and unselect some of them if you want. I did a couple for myself, pick the ones closest to me. After this, make sure to hit the save button at the bottom.
     
    However I'm not done with the preference settings yet... After getting a small number of servers picked based off latency by it's own testing, and also checking over them yourself. I wouldn't have no more then 8-10 servers selected.
     
    Now scroll down a little, and you will see "No. download streams" with a box beside it. You can pick between 1-32. I honestly think for most of us "4" will be enough. That will be the amount of servers it will use while testing. Do the same for the upload side, which is right below it.
     
    For awhile I was using 16+ for each test I done, and I now don't recommend using that high of a number of servers for each test. Reason being, your overall result's will depend on all the servers used during that test. For me, I'm on the east coast of the US, and when I'm doing one of these test using 16+ servers. I'm likely using several servers on the west coast of the US. With a mixature of servers all over, there's so many things that can affect your routing from one minute to the next.
     
    So my final opinion on this, keep the number of servers used for the test low, and use servers close to you. Because this to me will give you more accurate result's, when it comes to the bufferbloat part of this test. Finally make sure after any preference setting changes, you make sure to click the "save" button at the bottom.
     
     
     
    5. After doing the stuff above, I have been seeing more steady result's with the dslreports.com speedtest, in terms of bufferbloat, and my overall results. I don't feel the current default settings used for their speedtest, is optimized very well for testing, and getting the most accurate results. Ultimately I think by default they're running the test using to many servers, which can be from far away. With that, comes a lot of possible routing issue's. Some of them you have no control over, and isn't an issue with your connection. However whatever each server is reporting back, ultimately is included at the end of the test, and will factor into your final result.
  11. Like
    lilstone87 got a reaction from Netduma Fraser in Why is my Anti-Bufferbloat not working?   
    Good to hear Alex. I spent a couple days messing around with things on my end, and finally on the test's end with settings. Plus i overlooked many test result's, before i decided to post these findings.
     
    I'm not one who will post about something, unless i feel 100% confident it's true. So like i said i took my time on this, and honestly probably burnt threw 10-15gb of data over a couple day period, just running this test repeatedly.
     
    Ultimately i'm happy you were able to take the info i provided, put it to use, and get the same kind of results i got. Which are what people want to see, if their connection is running optimally.
     
    Finally i hope others who are having trouble getting results they want with this test, see my earlier post, and are able to put my suggestions to good use. As i think the test can be good to use, it just isn't optimized to provide accurate results, when using its default settings.
  12. Like
    lilstone87 got a reaction from Netduma Admin in Why is my Anti-Bufferbloat not working?   
    Well I have did more testing, and digging on this, the last couple days. I noticed a couple things, and I'm gonna share my findings below.
     
     
    1. Oddly at times I noticed my result's were not the best while using google chrome. I used firefox, and things seemed more steady. I have been able to get some good result's with chrome as well though. So I wouldn't say not use it. I tried using windows 10 built in IE browser, however I tried a couple test's, all failed when trying to do the upload side of the test. So I say stay away from IE for testing.
     
    2. When running this test, I strongly suggest cutting all bandwidth usage on the device you're testing on. So if you're on your pc, which you shouldn't be testing over a wifi device anyways. So testing while on a PC/Laptop. Close any apps/browser tabs that are using active bandwidth till testing is over. Also I highly recommend when testing on dslreports.com, try to only have it open within the browser you're using. I feel that will minimize any other tabs within the browser somehow causing the test an issue.
     
    3. Do yourselves a favor, and create an account on dslreports.com, will only take a short time to do so. Reason being, you can configure your "Preferences" settings for the speedtest, once saved, they will stay linked to your account. I feel configuring the preference settings is VERY important with this speedtest. I will explain more below.
     
    4. Reason to setup preference settings. First you can select the servers you want to use, for the test. At the top you have a option to let it pick some servers for you based off of either Latency, or Bandwidth. I suggest using the "Latency" option. After that's done running, it will have the servers it picked with a check on them. After that, you can look at the one's it picked, and unselect some of them if you want. I did a couple for myself, pick the ones closest to me. After this, make sure to hit the save button at the bottom.
     
    However I'm not done with the preference settings yet... After getting a small number of servers picked based off latency by it's own testing, and also checking over them yourself. I wouldn't have no more then 8-10 servers selected.
     
    Now scroll down a little, and you will see "No. download streams" with a box beside it. You can pick between 1-32. I honestly think for most of us "4" will be enough. That will be the amount of servers it will use while testing. Do the same for the upload side, which is right below it.
     
    For awhile I was using 16+ for each test I done, and I now don't recommend using that high of a number of servers for each test. Reason being, your overall result's will depend on all the servers used during that test. For me, I'm on the east coast of the US, and when I'm doing one of these test using 16+ servers. I'm likely using several servers on the west coast of the US. With a mixature of servers all over, there's so many things that can affect your routing from one minute to the next.
     
    So my final opinion on this, keep the number of servers used for the test low, and use servers close to you. Because this to me will give you more accurate result's, when it comes to the bufferbloat part of this test. Finally make sure after any preference setting changes, you make sure to click the "save" button at the bottom.
     
     
     
    5. After doing the stuff above, I have been seeing more steady result's with the dslreports.com speedtest, in terms of bufferbloat, and my overall results. I don't feel the current default settings used for their speedtest, is optimized very well for testing, and getting the most accurate results. Ultimately I think by default they're running the test using to many servers, which can be from far away. With that, comes a lot of possible routing issue's. Some of them you have no control over, and isn't an issue with your connection. However whatever each server is reporting back, ultimately is included at the end of the test, and will factor into your final result.
  13. Like
    lilstone87 got a reaction from Alex49H in Why is my Anti-Bufferbloat not working?   
    Good to hear Alex. I spent a couple days messing around with things on my end, and finally on the test's end with settings. Plus i overlooked many test result's, before i decided to post these findings.
     
    I'm not one who will post about something, unless i feel 100% confident it's true. So like i said i took my time on this, and honestly probably burnt threw 10-15gb of data over a couple day period, just running this test repeatedly.
     
    Ultimately i'm happy you were able to take the info i provided, put it to use, and get the same kind of results i got. Which are what people want to see, if their connection is running optimally.
     
    Finally i hope others who are having trouble getting results they want with this test, see my earlier post, and are able to put my suggestions to good use. As i think the test can be good to use, it just isn't optimized to provide accurate results, when using its default settings.
  14. Like
    lilstone87 got a reaction from pollutionblues in Why is my Anti-Bufferbloat not working?   
    Here's a test I just did, to show I'm not just posting what I feel might be right. I forgot to attach it to my post from a few minutes ago.
     

     
    EDIT:
    Here's another test I just did from a minute ago, where I severely limited my speeds, I still got "A" for bufferbloat. Before best I seen was "B" for bufferbloat. Disregard the "F" for speed, as that's based off my average which would normally be 330/30. But I limited my speed for this test, and a little bit for the test above as well.
     

  15. Like
    lilstone87 got a reaction from pollutionblues in Why is my Anti-Bufferbloat not working?   
    Well I have did more testing, and digging on this, the last couple days. I noticed a couple things, and I'm gonna share my findings below.
     
     
    1. Oddly at times I noticed my result's were not the best while using google chrome. I used firefox, and things seemed more steady. I have been able to get some good result's with chrome as well though. So I wouldn't say not use it. I tried using windows 10 built in IE browser, however I tried a couple test's, all failed when trying to do the upload side of the test. So I say stay away from IE for testing.
     
    2. When running this test, I strongly suggest cutting all bandwidth usage on the device you're testing on. So if you're on your pc, which you shouldn't be testing over a wifi device anyways. So testing while on a PC/Laptop. Close any apps/browser tabs that are using active bandwidth till testing is over. Also I highly recommend when testing on dslreports.com, try to only have it open within the browser you're using. I feel that will minimize any other tabs within the browser somehow causing the test an issue.
     
    3. Do yourselves a favor, and create an account on dslreports.com, will only take a short time to do so. Reason being, you can configure your "Preferences" settings for the speedtest, once saved, they will stay linked to your account. I feel configuring the preference settings is VERY important with this speedtest. I will explain more below.
     
    4. Reason to setup preference settings. First you can select the servers you want to use, for the test. At the top you have a option to let it pick some servers for you based off of either Latency, or Bandwidth. I suggest using the "Latency" option. After that's done running, it will have the servers it picked with a check on them. After that, you can look at the one's it picked, and unselect some of them if you want. I did a couple for myself, pick the ones closest to me. After this, make sure to hit the save button at the bottom.
     
    However I'm not done with the preference settings yet... After getting a small number of servers picked based off latency by it's own testing, and also checking over them yourself. I wouldn't have no more then 8-10 servers selected.
     
    Now scroll down a little, and you will see "No. download streams" with a box beside it. You can pick between 1-32. I honestly think for most of us "4" will be enough. That will be the amount of servers it will use while testing. Do the same for the upload side, which is right below it.
     
    For awhile I was using 16+ for each test I done, and I now don't recommend using that high of a number of servers for each test. Reason being, your overall result's will depend on all the servers used during that test. For me, I'm on the east coast of the US, and when I'm doing one of these test using 16+ servers. I'm likely using several servers on the west coast of the US. With a mixature of servers all over, there's so many things that can affect your routing from one minute to the next.
     
    So my final opinion on this, keep the number of servers used for the test low, and use servers close to you. Because this to me will give you more accurate result's, when it comes to the bufferbloat part of this test. Finally make sure after any preference setting changes, you make sure to click the "save" button at the bottom.
     
     
     
    5. After doing the stuff above, I have been seeing more steady result's with the dslreports.com speedtest, in terms of bufferbloat, and my overall results. I don't feel the current default settings used for their speedtest, is optimized very well for testing, and getting the most accurate results. Ultimately I think by default they're running the test using to many servers, which can be from far away. With that, comes a lot of possible routing issue's. Some of them you have no control over, and isn't an issue with your connection. However whatever each server is reporting back, ultimately is included at the end of the test, and will factor into your final result.
  16. Like
    lilstone87 got a reaction from Netduma Fraser in Why is my Anti-Bufferbloat not working?   
    Well I have did more testing, and digging on this, the last couple days. I noticed a couple things, and I'm gonna share my findings below.
     
     
    1. Oddly at times I noticed my result's were not the best while using google chrome. I used firefox, and things seemed more steady. I have been able to get some good result's with chrome as well though. So I wouldn't say not use it. I tried using windows 10 built in IE browser, however I tried a couple test's, all failed when trying to do the upload side of the test. So I say stay away from IE for testing.
     
    2. When running this test, I strongly suggest cutting all bandwidth usage on the device you're testing on. So if you're on your pc, which you shouldn't be testing over a wifi device anyways. So testing while on a PC/Laptop. Close any apps/browser tabs that are using active bandwidth till testing is over. Also I highly recommend when testing on dslreports.com, try to only have it open within the browser you're using. I feel that will minimize any other tabs within the browser somehow causing the test an issue.
     
    3. Do yourselves a favor, and create an account on dslreports.com, will only take a short time to do so. Reason being, you can configure your "Preferences" settings for the speedtest, once saved, they will stay linked to your account. I feel configuring the preference settings is VERY important with this speedtest. I will explain more below.
     
    4. Reason to setup preference settings. First you can select the servers you want to use, for the test. At the top you have a option to let it pick some servers for you based off of either Latency, or Bandwidth. I suggest using the "Latency" option. After that's done running, it will have the servers it picked with a check on them. After that, you can look at the one's it picked, and unselect some of them if you want. I did a couple for myself, pick the ones closest to me. After this, make sure to hit the save button at the bottom.
     
    However I'm not done with the preference settings yet... After getting a small number of servers picked based off latency by it's own testing, and also checking over them yourself. I wouldn't have no more then 8-10 servers selected.
     
    Now scroll down a little, and you will see "No. download streams" with a box beside it. You can pick between 1-32. I honestly think for most of us "4" will be enough. That will be the amount of servers it will use while testing. Do the same for the upload side, which is right below it.
     
    For awhile I was using 16+ for each test I done, and I now don't recommend using that high of a number of servers for each test. Reason being, your overall result's will depend on all the servers used during that test. For me, I'm on the east coast of the US, and when I'm doing one of these test using 16+ servers. I'm likely using several servers on the west coast of the US. With a mixature of servers all over, there's so many things that can affect your routing from one minute to the next.
     
    So my final opinion on this, keep the number of servers used for the test low, and use servers close to you. Because this to me will give you more accurate result's, when it comes to the bufferbloat part of this test. Finally make sure after any preference setting changes, you make sure to click the "save" button at the bottom.
     
     
     
    5. After doing the stuff above, I have been seeing more steady result's with the dslreports.com speedtest, in terms of bufferbloat, and my overall results. I don't feel the current default settings used for their speedtest, is optimized very well for testing, and getting the most accurate results. Ultimately I think by default they're running the test using to many servers, which can be from far away. With that, comes a lot of possible routing issue's. Some of them you have no control over, and isn't an issue with your connection. However whatever each server is reporting back, ultimately is included at the end of the test, and will factor into your final result.
  17. Like
    lilstone87 got a reaction from Alex49H in Why is my Anti-Bufferbloat not working?   
    Here's a test I just did, to show I'm not just posting what I feel might be right. I forgot to attach it to my post from a few minutes ago.
     

     
    EDIT:
    Here's another test I just did from a minute ago, where I severely limited my speeds, I still got "A" for bufferbloat. Before best I seen was "B" for bufferbloat. Disregard the "F" for speed, as that's based off my average which would normally be 330/30. But I limited my speed for this test, and a little bit for the test above as well.
     

  18. Like
    lilstone87 got a reaction from Alex49H in Why is my Anti-Bufferbloat not working?   
    Well I have did more testing, and digging on this, the last couple days. I noticed a couple things, and I'm gonna share my findings below.
     
     
    1. Oddly at times I noticed my result's were not the best while using google chrome. I used firefox, and things seemed more steady. I have been able to get some good result's with chrome as well though. So I wouldn't say not use it. I tried using windows 10 built in IE browser, however I tried a couple test's, all failed when trying to do the upload side of the test. So I say stay away from IE for testing.
     
    2. When running this test, I strongly suggest cutting all bandwidth usage on the device you're testing on. So if you're on your pc, which you shouldn't be testing over a wifi device anyways. So testing while on a PC/Laptop. Close any apps/browser tabs that are using active bandwidth till testing is over. Also I highly recommend when testing on dslreports.com, try to only have it open within the browser you're using. I feel that will minimize any other tabs within the browser somehow causing the test an issue.
     
    3. Do yourselves a favor, and create an account on dslreports.com, will only take a short time to do so. Reason being, you can configure your "Preferences" settings for the speedtest, once saved, they will stay linked to your account. I feel configuring the preference settings is VERY important with this speedtest. I will explain more below.
     
    4. Reason to setup preference settings. First you can select the servers you want to use, for the test. At the top you have a option to let it pick some servers for you based off of either Latency, or Bandwidth. I suggest using the "Latency" option. After that's done running, it will have the servers it picked with a check on them. After that, you can look at the one's it picked, and unselect some of them if you want. I did a couple for myself, pick the ones closest to me. After this, make sure to hit the save button at the bottom.
     
    However I'm not done with the preference settings yet... After getting a small number of servers picked based off latency by it's own testing, and also checking over them yourself. I wouldn't have no more then 8-10 servers selected.
     
    Now scroll down a little, and you will see "No. download streams" with a box beside it. You can pick between 1-32. I honestly think for most of us "4" will be enough. That will be the amount of servers it will use while testing. Do the same for the upload side, which is right below it.
     
    For awhile I was using 16+ for each test I done, and I now don't recommend using that high of a number of servers for each test. Reason being, your overall result's will depend on all the servers used during that test. For me, I'm on the east coast of the US, and when I'm doing one of these test using 16+ servers. I'm likely using several servers on the west coast of the US. With a mixature of servers all over, there's so many things that can affect your routing from one minute to the next.
     
    So my final opinion on this, keep the number of servers used for the test low, and use servers close to you. Because this to me will give you more accurate result's, when it comes to the bufferbloat part of this test. Finally make sure after any preference setting changes, you make sure to click the "save" button at the bottom.
     
     
     
    5. After doing the stuff above, I have been seeing more steady result's with the dslreports.com speedtest, in terms of bufferbloat, and my overall results. I don't feel the current default settings used for their speedtest, is optimized very well for testing, and getting the most accurate results. Ultimately I think by default they're running the test using to many servers, which can be from far away. With that, comes a lot of possible routing issue's. Some of them you have no control over, and isn't an issue with your connection. However whatever each server is reporting back, ultimately is included at the end of the test, and will factor into your final result.
  19. Like
    lilstone87 got a reaction from Alex49H in Anti bufferbloat issue   
    Fraser, wasn't some people having issue with HTTP vs HTTPS being selected when testing? I thought we went over this in another thread a little while back...
  20. Like
    lilstone87 got a reaction from Netduma Fraser in XR500 High Priority traffic   
    Fraser,
     
    I noticed not to soon after my last post, someone at my home had left, and when they returned home. Their phone reconnected, while the device manager tagged it playstation. So on the QoS page the high priority light showed red, as if high priority traffic was active.
     
    With that said, i think whenever a device is being improperly tagged as a playstation(gaming device). It's causing the high priority traffic light to appear active, and red, while it's active device on the network.
     
    After i noticed this, i properly assigned the device as a phone. Pretty sure after i did this the high priority traffic light turned off. I'm away from home till later tonight, and i know it's late for you guys in the UK. Just thought this was worth mentioning, seems like this may be a bug.
  21. Like
    lilstone87 got a reaction from Netduma Fraser in BF1 servers   
    Fraser I sent you a DM.
  22. Like
    lilstone87 got a reaction from fuzzy clam in DumaOS Update - Recent Progress   
    Well the only people who used/tested the newest build is the netduma guy's, and a couple UK guys who are close to them. All of which has even been said by them publicly. With that said.... There hasn't been anyone who has beta tested for them yet. The one's who have used the newer build, are very likely using a build most people would label a "Alpha" build at this point.
     
    So i understand people starting to get impatient it's not out yet. But i do think some people feel like there's a decent amount of us privately testing the build, and that's 100% not true at all. Also it was mentioned in the past that the "early adopters" of the duma would get to test before official release. Well to this point that hasn't happened, and honestly with the amount of time that has passed. Even "us" the ones who have had duma's since the start, have no ideal if/when we might get to test the build.
     
    There's nothing 100% at this point... We all could be waiting till official launch. Even though i would consider that not smart on there part. As it's always smart to expand testing of this kind, as it helps if there's bugs in build still. As the more people you have using it, the more different settings you will see being used. Which makes the possibility of finding a hidden bug easier, if it exist. Ultimately smart to do before a mass launch of a major update. I do think they will do this, I just know nothing is set in stone at this point.
     
    So there's no reason for anyone to be feeling left out at this point.
  23. Like
    lilstone87 got a reaction from ColonicBoom in DumaOS Update - Recent Progress   
    Well the only people who used/tested the newest build is the netduma guy's, and a couple UK guys who are close to them. All of which has even been said by them publicly. With that said.... There hasn't been anyone who has beta tested for them yet. The one's who have used the newer build, are very likely using a build most people would label a "Alpha" build at this point.
     
    So i understand people starting to get impatient it's not out yet. But i do think some people feel like there's a decent amount of us privately testing the build, and that's 100% not true at all. Also it was mentioned in the past that the "early adopters" of the duma would get to test before official release. Well to this point that hasn't happened, and honestly with the amount of time that has passed. Even "us" the ones who have had duma's since the start, have no ideal if/when we might get to test the build.
     
    There's nothing 100% at this point... We all could be waiting till official launch. Even though i would consider that not smart on there part. As it's always smart to expand testing of this kind, as it helps if there's bugs in build still. As the more people you have using it, the more different settings you will see being used. Which makes the possibility of finding a hidden bug easier, if it exist. Ultimately smart to do before a mass launch of a major update. I do think they will do this, I just know nothing is set in stone at this point.
     
    So there's no reason for anyone to be feeling left out at this point.
  24. Like
    lilstone87 got a reaction from Netduma Fraser in DumaOS Update - Recent Progress   
    User manual? I'm the MANual!! Nice to see though for the ones who need the help. Never to much when it comes to help, and explaining how to use something, for the ones who are more used to plug, and play when they use something.
  25. Like
    lilstone87 got a reaction from Collet005 in MY THOUGHTS ON NETDUMA ROUTER AFTER 30 DAYS.   
    I want to add in a bit on what you're seeing, and what you're expecting the netduma to do. As for what you're expecting the netduma to do, with games like COD, it's honestly unrealistic to have every game be great for you. Likely most games will be "Okay/Average" at best.
     
    The reason for this, and it has nothing to do with the netduma, nor any networking equipment you could be using home side. COD has for the last several years used dedicated servers to host each match. However loading into each pregame lobby is still P2P, but when you search for a lobby you ping the dedicated servers. As this is the way they have the networking setup for these games. Sadly.. Just because you're pinging at 20-25ms to the server, doesn't mean the other 10+ people in your lobby are pinging at low latency as well. Then you add in the "Lag Comp" COD has used for the last several years in there multiplayer. The lower ping people in the lobby are actually at a disadvantage due to this.
     
    With all that said, there's nothing the netduma itself can do to control this, and so ultimately it's up to the developers doing the networking design for these games to improve, and fix. Because all the "Netduma" can do for you is force connect you to as low as possible "Host" for the game. But has no control on others connecting to that "Host" itself. The only way the netduma could control all this, is if the games were true P2P, and you were able to be "Host" of the lobby. Because then the netduma could block the higher ping players from connecting, and you would have full control.
     
    However most of these online FPS now a days don't work this way, and honestly the games the netduma can help with the most now. Are Sport's type games, that use true P2P to connect you, and a opponent to play each other. I'm talking about 1vs1 type sport's games. Because then the netduma is limiting which players can connect to you due to what there ping is.
     
    Trust me I wish there was a easy way to fix these type issue's, and improve online gaming for most of us playing FPS type games, where ping/latency matters most. But like I said above.. Ultimately that's still in control of the game developers, and the way they have the networking setup. Biggest thing networking design developers for these games could do, is to have ping/latency limit's set for each server, and if you're above these limits, you can't play on that server. There's negatives to doing this though.. However most people shouldn't have to suffer, for others less then ideal connection, and there troubles.
×
×
  • Create New...