-
Posts
67 -
Joined
Basic Info
-
DumaOS Routers Owned
Netduma R1
XR500
Gaming
-
Connection Speed
Don't know/Won't say
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Suddenly getting rx and tx packet loss?
lockit14 replied to lockit14's topic in NETGEAR Nighthawk Support (XR range)
that was the lowest i've seen it. it was actually doing well past 5% today. closer to 18%, which i can show once i get home. But even that shouldn't be there ^^ without the router there's 0 packet loss whatsoever. I plug in directly to ONT, or use a different router and there's 0 loss. And the XR1000 hasn't had any before either. So is the router done, or is there anything that could possibly cause this issue. Because i'd like to keep on the XR1000, but at this point i'm fearing the router itself is done for since different cables and/or ports all have the same result. -
Suddenly getting rx and tx packet loss?
lockit14 replied to lockit14's topic in NETGEAR Nighthawk Support (XR range)
It's not the cable. I've tested multiple different cables, and it's all the same issue. It's definitely router related. Just don't know what could cause it. -
lockit14 started following Suddenly getting rx and tx packet loss?
-
Up until two days ago everything had been alright. 2 days ago i noticed that one of my streams to YT was getting terrible lag. Have spent the past 2 days trying to pinpoint what the issue, originally thinking it was a PC/OBS issue, since I hadn't touched the router. (XR1000) I downloaded startrinity continuous internet speed test tool. It shows a constant rx and tx packet loss between 1-5%. Went ahead and rebooted, as well as eventually completely resetting it, but still the same issue. So i bypassed the router and plugged directly from ONT to my PC: absolutely no packet loss. Any reason this would suddenly be happening?
-
It happened a few days ago, while connected through ethernet. When it happened my GF and her little sibling were in the living room playing fortnite and never once disconnected Is there any software, or tool that you know about that i could purchase or download that can detect the issue? That i can constantly have running and it detect the exact issue when the disconnect happens?
-
No the first pic was an older photo, just to show that i had it set up correctly, as far as setting a IP on Wan Settings page. I've had the .31 IP set for it for weeks now. I was just at work so couldn't take a current picture until i was back home this morning. Which i did and added to show current settings, all of which have been set for weeks/months now
-
This is how it's setup, except with the IP shown above ^^^ (I"m at work so only have this screenshot from when i set it up previously) Not it's the same setup and settings, just with the mentioned IP from above ^^ with most other devices assigned their own IP's as well, none of which have the same IP as my PC
-
Alright so i just had it happen, and i've been running continuous ping to my router for the past day and a half, with time stamps, and this is how it looks 1/19/2023 7:26:35 PM - Reply from 64.127.154.247: bytes=32 time=2ms TTL=64 1/19/2023 7:26:36 PM - Reply from 64.127.154.247: bytes=32 time=1ms TTL=64 1/19/2023 7:26:37 PM - Reply from 64.127.154.247: bytes=32 time<1ms TTL=64 1/19/2023 7:26:38 PM - Reply from 64.127.154.247: bytes=32 time=1ms TTL=64 1/19/2023 7:26:39 PM - General failure. 1/19/2023 7:26:40 PM - Reply from 64.127.154.247: bytes=32 time<1ms TTL=64 1/19/2023 7:26:41 PM - Reply from 64.127.154.247: bytes=32 time<1ms TTL=64 1/19/2023 7:26:42 PM - Reply from 64.127.154.247: bytes=32 time<1ms TTL=64 1/19/2023 7:26:43 PM - Reply from 64.127.154.247: bytes=32 time<1ms TTL=64 1/19/2023 7:26:44 PM - Reply from 64.127.154.247: bytes=32 time<1ms TTL=64 At the same time as that "general failure" this shows up in the logs in settings on my router. [DHCP IP: (192.168.1.31)] to MAC address D8:BB:C1:CD:9A:BE, Thursday, Jan 19,2023 19:26:40 EDIT: I also just happened to look into the ping results (it gets saved to a text note automatically) and noticed this 1/19/2023 7:26:35 AM - Reply from 64.127.154.247: bytes=32 time=1ms TTL=64 1/19/2023 7:26:36 AM - Reply from 64.127.154.247: bytes=32 time=1ms TTL=64 1/19/2023 7:26:37 AM - Reply from 64.127.154.247: bytes=32 time=1ms TTL=64 1/19/2023 7:26:38 AM - PING: transmit failed. General failure. 1/19/2023 7:26:39 AM - Reply from 64.127.154.247: bytes=32 time<1ms TTL=64 1/19/2023 7:26:40 AM - Reply from 64.127.154.247: bytes=32 time<1ms TTL=64 1/19/2023 7:26:41 AM - Reply from 64.127.154.247: bytes=32 time=5ms TTL=64 Exactly 12 hours before, general failure. At this exact moment I was disconnected from online cod. Any idea what this means? or why it done it? that mac and IP is for my PC that I'm using when it happened
-
The times in the log aren't accurate in comparison to actual time. It's was 1400 hours when I sent the log file, yet log file has events listed with time way past that. The disconnect happened about 10 mins before I downloaded the log file. About 15 mins before I posted that response ^^^. For me it was 2 PM mountain time. But log file isn't appearing as Mountain time, so I haven't any clue what time it would be listed as on it since the times are off
-
Here's a log file, and I had a disconnection around 5-20 mins before downloading the file. Also, I have my router time zone set correctly, but notice in the log that the times definitely don't match up. For instance it's got times well past 1400 hours, (2 PM) which is what it is currently, not sure if that is important or anything. Or if logs purely in regards to the top/bottom being most recent event and steadily follows that method of loggin log-1673816928234.txt
-
@Netduma Liamlog-1669836723840.txt including log. game disconnected a little after 4 AM this morning, between 4 and 5. EDIT: Actually, the router is an hour behind for some reason. i noticed the log only starts at 3:13 AM (which is 4:14) and that's when the disconnect happened So kinda useless seeing as it doesn't show anything up to or when the disconnect happpens