Problem Using (Even) WEP with EasyNet

[tygre]

Hi all!

Finally, I am back home with some time to fiddle with my upgraded Amiga (thanks AmigaKit! ) but I am having a surprising problem: after installing Prism2v2 and Miami, I can only connect to my router iff it is open! As soon as I put some kind of password, either using WEP or WPA... I cannot connect anymore... For examples:

• With the following Wireless.prefs file, I can connect (if the router is open)

network={
    ssid="SnowSnow"
    key_mgmt=NONE
}

• With the following Wireless.prefs file, I cannot connect (if the router is set to WEP 128bits)

network={
    ssid="SnowSnow"
    key_mgmt=NONE
    wep_key0="WhatIHaveDone"
    wep_tx_keyidx=0
}

Could it be that I must flash the firmware of my card? I don't think so because the doc. of Prism2v2 says that "cards with Lucent/Agere firmware only support WEP and TKIP." but it also says that "However, Lucent/Agere cards do not work with some modern access points (routers)." Could that be my case?

Here is my card information: I bought it on the 19 July, 2013, it is printed "AVAYA" on the up-side and on the down-side, it says:

• AVAYA
• S/N: 02UT5033039749
• T/N: 2BA20059 P/N: 016065/C
• MAC address: 00022DA4397D
• Encryption: 128RC4
• FCC ID: <some number>
• Canada: <some number>
• AR: <some number>
• <Something in Chinese> ...
• <Something in Polish>
• <Some more logos and numbers>
• Lucent Technologies PC24E-H-FC
• (and along the side: "Made in Taiwan")

My router is an ASUS WL-500gP v2.



Thanks in advance for any advice!

[amigakit.com]

Hi

You have put in the title that you have problems with EasyNet, but then you state you are not using EasyNet, but Miami.

If you are going to use the EasyNet software with Prism2v2, then follow the step-by-step guide we have put together to help users here:

http://www.amigakit.co.uk/support/easynet_wireless.php

If you need help on any part of our guide, then please ask.

[ncafferkey]

Originally Posted by tygre

Could it be that I must flash the firmware of my card? I don't think so because the doc. of Prism2v2 says that "cards with Lucent/Agere firmware only support WEP and TKIP." but it also says that "However, Lucent/Agere cards do not work with some modern access points (routers)." Could that be my case?

I think your diagnosis is correct. Your card doesn't need to be reflashed, so the problem could well be the hardware incompatibility you mentioned. You should try TKIP encryption before giving up though.

[tygre]

Hi amigakit.com and ncafferkey!

Thanks for your quick replies!

Sorry for overlooking EasyNet: I installed today EasyNet from the CD that came with the card, I followed step-by-step the instructions but still I am not able to connect. The Wireless.prefs file now is:

# EasyNet Wireless Settings <BEGIN>
network={
ssid="SnowSnow"
key_mgmt=WPA-PSK
psk="<MY PASS WORD>"
mode=0
}
# EasyNet Wireless Settings <END>

When I double-click on the EasyNet icon and then on "ONLINE", the EasyNet windows says "Going on-line..." (with a "rotating" line in front of it), then, very quickly, something like "Checking bsdsocket.library" and, finally, "Welcome to EasyNet". At this point, if I try the PING command in AmiTCP:BIN towards my router, it just hangs.

PING 192.168.0.1

I have with my router configured as "WPA-Personnel" / TKIP and "WPA2-Personnel" / AES. (On my router, I cannot do "WPA-Personnel" / AES and "WPA2-Personnel" / TKIP.) I also tried with WEP 128bits and a 13-character long key, still cannot connect.

What is it that I am doing wrong?

PS. Works well without any encryption and password, i.e., as "open system".
PPS. I tired updating EasyNet using LiveUpdate after setting my router as "open system" and connecting to it with the following versions but LiveUpdate always fail with "Update Error! Please try to download again":

• EasyNet 0.177 15.09.2013
• EasyNet.guide 0.2 15.06.2008
• WA 0.9.6 21.09.2000

[ncafferkey]

Originally Posted by tygre

What is it that I am doing wrong?

Probably nothing. Do I need to repeat that I think it's a hardware incompatibility?

[modrobert]

tygre,

I think the problem in this case is that your router accepts WiFi settings with AES involved which confuses the dated PCMCIA WiFi card during protocol handshake, you need WPA TKIP/PSK only ("WPA-Personnel" / TKIP), disable WPA2 and AES if possible. Your router also need to support 802.11b (11mbit WiFi).

For test purposes you can launch the prism2v2 driver manually from Amiga shell like this:

WirelessManager prism2.device VERBOSE

Then we will get some debug output to see what is going on when the WiFi card is connecting to the router.

