Erich: I too have had major problems with off-brand network interface cards both wired and wireless. One of the toughest problems I ever had to resolve involved a database getting corrupted occasionally - that problem turned out to be a generic NE2000 LAN card in one of the workstations.
As a result of these experiences, I have a rule that I always follow: no generic LAN cards. This is especially true for "less-mainstream" O/S such as Linux or OS/2. LAN cards are very cheap, so why go through the headaches to save $10? Just stick with one of the top market leaders (I use Intel and 3Com) and you know that, regardless of O/S, the drivers will be well-tested and well-supported. You may very well eventually resolve the issue with new drivers from LinkSys, a newer revision of the card, Linux reinstalls/patches, LinkSys technical support, etc. Then again, there is a significant possibility that you will *never* make the LinkSys card work acceptably with Linux. If it were me, I would simply replace the source of the problem: the wireless card and it's associated drivers. Again, I would go with a market leader that offers real technical support and just be done with it. That said, let me also clear up one point of confusion: WEP is a security protocol that exists between your wireless LAN card and the access point that it is talking to. Web sites, e-mail servers, ftp servers, etc. do not see, know or care about WEP. Wired Equivalent Privacy (WEP) just provides security across the radio link. WEP doesn't cross copper. As such, sites such as www.georgiadogs.com don't use WEP and never even see the protocol. WEP is strictly configured on your end, between your card and it's access point. Good luck! Ken Morley JM Technology Group -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
