Tutorial  Updated

Create an NDS-Compatible Hotspot on Linux

I'm creating this tutorial because this is a much better solution than using an old version of Windows or using Mobile Data for this functionality.

Requirements
  • Linux-compatible Wireless Adapter (WiFi Card)
  • Linux Distribution of your choosing (I'm using SteamOS for this tutorial)
  • Nintendo DS or Sony PSP
  • linux-wifi-hotspot installed
  • NDS users: nds-constraint DNS

Steps to achieve
  1. Open a terminal window and type or paste the following text:

    Code:
    wihotspot

    1665515112770.png


    OR simply launch "Wifi Hotspot" from your Applications Menu.

  2. After entering that text, a GUI window will appear. In this Window, set an SSID (Hotspot name) and click the box that says Open.

    1665515197302.png


  3. After setting your Hotspot to Open, it's important to do one or both of the following in the Advanced settings: Set your Hotspot to Hidden and/or add your console's MAC address to the Mac Filter text box.

    1665515308305.png


  4. Once you've done the above steps, you can now click "Create Hotspot" at the bottom to turn on your new hotspot!

    1665515420723.png


    If all is well, you will now see a PID to indicate that your hotspot is live and you can connect via the Nintendo DS or Sony PSP by inputting the SSID in a New connection.

    1665515510778.png


    The Connected devices list will populate when you run a connection test, like below:

    1665515572348.png
Congratulations, you've made your hotspot. You can now always launch this hotspot, which is now saved to your system by running the following in your terminal once again :)

Code:
wihotspot

You can also simply launch "Wifi Hotspot" from your Applications Menu.

Note: Whitelisting MAC addresses is the only way to be completely safe from other people connecting to your Hotspot. It is highly recommended that you do this.
 
Last edited by AkikoKumagara,
How did you install it on your steam deck please send up tutorial
If you're asking me, I didn't, but it may be possible. It depends on the capabilities of the Steam Deck's wireless NIC, which I have no knowledge of. My tutorial was made on a desktop with an Intel AX200 Wireless NIC.
 
Any advice for me?
If your settings match those in my screenshot and it still doesn't work, I don't really know what the problem is. It's likely an issue with Linux Wifi Hotspot. It may be worth trying the old version of this tutorial, which manually creates a WEP hotspot using NetworkManager.
 
If your settings match those in my screenshot and it still doesn't work, I don't really know what the problem is. It's likely an issue with Linux Wifi Hotspot. It may be worth trying the old version of this tutorial, which manually creates a WEP hotspot using NetworkManager.

Yeah, I did that too. When I do the old version I can get a WEP hotspot running and all my other devices can find and recognize the hotspot as a WEP hotspot but my DS and 3DS can't.

I did manage to get Linux Wifi Hotspot working after using the command line, then the GUI application started to work, however like the old method my DS and 3DS can't fond the hotspot.
 
Yeah, I did that too. When I do the old version I can get a WEP hotspot running and all my other devices can find and recognize the hotspot as a WEP hotspot but my DS and 3DS can't.

I did manage to get Linux Wifi Hotspot working after using the command line, then the GUI application started to work, however like the old method my DS and 3DS can't fond the hotspot.
Maybe there's something weird about your wireless adapter's broadcasting that makes it incompatible with the NDS/3DS. That'd be where I'd start investigating.
 
How
Yeah, I did that too. When I do the old version I can get a WEP hotspot running and all my other devices can find and recognize the hotspot as a WEP hotspot but my DS and 3DS can't.

I did manage to get Linux Wifi Hotspot working after using the command line, then the GUI application started to work, however like the old method my DS and 3DS can't fond the hotspot.
How did you install this on steam deck? Doesn't work for me
 
  • Like
Reactions: orangy57
I'm creating this tutorial because this is a much better solution than using an old version of Windows or using Mobile Data for this functionality.

Requirements
  • Linux-compatible Wireless Adapter (WiFi Card)
  • Linux Distribution of your choosing (I'm using SteamOS for this tutorial)
  • Nintendo DS or Sony PSP
  • linux-wifi-hotspot installed
  • NDS users: nds-constraint DNS

Steps to achieve
  1. Open a terminal window and type or paste the following text:

    Code:
    wihotspot

    View attachment 331441

    OR simply launch "Wifi Hotspot" from your Applications Menu.

  2. After entering that text, a GUI window will appear. In this Window, set an SSID (Hotspot name) and click the box that says Open.

    View attachment 331442

  3. After setting your Hotspot to Open, it's important to do one or both of the following in the Advanced settings: Set your Hotspot to Hidden and/or add your console's MAC address to the Mac Filter text box.

    View attachment 331444

  4. Once you've done the above steps, you can now click "Create Hotspot" at the bottom to turn on your new hotspot!

    View attachment 331445

    If all is well, you will now see a PID to indicate that your hotspot is live and you can connect via the Nintendo DS or Sony PSP by inputting the SSID in a New connection.

    View attachment 331446

    The Connected devices list will populate when you run a connection test, like below:

    View attachment 331447
Congratulations, you've made your hotspot. You can now always launch this hotspot, which is now saved to your system by running the following in your terminal once again :)

Code:
wihotspot

You can also simply launch "Wifi Hotspot" from your Applications Menu.

Note: Whitelisting MAC addresses is the only way to be completely safe from other people connecting to your Hotspot. It is highly recommended that you do this.
Wasted hours of my time trying to get a worthless subsystem and It is so close and installed but still won't launch WHAT ABOUT WINDOWS?!?!?
 
  • Haha
Reactions: SylverReZ
Wasted hours of my time trying to get a worthless subsystem and It is so close and installed but still won't launch WHAT ABOUT WINDOWS?!?!?
Figure it out and make a tutorial. This isn't for Windows or WSL, and I make that clear in both the thread title and the actual tutorial. Don't be angry at me, I didn't falsely advertise this.
 
  • Like
Reactions: SylverReZ
Figure it out and make a tutorial. This isn't for Windows or WSL, and I make that clear in both the thread title and the actual tutorial. Don't be angry at me, I didn't falsely advertise this.
:(
Post automatically merged:

Figure it out and make a tutorial. This isn't for Windows or WSL, and I make that clear in both the thread title and the actual tutorial. Don't be angry at me, I didn't falsely advertise this.
I thought it would work for WSL but I don't know Linux and I tried and it said it needed dependencies but I didn't know what to do and luckily you said it just didn't work. also it doesn't say that it doesn't work for WSL on the tutorial.
 
I thought it would work for WSL but I don't know Linux and I tried and it said it needed dependencies but I didn't know what to do and luckily you said it just didn't work. also it doesn't say that it doesn't work for WSL on the tutorial.
Why would I specify it NOT working for platforms it's not intended for? This is a Linux tutorial. Do I have to say it won't run on your refrigerator, too?

WSL ≠ A full Linux-based operating system. If you don't know this, that's really not my fault. Again, this tutorial states in the requirements that you need a Linux operating system, not WSL, not a virtual machine, not Windows.

If you're not willing to use a Linux-based operating system, this method is not for you.
 
  • Like
Reactions: SylverReZ
I didn't read the all the replies to this thread before writing this, so sorry if anyone has mentioned this in advance.

Looks like your mileage may vary heavily. Apparently it's rare for AP (master) mode to be supported with various wifi adapters under Linux. Some cards that used to support it even have hardware silently changed under the same model name to not support it later.

I dug out my old laptop for shits and grins that has an Intel Centrino N1000 (historically a shit wireless card under Linux IME). Some old internet threads say that you can apparently set up a hotspot with it in Windows (7), but the iwlwifi drivers in Linux don't support it.

If you've got a Linux system, save yourself some trouble and check if your wifi adapter supports AP mode via iw list | less, and see if AP is listed under supported modes. If not, it won't work. You need hardware that supports it to have a shot.

The Marvell 88W8897 on my main computer supports AP mode in Linux. I guess I'll try this one next. Can't say I am particularly thrilled about that though, but then nobody is thrilled about running an open wifi access point for anything (WEP may as well be the same as open, practically).

Thanks for the tutorial! I didn't know about linux-wifi-hotspot.
 
I think my motherboard’s built in Realtek Wifi adapter is not compatible at all with this. I tried both this method and the one on archive, and neither of them worked. For the new method, I was unable to put any option for Wi-Fi interface, and for the archived one, I don’t have the option to do WEP security. Either it’s my motherboards Wi-Fi adapter, or it’s my router.
Post automatically merged:

I just tried with an HP Laptop that's older than 2020, but it still has the Wifi interface option greyed out.
Post automatically merged:

I also tried the archived method with the laptop, the same thing. I can't select WEP.
 
Last edited by Readmit,
First I want to congratulate you for this simple and useful tutorial. and see how people who don't know/use linux come to complain that it doesn't work on Windows/WSL, just be patient

I would like to add that, if you are only connected through wifi, you select as wifi interface and internet interface the same wifi card and you get an error.
Try disconnecting from the wifi signal (do not turn off the wifi in configuration, just disconnect it from the signal) and use another interface for the internet interface (it can be an Ethernet connection or a cell phone that can share internet through USB) and try again.

This happened to me because I have an old laptop (with Debian / Gnome) that I use for some simple servers. Apparently the wifi card it has is not able to create a wifi signal while it is connected to one. So after some tests, I thought of that method and it worked. I don't know how many people found this to work, as it was mostly intuitive since linux-wifi-hotspot doesn't specify the errors very well

Note, I don't know if you mentioned it in the previous version of the tutorial, but nds-constraint DNS is not used in this version even though you mention it. If it's not necessary you could remove it or put it at the end in case it was used in certain situations.
 
  • Like
Reactions: NitroShell
How do you setup the dependencies on SteamOS? I've been trying but nothing makes sense (sorry I'm horrible at things like this)
 
How do you setup the dependencies on SteamOS? I've been trying but nothing makes sense (sorry I'm horrible at things like this)
I haven't got experience with SteamOS on a Steam Deck and can't guarantee it will work (as far as hardware support is concerned), but it should be as simple as installing and using an AUR helper, such as `yay`, to download and install wihotspot.

Code:
yay -S linux-wifi-hotspot

If you're still having dependency issues afterwards, individually install the dependencies, as needed, listed on the git repo.
 
I am having trouble successfully testing connection on my DS lite with Pokemon Pearl (authentic) using this method.

for reference I'm using a DS lite with DNS set to manual at many different DNS servers online like wiimfi, and wihotspot wifi interface "wlp4s0". I'm also using a fresh install of Linux Mint

When I click test connection the connection symbol will hold green for a while then will get either error 52100, 20100 or 20110 depending on if i set secondary DNS to wiimfi servers instead of 8.8.8.8, or if im not auto obtaining IP address ( I'm not sure if im doing this setting right i have ip set to 192.168.12.31, subnet 0.0.0.0, and gateway 192.168.12.1 although i have tried gateway as the same as DNS and subnet as 255.255.255.0

I've tried restarting everything and clearing configs and just about everything i could find online about this and still can't get it to connect.

Is there anything else I should try? I'm not very experienced in anything networking
Hi did you ever fix this? I'm having the same issue. (Using the old tutorial, wihotspot loads forever if I try to do it through that) Strangest part is that wihotspot used to just work fine but something must have happened in an update.
 

Site & Scene News

Popular threads in this forum