The advantage of this specific PCMCIA WiFi card; PC24E-H-FC (aka Orinoco Silver) is that the WPA TKIP/PSK encryption is done on-the-fly in hardware, so you should try to use that combination in the router to offload your Amiga CPU.

There are some pitfalls worth mentioning:

* If you at any point tried to install AmiTCP it will (without notice) overwrite the prism2.device file with an older version making future attempts fail, if that happened to you then install the prism2v2 driver again (maybe a reinstall of EasyNet does that also, not sure).

* When you set a new "clear text" password the first time, the prism2v2 driver will calculate the PSK hex key, this takes long time (a minute or two), so be patient before starting to ping hosts. Second boot/load will be much quicker when the HEX key is already saved in the config file.


Here is my slightly obfuscated wireless.prefs file (using exactly the same model of WiFi card as OP).

network={
        ssid="myrouter"
        scan_ssid=1
        #psk="foofoo"
        psk=64f708a87be477f3c0689e7490d141b95126edf986e6fc1a1cf7f1bca5692600
}

Note how the WirelessManager (from the prism2v2 package) replaced the clear text password (psk="foofoo") with the actual PSK hex key automatically by commenting out the setting using '#'. If you want to try my config then make sure you remove the line with the long hexadecimal number and remove the comment '#' in front of the PSK clear text password setting.

Use this wireless.prefs if you want to try my settings:

network={
        ssid="myrouter"
        scan_ssid=1
        psk="foofoo"
}

I don't know how the EasyNet software deals with this "clear text to hex key conversion" in the prism2v2 driver, but maybe others can help with that.

Personally I use AmiTCP v3.02b2 to get more control rather than easy install. If you want to try there are some good instructions here, just remember the pitfall with the prism2.device file being overwritten, you need to reinstall the driver after installing AmiTCP.

[tygre]

@ncafferkey

I read you loud and clear but before I bring in older routers (if I can find some), set them up, and tried them one by one, I would rather rule out that I have misconfigured something

@modrobert

Thanks a lot for your help! Following your advice, I reinstalled prism2v2 on top of the one that was installed by EasyNet, then I tried the WirelessManager command in verbose mode and found something interesting: after lots of steps, my card and router reach the 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE state! But then, for some reasons, the hand-shake fails. Here is an excerpt from the complete log file:

State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 48:5b:39:42:60:76 (ver=1)
WPA: PTK derivation - A1=00:02:2d:a4:39:7d A2=48:5b:39:42:60:76
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 07 a6 e8 94 3e 33 84 01 3a 7f df 2c f5 8a fc 18 72 57 d8 c5 ae e3 74 30 a9 2e cf 5c 66 3a ec 49 e2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5e 9d a8 3a 23 17 7f 89 8c 3f 90 fd 2e 2f 0c e6 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
Disassociation notification
WPA: 4-Way Handshake failed - pre-shared key may be incorrect

To me, it says that the hex key in my Amiga (generated when installing prism2v2 from the text key, as you mentionned) and the key in my router are not the same although they are identical textually.

Do you think that I am in the right track? Or did I miss something else before the hand-shake? (I attach the complete log file...)

Thanks in advance!

PS. I will go now on to do more experiments with WEP and clear-text passphrase...

[modrobert]

tygre,

Avoid using WEP, it is pretty much like running the WiFi network "open" security wise.

As mentioned before, you need to configure WPA TKIP/PSK ("WPA-Personnel" / TKIP) in the router, disable WPA2 and AES, do *NOT* accept both.

After checking your log, I had similar problems with failed handshake when configuring my router to "Enable WPA/WPA2", after changing to "Enable WPA Only" it worked fine.

[amigakit.com]

@tygre

The Prism2v2 we supplied is the latest version- EasyNet automatically configures it correctly and checks for version numbers. There is no need to install another Prism2v2 over EasyNet as it could cause configuration problems !

Are you using WPA-TKIP now in your router ?

To check your configuration go to the Help menu in Easynet and select Network Configuration option

[tygre]

@modrobert

Unfortunately, in the router ASUS WL-500gp v2, I could not find any way to disable WPA and AES. As far as I can tell, I must choose either "Shared Key" (WEP), "WPA-Personnal" and TKIP, or "WPA2-Personal" and AES.There is also "WPA-Auto-Personal" and the same ones with "Enterprise" instead of "Personal". Any idea how I could only enable WPA?

@amigakit.com

I reinstalled my Workbench and reinstall from scratch NetCPM010 and EasyNet using the disk and CD-Rom and following the instructions coming with the card. I attach the log when selecting "Help -> Configuration Help.." in EasyNet. It says that it uses prism2.device version 1.7.

Then, I installed prism2v2, which installs prism2.device version 2.5. I attach the log from EasyNet as well as the log from C:WirelessManager prism2.device VERBOSE. (In this specific log, I tried to use WEP.)

