Great news!

I guess I just don't understand about the "black" and
"white edge connectors"...

I have the AmiKit wifi card (OEM unknown) and the card
is wholly green. What I'd call the "edge connector"
(the connection on the edge to the PCI slot), as well
as the antenna connector, are all copper.
The print on the card is white, FWTW.

From what I've seen (as well as the 6 cards that are
visible from my chair), the edge connectors are always
either copper or silver.

Maybe it would be better to address the card I suspect
most of us have - the AmiKit "NETPCI001" wifi card....

Is it compatible?

Does the new driver provide WPA and WPA2 with it?

Does one have to find a peecee to reflash the card?


THANKS!

PJS

edit: reformatted

That's the card I have.

Yes, you have to find a PC, preferably running Windows XP 32bit, and flash it to pk010101 and sf010704.

It provides WPA and WPA2 (both TKIP and AES in either WPA mode).

Some cards don't support CCMP (aka AES) encryption, but what you and I have do.

I think when he's refering to edge connectors, he means on PCMCIA cards.

I've got this device driver, and it is working for me so long as my SSID is not hidden and I use a static IP. Although DHCP does work in WEP. I've emailed Neil about both issues.

the colour of the edge connector matters for PCMCIA cards (for A600/1200), and from what i gather you have a PCI card.

*edit*

too slow ;)

That's a great update for prism2.device.

I'm having issues though. Anything other than WEP, and no data can reach the Amiga unless the Amiga requested it. Hence IRC, FTP and Web Browsing works, but DHCP (UDP, connection-less), pinging the machine (ICMP), and any servers don't work.

Will keep you all updated.

Congrats to the maker of the driver !

Great news about the WPA support!

@MickJT:
Quote:
Ouch. Well, hopefully those two can be sorted as well. They are absolute requirements for me to actually start using the NETPCI001 card I've had lying around for a few years waiting for WPA to be supported. Well, I guess if I absolutely had to, I could work around the lack of DHCP, but not the SSID thing. I will not advertise our WiFi to neighbours or bypassers.

Looking forward to hearing Neil's answer.

Best regards,

Niels

Hidden SSID and incoming connection issue confirmed by Neil. 1st problem fixed, 2nd problem being worked on.

I have one of these:

0x1260 0x3873 Intersil Corporation Prism 2.5 Wavelan chipset

(a) Is it compatible?
(b) Where do I get the firmware update, and how do I flash it?
(c) Can somebody lend me a PC to do the flashing?

oh, and (d) is there any way of finding out on OS4 which firmware version I have already?

@Chris, I think that one might only be able to do TKIP encryption, seeing as WaveLAN is Lucent/Agere.

Firmwares are here

http://linux.junsun.net/intersil-prism/

Also there, shows you how to find out the NICID of the card. I don't think you can do it on an Amiga. Maybe if you ran Debian Linux.

@MickJT

Thanks.

Quote:

My Linux install is broken/not bootable, and I never got my wireless card working with it anyway.

It's an interesting thought though - the firmware upgrade might be possible under Debian PPC.

I had another look at the manual and compatibility list, and it mentions one card with a WaveLAN 2.0 chipset, and says it is not compatible.

Best thing to do is double-check with Neil.

@MickJT

Thanks for the info... I'm going to hit paypal
next and get in touch with Neil.

Then I just have to find someone that has a peecee
that will flash the card for me.

Thanks,

PJS

@MickJT

My card works with the existing driver in WEP mode, it's the WPA support I wasn't sure about.

@Chris

Your card will support TKIP and CCMP/AES once reflashed. It's unlikely to already have a WPA-capable firmware: AFAIK none of these cards left the factory with this firmware.

@MickJT:
Quote:
Ah, great! Looking forward to the next update, then. Good job, Neil!

Best regards,

Niels

@neil

Fab! I'll be in touch once I've sorted the firmware update out.

Well my incoming connection issue is still being looked into. Sent some logs to Neil. Seems to be an issue with decryption of broadcast frames.

All issues now fixed.