Saint-14 Posted August 4, 2020 Share Posted August 4, 2020 On 7/1/2020 at 6:48 PM, Netduma Fraser said: I've not heard anything from Alex on this so if he's not able to do so by Friday I will try to do it myself on the weekend and see what is happening. nothing new in over a month now, is Destiny 2 now a forgotten game on PC? any are you simply not able to give us the features we previously had prior to the changes steam/bungie made to the game? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 4, 2020 Administrators Share Posted August 4, 2020 No we certainly haven't forgotten it, I think the latest was that we needed to do something different for Destiny and we had a few ideas on how to do that but it requires more work/investigation than anticipated as it won't just be a cloud update. Link to comment Share on other sites More sharing options...
tiger Posted August 31, 2020 Share Posted August 31, 2020 Hi everyone! I been trying to figure out how to prevent random players connect to me during matchmaking. To do so on PS4 you just need to drop all forward-chain traffic on udp-port 3074 except traffic from player's ip-addresses that need to be able to join your session. Before Destiny 2 PC moved to "Steam Networking Sockets" we were able to do same on PC but using udp-port 3097. That's super easy. But when we trying to do the same on PC now - there's no result. Well I've start to dig deeper. And here's what I found. After Destiny 2.8.0 release the only way to figure out ip-address from which player connecting to your session is to look deep into network packets. What to look for? SteamID64 (17-digit string)! For example, I know my friend's SteamID64. When he join my fireteam, I see packets which contain following string "steamid:xxxxxxxxxxxxxxxxx" (SteamID64 of my friend). Let's call it "THE RIGHT ONES" packets. Those packets flowting throught random udp-ports in range 27000-27100. I can see ip-addresses those packets came from. But at the same time there is packets with different steamid-string (not my friend's SteamID64), but came from same ip-addresses using other udp-ports in range 27000-27100. Droping forward-chain traffic on every udp-ports in range 27000-27100 will result nobody could join my session (and I'm also unable to join anybody - "solo-mode"). But droping forward-chain traffic on every udp-ports in range 27000-27100 except those ports which "THE RIGHT ONES" came from gives no results - everybody can join my session. So I'm stuck(( My aim is to make kind of white-list of users that can join my session. Have no idea, how to make it now after that update of Destiny 2. P.S. I'm using RouterOS Link to comment Share on other sites More sharing options...
Cristiano GG Posted September 11, 2020 Share Posted September 11, 2020 Qualcuno sa perché la lista delle persone corrispondenti è scomparsa? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted September 11, 2020 Administrators Share Posted September 11, 2020 9 hours ago, Cristiano GG said: Qualcuno sa perché la lista delle persone corrispondenti è scomparsa? Ciao, benvenuto nel forum! Scusa, non capisco la traduzione, potresti chiarire per favore? - Hello, welcome to the forum! Sorry I do not understand the translation, could you clarify please? Link to comment Share on other sites More sharing options...
Saint-14 Posted September 12, 2020 Share Posted September 12, 2020 Any news on this? the silence regarding this issue is deafening tbh There are many people that have purchased these routers just for Destiny on PC and now we are all left with expensive door stops. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted September 12, 2020 Administrators Share Posted September 12, 2020 5 hours ago, Saint-14 said: Any news on this? the silence regarding this issue is deafening tbh There are many people that have purchased these routers just for Destiny on PC and now we are all left with expensive door stops. The latest update is that we will have to actually do research and potentially implement some changes in order to allow it to work and this will take some time. Link to comment Share on other sites More sharing options...
Stobbee Posted October 12, 2020 Share Posted October 12, 2020 Hello guys! Still wondering if there will be a fix for this issue. It has been a lot of months now and duma os 3.0 is already out, could you please focus on this? There are a lot of people playing this game that would like to know if there will ever be a fix. Link to comment Share on other sites More sharing options...
Saint-14 Posted October 12, 2020 Share Posted October 12, 2020 54 minutes ago, Stobbart said: Hello guys! Still wondering if there will be a fix for this issue. It has been a lot of months now and duma os 3.0 is already out, could you please focus on this? There are a lot of people playing this game that would like to know if there will ever be a fix. To be frank I honestly feel that they have done NOTHING to even see if anything can be done, let's face it the support for the routers we paid hundreds for is none existant at this point. Personally I am very annoyed as I paid all this money solely due to it's Destiny 2 capabilities and to see them seem to not do a damn thing once things changed on Steam is frustrating to say the least. Prove me wrong NetDuma Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted October 13, 2020 Administrators Share Posted October 13, 2020 As I mentioned previously, this isn't something we can fix in a simple cloud update. This issue requires quite a lot of investigation and clever solutions that would need to be made, it is far from simple, that is why it will take some time. I know it is frustrating but it's not a process we can really speed up. Link to comment Share on other sites More sharing options...
Saint-14 Posted October 13, 2020 Share Posted October 13, 2020 3 hours ago, Netduma Fraser said: As I mentioned previously, this isn't something we can fix in a simple cloud update. This issue requires quite a lot of investigation and clever solutions that would need to be made, it is far from simple, that is why it will take some time. I know it is frustrating but it's not a process we can really speed up. It has been 7 months how long do you need? Link to comment Share on other sites More sharing options...
Stobbee Posted November 5, 2020 Share Posted November 5, 2020 Guys I don't want to bother you but do we have to accept once for all that geo filter on D2 will never work again? It's just to know, so we'll not ask for this anymore in the future. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted November 5, 2020 Administrators Share Posted November 5, 2020 14 hours ago, Stobbart said: Guys I don't want to bother you but do we have to accept once for all that geo filter on D2 will never work again? It's just to know, so we'll not ask for this anymore in the future. No I don't believe so. We've had reports that it is actually working on particular DumaOS routers on specific versions so we're investigating that at the moment. If that is the case and we can figure out why then that will allow us to get it supported again quicker than previously thought. Link to comment Share on other sites More sharing options...
Stobbee Posted November 5, 2020 Share Posted November 5, 2020 It is working in the wrong way! The player and servers position is not right. It shows my friends in italy outside, somewhere in Europe Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted November 5, 2020 Administrators Share Posted November 5, 2020 59 minutes ago, Stobbart said: It is working in the wrong way! The player and servers position is not right. It shows my friends in italy outside, somewhere in Europe That's nothing to do with Destiny, that's to do with IP location which can be inaccurate, add them to your allow list and you'll be able to connect to them regardless. Link to comment Share on other sites More sharing options...
Stobbee Posted November 5, 2020 Share Posted November 5, 2020 isn't it because of steam hiding their ips and showing them somewhere else?? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted November 5, 2020 Administrators Share Posted November 5, 2020 I was referring to the friends but the servers yes quite possibly, I'm not the one testing it so I can't be sure on that front. Link to comment Share on other sites More sharing options...
Saint-14 Posted November 8, 2020 Share Posted November 8, 2020 On 11/5/2020 at 6:09 PM, Netduma Fraser said: I was referring to the friends but the servers yes quite possibly, I'm not the one testing it so I can't be sure on that front. Could I ask that you perhaps get an update from whomever is supposed to be doing the "testing" and let all the paying customers here know what kind of progress if any has been made? Thanks in advance Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted November 8, 2020 Administrators Share Posted November 8, 2020 1 hour ago, Saint-14 said: Could I ask that you perhaps get an update from whomever is supposed to be doing the "testing" and let all the paying customers here know what kind of progress if any has been made? Thanks in advance I will chase again. Link to comment Share on other sites More sharing options...
Saint-14 Posted November 9, 2020 Share Posted November 9, 2020 22 hours ago, Netduma Fraser said: I will chase again. Thank you Link to comment Share on other sites More sharing options...
lunafaction Posted December 9, 2020 Share Posted December 9, 2020 On 11/5/2020 at 3:48 PM, Netduma Fraser said: No I don't believe so. We've had reports that it is actually working on particular DumaOS routers on specific versions so we're investigating that at the moment. If that is the case and we can figure out why then that will allow us to get it supported again quicker than previously thought. Could you state which specific router and version has reported as working? As an update to this, Destiny 2 have now stated that all consoles will be given the same DDOS protection as PC in 2 months time and so the Geo Filter for console will also lose all functionality too. I made a post in regards to the geo filter no longer working on PC back in March and then 4 months later after what seemed to be stalling and lip service, we were told "After digging into it more, there is no way around it at the moment unfortunately. We will keep trying but it doesn't look possible right now." The tone of this thread is quite vitriolic as it is and I don't want to add to that, but it has been 9 months now since we lost the core functionality of the router and all that ever seems to be said is that it will be investigated or "chased up" but nothing ever really comes from it. It would be much more palatable to just be told that Destiny 2 has lost functionality and it will not be worked on to restore those features. Ideally though it would be nice to have an update directly from the person testing this (if they exist) and to be told the likelihood of the Geo Filter working again in the future, even if the answer is 0% chance. I think this is important now more than ever, considering consoles are about to lose functionality too. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted December 9, 2020 Administrators Share Posted December 9, 2020 I've been told that the XR700 and old versions of the R1 work but I haven't been able to verify this myself. I totally understand, I've asked @Netduma Alex to post when he can about the current state of Destiny 2 compatibility. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted December 10, 2020 Administrators Share Posted December 10, 2020 If you change your device to the PlayStation device type and add it to the Geo-Filter and choose the manual option does it work then? Link to comment Share on other sites More sharing options...
Saint-14 Posted December 10, 2020 Share Posted December 10, 2020 54 minutes ago, Netduma Fraser said: If you change your device to the PlayStation device type and add it to the Geo-Filter and choose the manual option does it work then? Tested this using a very early R1 with FW 2.1.3.29 Even though it shows triangles on the geo-filter it still connects to them and I load in with a full tower of random people, (this was with a 69 miile radious home circle in the midle of the ocean) Not 100% sure what you meant about "choose the manual option" because once I select the device it just adds it it does not ask me anything else. Can you confirm what fw version I should be using for these tests? Could you take a look at this PC app that was developed in order to block out unwanted people from your destiny sessions https://github.com/DrNoLife/Destiny-2-Solo-Enabler you can download the latest version here https://github.com/DrNoLife/Destiny-2-Solo-Enabler/releases/ perhaps this would be able to be implemented so that these routers do not become obsolete for all the Destiny solo players I look forward to hearing back hopefully sooner rather than later Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted December 10, 2020 Administrators Share Posted December 10, 2020 So you were using Ping Assist? I wouldn't recommend it for Destiny. You would have connected to a server which is why people would have connected as they would have connected to the server and then to you. If you try in the crucible, using normal radius over your location, no PA does it work? If you could use the R1 3.0 beta just to make sure that would be great. Thanks we'll take a look at those if we can't get this sorted. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.