[Bug 278619] New: Lucent / Agere ORiNOCO card does not connect when multiple WEP keys are present in AP
https://bugzilla.novell.com/show_bug.cgi?id=278619 Summary: Lucent / Agere ORiNOCO card does not connect when multiple WEP keys are present in AP Product: openSUSE 10.3 Version: Alpha 4plus Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: casualprogrammer@yahoo.com QAContact: qa@suse.de Continued from Bug 249709 On a Sony Vaio PCG-SRX51P with built in Lucent / Agere ORiNOCO mini PCI WLAN card ( this is actually a PCMCIA device with a PCI piggyback ) running openSuSE 10.3 alpha4 connection with an AP is not possible as long as there are multiple WEP keys present in the AP ( FRITZ!Box Fon WLAN (UI), Firmware-Version 08.04.27 ). On issuing iwconfig eth1 essid xyz key 123 ifrenew eth1 no lease would be offered by the AP although the device is shown as connected by the AP. Only after removing all but one WEP keys would the connection take place. As this does not happen with the ipw3945 ( it connects with any of the 4 stored WEP keys ) it looks like a orinoco_cs driver issue, rather than an AP issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=278619 jbenc@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=278619 jbenc@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |jbenc@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=278619 ------- Comment #1 from jbenc@novell.com 2007-05-28 12:15 MST ------- According to comment #15 in bug 249709, the card is associated. Could you run tcpdump on the eth1 interface (tcpdump -ni eth1) and attach the result? (Let it run for several tens of seconds.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=278619 ------- Comment #2 from casualprogrammer@yahoo.com 2007-05-28 13:48 MST ------- This is interesting, as soon as I entered more WEP keys the connection was lost. nm-applet was still indicating the WEP Network with its IP, while iwconfig would show the essid of a nearby open network ( I have some 20 networks around here ) and claim association. issuing #service network restart would have nm-applet trying to reconnect and challenge me with the key-dialogue. None of the keys would work. Switching back to ifup with YaST, then restarting network service again. Issuing #iwconfig eth1 essid 'wepnetwork' key s:mykey, followed by ifup eth1 would connect immediately to the open network. ( This is how I am connected now ). Not sure how we get this in a state and sequence you may be able to follow. tcpdump -ni eth1 shows (just the last few lines) 21:30:09.210103 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 1 win 365 <nop,nop,timestamp 5016423 297557269> 21:30:09.211093 IP 192.168.182.54.3189 > 212.58.240.132.80: P 1:818(817) ack 1 win 365 <nop,nop,timestamp 5016424 297557269> 21:30:09.357271 IP 212.58.240.132.80 > 192.168.182.54.3189: . ack 818 win 32711 <nop,nop,timestamp 297557284 5016424> 21:30:09.360258 IP 212.58.240.132.80 > 192.168.182.54.3189: P 1:341(340) ack 818 win 32711 <nop,nop,timestamp 297557284 5016424> 21:30:09.360337 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 341 win 432 <nop,nop,timestamp 5016461 297557284> 21:30:09.363615 IP 212.58.240.132.80 > 192.168.182.54.3189: . 341:1781(1440) ack 818 win 32711 <nop,nop,timestamp 297557284 5016424> 21:30:09.363769 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 1781 win 613 <nop,nop,timestamp 5016462 297557284> 21:30:09.500199 IP 212.58.240.132.80 > 192.168.182.54.3189: . 1781:3221(1440) ack 818 win 32711 <nop,nop,timestamp 297557297 5016461> 21:30:09.500346 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 3221 win 794 <nop,nop,timestamp 5016496 297557297> 21:30:09.502982 IP 212.58.240.132.80 > 192.168.182.54.3189: P 3221:4661(1440) ack 818 win 32711 <nop,nop,timestamp 297557297 5016461> 21:30:09.505673 IP 212.58.240.132.80 > 192.168.182.54.3189: . 4661:6101(1440) ack 818 win 32711 <nop,nop,timestamp 297557298 5016462> 21:30:09.508422 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 4661 win 975 <nop,nop,timestamp 5016497 297557297> 21:30:09.508407 IP 212.58.240.132.80 > 192.168.182.54.3189: P 6101:7541(1440) ack 818 win 32711 <nop,nop,timestamp 297557298 5016462> 21:30:09.509432 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 6101 win 1156 <nop,nop,timestamp 5016497 297557298> 21:30:09.510414 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 7541 win 1337 <nop,nop,timestamp 5016498 297557298> 21:30:09.643156 IP 212.58.240.132.80 > 192.168.182.54.3189: . 7541:8533(992) ack 818 win 32711 <nop,nop,timestamp 297557312 5016496> 21:30:09.643320 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 8533 win 1517 <nop,nop,timestamp 5016532 297557312> 21:30:09.646286 IP 212.58.240.132.80 > 192.168.182.54.3189: . 8533:9973(1440) ack 818 win 32711 <nop,nop,timestamp 297557312 5016496> 21:30:09.650468 IP 212.58.240.132.80 > 192.168.182.54.3189: . 9973:11413(1440) ack 818 win 32711 <nop,nop,timestamp 297557312 5016497> 21:30:09.653238 IP 212.58.240.132.80 > 192.168.182.54.3189: . 11413:12853(1440) ack 818 win 32711 <nop,nop,timestamp 297557312 5016497> 21:30:09.655937 IP 212.58.240.132.80 > 192.168.182.54.3189: . 12853:14293(1440) ack 818 win 32711 <nop,nop,timestamp 297557312 5016497> 21:30:09.656578 IP 212.58.240.132.80 > 192.168.182.54.3189: P 14293:14701(408) ack 818 win 32711 <nop,nop,timestamp 297557312 5016497> 21:30:09.656945 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 9973 win 1698 <nop,nop,timestamp 5016533 297557312> 21:30:09.657948 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 11413 win 1879 <nop,nop,timestamp 5016534 297557312> 21:30:09.659115 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 12853 win 2060 <nop,nop,timestamp 5016534 297557312> 21:30:09.660119 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 14293 win 2241 <nop,nop,timestamp 5016535 297557312> 21:30:09.661956 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 14701 win 2421 <nop,nop,timestamp 5016535 297557312> 21:30:14.365817 IP 212.58.240.132.80 > 192.168.182.54.3189: F 14701:14701(0) ack 818 win 32711 <nop,nop,timestamp 297557785 5016535> 21:30:14.402705 IP 192.168.182.54.3189 > 212.58.240.132.80: . ack 14702 win 2421 <nop,nop,timestamp 5017722 297557785> 21:30:23.180118 IP 192.168.182.54.3189 > 212.58.240.132.80: F 818:818(0) ack 14702 win 2421 <nop,nop,timestamp 5019916 297557785> 21:30:23.313765 IP 212.58.240.132.80 > 192.168.182.54.3189: . ack 819 win 32711 <nop,nop,timestamp 297558679 5019916> 21:30:38.196829 IP 192.168.182.54.26407 > 63.245.213.21.80: F 501:501(0) ack 709 win 7080 21:30:38.197806 IP 192.168.182.54.26406 > 63.245.213.21.80: F 535:535(0) ack 666 win 6650 21:30:38.253579 IP 63.245.213.21.80 > 192.168.182.54.26407: F 709:709(0) ack 502 win 8190 21:30:38.253734 IP 192.168.182.54.26407 > 63.245.213.21.80: . ack 710 win 7080 21:30:38.255211 IP 63.245.213.21.80 > 192.168.182.54.26406: F 666:666(0) ack 536 win 8190 21:30:38.255277 IP 192.168.182.54.26406 > 63.245.213.21.80: . ack 667 win 6650 1045 packets captured 1045 packets received by filter 0 packets dropped by kernel The ip address is that of the open network. While iwconfig eth1 shows: iwconfig eth1 Warning: Driver for device eth1 has been compiled with version 22 of Wireless Extension, while this program supports up to version 21. Some things may be broken... eth1 IEEE 802.11b ESSID:">per aspera ad astra<" Nickname:"HERMES I" Mode:Managed Frequency:2.432 GHz Access Point: 00:18:84:11:BB:51 Bit Rate:11 Mb/s Sensitivity:1/3 Retry limit:4 RTS thr:off Fragment thr:off Encryption key:3139-3432-3132-3237-2D6C-696E-69 Security mode:open Power Management:off Link Quality=19/92 Signal level=-72 dBm Noise level=-91 dBm Rx invalid nwid:0 Rx invalid crypt:62 Rx invalid frag:2625 Tx excessive retries:99 Invalid misc:0 Missed beacon:0 which would be correct, only the ip should look more like 192.168.0.xx ifstatus eth1 shows: ifstatus eth1 eth1 eth1 configuration: wlan-id-00:02:2d:5c:f5:ef eth1 DHCP client (dhcpcd) is running IPADDR=192.168.182.54 NETMASK=255.255.255.0 GATEWAY=192.168.182.1 DOMAIN='key.chillispot.org' DNS=192.168.0.25,192.168.0.25 DHCPSIADDR=0.0.0.0 DHCPCHADDR=00:02:2D:5C:F5:EF REBINDTIME=525 eth1 is up 3: eth1: <BROADCAST,MULTICAST,NOTRAILERS,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:02:2d:5c:f5:ef brd ff:ff:ff:ff:ff:ff inet 192.168.182.54/24 brd 192.168.182.255 scope global eth1 inet6 fe80::202:2dff:fe5c:f5ef/64 scope link valid_lft forever preferred_lft forever eth1 IP address: 192.168.182.54/24 Configured routes for interface eth1: default 192.168.0.1 - - 169.254.0.0 - 255.255.0.0 eth1 Active routes for interface eth1: 192.168.182.0/24 proto kernel scope link src 192.168.182.54 169.254.0.0/16 scope link default via 192.168.182.1 1 of 2 configured routes for interface eth1 up Please advise -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=278619 ------- Comment #3 from casualprogrammer@yahoo.com 2007-05-30 05:24 MST ------- Now, having reset everything I can't get in at all any more. Trying to do this step by step: 1.) Setting up the AP for the simplest secure method essid: cjp channel: 12 power: 100% mode: 802.11b 802.11g++: inactive WEP encryption: on WEP key length: 64 WEP key 1: 3132333435 (s:12345) 2.) I can get in with the ipw3945 with Network Manager as well as manual. 3.) Setting up the Sony / ORiNOCO a) YaST/Network Devices/Network Card/Global Options Traditional Method with ifup: checked Enable IPv6: unchecked Request Broadcast Response: unchecked DHCP Client Identifier: blank Hostname to Send: AUTO b) Overview Sony 82801 BA/BAM/CA/CAM Ethernet Controller IP 192.168.0.100 PCMCIA Lucent Orinoco, Prism II based, and similar... IP 192.168.0.50 c) Hostname/DNS Hostname: workstation1l Domain Name: ac Write Hostname to /etc/hosts: checked Name Server1: 192.168.0.1 Domain Search: ac d) Routing Default Gateway: 192.168.0.1 Enable IP Forwarding: checked 4.) Network Card Setup a) General Device Activation: Manually Firewall Zone: Internal Zone(unprotected) Enable ... Kinternet: unchecked Set MTU:1500(Ethernet,DSL broadband) b) Address Statically assigned IP Address:checked IP Address: 192.168.0.50 Subnet Mask: 255.255.255.0 c) Hardware Manual Network Card Configuration:checked ( can't be turned off ??? ) Configuration Name: wlan-id-00:02:2d:5c:f5:ef Hardware Name: bus-pcmcia-1.0 Hardware Configuration Name: bus-pcmcia-1.0 Module Name: orinoco_cs Options: blank pressing NEXT d) Wireless Device Settings Operating Mode: Managed Network Name(ESSID): cjp Authentication Mode: Open Key Input Type: ASCII Encryption Key: 12345 pressing WEP KEYS e) Wireless Keys Key Length: preset to 104, trying to change it offers a drop down list with options 64,128,104 ( this is Bug 249709 ), changing to 64 for now. Finishing Network settings. 4.) Checking YaST/System/etc/sysconfig Editor a) Hardware/Newtwork/wlan-id-00:02:2d:5c:f5:ef BOOTPROTO: static BROADCAST: blank ETHTOOL_OPTIONS: blank IFPLUGD_PRIORITY: 10 IPADDR:192.168.0.50/24 MTU: 1500 NAME: PCMCIA Lucent Orinoco, Prism II based, and similar wireless cards NETMASK: blank NETWORK: blank REMOTE_IPADDR: blank STARTMODE: manual UNIQUE:BnC0.jpmKAVAATH5 USERCONTROL:no WIRELESS_AP: blank WIRELESS_AUTH_MODE: open WIRELESS_BITRATE: 11 WIRELESS_CA_CERT: blank WIRELESS_CHANNEL: 12 WIRELESS_CLIENT_CERT: blank WIRELESS_CLIENT_KEY: blank WIRELESS_CLIENT_KEY_PASSWORD: blank WIRELESS_DEFAULT_KEY: blank WIRELESS_EAP_AUTH: blank WIRELESS_EAP_MODE: blank WIRELESS_ESSID: cjp WIRELESS_FREQUENCY: blank WIRELESS_KEY: blank WIRELESS_KEY_0: s:12345 WIRELESS_KEY_1: blank WIRELESS_KEY_2: blank WIRELESS_KEY_3: blank WIRELESS_KEY_LENGTH: 104 ( this should be 40 from step 3e ) seting it to 40 WIRELESS_MODE: Managed WIRELESS_NICK: blank WIRELESS_NWID: blank WIRELESS_PEAP_VERSION: blank WIRELESS_POWER: yes WIRELESS_WPA_ANONID: blank WIRELESS_WPA_IDENTITY: blank WIRELESS_WPA_PASSWORD: blank WIRELESS_WPA_PSK: blank _nm_name: bus-pcmcia-1.0 Saving results, only change WEP_KEY_LENGTH 5. Open a Terminal as root a) workstation1l:/home/cjp # service network restart Shutting down network interfaces: eth0 device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03) eth0 configuration: eth-id-08:00:46:54:1c:89 done eth1 eth1 configuration: wlan-id-00:02:2d:5c:f5:ef done Shutting down service network . . . . . . . . . . . . . done. Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done eth0 device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03) eth0 configuration: eth-id-08:00:46:54:1c:89 eth0 Startmode is 'manual' skipped eth1 eth1 configuration: wlan-id-00:02:2d:5c:f5:ef eth1 Startmode is 'manual' skipped Setting up service network . . . . . . . . . . . . . . done. SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... FATAL: Error inserting ip6table_mangle (/lib/modules/2.6.21-12-default/kernel/net/ipv6/netfilter/ip6table_mangle.ko): Unknown symbol in module, or unknown parameter (see dmesg) SuSEfirewall2: batch committing... SuSEfirewall2: Firewall rules successfully set b) workstation1l:/home/cjp # iwconfig eth1 Warning: Driver for device eth1 has been compiled with version 22 of Wireless Extension, while this program supports up to version 21. Some things may be broken... eth1 IEEE 802.11b ESSID:"cjp" Nickname:"HERMES I" Mode:Managed Frequency:2.457 GHz Access Point: None Bit Rate:11 Mb/s Sensitivity:1/3 Retry limit:4 RTS thr:off Fragment thr:off Encryption key:3132-3334-35 Security mode:open Power Management:off Link Quality=0/92 Signal level=134/153 Noise level=134/153 Rx invalid nwid:0 Rx invalid crypt:47 Rx invalid frag:1058 Tx excessive retries:5 Invalid misc:0 Missed beacon:0 c) workstation1l:/home/cjp # ifup eth1 eth1 eth1 configuration: wlan-id-00:02:2d:5c:f5:ef SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... FATAL: Error inserting ip6table_mangle (/lib/modules/2.6.21-12-default/kernel/net/ipv6/netfilter/ip6table_mangle.ko): Unknown symbol in module, or unknown parameter (see dmesg) SuSEfirewall2: batch committing... SuSEfirewall2: Firewall rules successfully set **** Note Error above !!! *** adding dmesg as attachment workstation1l:/home/cjp # dmesg > /home/cjp/Desktop/dmesg.txt d) After ifup eth1 you would expect the Wireless card to be set to the values entered above, wouldn't you ? workstation1l:/home/cjp # iwconfig eth1 Warning: Driver for device eth1 has been compiled with version 22 of Wireless Extension, while this program supports up to version 21. Some things may be broken... eth1 IEEE 802.11b ESSID:"cjp" Nickname:"HERMES I" Mode:Managed Frequency:2.457 GHz Access Point: None Bit Rate:2 Mb/s Sensitivity:1/3 Retry limit:4 RTS thr:off Fragment thr:off Encryption key:3132-3334-35 Security mode:open Power Management:off Link Quality=0/92 Signal level=134/153 Noise level=134/153 Rx invalid nwid:0 Rx invalid crypt:47 Rx invalid frag:1058 Tx excessive retries:5 Invalid misc:0 Missed beacon:0 Now ESSID, Mode, Encryption key and Security mode are set correctly, while Bit Rate is 2 instead of 11 ( is this correct ?? or will it be negotiated with the AP later ?? ) e) OK now let's try to browse someplace, like 192.168.0.2, which is the interface of the AP. Nope 404. Try to renew the IP address, not really, but I hope the binding is redone ??. workstation1l:/home/cjp # ifrenew eth1 eth1 eth1 configuration: wlan-id-00:02:2d:5c:f5:ef SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... FATAL: Error inserting ip6table_mangle (/lib/modules/2.6.21-12-default/kernel/net/ipv6/netfilter/ip6table_mangle.ko): Unknown symbol in module, or unknown parameter (see dmesg) SuSEfirewall2: batch committing... SuSEfirewall2: Firewall rules successfully set Doesn't look too good either... f) workstation1l:/home/cjp # ifstatus eth1 eth1 eth1 configuration: wlan-id-00:02:2d:5c:f5:ef eth1 is up 3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:02:2d:5c:f5:ef brd ff:ff:ff:ff:ff:ff inet 192.168.0.50/24 brd 192.168.0.255 scope global eth1 eth1 IP address: 192.168.0.50/24 Configured routes for interface eth1: default 192.168.0.1 - - 169.254.0.0 - 255.255.0.0 eth1 Active routes for interface eth1: 192.168.0.0/24 proto kernel scope link src 192.168.0.50 169.254.0.0/16 scope link default via 192.168.0.1 1 of 2 configured routes for interface eth1 up According to this we have an IP ( OK, we set it manually in step 4b ) and we have a route, yet no access possible. Reporting the Error from 5c separately, as this happens with eth0 as well and doesn't block internet access there. Any suggestions ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=278619 ------- Comment #4 from casualprogrammer@yahoo.com 2007-06-02 11:53 MST ------- 5 d) is actually in error, there must have been some residue from previous iwconfigs. In fact neither essid nor key gets set by ifup or service network restart. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=278619 User jbenc@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=278619#c5 Jiri Benc <jbenc@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME --- Comment #5 from Jiri Benc <jbenc@novell.com> 2008-10-02 12:42:56 MDT --- Wasn't able to do anything with that for too long, sorry. Please reopen if 11.0 or 11.1 still have the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com