So where’s the update then?

[bcoe30]

37 minutes ago, cljackhammer said:

@Netduma Fraseris there an option for an extended return policy? I would like to wait , but honestly several core features don’t work with the router. I’m tired of tinkering and would rather game on a stable platform.

Nope 👎 your stuck with it 

[TG3NOC1D3]

18 hours ago, BadBill_UK said:

So if your lucky enough to have your r3 stable then screw everyone else that’s having disconnect issues or whatever and say I am happy to wait ! That’s so selfish! And to start implying users don’t understand how routers work again how demeaning to others ! I personally am a certified network engineer with 20+ years experience. I understand what the hold up. God some people ! 

That's great, you're in the minority of people who understand how to bridge the ISP equipment and have it run as a plain modem and build out complex networks. However, yes, I am implying just by the numerous posts of people not getting their equipment connected, the common denominator is "I hooked it to my ISP device and it isn't working!" So yes, the logical output there is that they do not know how their ISP equipment works. They can call their ISP or use reddit or any other online forum to see if anyone has successfully bypassed the routing features in the device. If you take offense so easily to logical thought process, maybe you shouldn't be in networking.

 

I've seen maybe a handful of posts about disconnects or breaking issues. When they aren't widespread, just like in an enterprise environment, it is typically a isolated issue, as you should know. If every single person was having the issue, then yes, we could blame Netduma. I guarantee majority on here have never looked to see if their coax signal levels are out of spec or their light levels on their fiber and that could cause issues. Maybe the DHCP lease is renewing rapidly from the ISP device if they are using DMZ from the ISP and it is causing a disconnect. Lots of troubleshooting, hence why I said, if you're going to tinker with adding devices to your network, you should really understand the network environment in which you are tinkering. I won't apologize for being logical, nothing I have said is rude or condescending at all, just stating my observations. 

 

My point or tldr: I am not saying screw everyone else, I am saying people should work with their ISP as well as the team here, which I have seen numerous "I expect it to just work" or they post a scathing review of the unit and when offered help, NOPE! So no, I will not feel bad for lack of effort. Good day sir.

[Freebandzz]

So just got the r3 in yest took it out of the box was wondering if I need to do any update on it firmware on there now is v4.020 I see the newest version is 4.23 or something like that but I can see no where to update the firmware on the r3 even hit the top right 3 dots like I did on the r2 

[DARKNESS]

@FreebandzzGo to Settings>Troubleshooting>Upload Firmware

 

[BadBill_UK]

24 minutes ago, TG3NOC1D3 said:

That's great, you're in the minority of people who understand how to bridge the ISP equipment and have it run as a plain modem and build out complex networks. However, yes, I am implying just by the numerous posts of people not getting their equipment connected, the common denominator is "I hooked it to my ISP device and it isn't working!" So yes, the logical output there is that they do not know how their ISP equipment works. They can call their ISP or use reddit or any other online forum to see if anyone has successfully bypassed the routing features in the device. If you take offense so easily to logical thought process, maybe you shouldn't be in networking.

 

I've seen maybe a handful of posts about disconnects or breaking issues. When they aren't widespread, just like in an enterprise environment, it is typically a isolated issue, as you should know. If every single person was having the issue, then yes, we could blame Netduma. I guarantee majority on here have never looked to see if their coax signal levels are out of spec or their light levels on their fiber and that could cause issues. Maybe the DHCP lease is renewing rapidly from the ISP device if they are using DMZ from the ISP and it is causing a disconnect. Lots of troubleshooting, hence why I said, if you're going to tinker with adding devices to your network, you should really understand the network environment in which you are tinkering. I won't apologize for being logical, nothing I have said is rude or condescending at all, just stating my observations. 

 

My point or tldr: I am not saying screw everyone else, I am saying people should work with their ISP as well as the team here, which I have seen numerous "I expect it to just work" or they post a scathing review of the unit and when offered help, NOPE! So no, I will not feel bad for lack of effort. Good day sir.

OMG! Your logic is lacking logic! why are you even mentioning enterprise environments for a primarily gaming home router! its completely out of context.  You do know if there is bugs in the R3 firmware then certain connection configurations that somehow got missed during testing could occur. I am having ethernet disconnects on the LAN side but what if the bug affects the WAN side as well for others?  if yours is stable why even comment! to put others down and call them stupid! I am not upset just hate arrogant people who assume because they have no issues  everyone else must be at fault. Just because a problem isn't widespread or affects you doesn't mean it doesn't exist. All I can say congrats that yours is stable and connected. Good day sir

