Cisco 350 Bridge Series

mmira · July 15, 2008, 3:46am

Hello,
I need some help I have install opensuse 11 twice and I still can not connect to internet using wireless ( WIRE NETWORK WORKS ONLY) I have two wireless routers a linksys and a cisco 350.
The Linksys is connected to my DSL router and the Cisco is used just as an access point.

Both devices are shown as being seeing in the network but every single time I put the wep key on both instances it will not work.

With other distros my linksys is the only one that works it fails on the CISCO 350.

In previous releases the cisco has worked and i do not understand why it does not now.

In my windows machine i have no problem it works on both.

Would anybody help me out please? Any idea why?

Thank you very much.

Regards,
Mario

lwfinger · July 15, 2008, 4:44am

mmira wrote:
> Hello,
> I need some help I have install opensuse 11 twice and I still can not
> connect to internet using wireless ( WIRE NETWORK WORKS ONLY) I have
> two wireless routers a linksys and a cisco 350.
> The Linksys is connected to my DSL router and the Cisco is used just as
> an access point.
>
> Both devices are shown as being seeing in the network but every single
> time I put the wep key on both instances it will not work.
>
> With other distros my linksys is the only one that works it fails on
> the CISCO 350.
>
> In previous releases the cisco has worked and i do not understand why
> it does not now.
>
> In my windows machine i have no problem it works on both.
>
> Would anybody help me out please? Any idea why?
>
> Thank you very much.

When you put in the WEP key, I hope you are using a hexadecimal key, and not a
passphrase. There are several, incompatible ways to convert a given phrase to a
WEP key. Fortunately, WPA fixed that problem.

What does the output of a dmesg command say about your wireless? That is always
the first place to start.

If you are sure that the WEP key is correct, you need to use wireshark to
capture network traffic to see why you cannot connect. You didn’t mention what
wireless adapter you are using, but if the output of lsmod shows that mac80211
has been loaded, then you should post the problem and the critical part of the
wireshark dump on linux-wireless@vger.kernel.org.

Larry

mmira · July 15, 2008, 6:45am

Thank for your reply.

Yes I do enter the wep key in a Hex form. I am using a compaq nc6000 laptop.

Here it the messages I get from the supplicant log and messages.

WPA Supplicant log

