Bug 108004 - WEP Encryption doesn't work with SMC2602W Wireless Network Adapter
Summary: WEP Encryption doesn't work with SMC2602W Wireless Network Adapter
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 2
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-26 03:17 UTC by Rustin Horner
Modified: 2015-01-04 22:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-16 04:49:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rustin Horner 2003-10-26 03:17:46 UTC
Description of problem: WEP Encryption doesn't work with SMC2602W Wireless 
Network Adapter


Version-Release number of selected component (if applicable):SMC2602W


How reproducible:Does Not Work


Steps to Reproduce:
I'm unable to get this feature to work unless I disable the WEP option on my D-
link DI-614+ router.
    
Actual results:N/A


Expected results:N/A


Additional info:  Sorry I couldn't reproduce a fix for this problem.  WEP 
didn't work with the network adapter in all the test releases.

Comment 1 Harald Hoyer 2004-05-06 10:22:01 UTC
did you try it using iwconfig? if yes, then please switch the
component to kernel.

Comment 2 Rustin Horner 2004-05-06 13:57:51 UTC
I did try using iwconfig to configure WEP and had no luck.

Comment 3 Dave Jones 2004-12-08 05:27:16 UTC
any improvement with the latest errata kernel ?

Comment 4 Dave Jones 2005-04-16 04:49:10 UTC
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.



Note You need to log in before you can comment on or make changes to this bug.