[TG3NOC1D3]

25 minutes ago, BadBill_UK said:

OMG! Your logic is lacking logic! why are you even mentioning enterprise environments for a primarily gaming home router! its completely out of context.  You do know if there is bugs in the R3 firmware then certain connection configurations that somehow got missed during testing could occur. I am having ethernet disconnects on the LAN side but what if the bug affects the WAN side as well for others?  if yours is stable why even comment! to put others down and call them stupid! I am not upset just hate arrogant people who assume because they have no issues  everyone else must be at fault. Just because a problem isn't widespread or affects you doesn't mean it doesn't exist. All I can say congrats that yours is stable and connected. Good day sir

I never called anyone stupid but thank you for putting words in my mouth. I highly question if you have been in the industry because the only logic lacking is your own. Have you worked with the team to troubleshoot ethernet disconnects? Tried new cables? Used a cable tester to verify? I have seen numerous people complain but not be willing to work with the team on said issues. This is where I take issue with them berating the team that is working diligently to produce a solid product. That is serious ignorance on their part and makes the complaint invalid in my opinion. 

 

You say you are not upset but you're coming at me very aggressively which I do not understand. I brought up enterprise because with your claim of 20+ years of experience and being a certified network engineer, I would think that you would know better to blame the networking device when it is a very small group of people experiencing certain issues. If every person upgraded to .23 and it broke their device and we all had the same issues, I could see it being the code or scripting in the device. If we all had physical disconnect issues, I could see us all having lemons, that is not to say your issue is invalid before you put words in my mouth. You may very much have a physical issue and need a RMA, but you should bring this issue to the team and troubleshoot or bring valid proof of a physical port issue. Wireshark during a session to capture the disconnect would help this issue. 

I am not here to fight with anyone, I am here to help people understand they need to troubleshoot to verify the issue with the team is actually on the device so they can DOCUMENT the issues. I am sorry if my pro-troubleshoot outlook is bothersome to you, but that is how I am. I do not look highly on those who refuse to help themselves. 

[DARKNESS]

@BadBill_UK@TG3NOC1D3Ok let it go fellas we get it there bugs that affect the network and your mad about it at this point your just fighting each other 😂

 

[TG3NOC1D3]

Just now, DARKNESS said:

@BadBill_UK@TG3NOC1D3Ok let it go fellas we get it there bugs that affect the network and your mad about it at this point your just fighting each other 😂

 

I'm not mad at all lol. I am sitting in meetings at work and just fleshing out my thought process and why I feel the way I do. If people take my mindset negatively, they purely choose to do so on their own. I can't control that, so it is what it is to me. I'm done trying to help other make sense of it and help them help themselves. I'll continue enjoying my router working 🤷‍♂️

[DARKNESS]

@TG3NOC1D3Everyone has the right to have there opinion nothing's wrong with it 😂

 

[VeeDot]

Low Ping King just uploaded his video on youtube showing himself with the 4.0.40 firmware update.

 

i wonder if its close for release for everyone else, at this point everyone whos purchased an R3 is a beta tester

[BadBill_UK]

2 hours ago, TG3NOC1D3 said:

I never called anyone stupid but thank you for putting words in my mouth. I highly question if you have been in the industry because the only logic lacking is your own. Have you worked with the team to troubleshoot ethernet disconnects? Tried new cables? Used a cable tester to verify? I have seen numerous people complain but not be willing to work with the team on said issues. This is where I take issue with them berating the team that is working diligently to produce a solid product. That is serious ignorance on their part and makes the complaint invalid in my opinion. 

 

You say you are not upset but you're coming at me very aggressively which I do not understand. I brought up enterprise because with your claim of 20+ years of experience and being a certified network engineer, I would think that you would know better to blame the networking device when it is a very small group of people experiencing certain issues. If every person upgraded to .23 and it broke their device and we all had the same issues, I could see it being the code or scripting in the device. If we all had physical disconnect issues, I could see us all having lemons, that is not to say your issue is invalid before you put words in my mouth. You may very much have a physical issue and need a RMA, but you should bring this issue to the team and troubleshoot or bring valid proof of a physical port issue. Wireshark during a session to capture the disconnect would help this issue. 

