Jump to content


  • Content Count

  • Joined

  • Last visited

About Macusa69

  • Rank
  • Birthday 05/12/1969

Basic Info

  • Gender
  • Location
    Beirut - Lebanon
  • DumaOS Routers Owned
    Netduma R1

Recent Profile Visitors

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

  1. Hello Frayser, Any advantages by using this method ? connecting directly to the R1 through pppoe?
  2. Hello Stalker4hire-, I had the same problem as yours for several weeks. Tried everything to fix the UPNP issue but with no success. Reboot my R1 and even hard reset it but still the ports are showing in the UPNP section, even though the UPNP is turned off. But now I've found a solution to this but doing the follwoing: 1- Hard reset R1 ( firmware milestone 1.3 ). 2- Immediately after hard reset, downgrade to the old R1 os ( 1.03.6j ). 3- While on 1.03.6j , turn the UPNP OFF and hard reset 4- Immediately after hard reset the R1 upgrade to milestone 1.3 Everything now should be working as usual, you can portforwarding while UPNP is off. cheers,
  3. Hello Admin, I am already using the same ports mentioned in your reference. By doing what you suggested, it messed up my connection. Start connecting to P2P lobbies with much higher pings, whereas I always connected to dedicated servers. Frankly I don't care too much about open Nat, as long as I am having a good lobbies, connection etc... So I turned UPNP off, and boom, my R1 is great again. Please, please try to suggest to everyone to hard reset his router before upgrading to DUMAOS. For the past several months, I never had a stable experience with my Dumaos, sometimes it's acting good and sometimes better, but now it is much, much better after I downgraded to 1.03.6j and then I hard reset my R1 and then I upgraded to milestone 1.3 and made the setting mentioned above. Anyways, thank you very much for your help and support.
  4. And don't forget that I have put my R1 in DMZ, so UPNP is definitely off.
  5. Yes, both my modem and router. This way I find my connection to be better.
  6. That's what I did. Disable UPNP and portforward the required ports, and my R1 is in the DMZ of my router. I also tried enable UPNP without portforward but still moderate Nat in the game. I even changed two ( different brands ) ISP routers and still the same results. This is strange considering everything is working perfectly within the new milestone 1.3. I don't know if it's my ps4 pro? Forget to mention that I also have reserved an IP address for my PS4 in the DHCP section of the R1.
  7. That's what I thought. Anyways, I am obliged to use VPN becasue I am from the middle east and we usually get connected to SA ( Saudi Arabia ) server, which is unplayable. but while using a VPN to get connected to Europe, I get way better connection than SA server. and by the way, I am using EXPRESSVPN, it gives me a very fast and premium connection while using it.
  8. I am using a vpn in my PS4 Pro to play COD BO4. My Nat type in my console is Nat type 2, but in the game it shows moderate. I have made every possible way to change that but with no success. I have my ISP modem - Netduma R1 ( milestone 1.3 ) - ps4. Modem is in DMZ mode to Netduma ( portforwarded required ports - UPNP disabled ). Also I downgraded to the original Netduma os ( 1.03.6j ) and hard reset and then upgraded again to milestone 1.3 . I can tell, after doing that, that everything works exceptionally well and better than before, Ping assist works well, always connected to dedicated servers, connection in game is way better than before but the only persisting problem is till moderate Nat in the game. So my question is : USING A VPN DOES NOT GET YOU AN OPEN NAT ? PS: By the way you should ( DUMAOS guys ) suggest ( and this is a must to do step ) that before upgrading to milestone 1.3, every one should hard reset their Netduma R1 router before that.
  9. So, I understand from your replies that it's a common bug ?
  10. Please advise me what to do if you find a solution.
  11. my network settings does not show "Uncaught TypeError: Cannot read property 'name' of undefined" unless I reboot my R1. it's been happening frequently but not all the time. Just want to post this so that you can fix it in your next software update.
  • Create New...