Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: Sutty100 on June 28, 2012, 06:41:17 PM
-
So... I have installed the drivers for my Amigakit PCMCIA Wireless networking card and installed Easynet. I have entered in my network details which I am fairly confident are correct. Turned off security on my router just to test...but nothing! I am unable to ping the router or my pc.
What makes me worried is that the green light on the card is solid until I connect then starts flashing but after to that never stops flashing even if I disconnect and close Easynet.
Any help would be appreciated spent ages last night getting nowhere!
-
My setting config help is:
Version =
File Size = 414792
badsocket.lobrary = 3.28
Network Settings
Your IP adddress = 192.168.0.2
Network Mask = 255.255.255.0
Router/Gateway IP = 192.168.0.1
Network Domainname = virgin.net
Domain Name Servers
Primary DNS = 194.168.4.100
Secondary DNS 194.168.0.100 (In use)
Tertiary DNS =
Network Interface
Device = prism2.device (version 1.7 Installed)
Unit Number = 0
Wireless Settings = C:SetPrism2Defaults SSID ":-)" (version 1.2 installed)
Library = pccard.library (version 1.1 installed)
TCPIP Settings
MBUF_CONF_MAXMEM = 256K
Use Loopback = YES
Debug SANA = No
Gateway Mode = Yes
Hosts
192.168.0.1 router myrouter
Assigns
Assign AmiTCP "Workbench:Programs/Easy Net/AmiTCP
END OF REPORT
-
Is this smiley really the SSID of your WLAN?
-
Is this smiley really the SSID of your WLAN?
Yeah although I might change it to a :-( at this rate!
-
A flashing light on the wireless card means that it is not acquiring the wireless signal or that the SSID is not found.
-
";-)" is not a valid SSID, though manufacturers vary on it a bit.
Google acceptable SSID characters/limits and come up with something different, see if that works.
An excerpt from RFC:
Also: The following six characters are not allowed: ?, ", $, [, \, ],
and +. In addition, the following three characters cannot be the first
character: !, #, and ;.
-
And if you left SSID blanc, it just connectes first available nonsecured network
-
";-)" is not a valid SSID, though manufacturers vary on it a bit.
Google acceptable SSID characters/limits and come up with something different, see if that works.
An excerpt from RFC:
Also: The following six characters are not allowed: ?, ", $, [, \, ],
and +. In addition, the following three characters cannot be the first
character: !, #, and ;.
I did change it to amiga because I did wonder about it still didn't have any luck. I will try leaving it blank and see how I get on with that.
-
Ok so... I tried to leave teh ssid blank but then OK greys out so don't think I can do that. I am using classic workbench so I don't know if that comes with some files already there which might be conflicting?
Also quite often the amiga will lock up when connecting the light on the wifi card then stops flashing and goes solid.
-
Maybe you need to try the HARD way and install AmiTCP by hand.
Use this guide http://amigarealm.whdownload.com/archives/~patrikax/amiga/guides/AmiTCP_Install/ (http://amigarealm.whdownload.com/archives/%7Epatrikax/amiga/guides/AmiTCP_Install/)
The author is using PCMCIA Ethernet card, so instead using CNET device, just use Prism device.
Use the Prism2V2 for the driver and edit the wireless config file by hand. Read the docs for the prism2v2 how to edit the config file.
Make sure that the Wireless manager command in user-startup goes first before TCPIP.
-
Maybe you need to try the HARD way and install AmiTCP by hand.
Use this guide http://amigarealm.whdownload.com/archives/~patrikax/amiga/guides/AmiTCP_Install/ (http://amigarealm.whdownload.com/archives/%7Epatrikax/amiga/guides/AmiTCP_Install/)
The author is using PCMCIA Ethernet card, so instead using CNET device, just use Prism device.
Use the Prism2V2 for the driver and edit the wireless config file by hand. Read the docs for the prism2v2 how to edit the config file.
Make sure that the Wireless manager command in user-startup goes first before TCPIP.
I can't find the config file the file path makes no sense to me! 'ENVARC:Sys/Wireless.prefs'
Where is my sys folder? And what is ENVARC?
-
I never had any success with easynet.
I would advise abandoning easynet and jumping aboard the good ship MiamiDx
-
Just use Miami.
-
I can't find the config file the file path makes no sense to me! 'ENVARC:Sys/Wireless.prefs'
Where is my sys folder? And what is ENVARC?
The way I do it is this way:
Open shell/cli
Type: ed a
file>open click Volumes, choose ENVARC, then SYS, fined wireless.prefs.
Edit file per your requirement, read the prism2v2 manual before editing.
-
Just use Miami.
The amitcp is not that hard if you follow my previous guide link.
So, to get the wireless working you only need Amitcp and prism2v2 driver, and a little headache. But.., that's all.
-
Aye, AmiTCP is pretty simple with all the guides out there, but maybe a little over this fellows head atm, which is why I recommended Miami.
-
Ok so I followed the guide and now I can't boot to workbench unless I comment out the AmiTCP stuff in the user startup.
I get an error openDevice: Device or unit failed to open
Any advice on that one!?
To use Miami will I need to remove AmiTCP? I believe classic workbench has the installer for miami already on it?
-
Easynet drove me up the wall!! yes i think you should remove amitcp and have a fresh start with miami
Here is a link to setting up Miami dx:
http://www.amibay.com/showthread.php?t=24984
(especially useful at the end with the pics)
:)
-
No luck with Miami either! Could it be to do with my Indivison ACA Mk2 accelerator card? I inserted the line Run <>NUL: C:WirelessManager prism2.device
and then after this Miami has inserted assign Miami.
In my wireless Manager file I have
network={
key_mgmt=NONE
}
Which should search for an network which does not have security.
After the Amiga boots I run the Miami wizzard but it does not Detect the settings of the network and the wireless card just keeps blinking. It does not start blinking until Miami starts trying to detect settings.
Thinking of sending it back at the moment spent forever trying to get it working!
-
Here are some files from my configuration.
Some lines like IP, name and key, you need to change.
Maybe if you send me your files, we can look them over.
-
Hi,
Thanks for your help I have attached my files. I don't have a netDB-myhosts where did you place that file? Is it other computers on your network?
I have commented out the AmiTCP statements now but when I did have them uncommented they were in the format they are now.
-
In the interfaces file change the prism line to this:
prism dev=devs/networks/prism2.device
(I did it this way: prism dev=devs:networks/prism2.device and it did not work, I'm not sure why)
==============================
In the wireless.prefs do this:
network={
key_mgmt=NONE
}
==============================
In startnet (in my startnet example ignore the wep key stuff it was copy paste stuff mistake):
remove: AmiTCP:bin/login -f amiga_user
works fine w/o it in my setup.
==============================
Create the file netdb-myhost, its should be in the amitcp/db folder, you can open the example file and add your settings. (Nameserver is your DNS server):
; This host
HOST 192.168.1.12 amiga.something.com amiga
; Domain names
; Name servers
NAMESERVER 156.154.70.1
NAMESERVER 156.154.71.1
==============================
In the user-startup:
Remove AmiTCP:bin/startnet
==============================
when your amiga starts, make sure that the wireless card is plugged in. during the statup watch the power led turn on, this is when this command starts in user-startup: Run <>NIL: C:WirelessManager prism2.device
The active light should blink once in awhile.
I like to start the Amitcp by hand not automaticly, and it's good to start it manually for troubleshooting. You can do that from CLI, just type startnet before using internet.
Before you do startnet try to do this in CLI: ifconfig prism0 192.168.0.11 netmask 255.255.255.0
If there is no error then the rest should work.
-
";-)" is not a valid SSID, though manufacturers vary on it a bit.
Google acceptable SSID characters/limits and come up with something different, see if that works.
An excerpt from RFC:
Also: The following six characters are not allowed: ?, ", $, [, \, ],
and +. In addition, the following three characters cannot be the first
character: !, #, and ;.
Which RFC? The 802.11 standard says that an SSID can include any byte values, including unprintable ones. Any limitations on accepted characters are due to bugs. Having said that, such bugs definitely exist in various routers etc., so it's wise not to stress them by using odd characters.
-
I'm afraid that EastNet simplifies setting up AmiTCP v 3.0b; it does not help with the hardware all that much, in fact it took me 2 months to get online and only works on OS 3.x (they leave this out). After more than several emails I sent went unanswered by Amigakit's support staff (over a 2 moth period) I finally got some help. The next issue for me was connecting my 2 network printers so I could print; they never answered this one. I finally got all of MiamiDX downloaded and setup so 2.5 months after I started I could surf and print via my home network.
Here are a few hints: there is a downloadable key file for MiamiDX, if you have USB support, then a USB Ethernet dongle sets up easier than any other (for wireless, get a ZuniDigital wireless bridge -- Newegg on sale for not that much, I just bought another for 25 salad leaves US). Read through Amibay's help site for setups. If there is an area that doesn't work for you there are alot of folks out there to help.
-
In the interfaces file change the prism line to this:
prism dev=devs/networks/prism2.device
(I did it this way: prism dev=devs:networks/prism2.device and it did not work, I'm not sure why)
==============================
In the wireless.prefs do this:
network={
key_mgmt=NONE
}
==============================
In startnet (in my startnet example ignore the wep key stuff it was copy paste stuff mistake):
remove: AmiTCP:bin/login -f amiga_user
works fine w/o it in my setup.
==============================
Create the file netdb-myhost, its should be in the amitcp/db folder, you can open the example file and add your settings. (Nameserver is your DNS server):
; This host
HOST 192.168.1.12 amiga.something.com amiga
; Domain names
; Name servers
NAMESERVER 156.154.70.1
NAMESERVER 156.154.71.1
==============================
In the user-startup:
Remove AmiTCP:bin/startnet
==============================
when your amiga starts, make sure that the wireless card is plugged in. during the statup watch the power led turn on, this is when this command starts in user-startup: Run <>NIL: C:WirelessManager prism2.device
The active light should blink once in awhile.
I like to start the Amitcp by hand not automaticly, and it's good to start it manually for troubleshooting. You can do that from CLI, just type startnet before using internet.
Before you do startnet try to do this in CLI: ifconfig prism0 192.168.0.11 netmask 255.255.255.0
If there is no error then the rest should work.
Ok so I have changed those files so they are the same as yours except things like IP address. So now I can boot into workbench. But if I try startnet I get an error that this file is not executable.
And if I try the ifconfig I get AmiTCP/IP version 3 or later should be started first!
Also the LED on the wireless card remains solid!
Still at least workbench now starts!
Cheers for all your help so far though! :-)
-
Ok so I have changed those files so they are the same as yours except things like IP address. So now I can boot into workbench. But if I try startnet I get an error that this file is not executable.
And if I try the ifconfig I get AmiTCP/IP version 3 or later should be started first!
Also the LED on the wireless card remains solid!
Still at least workbench now starts!
Cheers for all your help so far though! :-)
Didn't realise I had to vavigate to the directory startnet was in and type Execute Startnet.
The output I get is as follows: ifconfig loctl (SIOCGIFFLAGS): no such interface
add host amiga.something.com: gateway locachost
add net default gateway 192.168.0.1 network is unreachable
I also get an AmiTCPIIP log that the device or unit failed to open
Is it a problem that I have AmiTCP installed on a different partition to where the prism2 driver is?
-
Most commonly AmiTCP does not store the location of you driver in its db/interfaces and, if using EasyNet, in the EasyNet.cfg file. Make sure they point directly to your NIC device (xxx.device) driver. It does care about much else if the dhcp is set properly. MiamiDX will set your IP address, mask and router IP address automatically; EasyNet doesn't do dhcp as easily.
-
Didn't realise I had to vavigate to the directory startnet was in and type Execute Startnet.
The output I get is as follows: ifconfig loctl (SIOCGIFFLAGS): no such interface
add host amiga.something.com: gateway locachost
add net default gateway 192.168.0.1 network is unreachable
I also get an AmiTCPIIP log that the device or unit failed to open
Is it a problem that I have AmiTCP installed on a different partition to where the prism2 driver is?
Another update! The LED does now blink once at startup. When I go to execute startnet I no longer get the can't open device (I changed the interfaces file to look into the Workbench: partition. But the host is still unreachable and ifconfig loctl (SIOCGIFFLAGS): no such interface.
I feel I am getting closer! Maybe...
-
You get this error: ifconfig loctl (SIOCGIFFLAGS): no such interface , because this command does not work: prism dev=devs/networks/prism2.device
I had exactly same problem. Maybe change the prism line to: prism dev=devs:networks/prism2.device
Check if the prism2.device is in Devs/Networks folder and play with the path.
Edit: When you get error when executing startnet, try this command: ifconfig prism0 192.168.0.11 netmask 255.255.255.0
When this one is not working: prism dev=devs:networks/prism2.device , this one will fail: ifconfig prism0 192.168.0.11 netmask 255.255.255.0
-
You get this error: ifconfig loctl (SIOCGIFFLAGS): no such interface , because this command does not work: prism dev=devs/networks/prism2.device
I had exactly same problem. Maybe change the prism line to: prism dev=devs:networks/prism2.device
Check if the prism2.device is in Devs/Networks folder and play with the path.
Edit: When you get error when executing startnet, try this command: ifconfig prism0 192.168.0.11 netmask 255.255.255.0
When this one is not working: prism dev=devs:networks/prism2.device , this one will fail: ifconfig prism0 192.168.0.11 netmask 255.255.255.0
I have tried all sorts of paths but it just wont find it I don't understand what the path could be! I have it located on a different partition to Amitcp Workbench:devs/networks/prism2.device Also the network card no longer flashes on startup!
Going backwards again now! Ah dear!
-
Which RFC? The 802.11 standard says that an SSID can include any byte values, including unprintable ones..
Might be older information? It used to be in the the 802.11 standard:
http://www.wirelessforums.org/alt-internet-wireless/ssid-33892.html
Specifically, IEEE 802.11-1999 7.3.2.1
I've found that wording in Cisco Aironet and Intel PDFs online.
My guess is, even if it's been changed, many devices are using the older standard and/or older firmware which uses the older standard.
desiv
-
@desiv
I don't think the standard has changed. The general gist of that thread is that Cisco et al. specified additional restrictions to suit their buggy firmware.
But I agree that that means the defacto standard disallows certain characters. In the real world, it's best to use only alphanumeric characters to be safe.
-
@Sutty100
You should check first if a wireless connection is being made. Temporarily disable WirelessManager from starting at boot, then try this in a shell:
WirelessManager prism2.device verbose
-
I noticed that if you don't start the wireless manager, the TCPIP will work and you can ping yourself, just not the gateway. Basicaly the over the air link won't work.
One thing I don't know, what is this for? Library = pccard.library (version 1.1 installed)
-
One thing I don't know, what is this for? Library = pccard.library (version 1.1 installed)
prism2.device needs it to parse the card's information.
-
So... I have installed the drivers for my Amigakit PCMCIA Wireless networking card and installed Easynet.!
I have the same card. It works just fine on my A1200 030 but on A600 3.1 ACA020 doesn't even flash LEDs. I copied A1200's OS just if I forgot something on settings but no luck. I think it's a PCMCIA prob for me and I have nothing else hardware to test the socket :-(
-
My best software buy in years is RoadShow68K. It is dead simple to use, has a large number of supported interfaces, and is the fastest TCP/IP stack I have ever used. I have never had it not work after 1) the one click install and 2) a simple copy of one file from Storage to DEVS. Oh, 3) a reboot.
-
And my friend you are going to end up with lots of pages of suggestive helps (as appreciative that be and you need to thank the people for helping you out) will end up in a dead end in the result. Not until one corrective suggestion occurs that will solve your problem ones and for all.
1) http://www.amiga.org/forums/showthread.php?t=63328
2) http://bytemyvdu.wordpress.com/2012/02/08/the-internet-and-an-amiga-a1200-prism2v2-drivers-wpawpa2/
(http://www.amiga.org/forums/showthread.php?t=63328)
-
Many moons ago i used easynet to get my Amiga 1200 on line and i had hell of a struggle ,and the only way for me was to ask o2 to give me a static ip adress which they did because as they said this is the only way i was ever going to get on the internet with them ,and they were right straight on line ,and no problem at all and quite fast ,Brian.
-
I'm still struggling with my easynet wireless card to.:(
I used the original software provided by amiga kit.
Strangely my amiga 1200 freezes as soon as i try to go online. Just a short blink from a led on the wirelesscard and thats it.
Checked the wirelesscard with a laptop and it worked fine, so the problem has to be the software or de hardware of my amiga. Tried miami-dx as well, wich results in the same problems.
Anyone an idea?
Is there a chance this is caused by timing issues?
-
Tried miami-dx as well, wich results in the same problems.
...
Is there a chance this is caused by timing issues?
Doubtful, but always possible.
I'd wonder about some type of software conflict first.
As I understand it, MiamiDX is pretty different software-wise from EasyNet (which is AmiTCP v3 I think). So it's probably not the IP stack.
If possible, can you boot with no startup sequence and then do some testing?
(You might need to do some manual assigns before everything will work)
Also, do you have cardpatch and cardreset in your startup-sequence?
Not using a wireless card here (yet, I have one, but haven't hooked it up).
desiv
-
Well, found it. It's my aca1232 accelarator thats causing the problem.
Freshly installed the software this morning.
1st try. rock solid after going online
2nd try, removed the acatune line from the startupsequence.
rock solid after going online.
3th try, removed the acatune card itself.
pushing online = online. :madashell: