Surfen über WLAN nach einiger Zeit nicht mehr möglich

[thobit]

Moin,
ich sitze hier gerade vor einem frisch aufgesetzten ubuntu 9.10. Jetzt habe ich das Problem, dass ich, nachdem ich enige Minuten im Netz unterwegs wahr nicht mehr weitersurfen kann. Er versucht eine Verbindung aufzubauen, aber es passiert nichts und nach einiger Zeit bekomme ich einen Seitenladefehler, da der Server nicht gefunden werden konnte. Allerdings bin ich noch immer im Netz eingeloggt (zischen 70 % und 80 % Empfangsstärke) und Torrents laufen problemlos weiter. Chatten über empathy ist ebenfalls möglich. Nur surfen will nicht mehr. Wenn ich die Verbindung wieder neu herstellen lasse kann ich wieder so knapp 5 Minuten ohne Probleme surfen. Dann geht's wieder nicht. Fehlermeldungen bekomme ich keine, da die Verbindung ja noch nach wie vor steht. Mit einem ping bekomme ich auch keine Antwort von irgendeiner Seite.

Ich nutze eine Linksys WMP54G-DE PCI-Karte. Antenne steht mit einer Verlängerung auf dem Schreibtisch.

mfg
thobit

 

[Gast1]

Ich nutze eine Linksys WMP54G-DE PCI-Karte.

Solche Angaben sind ein Muster ohne Wert, eindeutig wäre die PCI-ID.

 

[thobit]

lspci gibt folgendes aus:

03:07.0 Network controller: RaLink RT2561/RT61 802.11g PCI

versuche gerade noch die vendor und device id zu finden.

mfg
thobit

 

[Nemesis]

naja, taucht was in den logs auf, nachdem das surfen mal wieder nicht funktioniert ?
was sagt das syslog, messages etc. pp.

 

[thobit]

Fehlerinformationen sind nirgends zu finden. Hier mal die syslog Einträge vor und nach dem Ereignis

