Jump to content

Search the Community

Showing results for tags '1.03.06 settings NAT'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News & Community
    • News & Announcements
    • Feature Ideas & Improvements for DumaOS
    • Community Discussion
  • Support
    • Knowledge Base
    • Latest Firmwares
    • DumaOS on Netduma R2 Support
    • DumaOS on NETGEAR Nighthawk Support
    • DumaOS on Netduma R1 Support
    • 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

Marker Groups

  • Members

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





DumaOS Routers Owned

TS Model

Website URL





PlayStation Network

Xbox Live

Nintendo Switch


Gamer Type

Favourite Genres

Connection Speed

Found 1 result

  1. **Pour la version française, cliquez ici: http://forum.netduma.com/topic/20615-si-vous-souhaitez-configurer-vous-m%C3%AAme-votre-netduma-ou-loptimiser-au-mieux-cest-ici/ ** Hello everyone, Following many requests, I present today the best configuration (from my point of view) available on the current version of the NetDuma. I hope this topic can help you before the arrival of the new firmware. I will expand this topic as best I can to please everyone so do not hesitate to come back later for news (I think add updates regularly enough) and give me your reviews / tips to improve it At best: http://forum.netduma.com/topic/20728-the-best-settings-imo-for-the-10306-firmware-feedbacks-and-suggestions/ I'm talking to new users as well as experienced users, even confirmed users playing on COD, Destiny, FIFA, ... on any medium (Game Console or PC). I would like to point out that these adjustments are the result of my experience and advices I have been able to glean over the months. 1) Configuring your ISP modem – (Modem with built-in Router combo units.) At first, we will dwell on the configuration of your ISP modem/router combo unit. I would not dwell on the specificities of each box (DHCP, static IP, ...) and lets you search the information by yourself. You can configure your ISP modem with your NetDuma in two ways: DMZ or bridge. A DMZ is a virtual zone designed to accommodate equipment that will not be affected by the security rules of the box (but this is still the main router) while the bridge mode is used to make your NetDuma your router Main and connected "directly" to the Internet. The DMZ is available in most the ISP modem with built-in routers combo units of the market but this is not necessarily the case for bridge mode. Be aware that some ISPs lock down the modems UI or may not allow access to the modems UI. Contact your ISP for help and information regarding this if needed. If you want to configure a DMZ (to be done on your modem): For modems with built-in router combo units. A) Configure a Reserved IP address for the R1 on the Modem/Router You must configure a reserved IP with the NetDuma's MAC address (this is available on the back of the router on the label.) Example: 56: 2d: 36: p9: 56: b2) on the modem. Enable DMZ You must activate the DMZ for the reserved IP address you defined earlier. Place the IP address that was reserved for the R1 router into the modems DMZ. C) Disable UPNP on the modem. If feature is available. (UPNP allows automatic opening of ports used for your applications and games. Since the NetDuma will take over this task, it is preferable to disable it.) D) Delete all port forwarding rules on the ISP Modem/Router and R1 router If you had previously set up rules for your console, you should delete them E) If you want to configure the bridge mode: Putting a modem/router into modem only mode. As for bridge mode, Some ISPs use DHCP to pass the WAN IP address like Cable ISPs or with ADSL, use PPPoE to pass the WAN IP address. For ADSL/PPPoE connections, user name and password maybe needed to input on to the NetDuma R1 so that it can authenticate thru the bridged modem. This is only seen on some DSL ISP services. Cable ISPs do not use authentication and just use DHCP to pass the WAN IP address to the NetDuma R1 router. No configuration needed for most Cable ISP services. After the modem is bridged fully, the WAN IP address should appear on the R1 router if all is configured correctly. Test with a Lan wired PC directly to the NetDuma R1 router and test of internet connectivity. Users should contact their ISP providers for additional help and information if they need there modem/routers bridged when using an external router like the NetDuma R1. Some ISPs may not support bridging of modem/routers or the actual hardware may not be supporting of bridge mode. Additional Info: http://www.practicallynetworked.com/networking/fixing_double_nat.htm http://computer.howstuffworks.com/nat.htm 2) Configuring your Netduma (preferably Chrome or Firefox and AdBlock disabled) A) Verify the Netduma firmare version Make sure the Netduma version is the 1.03.06g or 1.03.06h (if you are a new user, you should already be on the latest version). If this is not the case, please post a message here: http://forum.netduma.com/topic/11018-major-netduma-upgrade-now-available-v-1036/ You can also post a topic in our section or ask for help here: http://forum.netduma.com/topic/19568-besoin-daide-pour-le-param%C3%A9trage-de-votre-netduma-cest-ici-que-%C3%A7a-se-passe/ Enable "Enable cookies" To ensure that the options set in your Netduma are backed up, make sure that the option is checked in the "Settings" tab and then "Miscellaneous". 3) Locate your console Your console may be recognized as an “unnamed device” by your Netduma in the connected devices list. To find it, turn on your console and go to the network settings. You can edit the host name of the console within its network settings so that the console appears on the R1s connected device list correctly for easier identification. Locate the IP address associated with your console and compare to the list of devices on the Device Manager page. After locating your equipment with the IP address (note this value, it will serve you later), you can rename it to facilitate your needs. 4) Configure host filtering Host filtering will allow you to delimit a geographical area that will limit the number of players that can connect to your host. You will now be connected to hosts with very low ping and therefore much more fluid gameplay. To set the host filtering on your console, click the Select service button. Choose your console then the service that will be associated with it (PSN, Xbox Live, ...). In the geo-filter section, click on the house icon and click on your geographical area again (you can use the magnifier icon and the zoom factor to delimit a zoom area on the map). Adjust the radius of the filter with the Filter by Distance bar according to your geographical area (800Km for Europe for example and more in less densely populated areas). The ping assist can be reduced to zero and you can activate the strict mode option if you are playing Call of Duty. 5) Configure congestion control This section will allow you to optimize your connection in order to cancel "latency and make the network flow of your gaming device a priority. In the Anti-Flood section, select the "Reactive" algorithm and then adjust both bars to 100%. Click on the "Set Bandwidth" button, you will now be able to enter information about your bandwidth. To best adjust these values, try a test at http://www.speedtest.net and retrieve the values. You can then type them and confirm by clicking on "Update Bandwidth". A pop up window appears, click "No". You can return to the previous window by clicking on the "Congestion Control" tab. Switch back your download and upload to 70%. Touch the Device Prioritization section only if you use a computer to stream your games. If so, locate your computer on the star and adjust the priority level for that device. For Hyper-traffic, click "Add New Hyper Service". Select your console then the service (which will be the same as you previously selected in the host filtering). 6) Configure DHCP Lease Here you will set up a reserved IP address for your console. Click the "Reserved" button and then enter the last number of the IP address you wrote down. Once this is set, your game console will always get the same IP address when it is turned on. It should never change. 7) Configure port forwarding You will be able to define rules and open the ports necessary for communication in your console, the associated system and the game for better fluidity. Here are the known ports to open: - PSN or XBOX Live TCP / UDP: 1024-65535 You will need to enter the IP address value associated with your console previously noted for each rule. (I leave you to find the ports to open according to your game if your console does not appear here (Wii, Nintendo Switch, ...). Then click "Apply" to confirm. 8) Disable UPNP Simply uncheck the Enabled option and click the "Apply" button (if the load is too long, click on the NetDuma button in the top left corner). 9) Configure the LAN & WAN part You can disable IPv6 by clicking "Disabled" and then "Apply". This should be disabled for users that do not have native IPv6 support from there ISP services. For experienced users: you can define a fixed MTU. To do this, disable the MTU auto by clicking "Disabled" and enter the desired value (1492 for ADSL, 1500 for a cable or fiber connection). Automatic is preferred is most cases. 10) Configure the Miscellaneous part Make sure the following options are checked: - Enable Cookies - Allow self-feedback (no personal data ever) to help improve the R1 - Allow Remote Access to NetDuma tech support 11) Configure your console We now will finish with the network configuration of your console. Launch a manual configuration et register the following informations: IP address: 192.168.88.X Network mask: Gateway: Primary DNS: Secondary DNS: Proxy (if available): no DHCP hostname: not specified For the beginners, use the automatic value for the MTU. For the experienced users, use the same value of MTU used previously. My topic is now finished. A big thanks to Mr. e38BimmerFN who translated the entire thread. I hope that will help you as well as possible and I remain at your disposal for any additional information. As mention above, do not hesitate to inform me of your remarks and suggestions: http://forum.netduma.com/topic/20728-the-best-settings-imo-for-the-10306-firmware-feedbacks-and-suggestions/ See you soon on the forum fellas **Pour la version française, cliquez ici: http://forum.netduma.com/topic/20615-si-vous-souhaitez-configurer-vous-m%C3%AAme-votre-netduma-ou-loptimiser-au-mieux-cest-ici/ **
  • Create New...