Tutorial [HOW-TO] Have a homemade Streetpass Relay

[Bambamthepyro]

I am so confused right now.

Is there anyway possible that these methods can be cleaned up and turned to "idiot proof"?

Also, it there a version for Lollipop 5.0?

 

[Liberty]

I use VMWare and neither in Windows 8.1 nor Windows 7 I have an option to change the MAC in the preference settings. But on Windows 7 at least this tool worked. And I think it still does, but I don't get any Miis.

€dit: Reading this:
http://lizardsystems.com/wiki/change_mac_address/faq/change_mac_address_in_windows_7
http://blog.technitium.com/2011/05/tmac-issue-with-wireless-network.html

I just re-installed my network driver and changing my MAC does indeed still works.

So I have no clue why nzone.exe doesn't do anything.

Maccheck.cmd under Windows 8 tells me my network adapter isn't suitable, which is just not true.

Still need help.

 

[Syphos]

I am so confused right now.

Is there anyway possible that these methods can be cleaned up and turned to "idiot proof"?

Also, it there a version for Lollipop 5.0?

If you make something foolproof, only fools will use it. - Murphy's Law
DIfferent OS, different hardware, there is no way to make an X-to-X relationship a 1-to-1 for everyone.

Still need help.

A. Did you setup your VM to use that USB (disconnect from host) and restarted the VM?
B. Can the VM connect to the internet?
C: If there is a problem with the internals (does your Wifi even get detected) of that VM, I can't help.

 

[Scytheri0n]

I am so confused right now.

Is there anyway possible that these methods can be cleaned up and turned to "idiot proof"?

Also, it there a version for Lollipop 5.0?

If you make something foolproof, only fools will use it. - Murphy's Law
DIfferent OS, different hardware, there is no way to make an X-to-X relationship a 1-to-1 for everyone.

