Proud R3 Owner

Honestly that's not 100% accurate. I've got my settings pretty well dialed in. I can use most of the features I want ( not ip6, STP or adblocker because I don't need that) and I get really good results because of it. Honestly I kind of agree where they advertised hybrid VPN and it's still not here. Granted that doesn't affect me as I don't use that but I still see that's not good to advertise something that's not even there yet. Also the main issue for me (and it still happens now on the most updated fw) is when the R3 just decides to drop LAN connections abruptly. That's a big deal to me with a large household where everyone depends on stable Internet connectivity, not just for gaming but work and school.

Also changing DHCP lease time to 10000 can help as well

I got mine up and running before Christmas and I've had minimal issues since *.41 FW. I'll admit I went back to my previous setup for a while and put my R3 on the shelf as the Internet kept dropping from the LAN ports. But seriously for the most part I haven't had a ton of trouble since .41

I personally have my R3 in a DMZ off my tp-link archer ax11000 just for the homeshield IPS. I have ip6 and STP disabled. I have Cox gigablast service which is 1Gb down and (cringe) 35Mb up. I set my speed manually to 800/30 and set CC to 80/70. I get A+ on waveform consistently and for the most part we can do anything we want on the network simultaneously with nothing being affected, including large downloads, video calls, gaming, etc. Yes there are some issues but I'm happy with my purchase. I knew going in the WiFi wouldn't be strong enough for my house and yard so I have 2 ax11000 routers in AP mode for that. When the firmware is fixed with minimal issues, I'll do more with it but that's not saying I'm unhappy with the R3, I still think it's a great piece of tech and it'll only get better.

You have to understand when making fixes or debugging code, fixing one thing can break another if it has dependencies. They know there's a lot to do and I know they're working hard on it. Honestly if you're that unhappy, I get it, but don't short change yourself and just throw it away when it could be great eventually. I understand completely needing stable net as I have many backup routers to use if I need to, but I'm not gonna throw my R3 away or sell it as I feel it'll be a great device once some issues are sorted out.

You know I do notice that the logs will go black and I'm not able to see timestamps or actual log data sometimes, don't really know if it's a direct result of this. Also I notice that the UI, whether on the app or browser based, will be sluggish and will take more time that normal to populate data (i.e. CPU graph, advanced menus, etc) where the data location will be almost a blinking black area until data populates, which usually is almost instant (1-2 seconds) will take up to 10 seconds or so. Sometimes I will see some buffering in media or hang ups (hardwire) can't really be sure though if that's an issue with what I'm seeing in the logs or just an issue with the service. I'm sorry I can't be of more help.

Also I'm not sure what's going on here: Thu Apr 4 2024 20:34:54 kern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became fullkern.warn kernel: skb queue became full

I also notice I get this error every 2 minutes or so. daemon.err odhcp6c[4346]: Failed to send SOLICIT message to ff02::1:2 (Cannot assign requested address)

I've been looking at the log just after startup and there's a lot of errors, failures, etc.

Well if you put a router behind another router you'd want to put that second router in the DMZ as it has it's own firewall and relieves double NAT. Yes I agree if you only have 1 router DMZ leaves it completely open to everything which isn't very secure. However if you're putting a router in DMZ it has it's own security.

If you really wanted to do it right, you could potentially get one of those Asus routers and use it for your home network, put the R3 in it's DMZ and just use that for your gaming devices.

I get that and yes I have 4 kids and my wife and I also game. Sometimes there's multiple consoles, PCs etc at the same time being utilized simultaneously.

Right but as you can only use 4 devices in Geo filter, it would be beneficial to be able to have it enabled for gaming devices that aren't on Geo filter.

Honestly if they were going to implement steady ping as a network wide service, you'd think they'd make it's own menu item like Geo filter, smart boost or adblocker. Actually that's a pretty good idea to use the adblocker menu as a template as you could enable or disable it at the device level.

Steady ping when enabled only affects devices added to the Geo filter when filtering is enabled for said devices.

Make sure IP6 is disabled on WAN and LAN also as it breaks CC.

Ipv6 breaks CC for some reason. When I have IP6 enabled my waveform test scores don't reflect my CC settings. As soon as I turn off IP6 on WAN and LAN, I get A+. I think IP6 is fixed in the new firmware coming out soon though.

Turning off Geo latency and ping assist (setting it to 0) can help but that might just be for your Geo fence. I've also read where people have turned off smart boost as well.

Disable steady ping coz it adds latency to try to make a more stable latency profile.

The WAN and LAN ports on the R3 are 1Gbps.

So I'm on the DumaOS app looking to see if it'll pick up that I'm watching Hulu and I'm noticing it's labeled under unknown and uncategorized. Should be Hulu under video and streaming. I would assume this traffic wouldn't be prioritized correctly since it's not being detected/labeled correctly.

So after changing dhcp to 10k and rebooting, the CPU has calmed down. Not sure if the settings change or the reboot brought the CPU back down but only time well tell. I'll keep an eye on it and report back if I see the CPU maxed out consistently again.

Well my entire network is running behind the R3. My R3 is the only thing connected to my first ax11000 as it's only being used for intrusion protection with Homecare. I've used all the firmware so far, I'm on .41 now as I find it the most stable. I do not use STP as I don't have any loopbacks on the network. Honestly I think there is a bug with DHCP, I'm also seeing dhcp6 in the logs which is strange as I have ip6 disabled for LAN and wan as it doesn't pass from one router to another.

I do have it set to 1440 but I can definitely set it to 10k and give an update when I get home.

Actually I have 3 of them. Yes the R3 is behind one of them in DMZ using the first AX11000 as an IPS via Homecare. The other 2 are just APs as I find the WiFi of the R3 to be a bit lacking for my needs so it's turned off. I do have their MAC in IP reservation as 77.2-3 respectively. I also have them set to static IP within the APs themselves.