Intel 3945 roaming issues

I have some 1242 AP's set up with Cisco Fast roaming. My 3945 clients roam fine, but after a few seconds, they lose their IP address. If I have a constant ping going, my ping will drop for about 3 seconds, then replys will go for about 4 seconds. It will continue to do this about three times until stabilizing and then it works great until roaming again. Anyone have any ideas? TAC blames Intel. Intel says to work with Dell. Dell has no clue. Any help would be appreciated.

Hi Allan,
Have you tried tweaking Roaming Aggressiveness in the Intel PROSet client utility? You may also want to try turning off Auto-RF just to see if it makes any difference.
I had costumers which had problems with the ProSet Utility. We deinstlled ad used the Windows XP Wireless Zero configuration.
The Intel Wireless NIC have actual some issues with the Cisco environment.
Some examples from the forum:
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd73e2f
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=Security%20and%20Network%20Management&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.ee95e05
Please check if the wireless clients you use are specified in the "Cisco Compatible Client Devices" list:
http://www.cisco.com/web/partners/pr46/pr147/partners_pgm_partners_0900aecd800a7907.html
The mentioned versions can be found here:
http://www.cisco.com/warp/public/765/ccx/versions_and_features.shtml
Best regards,
Frank

Similar Messages

Intel 3945 won't work after update.

After updating a Thinkpad T60 with the Intel 3945 wireless card I am unable to connect to wireless. Wicd's GTK front end even fails to start, but the problem is not with Wicd. Anything attempting to access the card will hang, even 'ifconfig wlan0 up' hangs and I have to kill it.
Here is 'lsmod|grep iwl':
iwl3945 63543 0
iwl_legacy 45018 1 iwl3945
mac80211 203227 2 iwl_legacy,iwl3945
cfg80211 147716 3 mac80211,iwl_legacy,iwl3945
Here is the relevant information from everything.log:
Feb 22 06:48:49 t60-arch kernel: [ 4.832450] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s
Feb 22 06:48:49 t60-arch kernel: [ 4.832453] iwl3945: Copyright(c) 2003-2011 Intel Corporation
Feb 22 06:48:49 t60-arch kernel: [ 4.832641] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Feb 22 06:48:49 t60-arch kernel: [ 4.832657] iwl3945 0000:03:00.0: setting latency timer to 64
Feb 22 06:48:49 t60-arch kernel: [ 4.886080] iwl3945 0000:03:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
Feb 22 06:48:49 t60-arch kernel: [ 4.886084] iwl3945 0000:03:00.0: Detected Intel Wireless WiFi Link 3945ABG
Feb 22 06:48:49 t60-arch kernel: [ 4.886235] iwl3945 0000:03:00.0: irq 44 for MSI/MSI-X
Feb 22 06:48:49 t60-arch kernel: [ 4.930430] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
Feb 22 06:53:49 t60-arch kernel: [ 311.946831] iwl3945 0000:03:00.0: iwlwifi-3945-2.ucode firmware file req failed: -2
Feb 22 06:54:49 t60-arch kernel: [ 372.106844] iwl3945 0000:03:00.0: iwlwifi-3945-1.ucode firmware file req failed: -2
Feb 22 06:54:49 t60-arch kernel: [ 372.106853] iwl3945 0000:03:00.0: Could not read microcode: -2
Here is 'ls /lib/firmware/|grep 3945':
iwlwifi-3945-2.ucode
Here is 'rfkill list':
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
2: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
Obviously it is a firmware issue, even though linux-firmware is properly installed and has been reinstalled from other sources in an attempt to get it working.
Last edited by elliott (2012-02-22 20:10:44)

