Not what i expected for Destiny

[Ellert]

I have a Nedduma since a bit over a week, and have used it for about 3 hours.

It is now back in its box, as i lack the will to spend more time on dicking around in the interface and restarting destiny for 600 times.

 

The issues are the following:

The interface is overwhelming and messy, and does not work very well on any browser under osx.

Destiny on PS4 craps out constantly, and if it does, it kicks me back to the loading screen. Something with doing a 'cloud update' has scrolled past in these forums, no idea what or how, or why, nor why it takes so long to insert a couple ip addresses in a central whitelist or have the router record the ip adresses it encounters. And YES i want it to do deep packet inspection if that will automate this.

The geoip filter is a charming idea, but not very usefull. I dont care where players are from, as long as they are not skipping around like laggy timelords.

Ping based filtering would be a lot more usefull, if it would work propperly.

-  the measured numeric pingtimes do not correspond with the graph

-  pingtimes should use a running average to prevent disnconnection after a spike, or have some threshold to retain them after an initial triage at first connect. It is not clear if and how this is done.

-  the bars in the graph change color all the time

-  there is no log of the actual ip's, nor a relation to the graph

-  there is no way to whitelist my laggy friends from closeby or the non-laggy friends that live on the other side of the earth.

-  i dont see any indication or measure of the devil of all ping problems: packetloss

 

And last but not least: a clear and not too hard to follow step by step instructional document or video of how to set things up and tune them for specific purposes (in my case: "how to set up the netduma if you have a provider-bound router that can not be disabled", and "the best settings for destiny") would somewhat compensate for the lack of a proper manual and the jumble of an interface.

 

[iAmMoDBoX]

http://support.netduma.com/support/solutions/folders/16000076077

[ColonicBoom]

 

The interface is overwhelming and messy, and does not work very well on any browser under osx.

 

Destiny on PS4 craps out constantly.

 

have the router record the ip adresses it encounters.

 

The geoip filter is a charming idea, but not very usefull. I dont care where players are from, as long as they are not skipping around like laggy timelords.

Ping based filtering would be a lot more usefull, if it would work propperly.

 

the measured numeric pingtimes do not correspond with the graph

 

pingtimes should use a running average to prevent disnconnection after a spike, or have some threshold to retain them after an initial triage at first connect. It is not clear if and how this is done.

 

the bars in the graph change color all the time

 

there is no log of the actual ip's, nor a relation to the graph

 

there is no way to whitelist my laggy friends from closeby or the non-laggy friends that live on the other side of the earth

 

i dont see any indication or measure of the devil of all ping problems: packetloss

 

And last but not least: a clear and not too hard to follow step by step instructional document or video of how to set things up and tune them for specific purposes (in my case: "how to set up the netduma if you have a provider-bound router that can not be disabled", and "the best settings for destiny") would somewhat compensate for the lack of a proper manual and the jumble of an interface.

 

 

I think the interface is pretty clear and obvious compared to the majority of routers.

And it works perfectly well on Mac, perhaps you need to update your OS or your browsers. We recommend that you use Chrome but I don't remember having any problems using Safari when I've logged in there on autopilot a few times.

 

I can't comment on Destiny or PS4 as I own neither.

 

We can't have it recording IPs because of naughty people that like to DDOS. Servers come and go so the IDs are constantly being updated. And IPs often change too.

 

The Geo filter radius exists so that people can filter based on location, if you'd rather search by ping alone then set your home in the ocean and set a Ping Assist value of your base ping (to something big, Google, Twitter, etc) + 20ms approx.

 

Which graph are you talking about, ping to host? It's simply a graphical representation of the numbers, so you can easily see spikes without having to watch the number the whole time. But mine seems to correspond. Or do you mean that it doesn't correspond to a ping shown in-game? These in-game numbers are usually slightly higher because of some kind of processing / turnaround on the other side.

 

Not really sure what you mean about 'ping time running average'. Are you talking about the game servers kicking you out because you have a spike?

 

The bars in peer-ping change colour? I've never paid much attention to the colours to be honest but they are different colours to separate them from one another, it doesn't really matter what colour they are. I think they have further uses for gamers on PC but I'm on console so I rarely look at peer-ping myself.

 

There's no log of the IPs for security reasons, DDOS, etc. And there's no relation to the graph on console at the moment.

 

You whitelist your friends by setting them to 100% (or anywhere in the green) on the Allow/Deny sliders. The easiest way to know who's who is to invite them to a private game, one at a time, and name them. If they have a dynamic IP then they will need to be re-added whenever their IP changes.

 

