Open jayzone1 opened 4 years ago
nan-gogh
commented
4 years ago Hey there :) I have the same problem here. Found an older, closed issue where you suggested to enable the ldn_mitm sysmodule in Kosmos Toolbox. Well, it somehow doesn't appear there to be enabled and rebooting Atmosphere 0.11.0 (using fusee-primary) leads to crash.. does this happen because of the new Atmosphere update? I'd really appreciate any further help on this and thank you in advance!
alexandre-xn
commented
4 years ago I have the same issue on AMS 0.11.1. I also tried the build in https://github.com/spacemeowx2/ldn_mitm/issues/40#issuecomment-614502143 without success.
drizuid
commented
4 years ago did you enable ldn_mitm? you can open kosmos toolbox, click background services, verify ldn_mitm shows "on" then follow with the required reboot
for the second poster, if you've installed ldn_mitm 1.3.4 you need to have atmosphere 11. If you're on ldn_mitm 1.3.3 and on atmosphere 11, you need to upgrade to 1.3.4
for the third poster, #40's build is older than the 1.3.4 release. I'm using atmosphere 11 with the final 1.3.4 release without issue (but i did have to enable it as shown above)
xtheredshirtx
commented
4 years ago I just added 1.3.4 to my switch and I get the same error. I never installed this before so I don't know what I can do to get this working. I am running the latest version on Atmosphere 11.1
drizuid
commented
4 years ago I just added 1.3.4 to my switch and I get the same error. I never installed this before so I don't know what I can do to get this working. I am running the latest version on Atmosphere 11.1
you likely need to enable it. you can do so via tesla or kosmos toolbox.
Please help when i tried startong up idnmitm cfg on my NS it says ldn_mitm is not loaded or too old (requires ldn_mitm >= v1.1.2) what do i do?