Just updated and rebooted, but wireless still seems to be working for me (also have a T60 using iwl3945. Same modules loaded that gozes listed. Here's iwl3945 containing lines in my everything.log since the reboot
Apr 5 17:39:46 localhost kernel: [ 6.267873] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s
Apr 5 17:39:46 localhost kernel: [ 6.267877] iwl3945: Copyright(c) 2003-2011 Intel Corporation
Apr 5 17:39:46 localhost kernel: [ 6.268108] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Apr 5 17:39:46 localhost kernel: [ 6.268123] iwl3945 0000:03:00.0: setting latency timer to 64
Apr 5 17:39:46 localhost kernel: [ 6.322986] iwl3945 0000:03:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
Apr 5 17:39:46 localhost kernel: [ 6.322991] iwl3945 0000:03:00.0: Detected Intel Wireless WiFi Link 3945ABG
Apr 5 17:39:46 localhost kernel: [ 6.323145] iwl3945 0000:03:00.0: irq 46 for MSI/MSI-X
Apr 5 17:40:03 localhost kernel: [ 29.666416] iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9
I'm running the stock Arch kernel from the core repo right now and linux firmware package is 20120227-1. Let me know if there's other info I can give to try and help track down the difference.

Strange behavior with Cisco AP and Intel 3945 wireles card

Hi,
I have an interesting problem with an Intel 3945 A/G card, and my cisco APs.
1. Given:
Cisco 1100 and 1200 AP running IOS 12.3.8-JEA
Two laptop, one with Intel 2200 MPCI Card, the other with Intel 3945 MPCI Card
Microsoft AD with IAS radius server
a. 1 SSID with Simple EAP-TLS configuration Enterprise WPA/TKIP, no vlans, broadcast SSID. both card associate correctly and operate normally.
b. 2 SSID, 1 with simple EAP-TLS configuration Enterprise WPA/TKIP (broadcast), and 2nd SSID Open/No encryption/No authentication (not broadcasted), both cards associate correctly and operate normally.
c. 2 SSID, 1 with simple EAP-TLS configuration Enterprise WPA/TKIP (broadcast), and 2nd SSID WPS-PSK (not broadcasted), both cards operate normally.
Now it gets interesting:
c. 2 SSID, 1 with EAP-TLS/WPA Enterprise on its own VLAN 102, 2nd SSID Open/No Encryption/No authentication on a separate VLAN 105, VLAN 1 is used for admin and radius backhaul to IAS.
If both SSID are broadcasted via mbssid guest-mode both Intel cards work as expected
If neither SSID are broadcasted, both Intel cards work as expected
If either SSID is broadcasted via normal guest-mode command, the Intel 2200 associates and works correctly, but the Intel 3945 refuses to assocate to the AP.
Has anyone heard of side-effect?
Alan

I'm seeing a similar issue with the 3945 right now. However in my example the following is the case;
APs are 1200 series IOS upgraded running 802.11b interfaces only. There are multiple SSIDs NONE of which are broadcasting.
We've got a few different client types. The Cisco CB21ABG cards are fine, as are the Intel 2200 and 7920 phones. It's only the 3945 that has a problem and it's running Intel's 10.5.1.68 driver which is the latest. I'm considering downgrading it to an older driver.
Anybody got a definate fix for this Intel card???

Dell D620-Intel 3945 + PEAP

Has anyone noticed an issue with Dell D620 Laptops using the Intel 3945 card and WinXP with regards to PEAP authenication (mschapv2)? We are migrating to a LWAPP enviroment, but current we have a large autonomous AP enviroment. We have a very mobile group of users that just received new laptops and ever since they have had random connections issues with the 3945Intel card. The laptop will go from full strengh to no strengh without even moving. At times the laptop even gets in a state where it requires a reboot in order to get authenictated. We have tried the newest Intel proset 11.1 and that doesn't seem to have resolved the issues. There is nothing in any logs to point to an issue. You can have an older laptop with an intel 2200card right next to it and not have these issues.

Ensure that you don't have 2 client connection managers enabled in your PC. For example, a Microsoft WzC and a ADU on the same pc will result in lot of connectivity issues. In such cases. disable one of these client utilities.

Intel 3945 driver needs hotplug firmware

I'm having some issues getting the Intel 3945 wifi adapter to become recognized by Oracle Enterprise Linux 5.5.
It seems that the 802.11 and the driver are present however it seems to need a microcode piece as well. This is documented at:
[http://ipw3945.sourceforge.net/|http://ipw3945.sourceforge.net/]
Step 1 on the requirements listing is for the microcode.
The install docs say to look at /etc/hotplug/firmware.agent file to get the directory.
I just redid my installation and this file is still not present.
It also lists the steps to use the kernel source to come up with the directory.
So, make gconfig and take a look:
Device Drivers ->
Generic Driver Options ->
are present, however,
Hotplug firmware loading support
after that is not present. I saw some options for CPU hotplugging and memory hotplugging but the install docs are calling for this option which doesn't seem to be present.
So, what's the easiest way to get hotplugging support on this version of Linux? I've tried the Red Hat forums but everyone there says to just install the ucode to /lib/firmware and off you go.
thanks in advance,
alan

http://dag.wieers.com/rpm/packages/ipw3945d/
http://dag.wieers.com/rpm/packages/dkms-ipw3945/
http://dag.wieers.com/rpm/packages/ipw3945-firmware/
All of these kept giving 404 errors unless I chose the source option. Oh well. So I gave up and thought I'd just compile up the latest kernel and see if that would help.
I checked for the hotplug option and it still isn't there so I have no clue what Intel was talking about.
I did remember seeing another message about the ucode file having a different file name so I finally ran it down.
All you need to do is to find the firmware file and copy it so it reads:
/lib/firmware/iwlwifi-3945-2.ucode
and then service network start and up she comes. I tried various permutations of strace -f trying to figure out the filename but never could come up with it. Oh well. Then it's:
add the following to modprobe.conf
options iwl3945 disable_hw_scan=1
and finally:
service NetworkManager restart
to get the little network icon on the upper right-hand side so I can get the easy wifi access point pick list.
Then I ran firefox and it connected to web pages.
Thanks for effort,
alan

L2 Roaming issue with Avaya wireless phone on WISM -V6.0.196.0

Hello Friends,
I am facing Layer2 roaming issue with Avaya Wirless phone 3620 which are configured WPA / Pre-shared key auth with a SSID1 and face a cut or delay in the voice.
But when i use Cisco Wireless phones and try to roam between one LWAP to other i dont face a cut or delay in the vocie which are
Configured with 802.1x +CCKM auth .
Then i configured new SSID 3 with 802.1x+CCKM settings for the new Avaya wireless module 3631 , but still face cut and delay while doing Layer 2 roaming.
While i was using these AP in WDS mode i never faced this Layer 2 roaming issue with Avaya wireless phones.
In current WISM all the LWAPs are supporting properly to the Cisco phone and Wirelss laptop clients.
I request you to please let me know how do i proceed further to solve the issue and please let me know if anybugs or incompatibilty for WISM with Avaya wireless phones.
Appreciate your response.
Regards,
KA.

Hello ,
Can any body please respond to my above Query.
Thanks,
KA.

Atheros AR5001+ and Intel 3945/ABG [Golan] #2

Hello, everyone, I am trying to connect two network cards, an Atheros AR5001X + and an Intel 3945/ABG in Ad-Hoc mode, the cards are associated (apparently) but a machine does not ping and do not surf!
It is true that I have to use a different Broadcast for both wired and wireless?
I follow this steps on atheros(internet):
iwconfig ath0 mode ad-hoc essid "Wireless_Network"
ifconfig ath0 192.168.0.10 netmask 255.255.255.0 up
And Intel:
iwconfig wlan0 mode ad-hoc essid "Wireless_Network"
ifconfig wlan0 192.168.0.20 netmask 255.255.255.0 up
My modules is ath_pci(i tested ath5k too) and iwl3945.
And my Internet is HSDPA USB Modem(ZTE MF622).
Thanks in advance.

Hello, everyone, I am trying to connect two network cards, an Atheros AR5001X + and an Intel 3945/ABG in Ad-Hoc mode, the cards are associated (apparently) but a machine does not ping and do not surf!
It is true that I have to use a different Broadcast for both wired and wireless?
I follow this steps on atheros(internet):
iwconfig ath0 mode ad-hoc essid "Wireless_Network"
ifconfig ath0 192.168.0.10 netmask 255.255.255.0 up
And Intel:
iwconfig wlan0 mode ad-hoc essid "Wireless_Network"
ifconfig wlan0 192.168.0.20 netmask 255.255.255.0 up
My modules is ath_pci(i tested ath5k too) and iwl3945.
And my Internet is HSDPA USB Modem(ZTE MF622).
Thanks in advance.

WRT110 crashes with Vista SP1 and Intel 3945

I have a WRT110 with the latest firmware 1.0.4, an a Dell XPS1330 with the Intel 3945abg wireless card and the latest drivers in Intel. When ever my laptop tries to connect the router crashes and drops all other connections with other wireless devies and wired devices. I also have another laptop running XP that works great on the wireless connection. It's same to say the problem is limited to the Vista machine and the Intel 3945 wireless card. Now sure what to do?

I have the same problem. Took me a while to figure out that when i connected my Toshiba laptop with Vista and Intel 3945 Router and network crashed couldnot even get the router accessed on hardwired computer. Everything returns back to normal when laptop disconnected from wireless network
Customer support was not able to help, called them twice. I solved by connecting an old wireless router to one of the ports of Linksys and connect my Vista laptop on that wireless network. That is not really a solution but if you'd like to, return the router until they can at least admit that there is a problem with compatibility, upgrading firmware on wireless adaptor did not help.
(Mod note: Edited for guideline compliance.)
Message Edited by kent07 on 11-06-2008 06:33 PM

My WLAN chokes when going too fast (Intel 3945 w/ Netgear) [SOLVED]

I recently upgraded my Internet connection from 8/1 to 24/10 and since then I have been able to download at the highest speed without any problems, except for this one of course.
When I'm torrenting and getting higher than 2 MB/s (yes, megabytes) speeds, the connection suddenly "chokes" and puts some sort of threshold on itself at about 150 KB/s. The threshold is not put only on the torrents, but on my entire connection to *this* computer. All of the other computers connected to the router still work fine. This problem doesn't go away unless I reconnect myself to my router. This happens only on Linux, not on Windows as far as I can tell.
What can be the problem? I have Intel 3945 drivers and 2.6.31.
Last edited by skorpan (2009-11-30 21:39:20)

This is *EXACTLY* what has been happening to me; thought I was going crazy. I also have an intel iwl3945 and 2.6.31. My router is a netgear wgr614v6. When I associate from *this* computer, after a seemingly random period of time, my connection gets chocked from the normal ~1.5 mb/s to 113 kb/s. This only happens to this computer, however, it *doesn't* happen over the local network, just to the internet. I can only use my full bandwidth after re-associating with the router. I was thinking it had to be a bug in the router firmware, but this looks like too much of a coincidence now...
what router do you use?

Client roaming issue

I am trying to track down some performance issues on my wireless network, and hope someone out there will help educate me! My environment:
Access Points are all 1231, 1242, and 1252
The 802.11g radios are active
All APs are configured to use Channel 4
WEP security (I know, I know ...)
Clients are either laptop users (mostly Dells) or Intermec vehicle-mounted terminals with Prism NICs
Clients are VERY active as far as moving around the building
Here is what I *think* is happening:
The clients don't "roam" as quickly as I think they should - in other words, they remain associated to the active AP too long. Their signal gets too low before they pick up another AP.
I wonder if I need to adjust the data rates on the APs (like maybe disable the lowest ones). For example, if I disable the 1.0, 2, and 5.5 Mb/sec rates, does that mean that a client will look for another AP when the "speed" drops below 6 Mb/sec? If so, then by disabling the lowest data rates, the client would be forced to find another AP before the data rates drops to nothing, right?
I also don't understand the power ratings - I've just left them at the default settings - does this affect performance as well?
Thanks in advance ...

Hi Susan,
How are you doing today ... Sounds like you have a little mess on your hands. Lets sort through some of these issues. It also sounds like you are open to feedback, that is always great to hear!
First. I need to point out your channel selection and this could be a the likly cause for your roaming issue. Follow along and let me explain why.. There is a BIG miss understanding when doing wifi that folks think that all the AP needs to be on the same channel. In fact, you should only use channels 1,6 and 11. When you use the same channel off channels like 4 you cause interference.
Let me explain why with a real world example. Think back to the late 80s when cordless phones were hitting the market. Do you remember when you would pick up the phone and you would hear your neighbor's conversation? Well that is becuase you were on the same channel you shared the same freq. Now what happens when 4 people (on 2 calls) try to all talk at the same time!? It becomes a mess, right. "Can you say that again", "I didnt hear you", "What was that !?".
Well the same holds true with WiFi. If all the aps are on the same channel you have one big cordless phone call going, for exmaple.So the first thing we need to do is correct the channel issue before you do anything else. It WiFi channel uses 22 MHz of RF. Thus what you can only use 1,6,11. You also want to make sure you dont put like channels close together. For example, don't line up a hallway with all channel 1... here is some reading
http://www.cisco.com/en/US/docs/wireless/technology/channel/deployment/guide/Channel.html

Wicd woes...Intel 3945...assistance requested

I have tried to use Wicd in the past without success and now that it's coming to the [extra] repository I thought for sure it'd be working by now, but I'm not having any luck at all. It doesn't even manage my DHCP wired connection, and half the time the gui doesn't even appear when I launch it.
As the title states, I'm running an intel wireless 3945 (iwlwifi drivers) and I've installed the wicd from [testing]
My rc.conf:
MODULES=(vboxdrv coretemp i8k acpi-cpufreq cpufreq_ondemand fglrx b44 mii iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
HOSTNAME="dublin"
lo="lo 127.0.0.1"
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(lo !eth0 !wlan0)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
DAEMONS=(syslog-ng hal cpufreq wicd network !dhcdbd !networkmanager !@netfs @alsa @crond @cups @ntpd @sensors @sshd @transmissiond)
I've tried running it with and without the standard network daemon enabled--both have the same non-working result.
The console output when I run the tray and try to open the gui:
[thayer@dublin ~]$ /usr/lib/wicd/tray.py
attempting to connect daemon...
success
ERROR:dbus.proxies:Introspect error on :1.3:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
File "/usr/lib/wicd/edgy.py", line 85, in set_signal_image
config.DisableLogging()
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 64, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 136, in __call__
**keywords)
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 603, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
attempting to connect daemon...
success
starting...
refreshing...
ERROR:dbus.proxies:Introspect error on :1.3:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
File "./gui.py", line 956, in <module>
app = appGui()
File "./gui.py", line 695, in __init__
self.refresh_networks(fresh=False)
File "./gui.py", line 855, in refresh_networks
if wired.CheckPluggedIn() or wired.GetAlwaysShowWiredInterface():
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 64, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 136, in __call__
**keywords)
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 603, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
File "/usr/lib/wicd/tray.py", line 7, in <module>
import edgy
File "/usr/lib/wicd/edgy.py", line 214, in <module>
gtk.main()
KeyboardInterrupt
[thayer@dublin ~]$

Thanks you two for the advice, I've had some limited success with your tips...
schivmeister wrote:
As for the gui, only one click is needed. If you double-click, it won't appear For DHCP i presume you had pulled in dhcclient/dhcpcd, but sometimes configuring the IP takes a long time? This may be a DNS issue, and I suggest you try opendns.
But first, Network daemon should be enabled before wicd, the interfaces must not be disabled either. Also, 1.3.4 is definitely better than 1.3.1
The funny thing is, I already use opendns at the router level. You are correct that dhclient and dhcpcd was already installed and for the record I tried both clicking and running the gui in standalone mode.
Reversing the order of wicd and network in the daemons array appears to be what fixed the bigger issues. Uncommenting the interfaces might have helped too, but I'm going to try removing the wlan0 device because currently Arch hangs during boot while trying to find wlan0.
So anyway, I rebooted with these changes and was happy to see my wireless had connected flawlessly. However, I normally use the wired connection when I'm sitting in my office and when I tried to connect to it, it just defaults back to the wireless after a few seconds. I created a profile as directed, so it must be something else going on.
At any rate, I've got SOMETHING working with wicd, so thanks again...
UPDATE1:
I disabled (!) wlan0 from the interfaces array and Wicd still picks it up okay, so at least the network daemon doesn't hang at boot while trying to associate with wlan0.
Last edited by thayer (2007-11-21 16:23:29)

3945BG Intel Adapter PEAP issue

Hi, We have few SONY laptops with this builtin adapter.. Unfortunately, these adapters do not seem to work when PEAP with WinXP, is used with Cisco APs. TAC has already disowned this issue, saying it is a Intel issue. As we are not getting much of support from our Laptop vendor, i am just curious if anyone has this issue and found any good workaround...
If any third party supplicant can overcome this issue, please provide pointers.. We would like to evaluate before purchasing it..
Well, fyi.. i have upgraded the latest firware on Intel.

Checked this link the SONY only support CCX v3 that part of the PEAP may not work w/ Cisco AP.
http://www.cisco.com/web/partners/pr46/pr147/partners_pgm_partners_0900aecd800a7907.html
http://www.cisco.com/warp/public/765/ccx/versions_and_features.shtml
Better check w/ SONY what is their CCX support ver., or try to use other authentication method....
Hopes this help.

Layer 3 roaming issue

Hi all,
i have two wireless networks with two subnet (see the attached drawing) , all controllers run v4.2 access points type is 1020 .
the first network in hall 1 have 4 wlc in subnet 172.16.40.X , the security is WEP key for wireless phone
the second network in hall two have one WiSM in subnet 172.26.40.Y the security is WEP key for wireless phone also
all controllers and WiSM in same Mobility group .
the issue is ,when wireless phone roaming from hall one to hall two or from hall two to one it dropped the connection and not working
please advice

Examples :
WLC1 has management as 192.168.1.2
WLC2 has management as 192.168.1.3
WLC1 has the SSID "employees" linked to interface "emp_int" which has ip 192.168.50.2
WLC2 has the SSID "employees" linked to interface "employee_int" which has ip 192.168.80.2
In this case, we have layer 3 roaming. Meaning that normally the client would need to change its ip from 192.168.50.x to 192.168.80.x but thanks to mobility anchoring mechanism, the WLC2 forwards all traffic back to WLC1 so that the client can keep its ip address in 192.168.50.x
If the situation was that both employee interfaces were in the 192.168.50.x on both WLCs, then we would have layer 2 roaming. Meaning the client entry is simply moved to WLC2 and WLC2 handles all the traffic. WLC1 has nothing to do anymore with this client.
conclusion : the ip addresses of the management interfaces don't matter to decide if it's layer 2 or 3 roaming, it's the ip of the dynamic interface of SSID which matters
Nicolas
===
Don't forget to rate anwers that you find useful

IP Phone 7921 / 7925 roaming issues after WLC upgrade from Version 7.2 to 7.3 and / or 7.4

Hi,
We have a customer which is using a Cisco WLC 5508 and 3502I APs. As he used the 7.2.103 release, There were no issues with VoWLAN. Now he needed new APs and ordered the 2602I. To use them he needed to upgrade the WLC to a 7.3 or later release. After the upgrade, he now encounters problems while roaming with the phones. The phones were tested with FW 1.4.1, 1.4.2 and 1.4.3.
Configuration is set according to wireless voice design guides (VoWLAN DG 4.1, 7921 Deployment Guide). A Cisco TAC is also in progress, but they seem to be uncertain whether it is a wireless or CUCM issue, but I don't see a reason why it should be the CUCM when the only thing changed is the WLC Software Version.
Is there anybody who is aware of such issues and can offer help?
Thank you in advance.
Best regards,
Patrick

Hi,
we had a TAC ticket open with this customer and after some time, the TAC gave us the advise to use this release and the problems are now solved.
So for others having the same issue: If you only need to support the 2600 APs, stay with the latest 7.2 release as there are some issues with the 7.3 and 7.4 release. If the customer requires HA, AVC or any of the new features + wireless voice, be very careful as it seems that the newer releases are having problems with that. I hope that Cisco will fix this very soon.
regards,
Patrick

802.1X authentication and roaming issues

Hi there,
I have installed about 2 days ago one Cisco WCS 2504 and 11 APs. Everything is doing well regarding to WEP authentication. But I have a Radius Server that is alson running with some issues on wireless:
- Unless I open network settings and click connect on that config I cannot obtain a valid IP Address;
- Roaming is not working also;
FYI the certificate (on radius) has expired
TY

Not all these are radius issues
- WPA2 Wlan still ok (144Mbit), but dont know when roaming works (how can I know/change these settings?);
Look at the client adapter as there is usually a roaming aggressiveness option on these devices. Play around with that.
- Radius autenticated with 802.11 Data Encryption on 40 bits Key size connects always at 54Mbps (g) and auto authenticate but dont know when roaming works (how can I know/change these settings?);
802.11n only supports open authentication or WPA2/AES. WEP is not supported so that why you get up to 54mbps.
- Radius with 802.11 Data Encryption with none key size, doesnt authenticate connects 144Mbit but doesnt acquire IP Address
You have a configuration issue either in the WLC or the switch.
Sent from Cisco Technical Support iPhone App

Intel 3945 roaming issues

Similar Messages

Maybe you are looking for