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

nasc: Add SVCLOC and nzchk documentation #19

Merged
merged 2 commits into from
Feb 9, 2024

Conversation

DaniElectra
Copy link
Member

NASC behaves similarly to the NAS/NASWII servers, so some information has been extracted from existing docs of those servers.

Special thanks to:

NASC behaves similarly to the NAS/NASWII servers, so some information
has been extracted from existing docs of those servers.

Special thanks to:
- https://github.com/WiiLink24/wfc-server/blob/main/nas/auth.go
- https://wiki.tockdom.com/wiki/Network_Protocol/Server#naswii.nintendowifi.net
@jonbarrow
Copy link
Member

NASC behaves similarly to the NAS/NASWII servers

IIRC it's the exact same server (not the same physical server, but the same codebase). NASC stands for NAS-CTR

@DaniElectra
Copy link
Member Author

Yeah that makes sense. Should I change this phrasing then?

This is the authentication server of the 3DS. It is the succesor of the NAS and NASWII servers on the Nintendo DS(i) and the Wii.

@jonbarrow
Copy link
Member

Yeah that makes sense. Should I change this phrasing then?

This is the authentication server of the 3DS. It is the succesor of the NAS and NASWII servers on the Nintendo DS(i) and the Wii.

I would, yeah. It's also worth noting that this section:

A single endpoint (ac) is used for all requests. Other requests are redirected to http://www.nintendo.com.

Is also wrong. While games may officially only use /ac, other endpoints used by the Wii/DS do still exist and still work (at least partially)

For example the /pr endpoint, which checks for profanity, gives a proper response in NASC, and can be interacted with by making a custom request in NintendoClients

Screenshot from 2024-02-09 11-01-03

@DaniElectra
Copy link
Member Author

For example the /pr endpoint, which checks for profanity, gives a proper response in NASC

oh! I had only tested the /download endpoint which didn't work, so I didn't try others

@jonbarrow
Copy link
Member

oh! I had only tested the /download endpoint which didn't work, so I didn't try others

I can't actually get it to give me a response that makes sense, but it at least gives a response. Base on WiiLink it seems like there should be a 0 for every word, delimited by \t. But when I try sending multiple words I always just get back a single 0, even if it contains profanity

@DaniElectra
Copy link
Member Author

I can't actually get it to give me a response that makes sense, but it at least gives a response. Base on WiiLink it seems like there should be a 0 for every word, delimited by \t. But when I try sending multiple words I always just get back a single 0, even if it contains profanity

I tested with the NAS and NASWII domains and it gives the same results. I sent a message on the WiiLink discord server to see if I can get an answer about this

@DaniElectra
Copy link
Member Author

I think this should be good now then

@jonbarrow
Copy link
Member

lgtm

@jonbarrow jonbarrow merged commit 64cfd25 into PretendoNetwork:master Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants