Has been reports of the public PegaScape site suffering crashes and been offline, so I decided to create a Step by step tutorial about building the Pegascape Source and running it on Self Hosted mode.

If you need to run pegascape on a Ubuntu Machine, open a Terminal window and run the commands:

you need Python 2 on the system, so installed python2 and created an alias to python

sudo apt update
sudo apt install python2
alias python=/usr/bin/python2

Using the recommendation of @xradeon , installed the node and npm, 9.11.2 & 5.6.0 versions respectively (https://gbatemp.net/threads/pegascape-alternative.650182/post-10372685)

You need some base packages installed, curl to download the specific NPM version script, git to clone the repo, make and g++ to build the source

sudo apt install curl git make g++

In order to use a specific NPM version, I followed the instructions on https://stackoverflow.com/questions...l-a-specific-version-of-node-on-ubuntu-debian (Answer 56):

cd ~
curl https://raw.githubusercontent.com/creationix/nvm/master/install.sh | bash
source ~/.nvm/nvm.sh
nvm install 9.11.2
node --version
npm --version

As instructed by the README.MD on the original repo: https://github.com/noahc3/PegaScape#self-hosting
after install NodeJS & NPM, executed the next commands to clone the repo and build using NPM:

cd ~
git clone https://www.github.com/noahc3/PegaScape
cd ~/PegaScape/
npm install

on my system systemd-resolved was running so I had to stop it to be able to run integrated DNS

sudo systemctl stop systemd-resolved

As we are using a specific version of NPN which is installed for the user not system wide, if you use the command sudo node you get the "command not found" error

so you need to execute it with full path:

sudo /home/impeeza/.nvm/versions/node/v9.11.2/bin/node start.js --webapplet

Now the PegaScape server is running self hosted

To close the PegaScape site, you type .exit and press [ENTER]

Tested on a 4.1.0 console and works fine.

If you want to use caffeine is recommended to leave out the parameter --webapplet since that one is for fake news and might cause the problem using caffeine.

Remember there are another parameters to start.js:
--webapplet: To enable fake internet, allowing the Switch to pass the connection test and load things like Fake News.
--ip <html_server_ip_override> if the detected IP address for the HTML server is not preffered.
--host <dns_server_ip_override> if the detected IP address for the DNS server is not preffered.
--disable-dns if you want to disable the internal DNS server and use something else (dnsmasq, bind, etc).

 

[urherenow]

In ubuntu, when using sudo, you need extra flags to preserve the environment (paths and such). I almost always use sudo -HE (although only one of those... I forget which... is really necessary). This takes care of having to type the whole path, as long as that is part of the regular user's path in bash.rc

 

[impeeza]

In ubuntu, when using sudo, you need extra flags to preserve the environment (paths and such). I almost always use sudo -HE (although only one of those... I forget which... is really necessary). This takes care of having to type the whole path, as long as that is part of the regular user's path in bash.rc

Will try it, I did use -E in the past for some MSYS commands

Post automatically merged: Mar 13, 2024

In ubuntu, when using sudo, you need extra flags to preserve the environment (paths and such). I almost always use sudo -HE (although only one of those... I forget which... is really necessary). This takes care of having to type the whole path, as long as that is part of the regular user's path in bash.rc

Didn't work on my ubuntu.

 

[urherenow]

Will try it, I did use -E in the past for some MSYS commands

Post automatically merged: Mar 13, 2024

Didn't work on my ubuntu.

Then /.nvm/versions/node/v9.11.2/bin/ isn't set in ~/.bashrc in the path. It probably doesn't get added when (or the way) you installed it.

If you add it to the path, then "sudo -HE node start.js --webapplet" would suffice. Personally though, I'd make an easier .sh file to make executable and run instead. Doesn't even need the .sh extension, as long as you make it executable and the file starts with a shebang (#!/bin/sh), Ubuntu will know what to do with it.

For example, when I needed some extra steps to update the Atmosphere code between versions (because of sept), I simply typed updateat, and atmosphere updated, make clean, and built the new version. I dropped the updateat script into opt/devkipro/tools, since that was already in my path.

#! /bin/sh
git pull origin master
git submodule update --init --recursive
git fetch --all
make clean
export SEPT_00_ENC_PATH='/home/urherenow/projects/Atmosphere/sept-secondary_00.enc'
export SEPT_01_ENC_PATH='/home/urherenow/projects/Atmosphere/sept-secondary_01.enc'
export SEPT_DEV_00_ENC_PATH='/home/urherenow/projects/Atmosphere/sept-secondary_dev_00.enc'
export SEPT_DEV_01_ENC_PATH='/home/urherenow/projects/Atmosphere/sept-secondary_dev_01.enc'
make dist-no-debug

EDIT: In hindsight, it may be easier to forget about the path bit, because if you make a script, you'll only have to type it once, for the script. Look at me thinking about things the hard way...

 

[impeeza]

Then /.nvm/versions/node/v9.11.2/bin/ isn't set in ~/.bashrc in the path. It probably doesn't get added when (or the way) you installed it.

If you add it to the path, then "sudo -HE node start.js --webapplet" would suffice. Personally though, I'd make an easier .sh file to make executable and run instead. Doesn't even need the .sh extension, as long as you make it executable and the file starts with a shebang (#!/bin/sh), Ubuntu will know what to do with it.

For example, when I needed some extra steps to update the Atmosphere code between versions (because of sept), I simply typed updateat, and atmosphere updated, make clean, and built the new version. I dropped the updateat script into opt/devkipro/tools, since that was already in my path.

#! /bin/sh
git pull origin master
git submodule update --init --recursive
git fetch --all
make clean
export SEPT_00_ENC_PATH='/home/urherenow/projects/Atmosphere/sept-secondary_00.enc'
export SEPT_01_ENC_PATH='/home/urherenow/projects/Atmosphere/sept-secondary_01.enc'
export SEPT_DEV_00_ENC_PATH='/home/urherenow/projects/Atmosphere/sept-secondary_dev_00.enc'
export SEPT_DEV_01_ENC_PATH='/home/urherenow/projects/Atmosphere/sept-secondary_dev_01.enc'
make dist-no-debug

EDIT: In hindsight, it may be easier to forget about the path bit, because if you make a script, you'll only have to type it once, for the script. Look at me thinking about things the hard way...

Yes the issue here is the installation method of NPM and NODE I chose a "manual" script to do it because the NODE version restriction

Will try the script to set variables and try to normal NOM installation on Ubuntu to confirm

 

[Mthodmn101]

which dns ip do we remove and replace with our own from the previous pegascape setup? do we need to do further blocking of nintendo servers so the switch doesnt try and update?

 

[impeeza]

which dns ip do we remove and replace with our own from the previous pegascape setup? do we need to do further blocking of nintendo servers so the switch doesnt try and update?

When you have the PegaScape self hosted, you use as DNS the IP indicated by the node running, by example on my case:

192.168.209.140

 

[Mthodmn101]

When you have the PegaScape self hosted, you use as DNS the IP indicated by the node running, by example on my case:

View attachment 425859

192.168.209.140

previously i thought 2 dns ip were used but just using the dns listed in my self-hosted is fine? and wont allow any nintendo connection to mess it up?

 

[impeeza]

previously i thought 2 dns ip were used but just using the dns listed in my self-hosted is fine? and wont allow any nintendo connection to mess it up?

OK, this DNS setting is only to launch the vulnerability, after you have the console running you can setup DNS90 or better Atmosphere's DNSiTM

https://rentry.org/AvoidSwitchBan

 

[Mthodmn101]

OK, this DNS setting is only to launch the vulnerability, after you have the console running you can setup DNS90 or better Atmosphere's DNSiTM

https://rentry.org/AvoidSwitchBan

i was more referring to avoid getting the update nag when launching caffeine. (im not too versed on this and set this up for a relative a while ago)

 

[impeeza]

i was more referring to avoid getting the update nag when launching caffeine. (im not too versed on this and set this up for a relative a while ago)

me neither, hope somebody will help us.

 

[MrZizou325i]

Hello. Is there a solution to the problem of not being able to do the tutorial here? I don't have the capacity....

 

[impeeza]

Hello. Is there a solution to the problem of not being able to do the tutorial here? I don't have the capacity....

Yeah wait for someone to create a container solution or try it again

 

[MrZizou325i]

Sí, espera a que alguien cree una solución contenedora o inténtalo de nuevo.

Hola soy novato en todo esto. He seguido todos los pasos de tu tutorial, y en el último paso me da la siguiente información: Respondiendo con dirección 172.21.123.15
IP del conmutador DNS 172.21.123.15
Ahora, ¿cómo debo configurar mi conexión en el conmutador? Gracias y perdón por ser torpe.

Post automatically merged: Mar 18, 2024

Yeah wait for someone to create a container solution or try it again

Hi, I'm a newbie to all this. I have followed all the steps in your tutorial, and in the last step it gives me the following information: Responding with address 172.21.123.15
dns switch ip 172.21.123.15
Now how should I configure my connection on the switch? Thanks, and sorry I'm clumsy

 

[impeeza]

Hola soy novato en todo esto. He seguido todos los pasos de tu tutorial, y en el último paso me da la siguiente información: Respondiendo con dirección 172.21.123.15
IP del conmutador DNS 172.21.123.15
Ahora, ¿cómo debo configurar mi conexión en el conmutador? Gracias y perdón por ser torpe.

Post automatically merged: Mar 18, 2024

Hi, I'm a newbie to all this. I have followed all the steps in your tutorial, and in the last step it gives me the following information: Responding with address 172.21.123.15
dns switch ip 172.21.123.15
Now how should I configure my connection on the switch? Thanks, and sorry I'm clumsy

You config your Network settings to use DNS 172.21.123.15 and then run pegascape proccess.

 

[MrZizou325i]

You config your Network settings to use DNS 172.21.123.15 and then run pegascape proccess.

Good morning. I'm trying to access pegascape with the new DNS, but it keeps giving me an error... I don't know what I must be doing wrong. I am attaching images to see if you can help me...

 

[urherenow]

I'm pretty sure you can just accept it. As far as I can remember, it will report a failure if it can't talk to Ninty over the internet... which is a good thing. If you're sure your PC host is running, and running at 172.21.123.15, then just accept the settings and give it a try.

Edit: and I hope you're aware that this is only for fw 1.0.0-3.0.0 or 4.0.1-4.1.0

 

[MrZizou325i]

I'm pretty sure you can just accept it. As far as I can remember, it will report a failure if it can't talk to Ninty over the internet... which is a good thing. If you're sure your PC host is running, and running at 172.21.123.15, then just accept the settings and give it a try.

Edit: and I hope you're aware that this is only for fw 1.0.0-3.0.0 or 4.0.1-4.1.0

Hello. I don't know what I'm doing wrong... I put the DNS IP in the PC's browser bar and it opens the pegascape exploit. But I configure it in the console settings and it gives me a DNS error..... my firm version is 4.1.0

 

[geekclassy1]

Hello. I don't know what I'm doing wrong... I put the DNS IP in the PC's browser bar and it opens the pegascape exploit. But I configure it in the console settings and it gives me a DNS error..... my firm version is 4.1.0

I have about the same problem. On my PC every is fine, but when I try from the Switch it doesn't work.

I can connect to the network fine but I cannot launch the exploit, the internet page doesn't load at all..

Post automatically merged: Mar 22, 2024

Good morning. I'm trying to access pegascape with the new DNS, but it keeps giving me an error... I don't know what I must be doing wrong. I am attaching images to see if you can help me...

Did you check the IP address on the host computer (the computer that on which the VM is running) ?
If so try from another computer/ your phone. It can be a VM network issue (e.g your VM is set up to communicate only to the host or on local NAT)

 

[MrZizou325i]

I have about the same problem. On my PC every is fine, but when I try from the Switch it doesn't work.

I can connect to the network fine but I cannot launch the exploit, the internet page doesn't load at all..

Post automatically merged: Mar 22, 2024

Did you check the IP address on the host computer (the computer that on which the VM is running) ?
If so try from another computer/ your phone. It can be a VM network issue (e.g your VM is set up to communicate only to the host or on local NAT)

You're right. From the PC where I have mounted the VM it does load the exploit, then I have tried with the mobile phone connected to the same Wi-Fi network and the exploit does not load... How could I solve this? I am very new to these topics. Thank you