-
Posts
418 -
Joined
-
Last visited
-
Days Won
2
Everything posted by Proud R3 Owner
-
Also noticing in the logs: daemon.err odhcp6c[5767]: Failed to send SOLICIT message to ff02::1:2 (Cannot assign requested address) I have ipv6 turned off on both WAN and LAN so not sure why dhcp6 would be working in the backend. Also I'd almost want to recommend SLAAC (stateless dhcp6) for ip6 LAN instead of dhcp6.
-
Uptime is 2 days right now. If you check the time on the pictures I checked almost an hour later with no change. Just took another look while looking at the uptime and it's still pegged at 100%
-
Here's the log if it helps. R3_2024-03-25T23_47_19.491Z_logs.txt
-
Yeah so I don't know, we're only using the TV in our room right now. CPU 1 is still pegged at 100% with minimal network usage.
-
As the title says, I was just looking to see what the router hardware looked like since nobody's gaming, just a couple of Roku TVs streaming YouTube and Hulu and CPU 1 was just forever pegged at 100% which I could understand if I had a bunch of activity on the network or were using lots of services but we're not, barely touching the bandwidth streaming. Any thoughts?
-
I was getting the same thing, just cleared the cache and storage of the app and it worked.
-
Oh good, I thought it was a bit strange the logs were coming in so fast I literally couldn't download them off the app. I had to log in to the web UI to get them. Great to hear you've all sorted it, I knew you would.
-
Here's the logs, it was difficult to obtain. The logs were coming in so fast I couldn't download a copy. Finally was able to download, here's the logs I need to reboot now. R3_2024-03-22T16_05_10.087Z_logs.txt
-
I've always used 1452 for my mtu. Always just felt snappier to me.
-
MTU - Enter a value or Leave default
Proud R3 Owner replied to PharmDawgg's topic in Netduma R3 Support
I have personally always used 1452 as my mtu. Everything always felt snappier. Maybe I'm just old? -
As you can see I'm getting a good public ipv6 on the R3 I'm just not getting anything other than link local ipv6 IPs from the R3.
-
Yes I too have had successful results when connecting the R3 directly to the modem. It's just trying to pass that ip6 through from my tp-link archer ax11000 to the R3 isn't working right for some reason. I've used dhcp6, slaac/stateless and slaac/rdnss. The one that works is dhcp6 but the R3 is only distributing link local addresses.
-
I get that and honestly I have had that setup and yes ip6 did work. I use another router as an IPS device and pass the R3 through DMZ. I can see the ip6 in the R3 (2600: public ip) but I'm not sure if the R3 is using slaac or just dhcp6 on LAN as I should be able to get a public ip6 using stateless DHCP/slaac on the LAN of the other router I would assume. Not that I really need ip6 and it does mess up some cc features right now but it was just some food for thought honestly.
-
@Netduma Fraser fd and fe addresses are link local only Fraser. You wont be able to access anything outside of your local network using those (i.e. websites using ip6, online games using ip6). Hence why were not able to pass the ipv6 tests bud.
-
-
-
No, I see the IPv6 on the R3 but it's only giving me link local addresses over the network. Only getting fe: and fd: address from the R3.
-
@Netduma Fraser I was playing around with some settings last night. I was able to see the ip6 address as my public address in the R3 but alas the ip6 addresses the R3 was giving out were only link local again.
-
I'm not using an ISP router. I'm using a Motorola mb8611 > tp-link archer ax11000 > R3 (DMZ). TP-LINK router gets a good ip6 and can distribute via slaac wired and wireless I've checked that. When going into the R3 via DMZ however the R3 will only provide a fd/fe ip link local only. I've tried with slaac and dhcp6 on the tp-link. Imo slaac should work but it's not.
-
Just wanted to share, I do have ipv6 available from my ISP. However, when I give the R3 an ipv6 address through dhcp6 or slaac, it only distributes link local addresses (fe, fd).
-
I've been back on the R3 train for about a week or two now. I have it behind one of my tp-link archer ax11000's in DMZ using the archer only for 2.5Gb wan and Homecare. My Wi-Fi is disabled on the R3 and I'm using my other 2 archer AX11000's as APs. It would be nice if there could be an auto function for reboots, cloud sync and firmware updates with the user setting a time for these functions to trigger. It would also be nice to have one cloud sync that covers everything like adblock, ping heatmap, geo, etc. all at once.
-
Doesn't that give you a double NAT?
-
Hey just a question, when you put your r3 behind your Asus router in DMZ, does the AI protection still work for the R3 even though it's in DMZ? Thinking of doing the same with my tp-link archer ax11000 Homecare.
-
Best results I've had on waveform was too disable ipv6 on WAN/LAN, set my Internet speed manually lower than what I get by about 70%, set my sliders to cut my actual ISP speed to 50% and set CC to always. I also had telemetry, remote access and spanning tree disabled. Hope this helps.
-
ETA on new firmware with actual fixes
Proud R3 Owner replied to GavinA895's topic in Netduma R3 Support
I really hate to say this... My R3 currently is in it's box on a shelf in the garage. I did really want and try to make this router work with our environment but stable Internet is a requirement for us. I'm currently using another WiFi 6 router that yields good results but does not have the features I wanted, which DumaOS has. I may be in a different situation than others and have a few older (and newer) routers laying about, but don't be deceived. I'm not going anywhere. I still have plenty of faith in the NetDuma team and will be patiently waiting for the firmware version to come where everything works as intended. I really wish I could help more with logs and troubleshooting with the team but alas I'm a family man and have to think more about the needs of my family first. I'll be checking in from time to time seeing the issues and progress of newer firmware releases. God speed NetDuma, I still believe!