No matter if I try WEP or WPA, I cannot connect. When using WPA/TKIP, the WirelessManager log file complains that WPA: 4-Way Handshake failed - pre-shared key may be incorrect. Reading before this line, I noticed the line EAPOL: Supplicant port status: Unauthorized, which could mean that there could be a misunderstanding between the router and the card... but how could I resolve it?

Besides, others say that the problem could be a frequency problem, when using "ht" (which I guess means "high throughput") but not when using 2.4Ghz or 5Ghz. How can I set the frequency in my router? I could not find such an option...

Finally, yet others say that my problem could come from the encoding of the passkey but my passkey is just plain ASCII with some majuscules/minuscules, nothing weird.

Any idea what is happening? It really does seem like a hardward compatibility problem, as ncafferkey pointed out earlier but am I missing something?

Thanks in advance!

[tygre]

PS. Reading the log file in details, I noticed these lines:

WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 07 a6 e8 94 3e 33 84 01 3a 7f df 2c f5 8a fc 18 72 57 d8 c5 ae e3 74 30 a9 2e cf 5c 66 3a ec 49 e2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5e 9d a8 3a 23 17 7f 89 8c 3f 90 fd 2e 2f 0c e6 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02

Is that normal that the lengths of the hexdumps are different? I am not sure that they are related but at this point I am trying to figure out any possible problem...

PPS. When selecting "Help -> EasyNet Log..", a requester says that "Cannot open RAM:T/EasyNet.log".

PPPS. I am sure that the SSID of the router and of my config in the Amiga match by the way!

Thank you all for your help!

[modrobert]

tygre,

1) Choose "'WPA-Personnal' and TKIP".

2) Set a new clear text password in your router and System:Prefs/Env-Archive/Sys/Wireless.prefs (remove the existing hex PSK key and uncomment the PSK text password)

3) Reboot the Amiga.

4) Start the network and wait for two minutes (yes, it can take that long with new PSK text password, it will be fast next time with PSK hex key).

5) Test now, ping local hosts (eg. default gateway) on your lan.

[amigakit.com]

Please take note of what I have been saying in my last post: do not install third party programs which can conflict and stop EasyNet working. In post #1 you have been installing Miami, then installing Prism2 v1.7, then installing Prism2 v2.5 without using EasyNet to auto-configure and now I can see evidence that you have AMITCP v4 on your hard disk too.

I have read your EasyNet Network Configuration Help file and I can see problems immediately with your system and configuration:

1) Your bsdsocket.library is set to 4.1. You are using EasyNet standard edition so it should be version 3. This means that you have previously installed Genesis/AMITCP 4 at the location of System:AmiTCP. This will conflict with EasyNet and stop it working! Genesis files and EasyNet files cannot be mixed as they will stop each other from running correctly.

2) You have set the secondary DNS to "use" but it is blank - go to EasyNet's DNS settings in the Network configuration window and enter the second DNS or alternatively go to the TCP/IP settings and set DNS to "use the Primary DNS".

3) Wireless Settings are NOT configured from EasyNet- use EasyNet to auto-configure the wireless settings

4) Your are using EasyNet 0.175, the latest public version is 0.178 - you need to contact us to upgrade.

5) No hosts are set up. Go to the EasyNet Hosts Manager and click Add Host.. button to add some hosts then click SAVE and restart, go back into the Host Manager and click Ping Host button after selecting the host you wish to ping.



I also suspect that you have both the older prism2 v1.7 driver remnants installed at the same time as the prism2 v2 driver. Make sure your s:startup-sequence does not have C:SETPRISM2DEFAULTS and the s:wireless-startup file is deleted. This is very important.

[tygre]

Thanks a lot for your help and your patience

@modrobert

Unfortunately, I have tried again these steps but still the same problem and same kind of content in the log file...

@amigakit.com

1) I attached two log files: the original one with EasyNet and without prism2v2 and one with prism2v2. The one for the clean, original install of EasyNet is that one, which says that I have bsdsocket.library v3.28.

2) I didn't set a second DNS in the EasyNet configuration because I don't have one.

3) The log file for the clean, original install of EasyNet says:

++ Network Interface ++  

Device             = prism2.device (version 1.7 installed)
Unit Number        = 0
Wireless Settings  = C:SetPrism2Defaults SSID "SnowSnow" TEXTKEY StupidStupid1 (version 1.2 installed)
Library            = pccard.library (version 1.1 installed)

which has been set by EasyNet.

4) Do you mean through the Support page of your Web site? If so, then I just did it

5) Does it matter that no hosts are set? Pinging IP address didn't work, won't work more with names...

Thanks again a lot!

[tygre]