There is no measure of packet loss when you're gaming. You can run the diagnostics and it will tell you if it detects packet loss but you cannot do this when you are gaming because it will lock down your internet briefly while it tests. It's only a snapshot of your internet health though, if you think you have problems with your line then you should either download some third-party software (I use Ping Plotter) or use your 'command line' / 'terminal' on your computer.

If you have packet loss then you need to find out why and get it resolved.

 

It's not really possible to provide step-by-step instructions on how to set up with every different make/model of ISP-provided hub/router, there are hundreds of them.

The interface is not jumbled, it's simple.

 

If you would like some help to set up with your specific equipment then you will need to provide details of your equipment.

If you have a specific problem then you will need to detail the problem, your equipment and your settings and then we will be able to help.

[Chive972]

I have a Nedduma since a bit over a week, and have used it for about 3 hours.

It is now back in its box, as i lack the will to spend more time on dicking around in the interface and restarting destiny for 600 times.

 

The issues are the following:

The interface is overwhelming and messy, and does not work very well on any browser under osx.

Destiny on PS4 craps out constantly, and if it does, it kicks me back to the loading screen. Something with doing a 'cloud update' has scrolled past in these forums, no idea what or how, or why, nor why it takes so long to insert a couple ip addresses in a central whitelist or have the router record the ip adresses it encounters. And YES i want it to do deep packet inspection if that will automate this.

The geoip filter is a charming idea, but not very usefull. I dont care where players are from, as long as they are not skipping around like laggy timelords.

Ping based filtering would be a lot more usefull, if it would work propperly.

-  the measured numeric pingtimes do not correspond with the graph

-  pingtimes should use a running average to prevent disnconnection after a spike, or have some threshold to retain them after an initial triage at first connect. It is not clear if and how this is done.

-  the bars in the graph change color all the time

-  there is no log of the actual ip's, nor a relation to the graph

-  there is no way to whitelist my laggy friends from closeby or the non-laggy friends that live on the other side of the earth.

-  i dont see any indication or measure of the devil of all ping problems: packetloss

 

And last but not least: a clear and not too hard to follow step by step instructional document or video of how to set things up and tune them for specific purposes (in my case: "how to set up the netduma if you have a provider-bound router that can not be disabled", and "the best settings for destiny") would somewhat compensate for the lack of a proper manual and the jumble of an interface.

Hi mate,

 

let me show you how i works

 

Install Teamviewer on your MAC and send me the ID/password in PM.

You won't be disappointed.

[Netduma Fraser]

Hey, welcome to the forum!

 

Colonic has answered your post very well. In regards to Destiny cloud they seem to update the way matchmaking works with every update. Disable auto & bleeding edge cloud in miscellaneous settings and use manual numbers 33, 30 & 28. Some are reporting they're still getting booted so I'll do another as soon as I can. I would definitely take up Chive's kind offer to go through it with you as it should alleviate your concerns. Thank you for the feedback as well.

[antithesis]

Netduma works really well with Destiny, once you nail down a few settings.

 

First and foremost, disable Strict Mode in Geo-filter. That's likely why you're getting kicked from Destiny lobbies. Turn it off, problem should resolve.

 

Geo-filter with Ping Assist set to 0ms works as a surrogate Ping filter based on the distance of peers to you. Obviously, the closer the peer, the lower the ping will be, in most cases (they can still have a crappy connection). Set your distance lower if you notice red bars. Some will still get through if partied up with a friend inside the geo-filter, but otherwise it should be a clean lobby, which helps everyone.

 

Be sure to setup your Services at the top of Geo-filter and a Hyper-Traffic tunnel in Congestion Control. Leave the Distribution chart to default, but tick "Share excess".

 

Make sure you've got appropriate Up / Down bandwidth limits set in Device Manager, and adjust Settings > Misc to match your connection type, as per the wiki.

 

Head to dslreports.com and run the Speed Test. Based on the results, tweak Congestion Control > Upload Cap and Download Cap up and down until the DSL Reports results show A or A+ across the board. Line Speed is the least important stat, so don't be afraid to dial it down. Mine sits at about 80% Down and 60% Up. Note that I only use these settings while gaming. I don't use them myself, but you can use Profiles to make it easier to swap between gaming mode and general use modes.

 

I'm a Mac user and the UI works fine in all browsers. As recommended, try Chrome, but it also works in Safari, Firefox, Opera etc.

 

Many of us have made the same suggestions to improve the ping and map in Geo-filter to make it easier to correlate one with the other. Hopefully they're coming down the pipe in Netduma OS as that'll make filtering out red bars significantly easier.

 