That being said, my XZone method for Mac is fairly foolproof (although by no means perfect) and should be easily ported to Android (since Android is just Linux, after all). I have an older Android device, barely running JellyBean, I might give XZone a bash (lololol puns) on that, although it will be a lot more involved to run than XZone on a Mac (since you'd need to root and install a terminal app and some other tools etc). Its not at the top of my priorities list at the moment though so don't expect it any time soon.

 

[kheldar]

Hello guys, I'm kinda noob to HomePass so my questions could sound stupid but I'd really appreciate it if you could help me out. Here it goes :

I only own a wireless usb adapter which I use to connect to the internet. I followed Duke_srg's guide to set up a homepass on my computer but It doesn't work for me. Whenever I turn on the VM, WiFi on my Windows gets disabled and I can't see a new SSID because I can't even browse for new connections like he can do on the video. Am I missing a step which could be obvious to anyone but not to some noob like myself ? Like some extra piece of hardware or different router settings?

Images from VM :




Edit : Apparently my USB stick is not compatible with VM method. I want to try Windows Native method but when I run Maccheck file I receive this :



Does it mean that my USB stick is not compatible with this method either?

Edit 2 : I managed to set up a homepass using Native Windows mode on my friend's laptop and received Nintendo Zone icon on my n3ds. But since emunand is not updated I can't use Nintentdo Zone application, It asks for a system update. Now my question is how do i use this? I'm not receiving any streetpass notificiations and from what I gathered green led should be turned on when it's interacting but It's not.I may sound noobish but n3ds is my first Nintendo console and I'm not familiar with streetpass process because where I live there is no Nintendo.

Edit 3 : After trying to use it sometime I realized it doesn't work with a wired connection because internet sharing option gets disabled every time the mac changes. So I need two wireless adapters for this.


Thanks in advance!

 

[Oswarlan]

So I have a router that works for mac spoofing, and back in the pre-9.x days, (attwifi ssid) it worked amazingly for getting all the streetpasses I could care to get. Then didn't need/want to use it for awhile, so i turned it off. Now I'm trying to get it to work again, but my 3ds doesn't see a Nzone, nor does it get any streetpasses.
Currently using the NZ@McD1 ssid as mentioned in this guide under, as one would expect, the router category. Any ideas as to what I am doing wrong here?
TL;DR Worked on router with attwifi, doesn't work now with NZ@McD1.

Anybody have any ideas?

 

[Syphos]

Hello guys, I'm kinda noob to HomePass so my questions could sound stupid but I'd really appreciate it if you could help me out. Here it goes :

I only own a wireless usb adapter which I use to connect to the internet. I followed Duke_srg's guide to set up a homepass on my computer but It doesn't work for me. Whenever I turn on the VM, WiFi on my Windows gets disabled and I can't see a new SSID because I can't even browse for new connections like he can do on the video. Am I missing a step which could be obvious to anyone but not to some noob like myself ? Like some extra piece of hardware or different router settings?

Images from VM :

View attachment 17497 View attachment 17498 View attachment 17500 View attachment 17504 View attachment 17508

Single Wifi setup with VM won't even work.
You can't use that Wifi for Internet AND the VM at the same time, since the VM detaches it from windows..
So you need at least one seperate adapter, may it be wired or wireless.

View attachment 17515

Does it mean that my USB stick is not compatible with this method either?

Hm, the ASUS USB-N14 is a RT5372.
(Judging from it's shape, this is no "simple" Dongle, that's how Accesspoints look like)
Does that Device give you an option to set "network Adress" or "local MAC Administration"?
You will find usually these options using the Device Manager for your Device.
There are many ways to setup a MAC, but if all of them fail, you have to ditch that adapter for homepass.

Edit 2 : I managed to set up a homepass using Native Windows mode on my friend's laptop and received Nintendo Zone icon on my n3ds. But since emunand is not updated I can't use Nintentdo Zone application, It asks for a system update. Now my question is how do i use this? I'm not receiving any streetpass notificiations and from what I gathered green led should be turned on when it's interacting but It's not.I may sound noobish but n3ds is my first Nintendo console and I'm not familiar with streetpass process because where I live there is no Nintendo.

When you had recieved Streetpass Data, the 3DS blinks. That's how you know it works for streetpassing.
Nintendo Zone Symbol gets triggered by the SSID alone, so I guess you are using SSID NZ@McD1
Starting the Nintendo Zone App on the 3DS won't do anything, even if it connects, it says "Content is not avail in your region"

Can't help with emuNand
You can test the connection with the 3DS, but delete the saved connection data after a successful test.

Edit 3 : After trying to use it sometime I realized it doesn't work with a wired connection because internet sharing option gets disabled every time the mac changes. So I need two wireless adapters for this.

Wired + Wifi
Wifi + Wifi
Wifi
Where is the difference? None. The last one just won't work on its own.

I hope you weren't accidentally sharing the Wifi instead.
Share the wire (more stable IMO) - tell windows what Wifi will go through.
The wired connection should have a hand (depending on the OS used).
Do not tell any MAC cycling program to change the MAC on the wired!
IF your cycling program works correctly, it should change the MAC, disable the Wifi and enable it back on.
Windows has to do stuff behind the scenes, which takes a couple of seconds up to 1 minute.

Don't expect a streetpass as soon the Wifi is back up immediately. Patience.

Edit: LOL

 

[Taser9090]

I used this guide just so I could connect my 3DSs and Wii U to my laptop, and the StreetPass relay is just a bonus. I have a few questions:

I set up the SSID and MAC the same for my Windows 8 laptop and Android phone. However, it seems my two 3DSs are not getting any StreetPasses from it and I only get SpotPass data. Keep in mind that the relay used to work on my Android phone a year ago, but now it seems like it stopped working. I didn't change any settings that would affect the relay on the Droid phone. Anyone else having this problem?

It seems that only one device can be connected to Windows Virtual Wireless Adapter. Is there a way to change the settings so more than one can connect?

Is there a way to optimize the connection speed to devices connected to the virtual wireless adapter? I'm having some laggy matches in Smash and I think it's a problem on my end.

 

[DeaGrimm]

Syphos~
D-Link's DWA-125 has it's MAC printed on the casing.

I tried everything save for installing a manager-program to try and turn it into a AP.

At this point I wish I was dealing w/ analogical electronics, it'd be the point where I would rip off all of the ci's and wires from the protoboard, resist the urge to stomp all over them, test the wires and ci's to see if they are all in working order, and start from scratch.

So I went to the start menu, right-clicked on computer -> manage -> device manager -> Actions -> More actions -> Show -> Show hidden devices aaaand stared to re-install all the drivers.
Funny fact 1: Teredo Tunneling Pseudo-Interface had an error warning (fixed by changing the E8 to 0 on some parameter in the registry).
Funny fact 2: ugly baidu left-overs are now gone.

Didn't help any.
I renamed the "Console3DS" device to Homepass as not to confuse it with the "Console3DS" hostednetwork created by nzone.exe

So, any hostednetwork created by me can be accessed by the 3DS and connect to the internet (bytes are being sent AND received) 3DS's browser works.
The hostednetwork created by nzone.exe, for reasons unknown to me, cannot connect to the internet (bytes are sent but none are received) even though the device says it has access (IPv4) to the Internet I would test it in the 3DS but I dunno the password to the hostednetwork created by nzone.exe .

DHCP(?)/ICP(?) are as they should be, there is no IP clashing, netsh int ip reset reset.log and netsh winsock reset catalog commands had no effect.

My current reasoning: if nzone.exe can change my Wireless 1397 Mini-Card's MAC there is no reason why MACycle shouldn't be able to do the same. So I'll go bother the guys on MACycle's official post.

If I can get MACycle working I'll come back here and post what I did. =)

 

[kheldar]

Single Wifi setup with VM won't even work.
You can't use that Wifi for Internet AND the VM at the same time, since the VM detaches it from windows..
So you need at least one seperate adapter, may it be wired or wireless.



Hm, the ASUS USB-N14 is a RT5372.
(Judging from it's shape, this is no "simple" Dongle, that's how Accesspoints look like)
Does that Device give you an option to set "network Adress" or "local MAC Administration"?
You will find usually these options using the Device Manager for your Device.
There are many ways to setup a MAC, but if all of them fail, you have to ditch that adapter for homepass.




When you had recieved Streetpass Data, the 3DS blinks. That's how you know it works for streetpassing.
Nintendo Zone Symbol gets triggered by the SSID alone, so I guess you are using SSID NZ@McD1
Starting the Nintendo Zone App on the 3DS won't do anything, even if it connects, it says "Content is not avail in your region"

Can't help with emuNand
You can test the connection with the 3DS, but delete the saved connection data after a successful test.




Wired + Wifi
Wifi + Wifi
Wifi
Where is the difference? None. The last one just won't work on its own.

I hope you weren't accidentally sharing the Wifi instead.
Share the wire (more stable IMO) - tell windows what Wifi will go through.
The wired connection should have a hand (depending on the OS used).
Do not tell any MAC cycling program to change the MAC on the wired!
IF your cycling program works correctly, it should change the MAC, disable the Wifi and enable it back on.
Windows has to do stuff behind the scenes, which takes a couple of seconds up to 1 minute.

Don't expect a streetpass as soon the Wifi is back up immediately. Patience.

Edit: LOL
View attachment 17521

I thank you very much for your time and effort put in answering my questions. Everything's much clear in my head right now. I ordered a USB stick which has been confirmed working with Native Windows method. I gather I can use the usb stick as the AP for Homepass and my wifi adapter for actual internet connection. Am i right ?

 

[Liberty]

A. Did you setup your VM to use that USB (disconnect from host) and restarted the VM?
B. Can the VM connect to the internet?
C: If there is a problem with the internals (does your Wifi even get detected) of that VM, I can't help.

A. Of course.
B. Yes
C. Yes, I can see the WiFi-network and the HomePass-Macs.

My N3DS just doesn't get any StreetPasses. I just re-installed Windows 7 in my VM and at least the nzone.exe-method "technically" seems to work again, but I still don't get any StreetPasses. Or at least it takes 10x as long in comparison to my Old 3DS.

And the Debian-VM-method never worked at all. Not a single pass after several hours.

 

[Syphos]

I set up the SSID and MAC the same for my Windows 8 laptop and Android phone. However, it seems my two 3DSs are not getting any StreetPasses from it and I only get SpotPass data.

Did you setup that connection in the 3DS Wireless Connection options? You have to delete that there.

Keep in mind that the relay used to work on my Android phone a year ago, but now it seems like it stopped working. I didn't change any settings that would affect the relay on the Droid phone. Anyone else having this problem?

Are you running both devices AT THE SAME TIME with the same SSID and MAC?

It seems that only one device can be connected to Windows Virtual Wireless Adapter. Is there a way to change the settings so more than one can connect?

This hostednetwork Wifi-Adapter eats more then one.
There is no limit afaik.

Is there a way to optimize the connection speed to devices connected to the virtual wireless adapter? I'm having some laggy matches in Smash and I think it's a problem on my end.

Why don't you just your internet Router for that?
Homepass setup devices shouldn't be used for Internet, except Streetpass. (Since it is laggy as hell)
But in the end, you can use it how you want.

Syphos~
D-Link's DWA-125 has it's MAC printed on the casing.

My D-link DWL-122 has that too, but it allows changing.
I am downloading the driver about your DWA and found something odd (wonder if I got the right one)

However, your DWA is listed in the driver of my working streetpass device O-o
(Ok, it says "D-Link DWA-125 Wireless 150 USB Adapter(rev.A2)", my driver is from 2011.)
So I got some new drivers aaaand ... I had a dog and his name was BINGO!

Uninstall the D-link Driver Crap from your PC please, try installing this:
http://download.wireless-driver.com/driver/Ralink/USB(RT2870)/IS_AP_STA_RT2870_W7-3.2.4.0_Free.exe
Should give you this nifty tool :3



That's what I am using!
And its included in the driver package above.
(Cause if I run this, it gives me an option to "update driver" )
No more encrypted hostednetwork, yay.

I would test it in the 3DS but I dunno the password to the hostednetwork created by nzone.exe

Me neither. Doesn't matter anymore, since nzone won't be needed anymore.

My current reasoning: if nzone.exe can change my Wireless 1397 Mini-Card's MAC there is no reason why MACycle shouldn't be able to do the same. So I'll go bother the guys on MACycle's official post.

If I can get MACycle working I'll come back here and post what I did. =)

Did you try macshift on the DWA yet? almost the same as MACycle.
Download: http://devices.natetrue.com/macshift/macshift.zip
Use it like this from the inside of an Admin CMD :
macshift -i "Connection" 4E53504F4F40
Where it says Connection, just input the Name of the connection of the hardware device, keep the quotes intact!
It should shift that D-Link DWA's MAC to a prime MAC and the Virtual Wifi' MAC should switch too.
Or you can start up MACycle, set "Network Adapter" to that of the D-link DWA hardware and go switching (that's how I do it).
If this still fails... wtf is wrong with your PC?

You could try to do it the other way around so you use the D-link DWA for the internet, and the build-in Broadcom 1394 Wifi for homepass.

 

[Syphos]

OKay, guys. If your Wifi has one of these Ralink Chipsets;
RT61
RT73
RT2860
RT2870
RT2070
RT3070
RT2090
RT3090

or is listed here with its USB\VID_XXXX&PID_XXXX pair,
try installing this driver:

http://download.wireless-driver.com/driver/Ralink/USB(RT2870)/IS_AP_STA_RT2870_W7-3.2.4.0_Free.exe

or that, since it's from 2014 ; http://mediatek.com/en/downloads/usb/ 12/11/2014, 5.01.20.0000
This includes the Ralink Utility, but just renamed/reskinned to "Mediatek".
Both version support encryption free AP-Mode.

Device IDs that SoftAP (yeah it really is software based >_> ) does support:

[RT61]
DeviceID_1=PCI\VEN_1814&DEV_0301
DeviceID_2=PCI\VEN_1814&DEV_0302
DeviceID_3=PCI\VEN_1814&DEV_0401
 
[RT73]
DeviceID_1=USB\VID_148F&PID_2573
DeviceID_2=USB\VID_148F&PID_2671
DeviceID_3=USB\VID_0DB0&PID_6877
DeviceID_4=USB\VID_0DB0&PID_A874
DeviceID_5=USB\VID_0DB0&PID_6874
DeviceID_6=USB\VID_0DB0&PID_A861
DeviceID_7=USB\VID_1631&PID_C019
DeviceID_8=USB\VID_18E8&PID_6196
DeviceID_9=USB\VID_18E8&PID_6229
DeviceID_10=USB\VID_1044&PID_8008
DeviceID_11=USB\VID_1044&PID_800A
DeviceID_12=USB\VID_14B2&PID_3C22
DeviceID_13=USB\VID_0769&PID_31F3
DeviceID_14=USB\VID_0B05&PID_1723
DeviceID_15=USB\VID_0B05&PID_1724
DeviceID_16=USB\VID_18C5&PID_0002
DeviceID_17=USB\VID_1371&PID_9032
DeviceID_18=USB\VID_1472&PID_0009
DeviceID_19=USB\VID_1690&PID_0722
DeviceID_20=USB\VID_148F&PID_9021
DeviceID_21=USB\VID_0EB0&PID_9021
DeviceID_22=USB\VID_15A9&PID_0004
DeviceID_23=USB\VID_050D&PID_905C
DeviceID_24=USB\VID_050D&PID_905B
DeviceID_25=USB\VID_050D&PID_705B
DeviceID_26=USB\VID_0411&PID_00D8
DeviceID_27=USB\VID_18E8&PID_6238
DeviceID_28=USB\VID_0471&PID_200A
DeviceID_29=USB\VID_0CDE&PID_001C
DeviceID_30=USB\VID_0DB0&PID_4600
DeviceID_31=USB\VID_07B8&PID_B21B
DeviceID_32=USB\VID_07B8&PID_B21C
DeviceID_33=USB\VID_07B8&PID_B21D
DeviceID_34=USB\VID_07B8&PID_B21E
DeviceID_35=USB\VID_07B8&PID_B21F
DeviceID_36=USB\VID_2019&PID_AB01
DeviceID_37=USB\VID_2019&PID_AB50
DeviceID_38=USB\VID_0586&PID_3415
DeviceID_39=USB\VID_0DF6&PID_0024
DeviceID_40=USB\VID_0DF6&PID_0027
DeviceID_41=USB\VID_1740&PID_3701
DeviceID_42=USB\VID_0DF6&PID_002F
DeviceID_43=USB\VID_1740&PID_7100
DeviceID_44=USB\VID_7392&PID_7318
DeviceID_45=USB\VID_7392&PID_7618
DeviceID_46=USB\VID_14B2&PID_3C10
DeviceID_47=USB\VID_04E8&PID_4471
DeviceID_48=USB\VID_08DD&PID_0120
DeviceID_49=USB\VID_07D1&PID_3C06
DeviceID_50=USB\VID_04BB&PID_093D
DeviceID_51=USB\VID_7167&PID_3840
DeviceID_52=USB\VID_07AA&PID_002E
DeviceID_53=USB\VID_1B75&PID_7318
DeviceID_54=USB\VID_8516&PID_2571
 
[RT2860]
DeviceID_1=PCI\VEN_1814&DEV_0601
DeviceID_2=PCI\VEN_1814&DEV_0681
DeviceID_3=PCI\VEN_1814&DEV_0701
DeviceID_4=PCI\VEN_1814&DEV_0781
DeviceID_5=PCI\VEN_1814&DEV_3593
 
[RT2870]
DeviceID_1=USB\VID_148F&PID_2870
DeviceID_2=USB\VID_0B05&PID_1731
DeviceID_3=USB\VID_0B05&PID_1732
DeviceID_4=USB\VID_0DF6&PID_0017
DeviceID_5=USB\VID_14B2&PID_3C06
DeviceID_6=USB\VID_2019&PID_ED06
DeviceID_7=USB\VID_07D1&PID_3C09
DeviceID_8=USB\VID_050D&PID_8053
DeviceID_9=USB\VID_14B2&PID_3C07
DeviceID_10=USB\VID_14B2&PID_3C23
DeviceID_11=USB\VID_07AA&PID_002F
DeviceID_12=USB\VID_1044&PID_800B
DeviceID_13=USB\VID_148F&PID_2770
DeviceID_14=USB\VID_15A9&PID_0006
DeviceID_15=USB\VID_083A&PID_B522
DeviceID_16=USB\VID_083A&PID_7522
DeviceID_17=USB\VID_1740&PID_9701
DeviceID_18=USB\VID_14B2&PID_3C25
DeviceID_19=USB\VID_0B05&PID_1742
DeviceID_20=USB\VID_0471&PID_200F
DeviceID_21=USB\VID_13D3&PID_3247
DeviceID_22=USB\VID_083A&PID_6618
DeviceID_23=USB\VID_083A&PID_A618
DeviceID_24=USB\VID_07AA&PID_003C
DeviceID_25=USB\VID_1740&PID_9702
DeviceID_26=USB\VID_0E66&PID_0001
DeviceID_27=USB\VID_0E66&PID_0003
DeviceID_28=USB\VID_14B2&PID_3C27
DeviceID_29=USB\VID_14B2&PID_3C28
DeviceID_30=USB\VID_129B&PID_1828
DeviceID_31=USB\VID_0CDE&PID_0025
DeviceID_32=USB\VID_0DF6&PID_002B
DeviceID_33=USB\VID_07AA&PID_003F
DeviceID_34=USB\VID_0DF6&PID_002C
DeviceID_35=USB\VID_0DF6&PID_002D
DeviceID_36=USB\VID_1044&PID_800C
DeviceID_37=USB\VID_07D1&PID_3C11
DeviceID_38=USB\VID_7392&PID_7717
DeviceID_39=USB\VID_7392&PID_7718
DeviceID_40=USB\VID_07B8&PID_2870
DeviceID_41=USB\VID_07B8&PID_2770
DeviceID_42=USB\VID_2019&PID_AB24
DeviceID_43=USB\VID_18E8&PID_6259
DeviceID_44=USB\VID_07D1&PID_3C13
DeviceID_45=USB\VID_0B05&PID_1760
DeviceID_46=USB\VID_0B05&PID_1761
DeviceID_47=USB\VID_15A9&PID_0010
DeviceID_48=USB\VID_083A&PID_8522
DeviceID_49=USB\VID_083A&PID_7512
DeviceID_50=USB\VID_0DF6&PID_0039
DeviceID_51=USB\VID_0E66&PID_0009
DeviceID_52=USB\VID_0E66&PID_000B
DeviceID_53=USB\VID_13D3&PID_3262
DeviceID_54=USB\VID_0DF6&PID_003B
DeviceID_55=USB\VID_0E0B&PID_9031
DeviceID_56=USB\VID_0E0B&PID_9041
DeviceID_57=USB\VID_0DF6&PID_003C
DeviceID_58=USB\VID_1D4D&PID_0001
DeviceID_59=USB\VID_1D4D&PID_0002
DeviceID_60=USB\VID_1740&PID_0605
DeviceID_61=USB\VID_1740&PID_0615
DeviceID_62=USB\VID_0B05&PID_1731
DeviceID_63=USB\VID_5A57&PID_0280
DeviceID_64=USB\VID_5A57&PID_0282
DeviceID_65=USB\VID_0789&PID_0162
DeviceID_66=USB\VID_0789&PID_0163
DeviceID_67=USB\VID_0789&PID_0164
DeviceID_68=USB\VID_2001&PID_3C09
DeviceID_69=USB\VID_0DF6&PID_003F
DeviceID_70=USB\VID_100D&PID_9031
DeviceID_71=USB\VID_100D&PID_9032
DeviceID_72=USB\VID_083A&PID_D522
DeviceID_73=USB\VID_2019&PID_AB24
DeviceID_74=USB\VID_1737&PID_0070
DeviceID_75=USB\VID_1737&PID_0071
DeviceID_76=USB\VID_0411&PID_00E8
DeviceID_77=USB\VID_0411&PID_0148
DeviceID_78=USB\VID_0411&PID_0150
DeviceID_79=USB\VID_14B2&PID_3C08
DeviceID_80=USB\VID_14B2&PID_3C11
DeviceID_81=USB\VID_07AA&PID_0041
DeviceID_82=USB\VID_07AA&PID_0042
DeviceID_83=USB\VID_1737&PID_0070
DeviceID_84=USB\VID_1737&PID_0071
DeviceID_85=USB\VID_8516&PID_2870
DeviceID_86=USB\VID_8516&PID_2770
DeviceID_87=USB\VID_1761&PID_0B05
DeviceID_88=USB\VID_0DB0&PID_821A
 
DeviceID_89=USB\VID_0DB0&PID_821A
 
 
[RT2070]
DeviceID_1=USB\VID_148F&PID_2070
DeviceID_2=USB\VID_8516&PID_2070
DeviceID_3=USB\VID_177F&PID_0254
 
[RT3070]
DeviceID_1=USB\VID_148F&PID_3070
DeviceID_2=USB\VID_2019&PID_AB25
DeviceID_3=USB\VID_07B8&PID_307x
DeviceID_4=USB\VID_07B8&PID_3071
DeviceID_5=USB\VID_14B2&PID_3C12
DeviceID_6=USB\VID_7392&PID_7711
DeviceID_7=USB\VID_083A&PID_7511
DeviceID_8=USB\VID_148F&PID_3071
DeviceID_9=USB\VID_148F&PID_3072
DeviceID_10=USB\VID_1740&PID_9703
DeviceID_11=USB\VID_1A32&PID_0304
DeviceID_12=USB\VID_1044&PID_800D
DeviceID_13=USB\VID_13D3&PID_3273
DeviceID_14=USB\VID_1EDA&PID_2310
DeviceID_15=USB\VID_07B8&PID_3072
DeviceID_16=USB\VID_0DF6&PID_003E
DeviceID_17=USB\VID_2001&PID_3C0A
DeviceID_18=USB\VID_0DF6&PID_0040
DeviceID_19=USB\VID_148F&PID_3572
DeviceID_20=USB\VID_1D4D&PID_000C
DeviceID_21=USB\VID_07D1&PID_3C0A
DeviceID_22=USB\VID_0586&PID_341A
DeviceID_23=USB\VID_1B75&PID_3072
DeviceID_24=USB\VID_083A&PID_A512
DeviceID_25=USB\VID_1737&PID_0078
DeviceID_26=USB\VID_0411&PID_015D
DeviceID_27=USB\VID_07D1&PID_3C0B
DeviceID_28=USB\VID_1740&PID_9705
DeviceID_29=USB\VID_1740&PID_9801
DeviceID_30=USB\VID_1740&PID_9706
DeviceID_31=USB\VID_0DB0&PID_6899
DeviceID_32=USB\VID_0DF6&PID_0041
DeviceID_33=USB\VID_0DF6&PID_0042
DeviceID_34=USB\VID_07D1&PID_3C0D
DeviceID_35=USB\VID_07D1&PID_3C0E
DeviceID_36=USB\VID_1D4D&PID_000E
DeviceID_37=USB\VID_5A57&PID_5257
DeviceID_38=USB\VID_5A57&PID_0283
DeviceID_39=USB\VID_04BB&PID_0944
DeviceID_40=USB\VID_04BB&PID_0945
DeviceID_41=USB\VID_0DB0&PID_3820
DeviceID_42=USB\VID_203D&PID_1480
DeviceID_43=USB\VID_1690&PID_0744
DeviceID_44=USB\VID_1690&PID_0740
DeviceID_45=USB\VID_0DF6&PID_0048
DeviceID_46=USB\VID_0DF6&PID_0047
DeviceID_47=USB\VID_1690&PID_0740
DeviceID_48=USB\VID_1690&PID_0744
DeviceID_49=USB\VID_13D3&PID_3284
DeviceID_50=USB\VID_07D1&PID_3C0F
DeviceID_51=USB\VID_0DF6&PID_004A
DeviceID_52=USB\VID_07D1&PID_3C15
DeviceID_53=USB\VID_5A57&PID_0284
DeviceID_54=USB\VID_203D&PID_14A1
DeviceID_55=USB\VID_20B8&PID_8888
DeviceID_56=USB\VID_0DB0&PID_821A
DeviceID_57=USB\VID_0DB0&PID_899A
DeviceID_58=USB\VID_0DB0&PID_3870
DeviceID_59=USB\VID_0DB0&PID_870A
DeviceID_60=USB\VID_203D&PID_14A9
DeviceID_61=USB\VID_13D3&PID_3305
DeviceID_62=USB\VID_0930&PID_0A07
DeviceID_63=USB\VID_0DB0&PID_3821
DeviceID_64=USB\VID_04BB&PID_0947
DeviceID_65=USB\VID_04BB&PID_0948
DeviceID_66=USB\VID_1740&PID_9707
DeviceID_67=USB\VID_1740&PID_9708
DeviceID_68=USB\VID_1740&PID_9709
DeviceID_69=USB\VID_083A&PID_A701
DeviceID_70=USB\VID_083A&PID_A702
DeviceID_71=USB\VID_07D1&PID_3C16  <- "D-Link DWA-125 Wireless N 150 USB Adapter(rev.A2)"
DeviceID_72=USB\VID_148F&PID_3370
DeviceID_73=USB\VID_1737&PID_0078
DeviceID_74=USB\VID_0DB0&PID_3822
DeviceID_75=USB\VID_0DB0&PID_822A
DeviceID_76=USB\VID_0DB0&PID_3871
DeviceID_77=USB\VID_0DB0&PID_871A
DeviceID_78=USB\VID_8516&PID_307x
DeviceID_79=USB\VID_8516&PID_3071
DeviceID_80=USB\VID_8516&PID_3072
DeviceID_81=USB\VID_8516&PID_3572
DeviceID_82=USB\VID_1D4D&PID_0010
DeviceID_83=USB\VID_05A6&PID_0101
DeviceID_84=USB\VID_0B05&PID_1790
DeviceID_85=USB\VID_0E66&PID_0013
DeviceID_86=USB\VID_083A&PID_A703
DeviceID_87=USB\VID_0789&PID_0166
DeviceID_88=USB\VID_13D3&PID_3307
DeviceID_89=USB\VID_13D3&PID_3321
DeviceID_90=USB\VID_07FA&PID_7712
DeviceID_91=USB\VID_0789&PID_0166
DeviceID_92=USB\VID_07D1&PID_3C17
DeviceID_93=USB\VID_083A&PID_A703
DeviceID_94=USB\VID_13D3&PID_3322
DeviceID_95=USB\VID_1B75&PID_3071
DeviceID_96=USB\VID_1D4D&PID_0011
DeviceID_97=USB\VID_0DF6&PID_0050
DeviceID_98=USB\VID_04BB&PID_0947
DeviceID_99=USB\VID_04BB&PID_0948
DeviceID_100=USB\VID_2019&PID_5201
DeviceID_101=USB\VID_0DF6&PID_0051
DeviceID_102=USB\VID_0B05&PID_166A
DeviceID_103=USB\VID_7392&PID_7722
DeviceID_104=USB\VID_0789&PID_0168
DeviceID_105=USB\VID_0DF6&PID_0053
DeviceID_106=USB\VID_7392&PID_4085
DeviceID_107=USB\VID_2001&PID_3C17
DeviceID_108=USB\VID_0DB0&PID_822B
DeviceID_109=USB\VID_0DB0&PID_871B
DeviceID_110=USB\VID_0789&PID_0169
DeviceID_111=USB\VID_148F&PID_F101
DeviceID_112=USB\VID_07B8&PID_3073
DeviceID_113=USB\VID_07B8&PID_3074
DeviceID_114=USB\VID_0DB0&PID_822C
DeviceID_115=USB\VID_0DB0&PID_871C
DeviceID_116=USB\VID_13D3&PID_3329
DeviceID_117=USB\VID_0DF6&PID_0060
DeviceID_118=USB\VID_0DF6&PID_0062
DeviceID_119=USB\VID_148F&PID_5370  <- Mine, called "802.11n USB Wireless LAN Card", a Generic Ralink Device.
DeviceID_120=USB\VID_148F&PID_3573
DeviceID_121=USB\VID_0586&PID_341E
DeviceID_122=USB\VID_0586&PID_343E
DeviceID_123=USB\VID_0DF6&PID_005F
DeviceID_124=USB\VID_050D&PID_1003
DeviceID_125=USB\VID_1690&PID_0761
DeviceID_126=USB\VID_13D3&PID_3365
DeviceID_127=USB\VID_1EDA&PID_2012
DeviceID_128=USB\VID_13D3&PID_3329
DeviceID_129=USB\VID_F201&PID_5370
DeviceID_130=USB\VID_050D&PID_1103
DeviceID_131=USB\VID_148F&PID_F301
DeviceID_132=USB\VID_0B05&PID_179D
DeviceID_133=USB\VID_0B05&PID_17A7
DeviceID_134=USB\VID_2001&PID_3C15
DeviceID_135=USB\VID_2001&PID_3C19  <- "D-Link DWA-125 Wireless N 150 USB Adapter(rev.A3)"
DeviceID_136=USB\VID_2001&PID_3C1B
DeviceID_137=USB\VID_148F&PID_5372
DeviceID_138=USB\VID_148F&PID_5572
DeviceID_139=USB\VID_3574&PID_0065
DeviceID_140=USB\VID_3574&PID_0066
DeviceID_141=USB\VID_3574&PID_0067
DeviceID_142=USB\VID_0B05&PID_17AD
DeviceID_143=USB\VID_7392&PID_7733
DeviceID_144=USB\VID_0789&PID_016B
DeviceID_145=USB\VID_2001&PID_3C1A
DeviceID_146=USB\VID_1690&PID_0761
DeviceID_147=USB\VID_0DF6&PID_0068
DeviceID_148=USB\VID_1B75&PID_7733
DeviceID_149=USB\VID_0E66&PID_0021
DeviceID_150=USB\VID_2019&PID_ED19
DeviceID_151=USB\VID_0DF6&PID_0065
DeviceID_152=USB\VID_0DF6&PID_0066
DeviceID_153=USB\VID_0DF6&PID_0067
DeviceID_154=USB\VID_0B05&PID_17D1
DeviceID_155=USB\VID_13B1&PID_003E
DeviceID_156=USB\VID_0E8D&PID_7610
DeviceID_157=USB\VID_148F&PID_7601
DeviceID_158=USB\VID_148F&PID_761A
DeviceID_159=USB\VID_7392&PID_B711
DeviceID_160=USB\VID_7392&PID_A711
DeviceID_161=USB\VID_148F&PID_760b
DeviceID_162=USB\VID_0E8D&PID_7603
DeviceID_163=USB\VID_0E8D&PID_7612
 
[RT2090]
DeviceID_1=PCI\VEN_1814&DEV_2090
 
[RT3090]
DeviceID_1=PCI\VEN_1814&DEV_3090
DeviceID_2=PCI\VEN_1814&DEV_3091
DeviceID_3=PCI\VEN_1814&DEV_3092
DeviceID_4=PCI\VEN_1814&DEV_3062
DeviceID_5=PCI\VEN_1814&DEV_3562
DeviceID_6=PCI\VEN_1814&DEV_3592
DeviceID_7=PCI\VEN_1814&DEV_3060
DeviceID_8=PCI\VEN_1814&DEV_3290
DeviceID_9=PCI\VEN_1814&DEV_5390
DeviceID_10=PCI\VEN_1814&DEV_539F
DeviceID_11=PCI\VEN_1814&DEV_5392
DeviceID_12=PCI\VEN_1814&DEV_3593
DeviceID_13=PCI\VEN_1814&DEV_5592
DeviceID_14=PCI\VEN_1814&DEV_5362
DeviceID_15=PCI\VEN_14C3&DEV_7630

This list has been taken from the HWID.ini from that software.
If your device isn't listed, it's either unsupported as AP or too new.

ASUS USB-N14 802.11n Wireless USB Adapter aka. USB\VID_0B05&PID_17E8
isn't listed for AP-mode here (if this list decides about it).
But the Driver provided by ASUS for it is the same as Ralink, but older (2013) and lacks the Ralink Utility.

I own this TL-WN823N adapter with the Realtek RTL8192CU-chipset.

Its realtek, dunno about SoftAp-Software yet.


I never thought solving a Homepass problem would come down to downloading drivers and match them up >_>

 

[Scytheri0n]

OKay, guys. If your Wifi has one of these Ralink Chipsets;
RT61
RT73
RT2860
RT2870
RT2070
RT3070
RT2090
RT3090

or is listed here with its USB\VID_XXXX&PID_XXXX pair

Not to be picky, but maybe for our less tech savvy users, explain what VID and PID stand for and how they can find the vendor/product IDs for their unit. I would do it but I'm lazy and you are doing a brilliant job of being the resident hardware guru

For the first two, should it maybe be RT61xx & RT73xx? To ease confusion ...

 

[Scytheri0n]

A. Of course.
B. Yes
C. Yes, I can see the WiFi-network and the HomePass-Macs.

My N3DS just doesn't get any StreetPasses. I just re-installed Windows 7 in my VM and at least the nzone.exe-method "technically" seems to work again, but I still don't get any StreetPasses. Or at least it takes 10x as long in comparison to my Old 3DS.

And the Debian-VM-method never worked at all. Not a single pass after several hours.

How stringent is your firewall on your network? Although I'm not running a VM or using Debian (I'm using OS X), I was testing out some changes to XZone and trying to troubleshoot a user's connectivity issue and I noticed that if I have my firewall enabled then my internet sharing goes to poop. Everything appears to be working but there's just no breakout. Is it possible that a firewall could be causing your issue since you say that the VM is broadcasting the (B)SSID?

Try briefly disabling your Windows firewall (if you use the bog standard Windows Defender firewall, or whichever AV firewall you use) and attempt it again. If it works, check your firewall settings to make sure they allow full access for your VM and related services. I've noticed with Windows Defender that sometimes after an update (of Windows or of other software) that another entry is added to the firewall list without full permissions and I end up having issues.

 

[MichiS97]

Hi, I haven't done any HomePassing lately but two months ago I was able to get it to work flawlessly by using the VMWare method. However, I wanted to try it out again for Tomodachi Life but it's not working anymore for some reason. I'm using the exact same USB WiFi Adapter as before, namely the TL-WN822N V2 by TP-Link, but it just doesn't work anymore.

This is about as far is it gets. I can't run the modinfo command because it says that it's an invalid command.
Like I said, it used to work a while back. That was actually the very first VMWare build back then but I seem to have deleted it from my PC for some reason and the new one just doesn't work anymore. Also, the LED of my WiFi Adapter stays off entirely but it recognises the adapter since the driver shows up when I run lsmod

 

[Liberty]

How stringent is your firewall on your network? Although I'm not running a VM or using Debian (I'm using OS X), I was testing out some changes to XZone and trying to troubleshoot a user's connectivity issue and I noticed that if I have my firewall enabled then my internet sharing goes to poop. Everything appears to be working but there's just no breakout. Is it possible that a firewall could be causing your issue since you say that the VM is broadcasting the (B)SSID? Try briefly disabling your Windows firewall (if you use the bog standard Windows Defender firewall, or whichever AV firewall you use) and attempt it again. If it works, check your firewall settings to make sure they allow full access for your VM and related services. I've noticed with Windows Defender that sometimes after an update (of Windows or of other software) that another entry is added to the firewall list without full permissions and I end up having issues.