PS. This page at amigakit.com says that prism2v2 should be installed, should I?

[tygre]

Hi there again!

So, I did some more testing but still without any luck I formatted my Workbench partition (and all the others for that matter) as started from an original Workbench 3.0. Then, I installed NetPCM010 and, after rebooting, EasyNet v0.175.

Now, before going on-line, the log file (Help -> Configuration Help..) looks like the one mentioned by amigakit.com in a previous post, except from bsdsocket.library, which is said to be "unknown".

When I go on-line, EasyNet says "Going Online.." for a long time, about 2-3 minutes, before actually going to the next phase (live update). Then, the log file says that I have bsdsocket.library version 3.8.

Yet, a ping 192.168.0.1 stalls forever: I am not connected to my network and cannot reach my router. I attached two sets of log files taken from T: The ones before going on-line and after going on-line... Is there something wrong in my configuration? Should I provide you with any other config files to help?

Thanks again for your help and your patience!

[amigakit.com]

This page at amigakit.com says that prism2v2 should be installed, should I?

yes install it but let EasyNet configure it. Do not install the old Prism2 v1.7 as this could conflict with the newer Prism2v2.

We emailed you v0.178 of EasyNet - please use that version.

[tygre]

I don't have prism2 v1.7, it comes (I guess?) with EasyNet. I will install prism2v2 but it uses WirelessManager instead of SetPrism2Defaults, won't that be a problem?

I will also replace the program EasyNet, v0.175, by the new one that you sent me, v0.178...

Talk to you soon!

[ncafferkey]

@tygre

You're far more likely to solve this problem by following only the advice given by people in this thread, and not your own guesses or advice for Linux, FreeBSD etc. In particular, reinstalling Workbench/AmigaOS twice seems unnecessary, extreme and time consuming.

But, yes, "HT" stands for "High Throughput", which basically equates to IEEE 802.11n, which we're definitely not using with Orinoco cards :-)

[tygre]

Hi all!

Thanks a lot for your patience and advise! It is now working! Feels like

Here are the steps to get EasyNet v0.178 + prism2v2 to work: this is certainly neither the only nor the simplest way to get them to work, but this way worked for me after looots of trials and errors and thanks to the good advices in this thread!

I start from a new Workbench install (v3.0) and the EasyNet CD v0.175.

Icon: Install-EasyNet
····Installer:
········Check-box: Intermediate User
········Button: Proceed With Install
········Button: Proceed
········Nothing special, choose the destination, say yes to all questions
········Label: PLEASE NOW CONFIGURE EASYNET

····Dialog-box: Welcome to EasyNet
········Button: CONTINUE >>
····Window: Register
········Enter information

····Dialog-box: EasyNet needs to be setup correctly
········Button: Proceed >>
········Label: Choose prism2.device
········Button: Choose Settings..
········Window: Wireless Settings
············Text-box: Wireless Network Name (SSID)
············Button: SAVE
········Dialog-box: Once the wireless network interface is selected and saved, your computer needs to be rebooted
············Button: OK
········Button: SAVE

····Dialog-box: EasyNet needs to be setup correctly
········Button: Proceed >>
········Window: EasyNet Network Config
············Text-boxes:····Amiga's IP Address·······192.168.0.25
·································Amiga's Host Name·······PpareunChingu
·································Network Mask··············255.255.255.0
·································Network Domain Name···whatever
·································Gateway IP Address······192.168.0.1
············Button:····Configure DNS..
················Text-boxes: Primary DNS········216.252.64.75
················Text-boxes: Secondary DNS····216.252.64.76
················Button: OK
············Button: Save

····Window: EasyNet @2013 AmigaKit.com
········Close it

····Installer: INSTALLATION COMPLETE - PLEASE NOW REBOOT
········Button: Proceed
········Button: Proceed
········Installer closes

Reboot
If you try to connect at this point, you will get a dialog-box: EasyNet Error stating that the prism2.device cannot be found.

Icon: Install of prism2v2
····Installer:
········Check-box: Intermediate User
········Button: Proceed With Install
········Button: Proceed
········Text-box: What is your main network's name (SSID)?····Let it snow, let it sow...
········Button: Proceed
········Text-box: What is your main network's WPA passphrase?····duh
········Button: Proceed
········Label: Working on installation...
········Label: Generating key...
········Wait
········Label: Installation complete!
········Button: Proceed

Reboot

Copy EasyNet v0.178 into AmiTCP:
Edit S:User-Startup to remove the line Run <>NIL: C:WirelessManager prism2.device
Delete S:Wireless-Startup

You can now go on-line!



Thanks a lot all! Special thanks to AmigaKit.com!

PS. My router did not change, I only set it to use WPA + TKIP

PPS. Could a gentle moderator mark this thread as [Resolved], please?