You can identify and whitelist friends by partying up in chat or in Destiny before entering the Crucible, then using Geo-filter > Deny and Allow to whitelist their connections. Whilst IP addresses are not revealed in Netduma for privacy reasons (it'd make a DDoS attack on a peer very easy), you can easily locate your friends on the map while partied up. Given the map markers should match the number of peeps in your party before jumping into a multi-player lobby, this should be a walk in the park.

 

Once you get the settings bedded down, your friends and peers will thank you for it. I have a mate who lives 1000 kms away here in Oz who likes to party up with me because the Geo-filter gets rid of the red bar rabble and makes our shots crispy. We also identified a couple of other friends who would wreck our connections due to lag compensation, so we blocked them in the Duma

[Ellert]

Sorry, have been away for a bit. Work and stuff.

Anyway, thank you Chive, i might take you up on that, after i get something sorted first: my network layout.

I have attached my current setup and 3 proposed ways to fit in the Duma.

I obviously tried A first.

 

Some observations:

- The scanner/printer has wifi so can be disconnected from the wired network.

- the server in the basement MUST be reachable over 2 ports (i put 1 in the diagram but i just checked, 2 ports) and has a fixed internal ip.

- The shitty Fritzbox (god i despise that thing) can not be taken out, there is no way to fully replace that box with the Duma (can not log in onto the providers (xs4all) network and will not have phone). Also i do not believe it can be put into DMZ mode, so quite out of luck here, double NAT seems to be unavoidable.

- For option C i will have to pull an extra cable.

 

Any suggestions?

 

[iAmMoDBoX]

Sorry, have been away for a bit. Work and stuff.

Anyway, thank you Chive, i might take you up on that, after i get something sorted first: my network layout.

I have attached my current setup and 3 proposed ways to fit in the Duma.

I obviously tried A first.

 

Some observations:

- The scanner/printer has wifi so can be disconnected from the wired network.

- the server in the basement MUST be reachable over 2 ports (i put 1 in the diagram but i just checked, 2 ports) and has a fixed internal ip.

- The shitty Fritzbox (god i despise that thing) can not be taken out, there is no way to fully replace that box with the Duma (can not log in onto the providers (xs4all) network and will not have phone). Also i do not believe it can be put into DMZ mode, so quite out of luck here, double NAT seems to be unavoidable.

- For option C i will have to pull an extra cable.

 

Any suggestions?

 

 

B

[Netduma Fraser]

I would agree with MoD

[Ellert]

Note that in setup B the PS4 is not connected directly to the Duma, so is basically the most possible hops away from the outside.

Having the switch between the PS4 and the Duma like this will not hurt performance/ping ? I am unsure.

 

Hm, thought of a 3rd way to hook it up, with the essential stuff directly on the duma.

I will need to pull 2 cables instead of just one, but that is quite possible.

 

[Netduma Fraser]

As long as devices are connected behind the Netduma it can control it. Any possible ping increase would be minute - as in not worth worrying about at all. 

[Ellert]

okay, clear answer, thank you.

[Ellert]

hooked everything up as suggested, it was playable for a while, but now getting 'beavered' all the time.

[Netduma Fraser]

Manually select the cloud numbers and choose the last ones available. They're more up to date than the ones I mentioned previously in this post.

[Ellert]

Do you mean to select the last numbers in the drop boxes at Settings -> Misc settings -> Cloud Settings after disabling the 'auto cloud' checkbox ?

Those numbers are 35, 32 and 28.

 

If so, no difference. in fact, if anything, it got worse.

[Netduma Jack]

Do you mean to select the last numbers in the drop boxes at Settings -> Misc settings -> Cloud Settings after disabling the 'auto cloud' checkbox ?

Those numbers are 35, 32 and 28.

 

If so, no difference. in fact, if anything, it got worse.

 

Yes that's how you change the cloud version. Destiny is ongoing at the minute since they changed up their servers recently, we're upgrading the cloud a lot to incorporate their changes.

 

The latest cloud version is now 35, 33, 28. If you get kicked at all, look on your Geo-filter map and click on any 'padlock' icons you see. If you could provide us with the ID's of those servers here we can check if they need to be added to the cloud.

[Ellert]

How do i make it that i can select 33 in the middle dropbox? It goes from 1 to 32.

[Netduma Jack]

How do i make it that i can select 33 in the middle dropbox? It goes from 1 to 32.

 

Ah okay, I just asked Fraser and he's not yet released 33. The last numbers on the list are the latest. Please let us know how you get on with that version, though bear in mind it's still a work in progress. Auto-Cloud can be more stable, especially in other games like Call of Duty.