Jump to content

XR500 Noob

Members
  • Content Count

    10
  • Joined

  • Last visited

About XR500 Noob

  • Rank
    New

Basic Info

  • DumaOS Routers Owned
    XR500

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. When directly into the modem, yes. I've have been disconnected with and without the router involved.
  2. RP Attack] from source: 24.113.180.1, Sunday, January 26, 2020 00:03:09 [DoS Attack: ARP Attack] from source: 24.113.180.1, Sunday, January 26, 2020 00:02:03 [DoS Attack: ARP Attack] from source: 24.113.180.1, Sunday, January 26, 2020 00:01:59 [DoS Attack: ARP Attack] from source: 24.113.180.1, Saturday, January 25, 2020 23:57:11 [DoS Attack: ARP Attack] from source: 24.113.180.1, Saturday, January 25, 2020 23:56:36 [DoS Attack: ARP Attack] from source: 24.113.180.1, Saturday, January 25, 2020 23:54:49 [DoS Attack: ARP Attack] from source: 24.113.180.1, Saturday, January 25, 2020 23:53:42 [DoS Attack: ARP Attack] from source: 24.113.216.1, Saturday, January 25, 2020 23:51:42 [DoS Attack: ARP Attack] from source: 24.113.180.1, Saturday, January 25, 2020 23:43:44 [DoS Attack: UDP Port Scan] from source: 59.108.66.240, port 389, Saturday, January 25, 2020 23:43:38 [DoS Attack: UDP Port Scan] from source: 59.108.66.240, port 389, Saturday, January 25, 2020 23:43:31 [DoS Attack: UDP Port Scan] from source: 59.108.66.240, port 389, Saturday, January 25, 2020 23:43:25 [DoS Attack: UDP Port Scan] from source: 59.108.66.240, port 389, Saturday, January 25, 2020 23:43:08 [DoS Attack: ARP Attack] from source: 24.113.216.1, Saturday, January 25, 2020 23:37:22 [DoS Attack: SYN/ACK Scan] from source: 144.217.105.199, port 8080, Saturday, January 25, 2020 23:33:38 [admin login] from source 192.168.1.2, Saturday, January 25, 2020 23:24:12 [admin login] from source 192.168.1.2, Saturday, January 25, 2020 23:24:11 [DoS Attack: ARP Attack] from source: 24.113.115.1, Saturday, January 25, 2020 23:19:21 [DoS Attack: ACK Scan] from source: 44.224.142.197, port 443, Saturday, January 25, 2020 23:18:22 [DoS Attack: ACK Scan] from source: 44.224.142.197, port 443, Saturday, January 25, 2020 23:15:22 [DoS Attack: Jolt2] from source: 59.108.66.240, Saturday, January 25, 2020 23:14:13 [DoS Attack: UDP Port Scan] from source: 59.108.66.240, port 389, Saturday, January 25, 2020 23:13:52 [DoS Attack: ACK Scan] from source: 44.224.142.197, port 443, Saturday, January 25, 2020 23:12:22 [DoS Attack: ARP Attack] from source: 24.113.115.1, Saturday, January 25, 2020 23:11:23 [DoS Attack: ACK Scan] from source: 44.224.142.197, port 443, Saturday, January 25, 2020 23:09:22 [DoS Attack: ARP Attack] from source: 24.113.115.1, Saturday, January 25, 2020 23:09:12 [DoS Attack: RST Scan] from source: 176.9.48.73, port 443, Saturday, January 25, 2020 23:06:29 [DoS Attack: ACK Scan] from source: 44.224.142.197, port 443, Saturday, January 25, 2020 23:06:22 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:05:53 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:05:35 [DoS Attack: RST Scan] from source: 176.9.48.73, port 443, Saturday, January 25, 2020 23:05:35 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:05:26 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:05:15 [DoS Attack: UDP Port Scan] from source: 125.5.184.43, port 389, Saturday, January 25, 2020 23:05:10 [DoS Attack: RST Scan] from source: 176.9.48.73, port 443, Saturday, January 25, 2020 23:05:08 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:04:56 [DoS Attack: RST Scan] from source: 176.9.48.73, port 443, Saturday, January 25, 2020 23:04:54 [DoS Attack: RST Scan] from source: 176.9.48.73, port 443, Saturday, January 25, 2020 23:04:47 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:04:47
  3. [DoS Attack: RST Scan] from source: 176.9.48.73, port 443, Saturday, January 25, 2020 23:06:29 [DoS Attack: ACK Scan] from source: 44.224.142.197, port 443, Saturday, January 25, 2020 23:06:22 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:05:53 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:05:35 [DoS Attack: RST Scan] from source: 176.9.48.73, port 443, Saturday, January 25, 2020 23:05:35 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:05:26 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:05:15 [DoS Attack: UDP Port Scan] from source: 125.5.184.43, port 389, Saturday, January 25, 2020 23:05:10 [DoS Attack: RST Scan] from source: 176.9.48.73, port 443, Saturday, January 25, 2020 23:05:08 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:04:56 [DoS Attack: RST Scan] from source: 176.9.48.73, port 443, Saturday, January 25, 2020 23:04:54 [DoS Attack: RST Scan] from source: 176.9.48.73, port 443, Saturday, January 25, 2020 23:04:47 [DoS Attack: UDP Port Scan] from source: 67.231.245.66, port 389, Saturday, January 25, 2020 23:04:47 I get literally thousands of these a day. I get dc'd every 20-30 minutes for the last month. I've tried 3 different modems and routers, attempted everything I could find on the internet (new ip, vpn, settings, firewalls, dns, static and DCHP ip settings) to make the dc's stop. I've messaged multiple people for a tech support, could I please get some help with this 300 dollar router so I can use the internet that I pay for?
  4. You wouldn't happen to know if all these changes would make steam app un-oppenable would you? Just a shot in the dark here
  5. Wow. I've been dancing around the answer for like 3 days, you nade it seem so simple. Regardless, tyvm. As it seems I have a new ip and everything is working.
  6. So I got a new IP from turning off modem for an hour. I loaded xr500 and it displays new IP address after going through internet set up. I've reset my modem from my ISP and now I don't have internet access. "Your computer appears to be correctly configured, but the device or resource is not responding." This error has emerged from the windows network diagnostics tool.
  7. I have both to my knowledge. Ipv4 and 6 both pop up when I look for my IP. I'm currently waiting with my router modem off. Edit: idk if they do or not, would that make a difference? My ISP also told me no, I called them before searching the web for answers. Can I not command prompt a new one and put it into my xr500 with vpn overlay?
  8. Yeah I've had this issue through 2 modems and 2 routers for about 2 weeks now. Do I need to do anything in the set up options or will the new forced IP auto update? And now that i have a vpn I should be safe once it changes?
  9. Idk if I'm sold on the false positive because everytime they pop up in my logs, my entire net becomes unusable. My ping will jump anywhere from 300 to 12k and usually towards the later. I get dc'd from everything and have to wait for 10 to 20 minutes usually. Are you saying that it will self resolve because it's dynamic through isp?
  10. Basically, I've troubleshot my internet extensively (ISP techs, multiple ISP modem resets, new modem and router, every setting I could think to boost or limit my net issues) and finally found out that I was being DoS attacked through the XR500 logs. [DoS Attack: SYN/ACK Scan] from source: 89.187.186.70, port 80, Saturday, January 18, 2020 22:11:31 [DoS Attack: SYN/ACK Scan] from source: 89.187.186.65, port 80, Saturday, January 18, 2020 22:10:46 [DoS Attack: SYN/ACK Scan] from source: 89.187.186.70, port 80, Saturday, January 18, 2020 22:06:07 There are hundreds more, but here are some. First I set up a VPN through the XR500, which didn't rid me of the problem. I then went to my command prompt and created a new IP address, and then received a DoS attack soon after.I then tried to input a static IP from my command prompt. My net crashed, I reversed it back and now am stuck. I also just received this error, not sure what in regards too. (NetGear SOAP has failed) Ahh the timing: [DoS Attack: SYN/ACK Scan] from source: 89.187.186.175, port 80, Saturday, January 18, 2020 22:50:42 As I'm putting this request in. As my name indicates, I don't feel like I know enough to figure this out on my own. Please send help.
×
×
  • Create New...