@MopSec to say that i don't use the PC like you and certain things are a little more complicated to do with the smartphone.What does that have to do with using DNS MitM?
@MopSec to say that i don't use the PC like you and certain things are a little more complicated to do with the smartphone.What does that have to do with using DNS MitM?
I think you misread the changelog, these are about the changes made in 1.10.0, not 1.10.1:Update 21.1.0 required a new Atmosphere update, which has arrived with Atmosphère 1.10.1.
Apparently many Homebrew apps need to be recompiled (again!).
@Bigdrago smartphone&cellphone they are totally different,be careful not to choke while eating.Eating popcorn while reading dns stuff versus cellphone discussion.what is this
@Bigdrago smartphone&cellphone they are totally different,be careful not to choke while eating.
@Bigdrago maybe you didn't understand or read what i wrote,i use my smartphone and not my cell phone to transfer and communicate with my Switch and i don't know what to do or where to put that damned dnsmitm.You are talking about disabling automatic updates and people advice you to use dnsmitm and suddenly you are talking about using your cellphone which isnt related to automatic updates What is the connection and your real issue here?
sysmmc.txt would only apply to SysMMC. The file probably should be renamed to default.txt, that way it gets applied no matter if you use SysMMC or emuMMC. Then all that's left to do is reboot and check the log to confirm it's getting applied as expected, there's a detailed explanation on the links I posted (the guide and Atmosphere's documentation).@Nephiel thanks you very much for reply and the clarification.That looks correct, butsysmmc.txtwould only apply to SysMMC. The file probably should be renamed todefault.txt, that way it gets applied no matter if you use SysMMC or emuMMC. Then all that's left to do is reboot and check the log to confirm it's getting applied as expected, there's a detailed explanation on the links I posted (the guide and Atmosphere's documentation).
That looks correct, butsysmmc.txtwould only apply to SysMMC. The file probably should be renamed todefault.txt, that way it gets applied no matter if you use SysMMC or emuMMC. Then all that's left to do is reboot and check the log to confirm it's getting applied as expected, there's a detailed explanation on the links I posted (the guide and Atmosphere's documentation).
Block nintendo connection:
Create a file named default.txt in /atmosphere/hosts/
Add this to the text file:
# Block Nintendo Servers
127.0.0.1 *nintendo.*
127.0.0.1 *nintendo-europe.com
127.0.0.1 *nintendoswitch.*
95.216.149.205 *conntest.nintendowifi.net
95.216.149.205 *ctest.cdn.nintendo.net
If you plan to use Atmosphere on SysNAND for online play and EmuNAND for offline play, rename the file to emummc.txt.
To blank your serial info:
Create the file exosphere.ini in the root of your SD card
[exosphere]
debugmode=1
debugmode_user=0
disable_user_exception_handlers=0
enable_user_pmu_access=0
blank_prodinfo_sysmmc=0
blank_prodinfo_emummc=1
allow_writing_to_cal_sysmmc=0
log_port=0
log_baud_rate=115200
log_inverted=0
@Earthshine i set like this@NeoGranzon According to Atmosphere documentation, it is best to leave the default file as is and make a separate one for emuMMC or sysMMC depending on usage. https://github.com/Atmosphere-NX/Atmosphere/blob/master/docs/features/dns_mitm.md
Atmosphère defaults
By default, atmosphère's default redirections are parsed in addition to the contents of the loaded hosts file.
This is equivalent to thinking of the loaded hosts file as having the atmosphère defaults prepended to it.
This setting is considered desirable, because it minimizes the telemetry risks if a user forgets to update a custom hosts file on a system update which changes the telemetry servers.
yesJust installed newest atmosphere. But under settings - system it shows 21.0.0|AMS and 1.10.0|E
Shouldnt it show 1.10.1|E ?
A fatal error Occured when launching Atmosphere 1.10.1 May have Improberly Data in Atmosphere try Fixarchive bit on Hekate the Fixarchive bit on Hekate not Working.The atmosphere 1.10.1 is from Github made by SciresM.On the official release page. Was published 3 hours ago
@Earthshine so the posted image is wrong?default.txt should have these two lines:
# Nintendo telemetry servers
127.0.0.1 receive-%.dg.srv.nintendo.net receive-%.er.srv.nintendo.net
emummc.txt should have these lines:
# Block Nintendo Servers
127.0.0.1 *nintendo*
95.216.149.205 *conntest.nintendowifi.net
95.216.149.205 *ctest.cdn.nintendo.net
The last two lines (with 95.216.149.205) of emummc.txt are not necessary if you are using something like sys-patch and have the ctest options enabled, but it also doesn't hurt to keep those lines. Also, only the one *nintendo* line because the "*" acts as a wildcard and will block all of the other ones. No need for a long list.
Hope that helps.
@Earthshine so the posted image is wrong?
Sorry @Earthshine ,i already had the first file you attached and when i tried to connect to the Nintendo server it didn't give me the error,as it gives me now if i try with the primary and secondary DNS set like this 163.172.141.219(primary)207.246.121.077(secondary)and which i use together with Switch 90dns tester.Here. Just drop these into atmosphere/hosts and overwrite the ones that may already exist.
Edit: I also installed sys-patch and sigpatches for AMS 1.10.1After updating to HOS 21.0.0 and doing a fresh install of Atmosphere 1.10.1 and Hekate 6.4.2 I installed Sphaira 1.0.0 and at first launch in applet mode it ran fine.
After exiting and launching with title override it gets stuck on "Checking" forever (30 minutes tested).
Using applet mode I installed the forwarder for it and tried launching it again with the same results.
Rebooted my Switch and it launched using the forwarder. Exit and relaunched it via forwarder again and got stuck at "Checking". Same happens when using title override, it launched fine first time, but gets stuck at "Checking" on next launch. Only way to fix is a reboot.