I am not here to fight with anyone, I am here to help people understand they need to troubleshoot to verify the issue with the team is actually on the device so they can DOCUMENT the issues. I am sorry if my pro-troubleshoot outlook is bothersome to you, but that is how I am. I do not look highly on those who refuse to help themselves. 

I can see where your coming from and I myself went through trouble shooting with the team they were trying to blame my switch. I thought no wouldn’t be that but disconnected it anyway and turned out it wasn’t. Yes I agree about users not doing basic steps with the team even if they think it’s not the problem. But there is 100% a bug with the Ethernet side of this router! Could be the cpu overheating and shutting off the Ethernet controller who knows. Others have had WiFi issues but I am using WiFi for my PS5 to stop disconnects and it’s working ok. I still have to reboot the router every other day because it drops rest of my devices on Ethernet. Your logic is off though sir. Just because a small number of people have problems doesn’t mean the firmware is ok! Like I said everyone has different configurations which you should know if you’re an expert that can have different outcomes. So to blame the router is spot on! If people have their  network all running fine and only component that changed was router umm hmmm I wonder what the problem is ??? I can’t figure it out better rip all the Ethernet cables out and switches and buy new then blame the ISP it def won’t be the router ! Even if everyone is on .23 they will all have different problems depending on setup. I know some ISPs lock the MAC address of router to the ONT and they block them until you call them to reset it. I worked on an RAF base that had managed Ethernet ports by MAC address. Point is just because one R3 works on one setup it may not on another. Also the number of devices connected and types of devices can effect the outcome. I have 21 devices connected via WiFi and Ethernet. You may have a couple and be fine. 

[TG3NOC1D3]

5 minutes ago, BadBill_UK said:

I can see where your coming from and I myself went through trouble shooting with the team they were trying to blame my switch. I thought no wouldn’t be that but disconnected it anyway and turned out it wasn’t. Yes I agree about users not doing basic steps with the team even if they think it’s not the problem. But there is 100% a bug with the Ethernet side of this router! Could be the cpu overheating and shutting off the Ethernet controller who knows. Others have had WiFi issues but I am using WiFi for my PS5 to stop disconnects and it’s working ok. I still have to reboot the router every other day because it drops rest of my devices on Ethernet. Your logic is off though sir. Just because a small number of people have problems doesn’t mean the firmware is ok! Like I said everyone has different configurations which you should know if you’re an expert that can have different outcomes. So to blame the router is spot on! If people have their  network all running fine and only component that changed was router umm hmmm I wonder what the problem is ??? I can’t figure it out better rip all the Ethernet cables out and switches and buy new then blame the ISP it def won’t be the router ! Even if everyone is on .23 they will all have different problems depending on setup. I know some ISPs lock the MAC address of router to the ONT and they block them until you call them to reset it. I worked on an RAF base that had managed Ethernet ports by MAC address. Point is just because one R3 works on one setup it may not on another. Also the number of devices connected and types of devices can effect the outcome. I have 21 devices connected via WiFi and Ethernet. You may have a couple and be fine. 

We are gaining common ground here, my whole thought process has been around the ones who have not troubleshooted with the team. Those that have, I agree there are issues. The proven issues from those who tried to troubleshoot are very valid and real, I never denied this. However I have see way too many posts, some which are gone now (wonder why...) that complained out the arse about said issues but just wanted a refund and to send the router back. Those are the type I take issue with, not those that have done their part.

I do agree residential comes with it's own cases but my personal experience from viewing the issues on here are "ISP setup works, your router doesn't and now I have no internet." Seeing this makes me think the ISP gateway is a locked down device and may not actually allow IP Forwarding if you would. I know AT&T is notorious for this in America on their Fiber ONT Gateways, I used to use them and had to do a workaround that I found on some forums. So I agree and disagree, blaming the router isn't always the correct answer unless troubleshooting with the team and the ISP has led to the issue still persisting, then I agree.   

[TODDzillaInLA]

@Netduma Fraseri think the forums need to go back to the dont ask when the next update is like back in the r1 days 😂

[DiGz]

8 hours ago, TODDzillaInLA said:

@Netduma Fraseri think the forums need to go back to the dont ask when the next update is like back in the r1 days 😂

Those were the days lol