It is currently Sun, 16 Jun 2019 00:36:24 GMT

Author Message
 Strange WEP-failure with wlan-ng 1.14 and 1.15pre5

I'm running SuSE 8.0 on an IBM Thinkpad T30 with a built-in wireless
card (Prism2) using 40 bit WEP. I've tried wlan-ng 1.14 and 1.15pre5
and normally the card works just fine, but under very particular
circumstances (see below) the card suddenly hangs. To get the card
working again i even have to reload the prism2_pci (and the p80211 ?)

This problem occurs when i try to send (not receive) larger files
(typically at least 4-5 MB, compressed size) using cvs or rsync,
tunneled through ssh.

If I make a small change to this setup, _anyone_ of those below,
everything works just fine:

  1) receiving files instead
  2) sending smaller files, less than 1MB
  3) communicating through my ordinary Ethernet cable
  4) use cvs or rsync directly, without the ssh tunnel (not an option!)
  5) copying the files directly with scp


My test-files (I've tried many) consist of 5MB randomly generated binary
data (making possible ssh compression ineffective).

Version info:
  ssh : OpenSSH_3.4p1, using SSH protocol 1
  cvs : 1.11.1p1
  rsync : 2.4.6 and 2.5.5
  kernel (SuSE): 2.4.18-GB

Is there some problem with these wlan-ng drivers?
Any help would be appreciated.


 Mon, 14 Feb 2005 02:15:59 GMT   
 Strange WEP-failure with wlan-ng 1.14 and 1.15pre5
I get the exact same symptoms when trying to run an X-Server session
with WEP enabled. I'm using the RPM version linux-wlan-ng-0.1.10

 Wed, 02 Mar 2005 16:54:50 GMT   
 Strange WEP-failure with wlan-ng 1.14 and 1.15pre5

I have no problem doing 40 bit WEP with an SMC 2632W pc card using the
wlan-ng 1.13 (prism2_cs) that came with SuSE 8.0 as long as I kick my
Linksys WAP11 v2.2 AP back to 2 mbps.  Attempting to do 11 mbps WEP
frequently locks up the wireless end of the WAP11 (power cycling restores
it), but no problems on the Linux end (it reconnects as soon as the WAP11
is rebooted).  Open system works fine at 11 mbps (600+kB/s).  I have seen
reports that the WAP11 v2.2 AP also has problems with Linksys' own
wireless pc cards.

David Efflandt - All spam ignored

 Sat, 05 Mar 2005 12:35:08 GMT   
 Strange WEP-failure with wlan-ng 1.14 and 1.15pre5
As a follow up, I've noticed that the little password generator
that comes with linux-wlan-ng doesn't match up correctly with what is
produced by my wap11v2.2 ... entering the keys manually fixed the problem.
I'm very new to wireless, so it might just be something stupid I'm doing wrong ...

 Mon, 14 Mar 2005 08:00:26 GMT   
 Strange WEP-failure with wlan-ng 1.14 and 1.15pre5
"Todd M. Roy" <> wrote in message
wrong ...

I have this same problem using RH 8.0 (limbo and null betas).  I don't have
the reference at the moment, but do recall finding notes about it, that
there is a difference in the key generation process under Windows vs. Linux
and that you need to enter the Hex key manually as opposed to using the

HTH if only to validate the problem and your sanity....


 Mon, 14 Mar 2005 08:54:54 GMT   
 Strange WEP-failure with wlan-ng 1.14 and 1.15pre5
On 25 Sep 2002 17:00:26 -0700, Todd M. Roy <> wrote:

I noticed that nwepgen does match WAP11 v2.2 for 64(40) bit WEP key from
passphrase, but not for 128(104) bit.  Hopefully Linksys will soon come
out with firmware that solves a number of other problems with this WAP.  
My WAP11 came with firmware 1.009 which would frequently hang if doing WEP
over 2 mbps.  1.01g beta is almost there, but they overlooked first page
after config login (Apply button broken) which for now requires Windows
utility to change those settings.

David Efflandt - All spam ignored

 Tue, 15 Mar 2005 09:36:18 GMT   
 Strange WEP-failure with wlan-ng 1.14 and 1.15pre5

Apparently the software for the wpc11 card on windows also must share this
problem since I have one taking 128 bit with my wap11 ...

 Wed, 16 Mar 2005 03:11:42 GMT   
 Strange WEP-failure with wlan-ng 1.14 and 1.15pre5

Same type of problem here with a D-Link DWL-500 (DWL-650 in PCMCIA/PCI

Redhat 7.2 (2.4.7-10)
D-Link DWL-500 (using the prism2_cs driver)

2 problems observed:
- very likely a resource conflict with ALSA audio drivers (nothing works
  anymore on the wireless network, even after restart of the PCMCIA
  subsystem). This I could fix by putting PCIC_OPTS="irq_mode=0" in

- second, exactly the described behaviour of thi thread - network works on
  low load situation. However copying a large file (sending from the
  machine that eventually locks up) brings the network down. The card has
  to be reinitialized by eject/insert.
  This happens with 128bit and 40 bit WEP encrytion. This thread then
  gave me a kick to try with *no* WEP encryption - and *bing* copying
  some 100 megs with full speed works... (before it died after around
  5 meg) - well, there seems to be something REALLY fishy with WEP.
  Oh yes: The keys have been entered manually (locks up) and also
  been generated by the nwepgen tool (locks up too).


To mail me, include my GPG fingerprint in your message body.
Mails without the fingerprint may be trashed by the SPAM filter.

Key fingerprint = 13D1 19F5 77D0 4CEC 8D3F  A24E 09FC C18A 87BC DC94

 Fri, 18 Mar 2005 08:02:17 GMT   
   [ 8 post ] 

Similar Threads

1. linux-wlan-ng and WEP?

2. Problem with linux-wlan-ng WEP

3. wlan-ng driver and gnome wlan applets?

4. wlanctl-ng and wep

5. WLAN: WEP key generation with nwepgen?

6. wlan & wep

7. Suse 8.1 WLAN WEP Problem

8. Trouble with build of linux-wlan-ng

9. wlan-ng-0.2.1-pre17 DWL-122 Disconnects

10. Wireless problems (wlan-ng)

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software