Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should autoconfigure hosts for Infrastructure #19848

Open
hrydgard opened this issue Jan 10, 2025 · 4 comments
Open

Should autoconfigure hosts for Infrastructure #19848

hrydgard opened this issue Jan 10, 2025 · 4 comments

Comments

@hrydgard
Copy link
Owner

hrydgard commented Jan 10, 2025

We already have a built-in mechanism for remapping domains (see #19841), so there's no reason people should have to configure this manually. I want to make it a built-in list auto-updated from ppsspp.org.

Let's collect all the hosts settings needed for various games:

MOHH:

86.223.243.173 pspmoh07.ea.com
86.223.243.173 pspmoh08.ea.com
86.223.243.173 tos.ea.com

DNS: 86.223.243.173   (server also works as DNS)

SOCOM:

67.222.156.250 socomftb2.psp.online.scea.com
67.222.156.250 socompsp-prod.muis.pdonline.scea.com

Twisted Metal:

67.222.156.251   tmheadonpsp-prod.pdonline.scea.com

WipEout Pulse:

145.239.30.230 wipeoutpulse.online.scee.com
145.239.30.230 wipeoutpulse.muis.online.scee.com

Motorstorm: Arctic Edge/Motorstorm: Raging Ice:

145.239.30.230 motorstormpsp.muis.online.scee.com

Actually, with #19858 , all we need to do is configure the DNS per game.

So maybe something like (in JSON, just because, and designed for maintainability):

{
    "default": {
         "dns": "67.222.156.251",
    }
    "MOHH": {
        "ids": ["NPJH12345", "NPJH53155"],
        "dns": "142.24.13.25",
        "incompatible": ["Windows"],
    },
    "Wipeout Pulse": {
        "ids": [],
    },
    "etc",
}
@hrydgard hrydgard changed the title Should autoconfigure hosts for Should autoconfigure hosts for Infrastructure Jan 10, 2025
@hrydgard
Copy link
Owner Author

Interesting document:

https://docs.google.com/document/d/1B2BTbs2srlZ32SN8XVpqIm68_0oI4QOYshJvG0npXr0/edit?tab=t.0

I still don't understand whether we need to provide these, or if the "Primary DNS" that we use (67.222.156.250 ) is taking care of many of them.

@hrydgard
Copy link
Owner Author

hrydgard commented Jan 10, 2025

Ah, it seems we just tell the games about the configured primary DNS but we don't actually make use of it, from what I can tell. So what we really should do is make our own DNS queries to the specified DNS when a game calls sceNetInetInetAddr (the psp equivalent of getaddrinfo).

@ChaCheeChoo
Copy link

ChaCheeChoo commented Jan 10, 2025

while both games work both on DNS 145.239.30.230 and DNS 67.222.156.250 (via them redirecting the games to 145.239.30.230) for completeness sake:

WipEout Pulse:
145.239.30.230 wipeoutpulse.online.scee.com
145.239.30.230 wipeoutpulse.muis.online.scee.com

Motorstorm: Arctic Edge/Motorstorm: Raging Ice:
145.239.30.230 motorstormpsp.muis.online.scee.com

@hrydgard
Copy link
Owner Author

Alright, so I think the current plan is to have a mapping game id -> dns server on a JSON file on the server, and use the DNS to manually look up the urls. That way we won't need to list redirects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants