This repository has been archived by the owner on Sep 21, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 108
Multiple consoles connected to PegaSwitch #41
Labels
Comments
I'll start tackling this. Will it be a concern to use serial number in an identifiable way? I could see this being useful for someone mounting on the Internet and anyone being able to set their DNS to the given IP without needing to understand pega. I'm not sure if that is the intent of this feature though. |
We already run a public DNS which blocks Nintendo updates/error reporting. You should never ever expose your Pegaswitch instance to the internet :) |
@SomeoneWeird it seems the feature is more for people wanting to run things against multiple consoles at one time without having to do crazy things |
Yes, I know, I was responding to the second paragraph in your previous comment where you alluded to running pegaswitch on the internet :) |
misson20000
added a commit
that referenced
this issue
Oct 27, 2017
misson20000
added a commit
that referenced
this issue
Oct 30, 2017
initial support for multiple consoles (closing #41)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think it'd be cool to be able to connect multiple Switches to PegaSwitch at once. Give each one a name, include it in the prompt, and have a command to change which console is "active". This requires some method of uniquely identifying the console, assigning a name, and keeping track of these assignments. set:sys#68 GetSerialNumber() might be a good choice for the unique ID.
The text was updated successfully, but these errors were encountered: