Welcome, Guest. Please login or register.

Author Topic: Getting online with PiStorm32, Miami DX and Encrypted WiFi  (Read 138 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline AndyFCTopic starter

Getting online with PiStorm32, Miami DX and Encrypted WiFi
« on: April 28, 2024, 01:07:20 PM »
Here are the steps I took to be able to browse using the new WiFiPi wireless network driver, and Miami DX.

Version 0.1: First version to document my experiences - still finding and fixing typos

Downloads:
Emu68Tools from 23 April: https://github.com/michalsc/Emu68-tools/releases/download/nightly/Emu68-tools-20240423-75ea45.zip
Emu68 release 1: https://github.com/michalsc/Emu68/releases
Prism2v2: https://aminet.net/driver/net/prism2v2.lha
MiamiDX (demo): https://aminet.net/comm/tcp/MiamiDx10cmain.lha and https://aminet.net/comm/tcp/MiamiDx10c-MUI.lha (I already had this up and running with a 3COM PCMCIA card)

The info for where to copy the files is based on Michal Schultz's post: https://www.patreon.com/posts/wi-fi-alpha-102261532

Set up the Wireless network driver
1: Unpack Emu68 tools
2: Copy file Emu68-WiFi/Devs/Networks/wifipi.device to DEVS:Networks
3: Copy the whole folder emu68/WiFi/Devs/Networks/Firmware to Devs: (so you end up with Devs:Firmware containing a series of txt, bin and clm_blob files) NOTE: I didn't have the Devs:Firmware folder to start with but some of you might)
4: Unpack Prism2v2.lha you can choose to run the installer or copy some files manually

IF MANUAL
5: Copy Wirelsssmanager to C:
6: Create a text file in Envarc:sys/ called wireless.prefs
7: Add the lines
network={
     ssid="<name of your wireless network>"
     psk="<your network passphrase>"
}
8: Save the file
9: Reboot

IF USING THE INSTALLER:
5: Use expert mode
6: Choose 'No' when asked to install firmware for the Hermes chipset
7: Choose 'Yes' to set wireless preferences
8: Enter you wireless network name and password when prompted
9a: Choose whether or not to start WirelessManager automatically (it's up to you - see 'Observations' at the end)
9b: Finish the install and reboot

What's the difference between the two?
The process using the installer creates an encrypted version of the wireless password and uses that instead of the open text version. Handy if you don't want your password saved in plain text on your Amiga.
My personal experience is that I couldn't connect after setting up the wireless.prefs file manually, I would just get a timeout. Users Lemaru and Shaytam on the PiStorm discord assured me it should work without the encrypted PSK, so I uncommented the plain text line and commented out the encrypted line, rebooted and it then worked. The timeout was probably not related to the setup method I used (I have an old house with thick brick internal walls and Wifi can sometimes drop).

STARTING THE NETWORK
10: If you chose to use the installer and start automatically, and all being well, the wifipi.device should have been initialised on reboot.
11: If you have chosen the manual route open up a Shell and enter 'Wirelessmanager wifipi.device' - after a few seconds you hopefully get confirmation that you are associated with a MAC address, key negotiation is completed and CTRL-EVENT-Connected ie you're connected to the access point.

Configuring MiamiDX (Note I already use MiamiDX with a PCMCIA card and copied the original settings)
12: If not already done, install MiamiDX
13: Run and open up Hardware > New
14: Give it a name e.g. WiFiPi
15: Type of driver should default to SANA-II driver (if not change it to that)
16: In Driver enter DEVS:Networks/wifipi.device
17: Open SANA-II parameters
18: Choose 'Query Device' - the settings should auto-complete.
19: Choose OK to close the SANA-II parameters screen and again to close the Hardware Definition Screen
20: Choose Interfaces from the MiamiDX menu
21: Choose 'New'
22: My settings are:
 - Name: eth1
 - Alias: WiFiPi
 - Type: Ethernet
 - Hardware: (whatever you called the interface in step 14)
 - Priority: 10
 - IP type: Static
 - IP Address: something relevant to my network
 - Netmask Type: Static
 - Netmask: 255.255.255.0 (pretty common)
 - Gateway Type: static
 - Gateway: ip address of my router
 - Multicasts: disabled
 - Multicast pri: 0
 - Control panel: ticked
 - GUI default: unticked
 I don't have any Auto-connect/disconnect settings or Manual routes/aliases
TCP/IP settings:
 - Use ICMP: ticked
 - Fake IP: unticked
 - Get dynamic hostame, priority: 0
 - Get dynamic DNS servers: Ignore
 - Preferred offline state: Suspended
 - Get time: unticked
 - DHCP Enable: Ticked
 - Send hostname in request: Ticked
 - Host Name: Something you want to identify your Amiga on if looking in your router interface
23: OK to close the Interface TCP/IP Settings Window and again to close the Interface Definition Window
24: Right-click and choose 'Save' from the Settings menu

Now to test:
25: In MiamiDX, and the Interfaces section, select your newly created Interface and select 'Online'

Observations:
I Use Tinymeter and as soon as I run wirelessmanager the CPU drops to around 30%-33% free, so I'm going to continue to run this manually for now, only when I want to go online.
If you make any changes to the wireless.prefs file reboot for them to take effect.
« Last Edit: April 28, 2024, 01:39:58 PM by AndyFC »
A1200 in DIY Tower. 3.2 ROMs (softkicking 3.2.2), OS 3.2.2 with ClassicWB, CF card, CD RW and IDE to SD adapter running off the internal IDE port (using the A4000 4-port IDE adapter from Amigakit), Pistorm 32 lite with Pi4/2GB/Emu68 or Blizzard 1230-IV, with 32MB 60ns RAM and 50MHz 68882 FPU. 3COM PCMCIA Network card running with Miami DX.
MorphOS on PowerMac G5 and ATI 9600 pro