-
Posts
349 -
Joined
-
Last visited
Everything posted by AsNCo
-
As mentioned in a previous post on this thread, my setup is, Modem to (Wired) R3 to (Wired) Switches to (Wired) Asus AX11000 AP to (Wireless) 2nd AP. Basically, multiple phones have the WhatsApp Voice Call issue as well. To solve it, just have to turn off Wi-Fi on the phone and turn it on again to ensure a stable internet connection. Ok. The next time I encounter this, I'll try disconnecting the Ethernet from the R3 to the Asus AX11000 AP and reconnecting it again to see if Internet is restored that way.
-
Hi. It seems that the new 4.0.236 early access update has made the random disconnects worst. I have to disconnect Wi-Fi on my phone and to my 5G data and immediately, Instagram and even Facebook comments will finally load as seen in the 3 screenshots that happened last week. Reconnecting back to Wi-Fi, the internet on the phone will still be working. And worst, just hours ago, I had a WhatsApp voice call. And it worked for 5 seconds before the voice was cutting out followed by seeing my phone say reconnecting. I disconnected the Wi-Fi again and the call reconnected immediately and loading back Wi-Fi again will still maintain the call. FACEBOOK PICTURES NOT LOADING FACEBOOK COMMENTS NOT LOADING INSTAGRAM BOOKMARKS NOT LOADING AND STUCK IN INFINITE LOADING
-
I have the same setup as you aside from the Modem. Modem to (Wired) R3 to (Wired) Switches to (Wired) Asus AX11000 AP to (Wireless) 2nd AP. The new update brought the things like Amazon Echo Alexa sometimes just listening but not responding. Random things like Facebook comments not loading on my Phone until I disconnect from WiFi and using 5G to verify and see that it will actually load and then connecting back to WiFi, it also seems to work. Those kinds of issues. But I've been quietly observing as the frequency of it happening is not as bad either the R2 or the R3 initial release firmware; Can't recall specifically. Nevertheless, thank you all for speaking out and doing the research. Your post specifically kind of confirmed that it's happening with people close to my setup as well. So wanted to chime in.
-
Am I already in the early access too?
-
As a result, I was suspended multiple times on OW2 Ranked. Will this issue be fixed? Under Geo-Filter Settings, I unticked Strict Mode. Once I click the back button on the top left, and go back into Geo-Filter Settings, Strict Mode is engaged again. What gives?
-
The only way for you right now is to go into Congestion Control and lower the values there. The percentage in CC slider is based on the value you input in CC. So 50% of 1000Mbps will be 500Mbps. And... 50% of 400Mbps is 200Mbps. This should help you reach your intended ping latency in game. So you should set your Ping Optimizer to Low Latency Only to benefit from the high speeds and when a MP game starts, you'll get whatever CC percentage slider value you put in CC.
-
I had the same experience as you until I rebooted the router. Every time I reboot, there will 2 things that I'll need to change again because the settings doesn't stick. They are, Disable Steady Ping and Disable Speedtest Bypass. Now I redid the bufferbloat test. As for CC, I set it to Auto which in the Speed Settings, were set to (for my own ISP) 1Gbps up and down. The difference in the bufferbloat test between 'Low Latency Only' and 'Auto' in CC Modes makes a big difference in the ping when download or upload is active. 'Auto' gives me very close speeds to 'Low Latency Only' while giving me very low ping. So what I would recommend is to set it to 'Auto' and then reboot the router, and then Disable Speedtest Bypass & Steady Ping (if you so wish). Then redo your Bufferbloat test. The results should be a lot better. It is for me at least.
-
Guys, if you have full gigabit speeds, try Advanced Speeds set to 1000 for both up and down. Then on Congestion Control Mode, set it to Auto. It will lower your speeds slightly, but the trade off is much more stable ping. Allowing me to achieve A+ from A when it was set to Low Latency Only. Depending on what you get with Low Latency Only, you might see an improvement to the ping values especially when you set it to Auto. Even though there's not much reason to having low latency when you're not gaming, it might be great for Home Automation devices to respond to your actions more promptly thanks to having lower ping. On a side note, 0ms ping for both up and down is now easily achievable at higher speeds than last time where I need to set it a lot lower in CC.
-
Appreciate you mentioning that, but Fraser has mentioned that it is no longer necessary to factory reset though. So if bugs were found, and if there are others who have reported the same issue, I'm reporting it as is unless told specifically to factory reset which I'd hate to go through with the tonnes of Home Automation devices and family devices that is connected to the router.
-
Looking forward to the update whenever it's ready. Many thanks 😄
-
East Coast USA, with Geo Filter, Connecting to London with false ping
AsNCo replied to mindlash's topic in Netduma R3 Support
Ah! You're right! Many thanks! Was using Chrome. I think after I restarted my router, issue seems to be fixed in regards to the Ping Assist always changing back to 0ms after you pull it to anything higher. -
East Coast USA, with Geo Filter, Connecting to London with false ping
AsNCo replied to mindlash's topic in Netduma R3 Support
Hi. I too am having the same issue where Geo-filter is constantly allowing connections outside of my circle. At the same time, I can't really adjust Ping Assist. It will keep on changing back to 0ms. I did the troubleshooting above as recommended. But no dice. -
Hi. Just to clarify, mine is on the same PC that I use for gaming. Thus, it is in Geo-filter. I use Whatsapp Web to access my Whatsapp to quickly select multiple pictures using a mouse. That is where the discovery of the increased lag came from. Hope it helps clear any confusion.
-
Yeah. It's very weird as to why the packets are being delayed. But in Smartboost Upload section, it was classified as Facebook as the traffic when I was actively selecting on the pictures and videos
-
Yes, this is surprisingly weird. I know. Let me explain. I have work where there are a lot of picture/video exchanges in the group. So it is a daily routine on weekdays for me to delete the media. I can either do it on a phone or on my PC which I usually will choose there since it is also good practice to improve mouse aim since you have to select every one of the pictures and videos individually and no way to select multiple pictures from one point to another with everything in the middle selected. But... I notice that now, Whatsapp is lagging behind my mouse clicks by a lot leading to a lot of picture selections being ignored. Then I'll have to go back and reselect some unselected pictures and videos. So I had this feeling that it wasn't like this before. So I went into the R3 UI and turned off Steady Ping. Lo and behold. Picture selections are now instant and thus leading to little to no pictures going unselected after clicking on them. Is Steady Ping meant to affect any and all packets routing through the router and not just gaming packets? It was such a weird and unexpected thing to occur. I was wondering why the picture selections were a lot slower to respond to my mouse clicks by about 3-6 pictures behind the picture where I am currently selecting next. It is such a bizarre thing to discover and affect. Is there any workarounds or must I constantly access the router and remember to turn Steady Ping On and Off every time I finish work or gaming?
-
Wow! This is great! Finally Ping Optimizer is working as it should! Low Latency = Ignores Smart QOS bandwidth numbers and CC percentages and go full tilt of your internet connection. (Test is when not gaming) So even though I set a 1000 down and 550 up, it went past that and set both to my ISP's max speeds as it should. So 900+ down and 900+ up (Only issue left is the extremely high latency when upload is set higher than 70%. Am still getting over 150ms when upload is busy bufferbloat test) Auto = Follow Smart QOS bandwidth numbers that you've entered but doesn't follow CC percentages. (Test is when not gaming) As what it should be. So 900+ down and 550 up (As I input 1000 down and 550 up in Smart QOS) Always On = Applies both Smart QOS bandwidth numbers and the CC percentages. (Test is when not gaming) And as it suggests, applies your percentage limit. In my case, am getting 690 down and 550 up (As I set a 69% limit for down and 100% limit for up to get literally 0ms increase for both up and down from my idle latency numbers of 5ms. And since in Smart QOS, I still set it to 550 up to avoid the 150+ms latency for up.) Seriously a brilliant idea to allow us to have 3 options to play with. So it's just a matter of me switching between Low Latency or Auto when not gaming to take advantage of the high speeds for file transfers and YouTube downloads and whatnot or enjoying the low latency that my Smart QOS bandwidth numbers provide at the same time. Seriously many thanks for the .23 firmware. Wish I'd have requested it sooner. Can't wait for the R3 Early Access forums to make this process easier. 👍
-
Can I get the latest firmware too? Am currently happy with the temporary solution that @titofuenla provided. Many thanks again @titofuenla Hope the team gets their well deserved rest. Happy holidays!
-
This is in line with what I experienced using the simple Bufferbloat tests. Higher jitter and higher lag spikes when connection was on idle. So here's an example. CC Enabled (Speedtest Bypass Off) with 100/100 for both the R2 and R3 + R3 w Steady Ping R2 25th %ile: 3.2 ms 75th %ile: 3.9 ms 95th %ile: 4.3 ms Jitter: 0.5 ms R3 25th %ile: 7.3 ms 75th %ile: 9.5 ms 95th %ile: 12.6 ms Jitter: 1.6 ms R3 with Steady Ping 25th %ile: 3.5 ms 75th %ile: 4.5 ms 95th %ile: 7.2 ms Jitter: 0.8 ms
-
ANNOUNCEMENT: Introducing the Netduma R3
AsNCo replied to Netduma Lew's topic in News & Announcements
Instant bootup isn't realistic? Then the R2, the Asus AX11000 is clearly in your imagination. Or is it because it doesn't suit your narrative? I was talking in a nice way, 'if it's possible, that would be nice'. How is that snobby? It was your first reply to me that set the tone. Goodness. You clearly love to insult others for their preference/priorities for no reason but can't accept when others have something to say about your childish tone and behaviour. Grow up. I'm too old to entertain a snobby little know-it-all who thinks he's better than everyone and therefore deserves to criticise others for their priorities. There are many people with differing focus in life. Just because it doesn't align with yours, doesn't mean you have the right to insult others for it. PS. Agree with you on that. Waiting for the companies to come out with their matter hubs for to support their old devices. -
ANNOUNCEMENT: Introducing the Netduma R3
AsNCo replied to Netduma Lew's topic in News & Announcements
Many thanks for your assistance. Mine is a 1Gbps plan for both up and down. Real speeds are around 900+/-Mbps. I've just input it as 1000 for both up and down for simplicity sake in the congestion control percentage scaling. eg. 75% means roughly 750Mbps is what I mean by simplicity. Connection to the small little raspberry pi-looking ISP modem is via DHCP. -
ANNOUNCEMENT: Introducing the Netduma R3
AsNCo replied to Netduma Lew's topic in News & Announcements
Perhaps you weren't aware of your snobbery shining through your posts. His has none of it. It was purely informative. Not to mention, he explains it well without resorting to belittling others who has different expectations than you. Wanting a sub 20ms ping = laughable? We've been having the mindset that Ping is King for years and then suddenly, there's the new idea that stability is what we should be aiming for at the expense of higher latency. Of course it takes time for others to grasp that. I'm not going to take such info at face value. I'm going to give it time to cook and see for myself. 8.8.8.8 and 1.1.1.1 are literally my primary and secondary DNSes too as what you'd also recommend. So yup. As for why I need the boot-up time to be faster, I have a lot of Home Automation devices. They will start acting crazy and not be responsive if there has been a long enough delay without any internet. Simply restarting the modem, router and APs is not going to cut it. It will still act crazy. I'll have to physically go all around the house and manually turn off all of the Home Automation devices and then restart the router and APs first before turning on the Home Automation devices. Thus why, I love how fast my modem and R2 starts up. Both are up and running in under 20s. And because Ethernet gets the internet 1st in those 20 seconds, the APs are already there to make sure the Home Automation devices did not experience any internet downtime in those few short seconds. The reason why I have to keep rebooting the R2 every week or so is because of the random internet disconnects (not WiFi) causing problems for not just my Home Automation but also me and my family's phones where the only way to make sure the internet on the apps will load is by turning the WiFi off and on again. Hope that explains why I am particular about the boot time and the annoyance especially when you have this many Home Automation devices which are as finicky as they are. Like how even Alexa will randomly still be in listening mode when you've finished speaking to her and she's stuck there with the circle processing for quite a long time and then turning off like as if no one spoke. And you'll have to repeat again and then she'll suddenly execute the command twice in the process. Notice that that is an issue with the R2. Similarly with the XR500. Suspect it to be a DHCP issue. And yes, I've even allocated manual IP addresses to them. But hope this addresses my concern on the extremely slow boot-up time. PS, I've also suddenly randomly lost internet and my access to the R3. Even though the R3 was still up and running. Not just my wired desktop, but my other devices lost internet too. Resulting in me having to reboot the router. So that's another reason why I would need to reboot the R3 once in a while too. In the meantime, when I'm not gaming, which is what I mostly do since I don't have ample time to game anymore, I aim to make full use of my internet speed that I paid for. So is it wrong for me to not want my full bandwidth and low latency that my ISP offers? Again, if I wanted to jump on the hate bandwagon, the answer is simple. Don't buy and support the product. It's that simple. I've dropped COD for years for that very reason. The lag compensation being one of factors turning me off to it. Overwatch on the other hand feels a lot more responsive at low ping. Playing on servers outside my country, 60ms or more, I can easily experience lag. Thus my desire to keep it low since the servers are literally a few km away. But again, the ability to take advantage of lag compensation can also be great. Thus, I see the benefits to having a router that has this feature that can be used in years to come even if I can't take full advantage of it now. As for the hate bandwagon again, if I really wanted to bash it, I wouldn't have bought the R1, XR500, R2 and now the R3. I've been happy with the R2 despite there being a few issues. But I didn't bring it up for months as I'm overall, really satisfied with it. I noticed a few problems with the R3, some, were slightly worst than the R2 and thus, I wanted to bring any and all issues that I noticed in the hopes that there can be improvements made or fixes for it. It's as simple as that. There's no hate here. Just wanting my favourite product to be better. But then again, you started not acknowledging my issues and saying that they don't matter. How would that feel to someone? If I'm wrong educate me. Don't belittle me in the process. -
Can I also clarify, other than Speedtest Bypass, does it mean my game downloads and all will be capped to the Congestion Control settings? Is there any way to turn it off like Auto-Enable on the R2? Because based on the Bufferbloat test, even with Low Latency-Only, it seems to limit my download and upload even when there's no game being played. Unlike on the R2 where the CC limit is only applied when there's a multiplayer game. Is this as intended or a bug too?
-
1) Hi. I don't think it is Speedtest Bypass's fault. Even with Always On, Speedtest Bypass disabled, it is still affecting the latency all the way down to 71% upload. Just to clarify, I ran multiple tests. 'Disabled test' means Speedtest Bypass is enabled along with Low Latency Only, along with Steady Ping turned off and just to be double sure, I even set both to 100% before I ran the test. And then, another test with Steady Ping turned on. And to be in Ping Optimizer 'enabled' mode, It is now set to Speedtest Bypass disabled and in Always ON, along with both a test with Steady Ping turned on and off and as per normal, the values are both set to 100%. In both cases, there is still that 150ms of latency. I am doing up multiple tests to report this issue. But here you go. Some of the test results. R2 CC Disabled test (CC disabled + 100% up 100% down + Goodput) - Unloaded 3 ms -- Download Active +13 ms -- Upload Active +6 ms R2 (CC enabled + 100% up 100% down + Goodput) - Unloaded 4 ms -- Download Active +27 ms -- Upload Active +6 ms R3 PO Disabled test (Speedtest Bypass enabled + Low Latency Only + Steady Ping off + 100% up 100% down) - Unloaded 6 ms -- Download Active +6 ms -- Upload Active +150 ms R3 PO Enabled test (Speedtest Bypass disabled + Always ON + Steady Ping off + 100% up 100% down) - Unloaded 9 ms -- Download Active +0 ms -- Upload Active +152 ms So again, to answer your theory, no. Speedtest Bypass doesn't seem to be the culprit. Hope it helps you guys find out where the real problem lies and help you guys get to the bottom of this. My Busy Upload latency is in the hundreds until 74%. R3 75% upload test (Speedtest Bypass disabled + Always ON + Steady Ping off + 74% up 100% down) - Unloaded 5 ms -- Download Active +3 ms -- Upload Active +124 ms And then, it gets lower to... R3 72% upload test (Speedtest Bypass disabled + Always ON + Steady Ping off + 72% up 100% down) - Unloaded 8 ms -- Download Active +0 ms -- Upload Active +29 ms R3 71% upload test (Speedtest Bypass disabled + Always ON + Steady Ping off + 71% up 100% down) - Unloaded 7 ms -- Download Active +2 ms -- Upload Active +14 ms R3 70% upload test (Speedtest Bypass disabled + Always ON + Steady Ping off + 70% up 100% down) - Unloaded 8 ms -- Download Active +1 ms -- Upload Active +2 ms As you can see, the latency got exceptionally low at 70%. So there's something clearly wrong somewhere in the OS that needs a fix. 2) Can I also clarify, other than Speedtest Bypass, does it mean my game downloads and all will be capped to the Congestion Control settings? Is there any way to turn it off like Auto-Enable on the R2? Because based on the Bufferbloat test, even with Low Latency-Only, it seems to limit my download and upload. Is this as intended or a bug too? Hope to get issue fix. Happy holidays!
-
ANNOUNCEMENT: Introducing the Netduma R3
AsNCo replied to Netduma Lew's topic in News & Announcements
What I'm saying is we learnt that in school. Thus, the reminder about it was most helpful. Ever heard of forgetting what we've learnt? Yup. That's what I am saying. Anyway, are you here to help or just trying to fight everyone's genuine concerns and issues just because the product has met up to your standards but not that of others? Perhaps you should just let the devs help answer the questions or whether the devs need to know if there are really bugs that need to be taken care of as seen by how titofuenla too can replicate my results on this error in the buffer of the R3 as it was a Bufferbloat test to begin with. It will really help keep this thread from unnecessary clutter and especially side-tracking to prove one's job or status or whatever which is unneeded and a complete waste of time with the genuine concern going unanswered. Much appreciated on your cooperation on this matter. Thank you. -
ANNOUNCEMENT: Introducing the Netduma R3
AsNCo replied to Netduma Lew's topic in News & Announcements
Yup. The first one is just a preference thing. It matters to me. If my modem and R2 and Asus AX11000 can boot up so fast, I don't see why this is still acceptable in 2023. But again, just a preference. You'll be surprised. I was in the Practice Range in OW2 where the connection for both Steady Ping and without were both at around 40ms. So the experience should be the same right? Nope. You can literally see the game's hit response latency when steady ping is turned on vs the instant hit response that you get with Steady Ping off. That is that slight ms delay that was noticeable. You owned the R1 R2 and R3 just like me. You should know their 'Motto' in the past. 'Ping is King.' Nothing wrong with that thought. In the R2 and R3, the servers being ping-ed in Geo-filter shows 4ms. While in-game, it will say 13-14ms for the R2 and 13-15ms for the R3. And no. When I ran the tests, I ran BOTH with Steady Ping ON and Steady Ping OFF to see if it makes a difference. Similarly, when I choose to run the test with Speed Test Bypass turned OFF, it still shows that 100+ms of latency for the upload. If you've used the R1 all the way to R3, you know certain random features may affect others such as enabling ipv6 affecting speeds last time. It is better for me to be detailed and try every combo than just testing on the surface. You should have known better. Yeah. This was something I learnt when I was doing my Diploma as well. But thanks for the reminder. Appreciate it. Honestly, Bufferbloat does a great job summarizing the jitter, and the latency and all in a nice and concise manner. It was my go-to for not just me, but people aiming to have a stable connection via pFsense route. Hi. I don't think it is Speedtest Bypass's fault. Even with Always On, Speedtest Bypass disabled, it is still affecting the latency all the way down to 71% upload. Just to clarify, I ran multiple tests. 'Disabled test' means Speedtest Bypass is enabled along with Low Latency Only, along with Steady Ping turned off and just to be double sure, I even set both to 100% before I ran the test. And then, another test with Steady Ping turned on. And to be in Ping Optimizer 'enabled' mode, It is now set to Speedtest Bypass disabled and in Always ON, along with both a test with Steady Ping turned on and off and as per normal, the values are both set to 100%. In both cases, there is still that 150ms of latency. I am doing up multiple tests to report this issue. But here you go. Some of the test results. R2 CC Disabled test (CC disabled + 100% up 100% down + Goodput) - Unloaded 3 ms -- Download Active +13 ms -- Upload Active +6 ms R2 (CC enabled + 100% up 100% down + Goodput) - Unloaded 4 ms -- Download Active +27 ms -- Upload Active +6 ms R3 PO Disabled test (Speedtest Bypass enabled + Low Latency Only + Steady Ping off + 100% up 100% down) - Unloaded 6 ms -- Download Active +6 ms -- Upload Active +150 ms R3 PO Enabled test (Speedtest Bypass disabled + Always ON + Steady Ping off + 100% up 100% down) - Unloaded 9 ms -- Download Active +0 ms -- Upload Active +152 ms So again, to answer your theory, no. Speedtest Bypass doesn't seem to be the culprit. Hope it helps you guys find out where the real problem lies and help you guys get to the bottom of this. My Busy Upload latency is in the hundreds until 74%. R3 75% upload test (Speedtest Bypass disabled + Always ON + Steady Ping off + 74% up 100% down) - Unloaded 5 ms -- Download Active +3 ms -- Upload Active +124 ms And then, it gets lower to... R3 72% upload test (Speedtest Bypass disabled + Always ON + Steady Ping off + 72% up 100% down) - Unloaded 8 ms -- Download Active +0 ms -- Upload Active +29 ms R3 71% upload test (Speedtest Bypass disabled + Always ON + Steady Ping off + 71% up 100% down) - Unloaded 7 ms -- Download Active +2 ms -- Upload Active +14 ms R3 70% upload test (Speedtest Bypass disabled + Always ON + Steady Ping off + 70% up 100% down) - Unloaded 8 ms -- Download Active +1 ms -- Upload Active +2 ms As you can see, the latency got exceptionally low at 70%. So there's something clearly wrong somewhere in the OS.