Trying to associate with 00:40:96:57:15:aa (SSID=‘’ freq=2437 MHz)
Authentication with 00:40:96:57:15:aa timed out.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:40:96:57:15:aa (SSID='’ freq=2437 MHz)
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:40:96:57:15:aa (SSID=‘’ freq=2437 MHz)
Authentication with 00:40:96:57:15:aa timed out.
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:40:96:57:15:aa (SSID='’ freq=2437 MHz)
CTRL-EVENT-SCAN-RESULTS
Authentication with 00:00:00:00:00:00 timed out.

Now from messages log:

Jul 14 16:36:33 localhost NetworkManager: <info> Activation (wlan0) starting connection ‘’
Jul 14 16:36:33 localhost NetworkManager: <info> (wlan0): device state change: 3 → 4
Jul 14 16:36:33 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled…
Jul 14 16:36:33 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started…
Jul 14 16:36:33 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled…
Jul 14 16:36:33 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 14 16:36:33 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting…
Jul 14 16:36:33 localhost NetworkManager: <info> (wlan0): device state change: 4 → 5
Jul 14 16:36:33 localhost NetworkManager: <info> Activation (wlan0/wireless): connection '’ has security, and secrets exist. No new secrets needed.
Jul 14 16:36:33 localhost NetworkManager: <info> Config: added ‘ssid’ value ‘****’
Jul 14 16:36:33 localhost NetworkManager: <info> Config: added ‘scan_ssid’ value ‘1’
Jul 14 16:36:33 localhost NetworkManager: <info> Config: added ‘key_mgmt’ value ‘NONE’
Jul 14 16:36:33 localhost NetworkManager: <info> Config: added ‘auth_alg’ value ‘OPEN’
Jul 14 16:36:33 localhost NetworkManager: <info> Config: added ‘wep_key0’ value ‘<omitted>’
Jul 14 16:36:33 localhost NetworkManager: <info> Config: added ‘wep_tx_keyidx’ value ‘0’
Jul 14 16:36:33 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 14 16:36:33 localhost NetworkManager: <info> (wlan0): supplicant connection state change: 2 → 0
Jul 14 16:36:33 localhost NetworkManager: <info> Config: set interface ap_scan to 1
Jul 14 16:36:33 localhost NetworkManager: <info> (wlan0): supplicant connection state change: 0 → 2
Jul 14 16:36:37 localhost netplugd[1919]: No interface name
Jul 14 16:36:37 localhost netplugd[1919]: Callback failed

Hope this help.
Thanks
Mario

mmira · July 19, 2008, 2:23am

Hello Larry,

Larry as far as the output of lsmod yes MAC80211 tha comes up.
As i mention before the mireless networks are show or seen by the system is just connecting to them is the problem.

Would you lease let me know how to use wireshark I tried to configure but I could not get it to work I am new to this kind of tool.
Hope all this information helps.
Regards,
Mario

here it’s the output of dmesg:

ACPI: PCI Interrupt Link [C0C7] enabled at IRQ 11
ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [C0C7] -> GSI 11 (level, low) -> IRQ 11
ath5k_pci 0000:02:04.0: registered as ‘phy0’
phy0: Selected rate control algorithm ‘pid’
ath5k phy0: Atheros AR5213 chip found (MAC: 0x56, PHY: 0x
ACPI: PCI Interrupt 0000:02:0e.0[A] -> Link [C0C6] -> GSI 11 (level, low) -> IRQ 11
Driver ‘sr’ needs updating - please use bus_type methods
eth0: Tigon3 [partno(BMC5705mA3) rev 3003 PHY(5705)] (PCI:33MHz:32-bit) 10/100/1000Base-T Ethernet 00:0d:9d:90:
b6:85
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[0] TSOcap[1]
eth0: dma_rwctrl[763f0000] dma_mask[64-bit]

ACPI: PCI Interrupt Link [C0C7] enabled at IRQ 11
ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [C0C7] -> GSI 11 (level, low) -> IRQ 11
ath5k_pci 0000:02:04.0: registered as ‘phy0’
phy0: Selected rate control algorithm ‘pid’
ath5k phy0: Atheros AR5213 chip found (MAC: 0x56, PHY: 0x41)
ath5k phy0: RF5111 5GHz radio found (0x17)
ath5k phy0: RF2111 2GHz radio found (0x23)
tg3.c:v3.91 (April 18, 2008)
ACPI: PCI Interrupt Link [C0C6] enabled at IRQ 11
ACPI: PCI Interrupt 0000:02:0e.0[A] -> Link [C0C6] -> GSI 11 (level, low) -> IRQ 11
Driver ‘sr’ needs updating - please use bus_type methods
eth0: Tigon3 [partno(BMC5705mA3) rev 3003 PHY(5705)] (PCI:33MHz:32-bit) 10/100/1000Base-T Ethernet 00:0d:9d:90:
b6:85
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[0] TSOcap[1]
eth0: dma_rwctrl[763f0000] dma_mask[64-bit]

ath5k phy0: noise floor calibration failed (2412MHz)
ath5k phy0: noise floor calibration failed (2417MHz)
ath5k phy0: ath5k_chan_set: unable to reset channel 2 (2417 Mhz)
wlan0: failed to set channel 2 (2417 MHz) for scan
ath5k phy0: noise floor calibration failed (2412MHz)
ath5k phy0: ath5k_chan_set: unable to reset channel 1 (2412 Mhz)
wlan0: failed to restore operational channel after scan

ath5k phy0: noise floor calibration failed (5825MHz)
ath5k phy0: noise floor calibration failed (5825MHz)
ath5k phy0: noise floor calibration failed (5825MHz)
ath5k phy0: noise floor calibration failed (5825MHz)
ath5k phy0: noise floor calibration failed (5825MHz)
ath5k phy0: noise floor calibration failed (2412MHz)
ath5k phy0: ath5k_chan_set: unable to reset channel 1 (2412 Mhz)
wlan0: failed to set channel 1 (2412 MHz) for scan
usb 4-1: USB disconnect, address 3
ath5k phy0: noise floor calibration failed (2412MHz)
ath5k phy0: noise floor calibration failed (2412MHz)
ath5k phy0: noise floor calibration failed (2412MHz)
ath5k phy0: noise floor calibration failed (2412MHz)
ath5k phy0: noise floor calibration failed (2412MHz)
mtrr: no MTRR for 98000000,2000000 found

Output of messages for both access points: 1) CISCO 350

Jul 18 17:17:26 linux-u6e2 kernel: wlan0: Initial auth_alg=0
Jul 18 17:17:26 linux-u6e2 kernel: wlan0: authenticate with AP 00:0a:41:ee:c0:61
Jul 18 17:17:26 linux-u6e2 kernel: wlan0: RX authentication from 00:0a:41:ee:c0:61 (alg=0 transaction=2 status=0)
Jul 18 17:17:26 linux-u6e2 kernel: wlan0: authenticated
Jul 18 17:17:26 linux-u6e2 kernel: wlan0: associate with AP 00:0a:41:ee:c0:61
Jul 18 17:17:26 linux-u6e2 kernel: wlan0: authentication frame received from 00:0a:41:ee:c0:61, but not in authenticate state - ignored
Jul 18 17:17:26 linux-u6e2 kernel: wlan0: RX AssocResp from 00:0a:41:ee:c0:61 (capab=0x31 status=10 aid=2008)
Jul 18 17:17:26 linux-u6e2 kernel: wlan0: AP denied association (code=10)
Jul 18 17:17:27 linux-u6e2 kernel: wlan0: associate with AP 00:0a:41:ee:c0:61
Jul 18 17:17:27 linux-u6e2 kernel: wlan0: RX AssocResp from 00:0a:41:ee:c0:61 (capab=0x31 status=10 aid=2008)
Jul 18 17:17:27 linux-u6e2 kernel: wlan0: AP denied association (code=10)
Jul 18 17:17:27 linux-u6e2 kernel: wlan0: associate with AP 00:0a:41:ee:c0:61
Jul 18 17:17:27 linux-u6e2 kernel: wlan0: RX AssocResp from 00:0a:41:ee:c0:61 (capab=0x31 status=10 aid=2008)
Jul 18 17:17:27 linux-u6e2 kernel: wlan0: AP denied association (code=10)
Jul 18 17:17:27 linux-u6e2 kernel: wlan0: association with AP 00:0a:41:ee:c0:61 timed out
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: Initial auth_alg=0
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: authenticate with AP 00:0a:41:ee:c0:61
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: RX authentication from 00:0a:41:ee:c0:61 (alg=0 transaction=2 status=0)
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: authenticated
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: associate with AP 00:0a:41:ee:c0:61
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: authentication frame received from 00:0a:41:ee:c0:61, but not in authenticate state - ignored
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: RX AssocResp from 00:0a:41:ee:c0:61 (capab=0x31 status=10 aid=2008)
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: AP denied association (code=10)
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: RX AssocResp from 00:0a:41:ee:c0:61 (capab=0x31 status=10 aid=2008)
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: AP denied association (code=10)
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: associate with AP 00:0a:41:ee:c0:61
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: RX AssocResp from 00:0a:41:ee:c0:61 (capab=0x31 status=10 aid=2008)
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: AP denied association (code=10)
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: associate with AP 00:0a:41:ee:c0:61
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: RX AssocResp from 00:0a:41:ee:c0:61 (capab=0x31 status=10 aid=2008)
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: AP denied association (code=10)
Jul 18 17:17:44 linux-u6e2 kernel: wlan0: association with AP 00:0a:41:ee:c0:61 timed out
Jul 18 17:17:52 linux-u6e2 kernel: hub 2-0:1.0: unable to enumerate USB device on port 5

Second is from the LINKSYS:
Jul 18 17:20:27 linux-u6e2 kernel: wlan0: Initial auth_alg=0
Jul 18 17:20:27 linux-u6e2 kernel: wlan0: authenticate with AP 00:0f:66:2a:7d:f8
Jul 18 17:20:27 linux-u6e2 kernel: wlan0: RX authentication from 00:0f:66:2a:7d:f8 (alg=0 transaction=2 status=0)
Jul 18 17:20:27 linux-u6e2 kernel: wlan0: authenticated
Jul 18 17:20:27 linux-u6e2 kernel: wlan0: associate with AP 00:0f:66:2a:7d:f8
Jul 18 17:20:27 linux-u6e2 kernel: wlan0: RX AssocResp from 00:0f:66:2a:7d:f8 (capab=0x411 status=0 aid=4)
Jul 18 17:20:27 linux-u6e2 kernel: wlan0: associated
Jul 18 17:20:27 linux-u6e2 kernel: wlan0: switched to short barker preamble (BSSID=00:0f:66:2a:7d:f8)
Jul 18 17:20:27 linux-u6e2 dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 18 17:20:27 linux-u6e2 dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 18 17:20:27 linux-u6e2 dhclient: All rights reserved.
Jul 18 17:20:27 linux-u6e2 dhclient: For info, please visit ISC DHCP
Jul 18 17:20:27 linux-u6e2 dhclient:
Jul 18 17:20:27 linux-u6e2 dhclient: wmaster0: unknown hardware address type 801
Jul 18 17:20:27 linux-u6e2 dhclient: wmaster0: unknown hardware address type 801
Jul 18 17:20:27 linux-u6e2 dhclient: Listening on LPF/wlan0/00:11:85:1b:4f:ad
Jul 18 17:20:27 linux-u6e2 dhclient: Sending on LPF/wlan0/00:11:85:1b:4f:ad
Jul 18 17:20:27 linux-u6e2 dhclient: Sending on Socket/fallback
Jul 18 17:20:31 linux-u6e2 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jul 18 17:20:31 linux-u6e2 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jul 18 17:20:41 linux-u6e2 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 18 17:20:48 linux-u6e2 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jul 18 17:21:00 linux-u6e2 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Jul 18 17:21:12 linux-u6e2 dhclient: caught deadly SIGTERM
Jul 18 17:21:12 linux-u6e2 dhclient: could not restore resolv.conf: No such file or directory
Jul 18 17:21:12 linux-u6e2 kernel: wlan0: Initial auth_alg=0
Jul 18 17:21:12 linux-u6e2 kernel: wlan0: authenticate with AP 00:0f:66:2a:7d:f8
Jul 18 17:21:12 linux-u6e2 kernel: wlan0: RX authentication from 00:0f:66:2a:7d:f8 (alg=0 transaction=2 status=0)
Jul 18 17:21:12 linux-u6e2 kernel: wlan0: authenticated
Jul 18 17:21:12 linux-u6e2 kernel: wlan0: associate with AP 00:0f:66:2a:7d:f8
Jul 18 17:21:12 linux-u6e2 kernel: wlan0: disassociate(reason=3)
Jul 18 17:21:12 linux-u6e2 kernel: wlan0: RX AssocResp from 00:0f:66:2a:7d:f8 (capab=0x411 status=0 aid=4)
Jul 18 17:21:12 linux-u6e2 kernel: wlan0: associated
Jul 18 17:21:12 linux-u6e2 kernel: wlan0: disassociate(reason=3)

lwfinger · July 19, 2008, 4:00am

mmira wrote:
> Hello Larry,
>
> Larry as far as the output of lsmod yes MAC80211 tha comes up.
> As i mention before the mireless networks are show or seen by the
> system is just connecting to them is the problem.
>
> Would you lease let me know how to use wireshark I tried to configure
> but I could not get it to work I am new to this kind of tool.
> Hope all this information helps.

The best use of wireshark would be with a second computer with a wireless
interface. If you do not have another available, then I would just post the
dmesg output with a complete explanation on linux-wireless@vger.kernel.org.

Larry