Hi all! Just signed up to gbatemp to contribute to this thread. I just got my first 3DS on New 3DS release day so all this is new to me, but here are my findings.
- All of my tinkering has been on 9.5.0-22U. I only found out about streetpass/homepass/etc after updating.
- I'm doing Windows methods.
I started out trying
MACycle.
- MACycle v2.00 is cool, and has a nice UI, but relies on hostednetwork.
- hostednetwork-based solutions seem to have problems because WPA2-PSK security is required.
- I've read the MACycle thread and I was unable to get MACycle working.
Afterwards, I tried
the nzone.exe solution (which is far simpler) and got it to work.
- I ran nzone.exe on a Surface Pro 1 with only the wifi-card active.
- The Marvell Avastar 150N built into the Surface Pro 1 is capable of mac spoofing without silly octet mangling.
- nzone.exe operates by automatically configuring the hostednetwork, and creating a windows scheduled task for itself.
- The scheduled task will execute the command line you gave it (in my case nzone.exe start BASE16) every minute.
- when the glaciergaming post talks about "kick starting" it by running nzone.exe start BASE256, it's because that's exactly what the scheduled task does every time it runs.
- nzone.exe uses hostednetwork as well, but it ConsoleNintendo3DS for the SSID (which seems to be italian).
- Per this list, ConsoleNintendo3DS is expected to have a different SecurityMode than attwifi
- Perhaps SecurityMode 7 is WPA2-PSK.
- Is it thus validto assume that all 3DS units know of a password for ConsoleNintendo3DS hotspots?
- How else could this be working?
- Over time, running nzone.exe eventually put my Wi-Fi adapter into some invalid state in which nzone.exe could no longer start & stop it.
- Thus, after a couple StreetPass hits, I quickly stopped getting any (tested overnight).
- Unfortunately, while it was working, I StreetPassed the same three people at basically every MAC.
- I can't find the origin of nzone.exe aside from the download url, and the site at that DNS name doesn't seem to host a page.
Eventually, I realized that nzone.exe had configured for me a valid hosted network that the 3DS could use, and that I could maybe then administrate it with MACycle to achieve random cycling, custom MAC lists, and most importantly--durability.
- Using MACycle with the hostednetwork configured by nzone.exe, I was able to get some StreetPasses.
- Most of the MAC addresses I visit on the "Basic" set of 160 in MACycle result in no hits.
- I'm guessing this is because not many people are hitting those MAC addresses using ConsoleNintendo3DS
- Instead, they're probably using attwifi or NZ@McD1.
So all in all, limited success. I'd like to try experimenting with other networks, however I don't know the passwords for any of these other SecurityMode 7 hotspots so I can't spoof them--and even then, without knowing the real MAC addresses of those real hotspots it's unlikely that other people will be using those SSIDs with spoof MACs. Unfortunately, nzone.exe doesn't appear to be written in .NET so I can't disassemble it to see how it's creating the hostednetwork (and more importantly what password it's passing to netsh).
However, knowing that it's possible to use WPA2-PSK networks (as long as the 3DS expects that SSID to be WPA2-PSK) seems like a good discovery. It seems like the unsecured nature of attwifi and NZ@McD1 is a sore point for some people, so if we could figure out the password for ConsoleNintendo3DS it might be worth adding that SSID to
this recommendation so that people wanting network security (and windows users) have another option.
Hope this helps someone!
@
Psionic Roshambo:
@
BigOnYa:
