@Drummerboy Did you start WirelessManager? This is the process step-by-step:
1., you make a Wireless.prefs file which you think should work. 2., start WirelessManager from shell. Wait until it prints some lines to the shell window, which indicates it found the desired SSID and successfully connected to it. This can take up to 30 seconds (or more with slow CPUs). 3., if it fails to connect to the SSID you specified, press CTRL-C to exit WirelessManager, and tweak Wireless.prefs until it works. :) 4., if WirelessManager connected *THEN* press Online button in MiamiDx, to connect the TCP/IP layer of the network. 5., If it works, add the required WirelessManager line to s:user-startup, or make some shortcut script to start it when desired.
Few notes. - WirelessManager is part of prism2v2 package on Aminet, get it if you don't have it yet. You also need to update the SANA-II driver to the version which is found in this package. - the whole wireless connection thing is one level BELOW your TCP/IP stack, which will know nothing about it. Think the WirelessManager connecting as plugging in the cable on a wired network. - I don't recommend running WirelessManager all the time, because it's a CPU hog, especially with machines using a slow CPU (anything less than a '060, really), since it does all the WPA encryption/decryption which is normally done by the network hardware all by software on the main CPU (because your old network card which works in the Amiga can't support WPA by hardware). So only start it before you go online.
... I should really wrote a tutorial about this, with screenshots... This is roughly the 15th time I try to explain these things to someone... :) _________________ MorphOS, classic Amiga, demoscene, and stuff "When a bridge is not enough, build a Viaduct!" "Strip the Amiga community of speculation and we can fit every forum on a 720k floppy" (by resle) |