Closed dogty closed 2 years ago
There are things that need to be reviewed in my opinion I had feedbacks of people having trouble joining rooms or even seeing one (even though they were connected on the website) when 14.1.0 came out (no problem was seen in 14.0.0). When I looked at the logs getdisconnectreason was called a lot of times. Lan-play also seems to behave differently. I would have loved to debug more but I need two Switch in order to debug properly. I can give you the debug files I've recorded if you want.
It seems that the actions configuration needs to be updated, let me debug it
Out of curiosity where do you get the updated information on how you should set the action configurations? Where do you get the information on how a specific interface works?
A1:
https://github.com/spacemeowx2/devkitpro-action/tree/v2
Just compile it using act, and fix it by error message..Such as update libnx and toolchain.
A2: By reverse engineering the ldn service or a specific game with symbols(as far as I know, the first version of Diablo 3 leaked the elf file with symbols), it is possible to infer how the interface works
My mistake Ive already updated the actions configuration by fotking your actions you can check my fork if you want.
I was more interested in the re of the interfaces
The reverse part of the job is very boring... One thing I didn't mention is that when I first started writing ldn_mitm, I would use mitm to record the bare bytes of ipc, and then parse it manually....
Simply put, it's a cycle of error, restart, modify, update, and error again
That's what I started doing I thought there was maybe some kind of documentation the only thing I found was that https://github.com/kinnay/NintendoClients/wiki/LDN-Protocol#advertisement-frame it gave me a good starting point but I thought there was something else. Thank you!
https://switchbrew.org/wiki/LDN_services#Network_protocol
Look here too, although you may have already seen it
Yes I have but thank you!
Thanks, will try it later