Feb 20 15:03:28 rechenknecht wpa_supplicant[1101]: CTRL-EVENT-SCAN-RESULTS 
Feb 20 15:04:28 rechenknecht wpa_supplicant[1101]: CTRL-EVENT-SCAN-RESULTS 
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  (wlan0): device state change: 8 -> 3 (reason 0)
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  (wlan0): deactivating device (reason: 0).
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  (wlan0): canceled DHCP transaction, dhcp client pid 9698
Feb 20 15:05:31 rechenknecht kernel: [19579.948763] wlan0: disassociating by local choice (reason=3)
Feb 20 15:05:31 rechenknecht NetworkManager: <WARN>  check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess#012
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) starting connection 'Auto WLAN-EE6D88'
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  (wlan0): device state change: 3 -> 4 (reason 0)
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0/wireless): access point 'Auto WLAN-EE6D88' has security, but secrets are required.
Feb 20 15:05:31 rechenknecht avahi-daemon[927]: Withdrawing address record for 192.168.178.26 on wlan0.
Feb 20 15:05:31 rechenknecht avahi-daemon[927]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.178.26.
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  (wlan0): device state change: 5 -> 6 (reason 0)
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> disconnected
Feb 20 15:05:31 rechenknecht wpa_supplicant[1101]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Feb 20 15:05:31 rechenknecht avahi-daemon[927]: Interface wlan0.IPv4 no longer relevant for mDNS.
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  (wlan0): device state change: 6 -> 4 (reason 0)
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0/wireless): connection 'Auto WLAN-EE6D88' has security, and secrets exist.  No new secrets needed.
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Config: added 'ssid' value 'WLAN-EE6D88'
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Feb 20 15:05:31 rechenknecht NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Feb 20 15:05:31 rechenknecht NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  Config: set interface ap_scan to 1
Feb 20 15:05:31 rechenknecht wpa_supplicant[1101]: Failed to initiate AP scan.
Feb 20 15:05:31 rechenknecht NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Feb 20 15:05:43 rechenknecht wpa_supplicant[1101]: CTRL-EVENT-SCAN-RESULTS 
Feb 20 15:05:43 rechenknecht wpa_supplicant[1101]: Trying to associate with 06:24:fe:74:54:84 (SSID='WLAN-EE6D88' freq=2437 MHz)
Feb 20 15:05:43 rechenknecht wpa_supplicant[1101]: Association request to the driver failed
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Feb 20 15:05:43 rechenknecht wpa_supplicant[1101]: Associated with 06:24:fe:74:54:84
Feb 20 15:05:43 rechenknecht kernel: [19591.710116] wlan0: authenticate with AP 06:24:fe:74:54:84
Feb 20 15:05:43 rechenknecht kernel: [19591.713270] wlan0: authenticated
Feb 20 15:05:43 rechenknecht kernel: [19591.713275] wlan0: associate with AP 06:24:fe:74:54:84
Feb 20 15:05:43 rechenknecht kernel: [19591.716172] wlan0: RX AssocResp from 06:24:fe:74:54:84 (capab=0x431 status=0 aid=1)
Feb 20 15:05:43 rechenknecht kernel: [19591.716178] wlan0: associated
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Feb 20 15:05:43 rechenknecht wpa_supplicant[1101]: WPA: Key negotiation completed with 06:24:fe:74:54:84 [PTK=CCMP GTK=CCMP]
Feb 20 15:05:43 rechenknecht wpa_supplicant[1101]: CTRL-EVENT-CONNECTED - Connection to 06:24:fe:74:54:84 completed (reauth) [id=0 id_str=]
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> group handshake
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'WLAN-EE6D88'.
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  (wlan0): device state change: 5 -> 7 (reason 0)
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction (timeout in 45 seconds)
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  dhclient started with pid 9883
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) scheduled...
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) started...
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) complete.
Feb 20 15:05:43 rechenknecht dhclient: Internet Systems Consortium DHCP Client V3.1.2
Feb 20 15:05:43 rechenknecht dhclient: Copyright 2004-2008 Internet Systems Consortium.
Feb 20 15:05:43 rechenknecht dhclient: All rights reserved.
Feb 20 15:05:43 rechenknecht dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Feb 20 15:05:43 rechenknecht dhclient: 
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  DHCP: device wlan0 state changed normal exit -> preinit
Feb 20 15:05:43 rechenknecht dhclient: Listening on LPF/wlan0/00:1e:e5:23:30:19
Feb 20 15:05:43 rechenknecht dhclient: Sending on   LPF/wlan0/00:1e:e5:23:30:19
Feb 20 15:05:43 rechenknecht dhclient: Sending on   Socket/fallback
Feb 20 15:05:43 rechenknecht dhclient: DHCPREQUEST of 192.168.178.26 on wlan0 to 255.255.255.255 port 67
Feb 20 15:05:43 rechenknecht dhclient: DHCPACK of 192.168.178.26 from 192.168.178.1
Feb 20 15:05:43 rechenknecht dhclient: bound to 192.168.178.26 -- renewal in 388567 seconds.
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  DHCP: device wlan0 state changed preinit -> reboot
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Feb 20 15:05:43 rechenknecht NetworkManager: <info>    address 192.168.178.26
Feb 20 15:05:43 rechenknecht NetworkManager: <info>    prefix 24 (255.255.255.0)
Feb 20 15:05:43 rechenknecht NetworkManager: <info>    gateway 192.168.178.1
Feb 20 15:05:43 rechenknecht NetworkManager: <info>    nameserver '192.168.178.1'
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Feb 20 15:05:43 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Feb 20 15:05:43 rechenknecht avahi-daemon[927]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.178.26.
Feb 20 15:05:43 rechenknecht avahi-daemon[927]: New relevant interface wlan0.IPv4 for mDNS.
Feb 20 15:05:43 rechenknecht avahi-daemon[927]: Registering new address record for 192.168.178.26 on wlan0.IPv4.
Feb 20 15:05:44 rechenknecht NetworkManager: <info>  (wlan0): device state change: 7 -> 8 (reason 0)
Feb 20 15:05:44 rechenknecht NetworkManager: <info>  Policy set 'Auto WLAN-EE6D88' (wlan0) as default for routing and DNS.
Feb 20 15:05:44 rechenknecht NetworkManager: <info>  Activation (wlan0) successful, device activated.
Feb 20 15:05:44 rechenknecht NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Feb 20 15:05:44 rechenknecht ntpdate[9936]: adjust time server 91.189.94.4 offset 0.002874 sec

In der messages steht gar nichts.

dmesg gibt aus

[19388.058271] wlan0: disassociating by local choice (reason=3)
[19399.871368] wlan0: authenticate with AP 06:24:fe:74:54:84
[19399.876175] wlan0: authenticated
[19399.876185] wlan0: associate with AP 06:24:fe:74:54:84
[19399.878857] wlan0: RX AssocResp from 06:24:fe:74:54:84 (capab=0x431 status=0 aid=1)
[19399.878865] wlan0: associated
[19579.948763] wlan0: disassociating by local choice (reason=3)
[19591.710116] wlan0: authenticate with AP 06:24:fe:74:54:84
[19591.713270] wlan0: authenticated
[19591.713275] wlan0: associate with AP 06:24:fe:74:54:84
[19591.716172] wlan0: RX AssocResp from 06:24:fe:74:54:84 (capab=0x431 status=0 aid=1)
[19591.716178] wlan0: associated

mfg
thobit

P.S.: FTP Verbindungen werden auch unterbrochen

 

[Gast1]

Wenn das Ding kein Laptop ist, der sich in wechselnden Netzwerken bewegen soll, dann ist NWM eh unnützes Beiwerk und ifup zu bevorzugen.

Also auf die klassische Methode umstellen (ifup, Einrichtung über interfaces-Datei) und sehen, ob es damit besser wird.

Neuste Treiber (Stichwort compat-wireless) wären dann der nächste Schritt, falls das nicht hilft.

Und zur PCI-ID hilft "man lspci" weiter.

 

[thobit]

Ich denke ich habe den Fehler gefunden.
Ich habe das TCP Window Scaling deaktiviert und seitdem läuft alles wunderbar.

mfg
thobit