Jump to content

lilstone87

Clubhouse Member
  • Content Count

    279
  • Joined


Reputation Activity

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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...
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
     

  11. 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.
  12. 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.
  13. 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.
     

  14. 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.
  15. 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...
  16. 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.
  17. Like
    lilstone87 got a reaction from Netduma Fraser in BF1 servers   
    Fraser I sent you a DM.
  18. 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.
  19. 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.
  20. 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.
  21. 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.
  22. Like
    lilstone87 got a reaction from Macca61 in Why did you purchase the Netduma router?   
    Well here's one thing I think a lot of people who bought this router expected. As a lot of them are FPS players, mainly COD in general. They expected to go from "Okay" lobbies, to "Great" connection lobbies. The reality is though, the Netduma will only help you in connecting to lobbies(dedicated servers) in which have as low as possible ping/latency each time. However the Netduma has ZERO control on the other player's that are connected to the same server. Plus with a game like COD, they also use "Lag Comp" still. So honestly a large part of the time, the lowest ping/latency players are at a bit of a disadvantage in most lobbies.
     
    There isn't a one all, fix all to these type issues. But there's ways to improve things, most of it has to be done networking side, by the game developers. As only they can make it where there are limit's, in which they can set ping/latency limits that can keep certain players from being able to play on certain servers, and such. But there's a negative to this, but just because certain players have horrible connections, others shouldn't suffer because of them.
     
    A router like the netduma with some of the features it offers, and hopefully is improved upon in the very near future with DumaOS. Are still key to have/use for people who game at home often, and want to enjoy playing online. Having things like a Geo-Filter, and a QoS system in which can control both download, and upload bandwidth, on a per device bases is key. I will honestly say having solid QoS system, properly configured is VERY key imho.
     
    Not all QoS system's work as they should. Reason I say this, is just because you have say 100/10 internet connection. You don't want to be near maxing either download/upload limit. It's honestly key, when using a QoS system to have your limit's at like 75%, maybe even a bit lower, then what you pay for by your internet provider. Because when you near your bandwidth limit's, you greatly increase your overall ping/latency(jitter) while that bandwidth is in use.
     
    Now back to not all QoS systems working as they should, well some QoS systems will let you set your download/upload limits. However let the lowest priority devices still use damn near the max bandwidth you have set as your limit. Which when a higher priority device request bandwidth, is supposed to be granted the bandwidth it needs, and lower priority device suffers. But this isn't always the case, and not all QoS systems work like intended. So it's important to keep your overall limit's a good bit lower then what you pay for by your provider. Because jitter becomes a real problem, when you start pushing 70-75% usage on your overall total bandwidth. One other thing, regarding some QoS systems I have seen in the past/used even. They don't handle well when wireless devices are in use, as they don't rate limit control like they should, and even priorities at times are not respected as they should.
     
    So it's important to maintain your home network as much as possible with a solid working QoS in place. One other thing that's something outside most of our control, and I'm sure the reason some of you have purchased this router, expecting it to help/fix problems for you. That's internet issue's between the place you live, the internet modem you're using, the home's wiring, and wiring issue's in the area you live in. Which the last part would be on the ISP to fix, but is your responsibility to report to the ISP of problems with your internet. This type of stuff, there's no router out there that can help fix. You have to stay on your ISP about these type issues until they resolve them, before your quality of service ever improves.
     
    Finally with everything I typed above, I think to many people buy a router like the Netduma. Then expect instantly they're gonna turn into the terminator, and no one should be able to kill them online, be able to get killstreak, after killstreak, and be unstoppable. Fact of the matter is.. None of us are that great, quit letting your ego play tricks on you, it's not healthy my friend. if you think you are, you're living in fantasy land. Try enjoying games a bit more, and not expect to drop 25 killstreaks every game. You will end up nothing more then disappointed, likely grumpy, and a person not many people want to play with, due to you being angry all the time.
  23. Like
    lilstone87 got a reaction from Macca61 in Why did you purchase the Netduma router?   
    I see, and know of a lot of people who have bought this router, and aren't happy with the result's they're seeing. So I wanted to post this thread, and see what exactly people expected this router to do, and why they're not happy currently. Because I honestly feel like a lot of customers of the "Netduma" router are a bit mislead in what they think this router will do, and expect from it.
     
    So this will be a discussion type thread, and I'm sure there will be disagreement's. However I want everyone to be open minded as possible, and not take another person's opinion, PERSONAL. So I don't want this thread to turn into personal shots taken at one another, so be respectful to one another, and understand we will not always agree with one another, but there's no need to attack each other. We all have ONE common goal here, and that's improved online gaming. With all this said, if this thread does turn into personal attack's on one another, I will have it closed, and removed by a moderator.
     
    Let the discussion begin....
  24. Like
    lilstone87 got a reaction from ColonicBoom in DumaOS Announcement: Development Progress & Testing   
    The comment I highlighted in bold, is one of the exact reasons, if I was running the show you wouldn't be a early tester of any kind. You have all right to your own opinion, and such. But there's a time, and place, to keep certain things to yourself, and not look like an ass about it. 
     
    I have owned the netduma since damn near the time they started selling it. We all have stuff we're not happy about, but being rude about it, on a public forum isn't proper either. You claim to be a "Dev" yourself, so you should know better then to be like this, because with the way social media is now a days. Just look at the COD community, with the way they openly abuse/threaten dev's over the game not playing exactly the way they want it to. If you want to test things, and help out. You should know acting this way isn't the way to go about it, and I put money on it. If you're a "developer" as you say you are, if I was to make comment's like above, I bet you wouldn't want to give me access to test a new build, you had done with such comments.
     
    Anyways I'm not trying to drive this thread off-topic, so I apologize for doing so with what I had to say. But just like many of you waiting for this newer build, so am I. I enjoy playing video games as much as anyone here. To be honest, and frank, my netduma has been in its box for many of month's now. So I haven't used mine in a while either, and want to test the new firmware ASAP. Yet again.. I'm not gonna be all public about things I don't like, if it bothers you that much. Maybe you should talk about it with the netduma guys privately, and be sensible about it.
  25. Like
    lilstone87 got a reaction from Alex49H in DumaOS Announcement: Development Progress & Testing   
    I have just been using my main Netgear R9000 for a while now. does nothing to help with P2P type games, but with the way most games are setup for multiplayer, unless it's "True" P2P for multiplayer, even the netduma is limited in what it can do. As it can only control the dedicated server you connect to on games like COD. With that, you can still be playing Jim, and his cousin from 1,000 miles away. Ultimately it's up to the dev's doing the networking part of the game to keep people from connecting to dedicate servers that are 500+ miles away from them. Because you add there distance to the server, then the lag comp they use with COD, the person who's closer to the server is at a disadvantage due to it.
     
    I haven't personally played much COD this year, I have played more Titanfall 2 on PS4. Really a lot like the newer COD's in sense of movement, and such. But to me the game feels even smoother, and hit detection is better for me compared to COD. Playing Titanfall 2, then going back to play COD:IW. Titanfall made IW feel sluggish, and even downright slow at times, with poor hit detection. I have played COD online since COD4, and I will honestly say Titanfall 2 is a better shooter then IW is by far this year.
×
×
  • Create New...