unixadmin

Please forward this link to your engineer, it explains the architecture: https://partner.steamgames.com/doc/features/multiplayer/steamdatagramrelay

No I'm not using the router "wrong". Why does "turbo mode" exist and it disables congestion control when used? Because processor can't handle that much bandwidth and shaping at the same time. That is fact, see the manual. Interface becoming slow happens much sooner than pushing turbo mode amounts of bandwidth, past 20Mbit/s it already slows down. That is all.

...and the answer is simple. Netduma hardware is too weak to do everything it's trying to do, they tried to keep the manufacturing costs down to a minimum. The product should have been based on higher performance mikrotik instead of the one it is. It only takes me to use about 20Mbit/s (meh) of bandwidth for the netduma interface to become unresponsive. Especially the Congestion Control menu, it is the worst, takes minutes to get a response. See, when you look at a menu like Congestion Control the httpd service on the router runs a bunch of scripts to gather information from the system and these scripts take ages to run, return the information, and the httpd then takes the results and displays them on the page as graphs, progress bars etc. When this process of gathering and presenting this information is that slow it is a sign that the router is spending most of its hardware resources handling the network traffic passing through the router (shaping it, prioritizing, looking up geo information, manipulating the firewall...).

Cabbage errors continue all day every day. Destiny 2 is NOT a supported game.

Constant "bat" and "cabagge" errors when connecting to Destiny 2 Crucible accompanied with padlock icons on the world map. Even though strict mode is OFF. It's been going on since Destiny 1 Rise Of Iron DLC, full year now. Fixes are never delivered because: "new Duma OS will fix everything", except new DumaOS didn't fix anything as it doesn't exist. Are we ever going to have fully working Destiny support again?

No, I know I did not buy such a product. But in making a custom frontend to system services I wish such frontends exposed more (not necessarily *all*) of the configuration settings for those services. Let's take PPPoE support in current Netduma firmware. It only exposes two settings: username and password, that's it, yet the pppoe client has dozens of other settings that are not exposed in the interface. I was unlucky to have great problems with PPPoE. There are ppoe client settings for more intelligent handling of timeouts and reconnecting to the provider that could have helped me, but I could not make use of them in any way. Now I can't use PPPoE and am forced to double NAT which is stupid. sysctl.d snippets in the same way are an interface to the kernel, more relevant to the networking stack of the kernel. Combined with a frontend to ethtool (this alone would be great too) we could experiment with settings that other routers recommend to their gamers.

Yes when dumbing down the interface please don't forget your advanced users (and those that will become advanced users in due time). Have an "unhide" button that can expose the hidden/advanced settings, and in fact expose more of the system compared to the current interface. If nothing else there is one way for you to expose a thousand tunables just by providing a single text field, a text field that overwrites /etc/sysctl.d/99-customer.conf with its contents.

They missed "fall 2016" deadline by 9 months. OK that in it self is not a problem. But they used that fall release as justification for not working on existing firmware, because all those improvements will supposedly be in the new firmware. But now the new firmware is nowhere to be seen, and state of old firmware is making many users unhappy.

Why is a mobile app needed when phones have browsers? I use geofilter with the touchscreen all the time. One problem I have with the mobile browser is that the "legend" covers too much of the map, so I have to untick "Show Legend".

When I get a party invite (outside my radius) I click on the Enable checkbox for the Host Filtering (to disable it, of course). Then I join the party, and tick the Enable checkbox again. When party is joined connections for the voice are established, and Netduma will not block/break-off existing connections when I re-enable the Host Filtering.

That's why you always over-estimate and when you nail it before that date you look like a hero. If you happen to screw it up you are still arriving "on time". Netduma devs shot them selves in the foot trying to generate marketing on twitter with fake "Fall release".

You can only control what goes out of your network, you have absolutely no control over what comes in.

The way I see it you buy Netduma first and foremost for the GeoIP filter. It is going to get you into a regional multiplayer match, despite idiotic matchmaking algorithms trying to force international matches (like the pathetic ones Bungie develops), but from there on it has no further influence. Maybe you are playing your very neighbour in a regional match thanks to Netduma, but Netduma can't influence the fact they choose to play over wi-fi and install their wi-fi router next to a microwave that drops packets every time his girlfriend heats up a piece of chicken. Second item of value is the anti-jitter which provides a stable ping during heavy local network congestion. That's it, all it is, and nobody should expect old or new version of anti-jitter to somehow magically fix noisy DSL lines and climb poles to replace old cables.

Bungie uses Activision's company DemonWare as their service provider for matchmaking servers (and it has long been my belief for their matchmaking software, which is why they need 6 months to get an adjustment made to the algorithms but I digress). Not much is known about their services. Some information trickled from Call Of Duty over the years... for example how they attempt to match players that have different NAT levels together. Maybe when this happens the 3 players on a server in SC datacenter were closed NAT players being tunneled through there. (There are also such servers in London, Ireland (DemonWare's home), Japan... and some other places I've noticed over time.)

I use Host Filtering, Hyper-Lane, Port Forwarding (5 ports above 65000) and UPnP all at the same time on v1.03.6h. Uptime is some 2 months now without any slowing down of the interface. There is one exception to this and it's the Host Filtering page which is slow because drawing the map is bound to a single CPU core. My system has no hardware acceleration available to let the graphics card handle it and even if your Windows does have it if you use Firefox you could still see worse performance than with another browser. Enabling the "Low Resolution Map" feature helps, it's the browser that's slow not Neduma here. Games like Destiny and CoD claim 30 or more ports have to be forwarded for them to "work properly". Maybe Netduma slowing down on pages other than Host Filtering is proportionate to the number of forwarded ports? Only 5 ports on mine don't seem to have any impact, but I never tried adding >30 forwarding rules.