Bug 74936 - orinoco_cs problem with when using SSL with wireless encryption enabled
Summary: orinoco_cs problem with when using SSL with wireless encryption enabled
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
(Show other bugs)
Version: 8.0
Hardware: i686 Linux
Target Milestone: ---
Assignee: Jeff Garzik
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2002-10-02 21:55 UTC by Satish Balay
Modified: 2013-07-03 02:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 15:39:58 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Satish Balay 2002-10-02 21:55:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
A very mysterious problem. When using a Lucent Wavelan PCMCIA Silver (64bit
encryption) card, if wireless incryption is enabled, https:// requests from
browser (mozilla/galeon/lynx) don't work. mozilla/galeon just hang, where lynx
gives ssl error.

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

How reproducible:

Steps to Reproduce:
1.Install Redhat8.0 on a laptop (i've used IBM ThinkPad 600E)
2.insert Lucent Wavelan Silver PCMCIA 802.11b card. This by default loads
orinoco_cs driver
3.Set the correct wireless parameters using iwconfig something like:

/sbin/iwconfig eth0 essid correctID key correctNumericalKey

4. Now start up a web browser and try accessing a https:// site for eg:

lynx https://mail.yahoo.com

Actual Results:  [balay@localhost balay]$ lynx https://mail.yahoo.com

Looking up mail.yahoo.com
Making HTTPS connection to mail.yahoo.com
Secure 168-bit TLSv1/SSLv3 (EDH-RSA-DES-CBC3-SHA) HTTP connection
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Unexpected network read error; connection aborted.
Can't Access `https://mail.yahoo.com/'
Alert!: Unable to access document.

lynx: Can't access startfile

Expected Results:  
Access should go through.

Additional info:

This problem  shows up with mozilla, galeon (no error messages, just hang most
of the time). I've tried a bunch of other https:// sites (including

The problem disappears when I do any of the following:

1.Disable encryption for wireless netowrk.
2.Use a wired (ethernet) network
3.use wvlan_cs driver instead of orinico_cs (This is the default for redhat 7.2
which has worked fine without problems for me)
4. Using an Orinoco Gold card with 128bit encryption.

Perhaps this bug report can be forwarded upsteam to orinoco_cs developers?

I still can't comprehend how 'a driver bug' (if thats what it is) can affect ssl
connections only. So far I have't seen any other weird behavior. Regular web
browsing is not affected. My ssh connections work fine.

Comment 1 John A. Barbuto 2002-10-06 20:01:55 UTC
I'm using an Orinoco Gold card with 128 bit encyption with a Linksys WAP11
access point, and I'm having this problem as well.  It also affects the
operation of up2date, since it uses SSL.  I didn't have this problem with 7.3.

Comment 2 Need Real Name 2002-10-08 19:28:30 UTC
I don't know if this is helpful, but this isn't an "Always" problem here. I have
8.0, an Orinoco Silver with WEP enabled using orinoco_cs, and I have no problem
getting to https sites. Running in Ad-Hoc mode.  Happy to supply any more
relevant information if anyone can think of any.

Comment 3 Bugzilla owner 2004-09-30 15:39:58 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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