Roaming - Ich komm nicht weiter

Forum zu den aktuellen LANCOM Wireless Accesspoint Serien

Moderator: Lancom-Systems Moderatoren

Antworten
tmueller
Beiträge: 3
Registriert: 30 Apr 2012, 13:06

Roaming - Ich komm nicht weiter

Beitrag von tmueller »

Hi zusammen,

vorab möchte ich mich schon mal für den langen Thread entschuldigen, aber ich versuche es, so ausführlich wie möglich zu machen. Ich habe hier mich hier im Forum schon eingelesen und auch schon ähnliche Themen gefunden, aber leider keine Lösung. In dem folgenden Thema wird eigentlich so ziemlich genau das gleiche Thema angesprochen, was wir haben, aber wir können nicht einfach die HP Router austauschen (wenn es denn daran liegt, was ich bei uns nicht glaube...) --> http://www.lancom-forum.de/topic,11220, ... bleme.html

Unser Aufbau:

1x WLC-4006
4x L-322agn
2x SSID (intern + Gäste mit Public Spot)
2x HP Procurve Router/Switches

Das WLAN funktioniert eigentlich problemlos und man kann ganz normal arbeiten, bzw. im Internet surfen. Sobald man aber den Standort wechselt und sich das Gerät im Hintergrund auf einen anderen Accesspoint verbindet, geht erstmal gar nichts mehr. Das WLAN auf dem Gerät zeigt immer verbunden an, aber man kann nichts mehr im Netz machen. Nicht mal ein Ping auf AGN/WLC oder Router/Switch ist möglich. Das ganze hält dann so ca. 3-6 Minuten an und dann geht es einfach so wieder. Es ist nicht ersichtlich, an was es liegt.

Es spielt auch keine Rolle ob Handy/PDA (Android/Windows/Iphone) oder Notebook (Windows, Mac und Linux). Wir haben hier wirklich von jedem was im Einsatz und das Verhalten ist bei allen exakt das gleiche.

Ich habe hier mal Log Auszüge aus den Access Points und von meinem Notebook:

Auszug, nachdem ich das WLAN Modul eingeschalten habe:

Code: Alles auswählen

Successful connect:

Apr 30 11:37:12 HOSTNAME NetworkManager[1189]: <info> (wlan0): deactivating device (reason 'managed') [2]
Apr 30 11:37:12 HOSTNAME NetworkManager[1189]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Apr 30 11:37:12 HOSTNAME NetworkManager[1189]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Apr 30 11:37:12 HOSTNAME NetworkManager[1189]: <info> (eth0): now managed
Apr 30 11:37:12 HOSTNAME NetworkManager[1189]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 30 11:37:12 HOSTNAME NetworkManager[1189]: <info> (eth0): bringing up device.
Apr 30 11:37:12 HOSTNAME NetworkManager[1189]: <info> (eth0): preparing device.
Apr 30 11:37:12 HOSTNAME NetworkManager[1189]: <info> (eth0): deactivating device (reason 'managed') [2]
Apr 30 11:38:29 HOSTNAME NetworkManager[1189]: <info> WiFi now enabled by radio killswitch
Apr 30 11:38:29 HOSTNAME NetworkManager[1189]: <info> (wlan0): bringing up device.
Apr 30 11:38:29 HOSTNAME kernel: [ 2348.438222] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 30 11:38:29 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: starting -> ready
Apr 30 11:38:29 HOSTNAME NetworkManager[1189]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Apr 30 11:38:29 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: ready -> inactive
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Auto-activating connection 'SSID'.
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) starting connection 'SSID'
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> (wlan0): preparing device.
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0/wireless): access point 'SSID' has security, but secrets are required.
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0/wireless): connection 'SSID' has security, and secrets exist.  No new secrets needed.
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Config: added 'ssid' value 'SSID'
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Config: added 'scan_ssid' value '1'
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Config: added 'auth_alg' value 'OPEN'
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Config: added 'psk' value '<omitted>'
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> Config: set interface ap_scan to 1
Apr 30 11:38:33 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: inactive -> scanning
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Apr 30 11:38:35 HOSTNAME kernel: [ 2355.057329] wlan0: authenticate with 00:a0:57:18:d0:31 (try 1)
Apr 30 11:38:35 HOSTNAME kernel: [ 2355.059154] wlan0: authenticated
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: authenticating -> associating
Apr 30 11:38:35 HOSTNAME kernel: [ 2355.127346] wlan0: associate with 00:a0:57:18:d0:31 (try 1)
Apr 30 11:38:35 HOSTNAME kernel: [ 2355.133479] wlan0: RX AssocResp from 00:a0:57:18:d0:31 (capab=0x431 status=0 aid=5)
Apr 30 11:38:35 HOSTNAME kernel: [ 2355.133485] wlan0: associated
Apr 30 11:38:35 HOSTNAME kernel: [ 2355.143046] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'SSID'.
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> dhclient started with pid 4159
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Beginning IP6 addrconf.
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Apr 30 11:38:35 HOSTNAME dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Apr 30 11:38:35 HOSTNAME dhclient: Copyright 2004-2010 Internet Systems Consortium.
Apr 30 11:38:35 HOSTNAME dhclient: All rights reserved.
Apr 30 11:38:35 HOSTNAME dhclient: For info, please visit https://www.isc.org/software/dhcp/
Apr 30 11:38:35 HOSTNAME dhclient: 
Apr 30 11:38:35 HOSTNAME NetworkManager[1189]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Apr 30 11:38:36 HOSTNAME dhclient: Listening on LPF/wlan0/18:3d:a2:53:32:c8
Apr 30 11:38:36 HOSTNAME dhclient: Sending on   LPF/wlan0/18:3d:a2:53:32:c8
Apr 30 11:38:36 HOSTNAME dhclient: Sending on   Socket/fallback
Apr 30 11:38:36 HOSTNAME dhclient: DHCPREQUEST of 172.16.1.182 on wlan0 to 255.255.255.255 port 67
Apr 30 11:38:36 HOSTNAME dhclient: DHCPACK of 172.16.1.182 from 172.16.1.50
Apr 30 11:38:36 HOSTNAME dhclient: bound to 172.16.1.182 -- renewal in 294120 seconds.
Apr 30 11:38:36 HOSTNAME NetworkManager[1189]: <info> (wlan0): DHCPv4 state changed preinit -> reboot
Auszug aus dem betreffenden AGN beim erfolgreichen Connect:

