Project New Public Pegascape DNS - Replacement for the Public EOL DNS by noahc3

[Luc20100]

ok, apparently I do not have the tab installed within Pegascape. So, I am not sure what I need to do? Looks like I only have Caffeine and HBL tabs within Pegascape.

Post automatically merged: Aug 1, 2024

I went back through all my backups and logically reasoned I could have a corrupt Atmosphere file that is preventing me from loading exploit. Since the last time I had to restore my Switch was through a power loss and battery not charging. I deleted the switch and atmoshere folders and re-added 1.7.0 Atmosphere back onto the SD card. Bam, the exploit worked this time. Thanks for the guides!

 

[einhuman197]

ok, apparently I do not have the tab installed within Pegascape. So, I am not sure what I need to do? Looks like I only have Caffeine and HBL tabs within Pegascape.

Post automatically merged: Aug 1, 2024

I went back through all my backups and logically reasoned I could have a corrupt Atmosphere file that is preventing me from loading exploit. Since the last time I had to restore my Switch was through a power loss and battery not charging. I deleted the switch and atmoshere folders and re-added 1.7.0 Atmosphere back onto the SD card. Bam, the exploit worked this time. Thanks for the guides!

Hey, sorry for the late reply! Glad it works for you now!

I have no ICMP to your DNS

Regarding the fact that you weren't able to Ping the Server: Good point! It's the default network configuration of Oracle Cloud Machines to drop basically all ICMP Traffic, that includes the Echo Reply/Ping. I forgot to change that when configuring the machine. I enabled all ICMPv4 Traffic now (@ Nintendo pls don't DDoS), feel free testing pinging it! It works on my side.

Just as a side note: I didn't enable ICMPv6 or IPv6 on the machine. While Oracle supports Full Dual Stack and it'd be a very good thing for any public Service on the Internet to have IPv6 nowadays, sadly the Switch isn't able to handle IPv6 DNS Servers, it's stuck with Legacy IP. So configuring Dual Stack for the entire machine just doesn't make sense, because the Switch can't handle it.

We'll see what we can do regarding public hosting once IPv4 Flag Day comes around, maybe some NAT46 magic in the internal network will be needed once ISPs stop providing Legacy IP addresses to customers. The entire npm project might need some patches, I haven't checked if it works with IPv6 Requests. But I think that'll only be a problem in several years down the road.

 

[almmiron]

any build of the fakenews injector works on new fw/atm 18 or 19.00? i mean, i want to launch it only to unninstal pegascape, i've got a switch with one installed and can't get rid of it without formating /restoring the nand.

 

[Hayato213]

any build of the fakenews injector works on new fw/atm 18 or 19.00? i mean, i want to launch it only to unninstal pegascape, i've got a switch with one installed and can't get rid of it without formating /restoring the nand.

If your OFW is above 4.1.0 then it won't work.

 

[DetonaHard]

Hi there!
Is it still up?

 

[einhuman197]

Hi there!
Is it still up?

Hey, always has been! Health Logs looks clean, and I just confirmed it's working with my Switch. Does is still not work for you?

any build of the fakenews injector works on new fw/atm 18 or 19.00? i mean, i want to launch it only to unninstal pegascape, i've got a switch with one installed and can't get rid of it without formating /restoring the nand.

I think you need to build it from the sources. There were plenty of Patches from Nintendo over the years that change access with homebrew. You have the Firmware 19 on emuNAND, right? On SysNAND you obviously need to stay on 4.1.0 max. If you're above that, you are out of luck without a modchip.

 

[DetonaHard]

Hey, always has been! Health Logs looks clean, and I just confirmed it's working with my Switch. Does is still not work for you?


I think you need to build it from the sources. There were plenty of Patches from Nintendo over the years that change access with homebrew. You have the Firmware 19 on emuNAND, right? On SysNAND you obviously need to stay on 4.1.0 max. If you're above that, you are out of luck without a modchip.

I tested it right now and it appears to be working!

Thank you very much!

 

[AcIdPort]

Hello, I used your DNS and I hosted PegaScape on my PC too. After the caffeine notification shows up, I tap the text field and press the power button, but nothing happens. What could it be? Switch firmware is 4.1.0.

Thanks.

update: I just did a fresh atmos and hekate install in my SD. It works fine!

 

[einhuman197]

There now is a second PegaScape Instance running online, thanks to and maintained by @viperware. It is operating in WiFi Auth Mode. I updated my first post in this thread with all the details!

 

[ArcangelSP]

First of all Thank you, I needed to update the DNS and found yours.
Second I have not clear the difference between your in applet mode and the one in Wifi Auth Mode, It doesn´t change nothing right? connect to the wifi, launch pegascape and Emunand.
And last there is any guide/recomendation to host my own dns with theses requirements using a server ubuntu/debian/proxmox what is your recomendation.
Thanks again.

 

[einhuman197]

First of all Thank you, I needed to update the DNS and found yours.
Second I have not clear the difference between your in applet mode and the one in Wifi Auth Mode, It doesn´t change nothing right? connect to the wifi, launch pegascape and Emunand.
And last there is any guide/recomendation to host my own dns with theses requirements using a server ubuntu/debian/proxmox what is your recomendation.
Thanks again.

Choosing between the Applet Mode and WiFi Auth Mode depends on how you used to launch PegaScape. If you have the "Launch Pegascape" News injected within your News Applet and you launch it that way, the Applet Mode IP is the DNS for you. If you launch PegaScape through the WiFi Authentication Prompt, then you need to use the WiFi Auth DNS.

I had good luck on my VPS with Ubuntu 22.04 LTS. It should work with any Debian Based Distribution just fine. Just keep in mind that while running PegaScape, the DNS of your machine will not work, as Port 53 usually used for DNS Requests is occupied by your machine operating a DNS Server itself. Also because it uses ancient node.js it might be an avoidable security risk on existing systems. So if you want a PegaScape DNS in your network, you should make a dedicated vm. You barely need any resources though, you should be fine with Single Core, 1GB RAM or even 512MB RAM, maybe 10GB of Disk Space (Ubuntu 22.04 LTS Minimal needs around 8.5GB, the node.js and Files from the Repo only need a few MB each).