Apart from Windows Defender I do not use anything that could be even remotely labeled as a firewall and everything worked on my O3DS. So I didn't change anything regarding my configuration. What puzzles me the most is that non of the Debian-VMs are working because Linux doesn't offer restricted drivers, like Windows does. I'll stick with nzone.exe for now, because at least I get some StreetPasses, but still, it's a very confusing situation.

 

[Syphos]

Not to be picky, but maybe for our less tech savvy users, explain what VID and PID stand for and how they can find the vendor/product IDs for their unit. I would do it but I'm lazy and you are doing a brilliant job of being the resident hardware guru

For the first two, should it maybe be RT61xx & RT73xx? To ease confusion ...

Ever seen an RT61XX?

Here is an explaination about...

Spoiler

Each device you buy (even generic) has a XXX\VEN_YYYY&DEV_ZZZZ pair.
USB = The type of connection, can also be PCI for buildin card or AGP or else.
VID = Vendor ID, these are unique to a vendor, like D-Link, ASUS, and so on.
PID = Product ID, these are unique per product. Identical devices have identical values.

A driver detects an device by its XXX/YYYY/ZZZZ pair.
(Or the other way around, a driver will only install, if such an device is present.)

Usually Firms buy stuff, rename it (also known as "branding" ) and sell it back to ya.
Sometimes they won't even put effort in it to change the VID/PID pair, so the "original" driver will work.
If they make their own device, they use known and widely-distributed chips, so they are sometimes compatible to another.

To find your VID/PID, open "Device Manager", search for your device, open its properties and look for "Details".
(I am on WinXP, so there will be difference in finding it, but its in that "properties" window.)


How it looks like:

 

[Scytheri0n]

Ever seen an RT61XX?

I meant those xx's as placeholders since RT61 seems a little too short for a model number But I concede to your point ...

 

[MichiS97]

Can somebody recommend me a USB WiFi Adapter that's guaranteed to work with the VMWare method? I own a TP-Link TL-W822N V2 and it used to work on the very first VMWare image duke_srg posted on here but I seem to have deleted it from my hard drive for some reason and the new image just doesn't work for me anymore. It recognizes the adapter and shoes the correct driver when I use lsmod | grep mac80211 but it doesn't start the hotspot. The furthest I get is this screen:

It really annoys me since it used to work flawlessly...