Code: Alles auswählen

Index       Time                  Interface  Event                                                                                       Address          Reason                                                                                                                         
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
3603        04/30/2012 11:38:19   WLAN-1     Determined IPv4 address for station 18:3d:a2:53:32:c8 []:                                   183da25332c8     172.16.1.182                                                                                                                   
3602        04/30/2012 11:38:19   WLAN-1     Connected WLAN station 18:3d:a2:53:32:c8 []                                                 183da25332c8                                                                                                                                    
3601        04/30/2012 11:38:19   WLAN-1     Key handshake with peer 18:3d:a2:53:32:c8 successfully completed                            183da25332c8                                                                                                                                    
3600        04/30/2012 11:38:19   WLAN-1     Completed handover for WLAN station 18:3d:a2:53:32:c8 []                                    183da25332c8     (old BSSID is 00:a0:57:18:cf:54)                                                                                               
3599        04/30/2012 11:38:19   WLAN-1     Associated WLAN station 18:3d:a2:53:32:c8 []                                                183da25332c8                                                                                                                                    
3598        04/30/2012 11:38:19   WLAN-1     Associated WLAN station 18:3d:a2:53:32:c8 []                                                183da25332c8
Nun bin ich an einen anderen Standort gegangen und habe das hier erhalten:

Code: Alles auswählen

