Jump to content

Search the Community

Showing results for tags 'upnp'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News & Community
    • News & Announcements
    • Feature Ideas & Improvements for DumaOS
    • Community Discussion
  • Support
    • Knowledge Base
    • Latest Firmwares
    • DumaOS on NETGEAR Nighthawk Support
    • DumaOS on Netduma R1 Support (Open Beta)
    • Original Netduma R1 Firmware Support
    • Call of Duty Support
    • New Games for the Geo-Filter
  • Duma Army Lounge
    • Gamer Talk
    • TechnoBabble
    • Off Topic
  • International Language Forums
    • NETDUMA Deutsch
    • NETDUMA Español
    • NETDUMA Français
  • 1 on 1 Support
    • Request 1 on 1

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


Interests


Website URL


Skype


Twitter


Discord


Steam


PlayStation Network


Xbox Live


Nintendo Switch


Battle.net


Connection Speed

Found 9 results

  1. Hi All, For the last two days I've been getting DDOS'd offline on my Xbox One X. (I play Call of Duty WW2 and my ranking encourages dislike from other players.) The first time it happened was at halftime during a game of domination. Since then, my console has been randomly losing internet connection. Below are logs from my XR500- does anyone have experience with this? Do I need to do a factory reset on my Xbox console? I've turned UPNP off for the time being, but I'm not sure if there are other settings I need to enable/disable on the XR500. [DoS Attack: SYN/ACK Scan] from source: 54.36.24.186, port 9987, Wednesday, May 30, 2018 13:30:49 [DoS Attack: SYN/ACK Scan] from source: 54.36.24.186, port 9987, Wednesday, May 30, 2018 13:43:09 [DHCP IP: 192.168.1.8] to MAC address 98:e0:d9:a2:ee:95, Wednesday, May 30, 2018 13:51:32 [DumaOS] DHCP new event., Wednesday, May 30, 2018 13:51:32 [DumaOS] DHCP new lease allocated., Wednesday, May 30, 2018 13:51:32 [internet connected] IP address: , Wednesday, May 30, 2018 14:36:13 [DHCP IP: 192.168.1.8] to MAC address 98:e0:d9:a2:ee:95, Wednesday, May 30, 2018 14:37:40 [DumaOS] DHCP new event., Wednesday, May 30, 2018 14:37:40 [DumaOS] DHCP lease change., Wednesday, May 30, 2018 14:37:40 [DoS Attack: SYN/ACK Scan] from source: 54.39.41.224, port 4444, Wednesday, May 30, 2018 15:20:31 [uPnP set event: del_nat_rule] from source 192.168.1.3, Wednesday, May 30, 2018 15:30:19 [uPnP set event: add_nat_rule] from source 192.168.1.3, Wednesday, May 30, 2018 15:34:56 [uPnP set event: del_nat_rule] from source 192.168.1.3, Wednesday, May 30, 2018 15:36:23 [uPnP set event: add_nat_rule] from source 192.168.1.3, Wednesday, May 30, 2018 15:36:26 [DoS Attack: SYN/ACK Scan] from source: 185.53.160.216, port 80, Wednesday, May 30, 2018 15:50:40 [DoS Attack: SYN/ACK Scan] from source: 54.39.41.224, port 4444, Wednesday, May 30, 2018 15:55:14 [DumaOS] Resync R-App store cloud, Wednesday, May 30, 2018 16:08:25 [DumaOS] HTTP download failed with code '404', Wednesday, May 30, 2018 16:08:25 [DumaOS] R-App store cloud sync failed, Wednesday, May 30, 2018 16:08:25 [DumaOS] Cloudsync DPI result 'false','All mirrors are down', Wednesday, May 30, 2018 16:09:09 [admin login] from source 192.168.1.2, Wednesday, May 30, 2018 16:25:43 [DHCP IP: 192.168.1.2] to MAC address cc:40:d0:43:0c:4d, Wednesday, May 30, 2018 16:43:39 [DumaOS] DHCP new event., Wednesday, May 30, 2018 16:43:39 [DumaOS] DHCP lease change., Wednesday, May 30, 2018 16:43:39 [WLAN access rejected: incorrect security] from MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:43:46 [DHCP IP: 192.168.1.6] to MAC address 1c:5c:f2:e1:28:89, Wednesday, May 30, 2018 16:43:46 [DumaOS] DHCP new event., Wednesday, May 30, 2018 16:43:46 [DumaOS] DHCP lease change., Wednesday, May 30, 2018 16:43:46 [WLAN access rejected: incorrect security] from MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:43:49 [WLAN access rejected: incorrect security] from MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:44:26 [WLAN access rejected: incorrect security] from MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:44:29 [WLAN access rejected: incorrect security] from MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:44:38 [WLAN access rejected: incorrect security] from MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:44:41 [DHCP IP: 192.168.1.3] to MAC address 2c:54:91:50:fb:d1, Wednesday, May 30, 2018 16:44:48 [DumaOS] DHCP new event., Wednesday, May 30, 2018 16:44:48 [DumaOS] DHCP lease change., Wednesday, May 30, 2018 16:44:48 [DHCP IP: 192.168.1.51] to MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:44:56 [DumaOS] DHCP new event., Wednesday, May 30, 2018 16:44:56 [DumaOS] DHCP lease change., Wednesday, May 30, 2018 16:44:56 [DHCP IP: 192.168.1.51] to MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:44:57 [DumaOS] DHCP new event., Wednesday, May 30, 2018 16:44:57 [DumaOS] DHCP lease change., Wednesday, May 30, 2018 16:44:57 [DHCP IP: 192.168.1.34] to MAC address cc:40:d0:43:0c:4d, Wednesday, May 30, 2018 16:51:06 [DumaOS] DHCP new event., Wednesday, May 30, 2018 16:51:06 [DumaOS] DHCP new lease allocated., Wednesday, May 30, 2018 16:51:06 [admin login] from source 192.168.1.34, Wednesday, May 30, 2018 16:51:09 [WLAN access rejected: incorrect security] from MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:51:12 [DHCP IP: 192.168.1.4] to MAC address 94:9a:a9:c3:2a:44, Wednesday, May 30, 2018 16:51:13 [DumaOS] DHCP new event., Wednesday, May 30, 2018 16:51:13 [DumaOS] DHCP lease change., Wednesday, May 30, 2018 16:51:13 [WLAN access rejected: incorrect security] from MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:51:15 [DHCP IP: 192.168.1.6] to MAC address 1c:5c:f2:e1:28:89, Wednesday, May 30, 2018 16:51:17 [DumaOS] DHCP new event., Wednesday, May 30, 2018 16:51:17 [DumaOS] DHCP lease change., Wednesday, May 30, 2018 16:51:17 [WLAN access rejected: incorrect security] from MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:51:35 [WLAN access rejected: incorrect security] from MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:51:38 [DHCP IP: 192.168.1.2] to MAC address 70:14:a6:46:d7:16, Wednesday, May 30, 2018 16:51:54 [DumaOS] DHCP new event., Wednesday, May 30, 2018 16:51:54 [DumaOS] DHCP new lease allocated., Wednesday, May 30, 2018 16:51:54 [DumaOS] Marking device that is marked 192.168.1.2 7 1., Wednesday, May 30, 2018 16:51:54 [DHCP IP: 192.168.1.254] to MAC address 2c:54:91:50:fb:d1, Wednesday, May 30, 2018 16:52:17 [DumaOS] DHCP new event., Wednesday, May 30, 2018 16:52:17 [DumaOS] DHCP new lease allocated., Wednesday, May 30, 2018 16:52:17 [DoS Attack: ARP Attack] from source: 192.168.1.3, Wednesday, May 30, 2018 17:03:27 Any help is greatly appreciated. Thank you!
  2. Hi. I have seen 1 or 2 comments regarding UPnP not working but as I have an open nat I paid no attention to it until just now. I have gone to advanced>>>upnp and noticed that the upnp port mapping is totally blank, even when playing C.O.D. As I have an open nat then upnp must be working, right? Something is askew though. B.D
  3. Hello , Im having an issue with UPNP its not triggering any ports although it used to work at first when i got the router an update maybe screw it up ? Im playing cod on ps4 it used to open port 3074 and 9038. but now nothing and gives me Moderate Nat in cod.
  4. I have a QNAP Nas and one of its characteristics is about automatically map services to the UPnP port forwarding. At first it did not work, after 1 week and a new factory reset, the UPnP rules started working, that is a weird behaviour (I was about to contact QNAP for some help). I also have a question about static routes, the absence of that option really bugs me out, how it's possible to block one of the core functionalities of a router? I saw a lot of old topics that was an incoming feature, is it true? I really do hope DumaOS will include this feature, with hopefully some good VPN control. Now for one feature request, I would like to request a smartdns/pi-hole dns control per device as the VPN config. That way it's really easy to enable and opt-out some devices that either are not from power users (that would adjust the pi-hole server). For now I tried using my NAS as a VPN server with the specific dns, but something gets wrong when the router tries to connect to a vpn within the local network, even with port forwarding enabled and working.
  5. Hello everyone! Just got my NETDUMA yesterday and already enjoyed some improved gameplay on WWII, so naturally I want to see how much better it can be. Console: XBOX1 ISP: Xfinity Download: 45 mbs Upload: 12 mbs Location: Midwest, USA Saw pings around 12-25ms Alright so I would like some clarification on a couple of questions. I have been doing my research for sure, but I am getting mixed answers. I am currently getting the "we detected another router" message so I would was thinking about adding my wan ip into the DMZ of my isp Modem Router, but this leads me to my questions. Does the "We detected another router" message matter if I have an open Nat? (I used to always get "open", didn't retest after setting up netduma with geofilter off) Is putting my wan ip into the DMZ "Safe." I understand the Netduma has a firewall, but is it considered adequate protection. Is there any point to this if you leave UPnP enabled? (I saw someone who suggested using Port Forwarding for xbox live and leaving UPnP enabled in the netduma.) Is there any drawback/benefits to port forwarding vs UPnP other than attempting to achieve an OPEN NAT How good is 12-15 ping? Is there any benefits to bridge mode? I shut off the WIFI of my xfinity router/modem, but did not put it in bridge mode. Should I give my xbox a reserved IP? I am well aware that you can google bridge mode, DMZ, UPnP and each term, but I have read for hours now and am still having trouble how they all relate to each other, which is preventing me from finding the right balance for my setup. Everything is working, but I am just trying to maximize my experience and knowledge. Thank you all in advance for time spent answering my questions.
  6. Im getting different answers while reading through different threads so can soomeone tell me for my setup should i have it ticked or unticked ? I have a Virgin hub than my netduma connected to the virgin hub
  7. Ok so this just happened!! Very weird, Duma has been up and running a fair while, setup is solid, wired connections, hyperlane etc etc. Its been solid but suddenly my UPnP table is showing this, my partners ps4 has gone mental and just demanded as many ports to 3074 as possible. we both play on wired connections with reserved IP's for our consoles, no port forwarding rules in place anywhere etc but clearly Duma or Console are not in sync. Any suggestions other than a reboot which is what i will now do but i don't want the issue just coming back. thanks
  8. Just using UPnP now shows open NAT in game on IW PS4 for port 3074. If you used to just use UPnP and switched to port forwarding you can now return to UPnP.
  9. Ok so the ongoing saga of two consoles on one network continues. Netduma is setup on point as when i play solo it works really well for the most part. Upnp is active and there are no port forward rules to conflict with it. Only one ps4, mine is active in the geo filter. Only mine is in hyperlane, again to prevent conflicts. UPnP table shows that port 9308 is directed to my ps4. It also shows 3074 is direct to mine. It has port mapped 3074 via another external port number to the other ps4 so in theory, open nat although the game on that machine reports moderate. My question is why doesn't port 9308 get port mapped the same way to the other ps4 via an alternate external port? We often find games together are pretty messy, activision talk horse kack about routing 3075 to the second console which doesn't work at all. case in point, if that were the solution they would allow the port mapping to switch it via UPnP to the second port. having tested the non UPnP setup and done port forwarding, the second console has massive issues and moderate NAT. port 9308 gets mapped immediately when i turn on my console after clearing the table so its clearly a core port for ps4's systems. i don't understand how the second console can simply be blocked and not mapped in the same manner as 3074 via UPnP. Its fairly safe to say that most posts on the web heavily criticise the ps4's poor UPnP qualities but can you guys buff it from your side at all? we can't join the same party as the first to join a party locks the second console out and then can lead to us getting totally kicked from a game and our NAT status gets messed up. How in the name of all sanity Sony didn't think that more than one console may exist on the same network is beyond me but i guess they figured saying next gen a lot may make magic happen to solve stuff they couldn't be bothered to address. we use our billion 8800nl in bridge mode and then the duma dials out to plusnet fibre, we get great solid speeds, both consoles run via powerline adaptors over lan so no wifi. all the mtu values are adjusted to plusnets recommended 1492 value on duma and consoles, ipv6 is disabled, deep packet processing etc in misc is all off as is local link ipv6 so its all in line on that front. any ideas or is it just down to sony being totally useless which is the general internet consensus?
×
×
  • Create New...