Apr 30 11:46:05 HOSTNAME wpa_supplicant[1255]: CTRL-EVENT-DISCONNECTED bssid=00:a0:57:18:d0:31 reason=4
Apr 30 11:46:06 HOSTNAME kernel: [ 2805.167843] cfg80211: All devices are disconnected, going to restore regulatory settings
Apr 30 11:46:06 HOSTNAME kernel: [ 2805.167853] cfg80211: Restoring regulatory settings
Apr 30 11:46:06 HOSTNAME kernel: [ 2805.167860] cfg80211: Calling CRDA to update world regulatory domain
Apr 30 11:46:06 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: completed -> disconnected
Apr 30 11:46:06 HOSTNAME kernel: [ 2805.172621] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain 
Apr 30 11:46:06 HOSTNAME kernel: [ 2805.172627] cfg80211: World regulatory domain updated:
Apr 30 11:46:06 HOSTNAME kernel: [ 2805.172631] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 30 11:46:06 HOSTNAME kernel: [ 2805.172635] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 30 11:46:06 HOSTNAME kernel: [ 2805.172640] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 30 11:46:06 HOSTNAME kernel: [ 2805.172644] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 30 11:46:06 HOSTNAME kernel: [ 2805.172648] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 30 11:46:06 HOSTNAME kernel: [ 2805.172652] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 30 11:46:06 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Apr 30 11:46:08 HOSTNAME wpa_supplicant[1255]: Trying to authenticate with 00:a0:57:18:d0:f9 (SSID='SSID' freq=2462 MHz)
Apr 30 11:46:08 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.852896] wlan0: authenticate with 00:a0:57:18:d0:f9 (try 1)
Apr 30 11:46:08 HOSTNAME wpa_supplicant[1255]: Trying to associate with 00:a0:57:18:d0:f9 (SSID='SSID' freq=2462 MHz)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.856928] wlan0: authenticated
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.858133] wlan0: associate with 00:a0:57:18:d0:f9 (try 1)
Apr 30 11:46:08 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: authenticating -> associating
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.865665] wlan0: RX ReassocResp from 00:a0:57:18:d0:f9 (capab=0x431 status=0 aid=5)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.865668] wlan0: associated
Apr 30 11:46:08 HOSTNAME wpa_supplicant[1255]: Associated with 00:a0:57:18:d0:f9
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.870695] cfg80211: Calling CRDA for country: CH
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873588] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873591] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873593] cfg80211: Updating information on frequency 2417 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873595] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873596] cfg80211: Updating information on frequency 2422 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873598] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873599] cfg80211: Updating information on frequency 2427 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873601] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873602] cfg80211: Updating information on frequency 2432 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873604] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873605] cfg80211: Updating information on frequency 2437 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873607] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873608] cfg80211: Updating information on frequency 2442 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873610] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873611] cfg80211: Updating information on frequency 2447 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873612] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873614] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873615] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873617] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873618] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873620] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873621] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873623] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873624] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873625] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873627] cfg80211: 2402000 KHz - 2482000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873629] cfg80211: Updating information on frequency 5180 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873630] cfg80211: 5170000 KHz - 5250000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873632] cfg80211: Updating information on frequency 5200 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873633] cfg80211: 5170000 KHz - 5250000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873634] cfg80211: Updating information on frequency 5220 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873636] cfg80211: 5170000 KHz - 5250000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873637] cfg80211: Updating information on frequency 5240 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873639] cfg80211: 5170000 KHz - 5250000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873640] cfg80211: Updating information on frequency 5260 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873642] cfg80211: 5250000 KHz - 5330000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873643] cfg80211: Updating information on frequency 5280 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873645] cfg80211: 5250000 KHz - 5330000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873646] cfg80211: Updating information on frequency 5300 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873648] cfg80211: 5250000 KHz - 5330000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873649] cfg80211: Updating information on frequency 5320 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873651] cfg80211: 5250000 KHz - 5330000 KHz @  KHz), (N/A mBi, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873652] cfg80211: Updating information on frequency 5500 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873654] cfg80211: 5490000 KHz - 5710000 KHz @  KHz), (N/A mBi, 2700 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873655] cfg80211: Updating information on frequency 5520 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873657] cfg80211: 5490000 KHz - 5710000 KHz @  KHz), (N/A mBi, 2700 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873658] cfg80211: Updating information on frequency 5540 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873660] cfg80211: 5490000 KHz - 5710000 KHz @  KHz), (N/A mBi, 2700 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873661] cfg80211: Updating information on frequency 5560 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873663] cfg80211: 5490000 KHz - 5710000 KHz @  KHz), (N/A mBi, 2700 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873664] cfg80211: Updating information on frequency 5580 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873666] cfg80211: 5490000 KHz - 5710000 KHz @  KHz), (N/A mBi, 2700 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873667] cfg80211: Updating information on frequency 5600 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873669] cfg80211: 5490000 KHz - 5710000 KHz @  KHz), (N/A mBi, 2700 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873670] cfg80211: Updating information on frequency 5620 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873672] cfg80211: 5490000 KHz - 5710000 KHz @  KHz), (N/A mBi, 2700 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873673] cfg80211: Updating information on frequency 5640 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873674] cfg80211: 5490000 KHz - 5710000 KHz @  KHz), (N/A mBi, 2700 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873676] cfg80211: Updating information on frequency 5660 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873677] cfg80211: 5490000 KHz - 5710000 KHz @  KHz), (N/A mBi, 2700 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873679] cfg80211: Updating information on frequency 5680 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873680] cfg80211: 5490000 KHz - 5710000 KHz @  KHz), (N/A mBi, 2700 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873682] cfg80211: Updating information on frequency 5700 MHz for a 20 MHz width channel with regulatory rule:
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873683] cfg80211: 5490000 KHz - 5710000 KHz @  KHz), (N/A mBi, 2700 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873684] cfg80211: Disabling freq 5745 MHz
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873685] cfg80211: Disabling freq 5765 MHz
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873686] cfg80211: Disabling freq 5785 MHz
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873687] cfg80211: Disabling freq 5805 MHz
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873688] cfg80211: Disabling freq 5825 MHz
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873691] cfg80211: Regulatory domain changed to country: CH
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873692] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873694] cfg80211:     (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873695] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873697] cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Apr 30 11:46:08 HOSTNAME kernel: [ 2807.873698] cfg80211:     (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
Apr 30 11:46:08 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: associating -> associated
Apr 30 11:46:09 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Apr 30 11:46:09 HOSTNAME wpa_supplicant[1255]: WPA: Key negotiation completed with 00:a0:57:18:d0:f9 [PTK=CCMP GTK=TKIP]
Apr 30 11:46:09 HOSTNAME wpa_supplicant[1255]: CTRL-EVENT-CONNECTED - Connection to 00:a0:57:18:d0:f9 completed (reauth) [id=0 id_str=]
Apr 30 11:46:09 HOSTNAME NetworkManager[1189]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Apr 30 11:46:09 HOSTNAME NetworkManager[1189]: <info> (wlan0): roamed from BSSID 00:A0:57:18:D0:31 (SSID) to 00:A0:57:18:D0:F9 (SSID)
Im alten AGN sehe ich dann das hier:

Code: Alles auswählen

Index       Time                  Interface  Event                                                                                       Address          Reason                                                                                                                         
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
3615        04/30/2012 11:45:52   WLAN-1     WLAN station 18:3d:a2:53:32:c8 [] roamed away                                               183da25332c8
Im neuen AGN das hier:

Code: Alles auswählen

Index       Time                  Interface  Event                                                                                       Address          Reason                                                                                                                         
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
5987        04/30/2012 11:46:54   WLAN-1     Determined IPv6 address for station 18:3d:a2:53:32:c8 []:                                   183da25332c8     fe80:0000:0000:0000:1a3d:a2ff:fe53:32c8                                                                                        
5986        04/30/2012 11:45:56   WLAN-1     Determined IPv4 address for station 18:3d:a2:53:32:c8 []:                                   183da25332c8     172.16.1.182                                                                                                                   
5985        04/30/2012 11:45:54   WLAN-1     Connected WLAN station 18:3d:a2:53:32:c8 []                                                 183da25332c8                                                                                                                                    
5984        04/30/2012 11:45:54   WLAN-1     Key handshake with peer 18:3d:a2:53:32:c8 successfully completed                            183da25332c8                                                                                                                                    
5983        04/30/2012 11:45:54   WLAN-1     Completed handover for WLAN station 18:3d:a2:53:32:c8 []                                    183da25332c8     (old BSSID is 00:a0:57:18:d0:31)                                                                                               
5982        04/30/2012 11:45:54   WLAN-1     Reassociated WLAN station 18:3d:a2:53:32:c8 []                                              183da25332c8                                                                                                                                    
5981        04/30/2012 11:45:54   WLAN-1     Authenticated WLAN station 18:3d:a2:53:32:c8 []                                             183da25332c8
Jetzt ging einfach so ca. 3-5 Minuten gar nichts. Nicht mal ein Ping auf eine interne IP, wie z.B. AGN, Router oder GW. Dann, wie aus dem Nichts, funktioniert der volle Zugriff wieder. Es ist in keinem Log irgendwas ersichtlich.

Auf den HP Routern ist IGMP für das Multicasting aktiviert und auf den Access Points sind auch in der IAPP Tabelle immer alle anderen Access Points zu sehen. Die Roaming Meldungen kommen ja auch an, wie man im Access Point Log sehen kann.
Ebenfalls kann ich nicht glauben, dass es ein Client Problem ist, da wir es wirklich mit jedem Client haben, egal ob Notebook oder Handy, Windows oder Linux, usw..

Kann es vielleicht an irgendwelchen ARP Caches liegen oder sonst was?? Ich bin wirklich am Ende meines Lateins und hoffe, mir kann jemand hier weiterhelfen.

Grüsse
Thomas
Zuletzt geändert von tmueller am 03 Mai 2012, 09:49, insgesamt 1-mal geändert.
Nach oben
Benutzeravatar
alf29
Moderator
Moderator
Beiträge: 6207
Registriert: 07 Nov 2004, 19:33
Wohnort: Aachen
Kontaktdaten:
Kontaktdaten von alf29

Beitrag von alf29 »

Moin,

Setzt Du L3-Tunneling ein oder nicht? Wenn nicht, hast Du
Dir mal angeschaut, ob die Switches bei einem Roaming-
Vorgang korrekt die Adressen der Clients auf einen anderen
Port umlernen?

Gruß Alfred
“There is no death, there is just a change of our cosmic address."
-- Edgar Froese, 1944 - 2015
Nach oben
tmueller
Beiträge: 3
Registriert: 30 Apr 2012, 13:06

Beitrag von tmueller »

Hallo Alfred,

vielen Dank für die schnelle Antwort.

Nein, Layer 3 Tunneling haben wir nicht eingerichtet. Die VLANs sind auf den HP Switches konfiguriert.

Wie meinst Du das, ob die Switches die Adressen der Clients auf einen anderen Port umlernen? Da werde ich grad leider nicht schlaus draus.

Gruss
Thomas
Nach oben
Benutzeravatar
alf29
Moderator
Moderator
Beiträge: 6207
Registriert: 07 Nov 2004, 19:33
Wohnort: Aachen
Kontaktdaten:
Kontaktdaten von alf29

Beitrag von alf29 »

Moin,

Dadurch, daß ein Client auf einen anderen AP roamt, ist
seine MAC-Adresse aus Sicht des Switches über einen
anderen Port erreichbar. Wenn man dem Switch das nicht
irgendwie beibringt, leitet er weiter Pakete für diesen
Client an den Port, an dem der "alte AP" hängt - wo
sie natürlich ins Leere laufen. Das geht dann so lannge, bis der Eintrag aus der Forwarding-Database des Switches
herausaltert, was irgendwo im Bereich von ein paar Minuten
dauert - und damit auf Deine Fehlerbeschreibung paßt.

LANCOM-APs schicken üblicherweise direkt nach Anmeldung
eines Clients einen Broadcast mit der Adresse des
Clients als Quell-MAC-Adresse, damit die Switches im
Netz sofort den neuen Pfad lernen. Für mich klingt das
so, als würde das bei Dir irgendwie nicht funktionieren -
dazu müßtest Du aber in die Forwarding-Database Deiner
Switche reinschauen. Wie das geht, weiß ich bei einem
HP-Switch nicht, aber jeder managebare Switch hat
so eine Funktion.

Gruß Alfred
“There is no death, there is just a change of our cosmic address."
-- Edgar Froese, 1944 - 2015
Nach oben
tmueller
Beiträge: 3
Registriert: 30 Apr 2012, 13:06

Beitrag von tmueller »

Hi Alfred,

besten Dank für den Hinweis. Ich habe nun auf unseren Switches, die "mac-age-time"
und die "ip arp-age" Zeiten runter (1 min.) gestellt. Anschliessend habe ich das
Roaming nochmals probiert und nun war maximal ein Unterbruch von 1 Minute da. Also
scheint es tatsächlich an den ARP Caches zu liegen. Allerdings will ich die Werte so
nicht lassen, da dadurch wesentlich mehr Netzwerktraffic verursacht wird.

Um dem Problem weiter auf die Schliche zu kommen, kannst Du mir vielleicht sagen,
wie ich im Lanconfig einen Trace auf Broadcast machen kann, den der AP schicken
sollte? Ich finde das nicht, bzw. ist das überhaupt möglich?

Gruss
Thomas
Nach oben
Antworten

Zurück zu „LANCOM Wireless aktuelle Accesspoints“