staging.inyokaproject.org

Verbindungprobleme mit Intel AC 7265 am Asus ZenBook UX305

Status: Ungelöst | Ubuntu-Version: Xubuntu 15.10 (Wily Werewolf)
Antworten |

nullmeridian

Avatar von nullmeridian

Anmeldungsdatum:
3. Februar 2009

Beiträge: Zähle...

Hallo!

Fast habe mich schon daran gewöhnt, dass am neuen Notebook erstmal das WLAN Probleme macht, bis es dann doch irgendwann geht.

Diesmal ging es zunächst ganz gut. Plötzlich (evtl. nach einem apt-get update) konnte keine Verbindung mehr aufgebaut werden. Auch mit dem externen EDIMAX USB-WLAN Adapter klappte es nur sporadisch und dann mit schlechter Performance.

Nachdem ich jetzt wie hier beschrieben diese Zeile

options iwlwifi 11n_disable=0

in /etc/modprobe.d/iwlwifi.conf eingetragen habe, wurde die Verbindung zwar aufgebaut, aber ich werde ständig wieder nach der Passwortlegitimierung gefragt. Woran kann das liegen?

Komischerweise, als ich eben die Zeile wieder auskommentiert habe, war das Verhalten hinterher noch das Gleiche.

Hier ein Systeminformationen was WLAN-Hardware und -Konfiguration angeht:

nunatak@zenbook:~$ ifconfig -a
lo        Link encap:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:65536  Metrik:1
          RX-Pakete:4159 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:4159 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:0 
          RX-Bytes:280204 (280.2 KB)  TX-Bytes:280204 (280.2 KB)

wlp2s0    Link encap:Ethernet  Hardware Adresse 34:13:e8:37:91:a5  
          UP BROADCAST MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:138 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:209 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000 
          RX-Bytes:24680 (24.6 KB)  TX-Bytes:34095 (34.0 KB)
nunatak@zenbook:~$ lspci -nnk | grep 0280 -A2
02:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59)
     Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:9110]
     Kernel driver in use: iwlwifi
nunatak@zenbook:~$ iwconfig
wlp2s0    IEEE 802.11abgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=22 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          
lo        no wireless extensions.
nunatak@zenbook:~$ rfkill list
1: phy0: Wireless LAN
     Soft blocked: no
     Hard blocked: no
2: asus-wlan: Wireless LAN
     Soft blocked: no
     Hard blocked: no
3: asus-bluetooth: Bluetooth
     Soft blocked: yes
     Hard blocked: no
nunatak@zenbook:~$ cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.1.1
nunatak@zenbook:/$ dmesg | grep iwl
[    1.601664] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-15.ucode failed with error -2
[    1.601682] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-14.ucode failed with error -2
[    1.608685] iwlwifi 0000:02:00.0: loaded firmware version 25.30.13.0 op_mode iwlmvm
[    1.639162] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210
[    1.640538] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[    1.640981] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[    1.741289] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[    1.778071] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
[    3.167514] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[    3.168108] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[    3.228866] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[    3.229464] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[    6.885733] iwlwifi 0000:02:00.0: No association and the time event is over already...
[    8.099342] iwlwifi 0000:02:00.0: No association and the time event is over already...
[    9.135990] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   10.859563] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   12.114818] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   13.103260] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   15.212138] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   17.292391] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   18.015380] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   21.675385] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   35.347746] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   52.529456] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   63.717210] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   65.371841] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   65.835744] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   70.561798] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   71.247224] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   72.281874] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   73.196575] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   76.857343] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   77.893446] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   78.924999] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   81.128964] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   85.214884] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   85.903202] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   87.039947] iwlwifi 0000:02:00.0: No association and the time event is over already...
[   95.034215] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  104.992122] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  112.852455] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  114.608110] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  256.792691] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  264.331317] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  269.724769] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  274.028032] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  274.717281] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  275.747285] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  276.781386] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  310.986914] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  322.207694] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  392.825547] iwlwifi 0000:02:00.0: No association and the time event is over already...
[  451.701144] iwlwifi 0000:02:00.0: No association and the time event is over already...

nullmeridian

(Themenstarter)
Avatar von nullmeridian

Anmeldungsdatum:
3. Februar 2009

Beiträge: 616

Deuten diese beiden Zeilen darauf hin, dass Komponenten der Firmware fehlen?

[    1.601664] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-15.ucode failed with error -2
[    1.601682] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-14.ucode failed with error -2

Dieser Bugreport lässt das vermuten.

Wenn ja, wie lassen sich diese fehlenden Teile der Firmware nachinstallieren? Und wieso hatte ich dann zunächst mehrere Tage kein Problem mit der WLAN-Verbindung?

elektronenblitz63

Avatar von elektronenblitz63

Anmeldungsdatum:
16. Januar 2007

Beiträge: 29307

Hallo,
die Firmware wird wahrscheinlich passen. Je nach verwendeter Modul- und Kernelversion wird eine entsprechende Firmwareversion benötigt. Das Modul lädt auch ältere Versionen, wenn keine aktuelleren gefunden werden.

ls -l /lib/firmware | grep 7265

Siehe auch https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi im Abschnitt Firmware (hier wird ja normalerweise ein 4.2-Kernel verwendet)

uname -a

Hier sollte also die Firmwaredatei iwlwifi-7265-13.ucode vorhanden sein.

Die entscheidenden Abfragen zur Eingrenzung des Fehlers fehlen leider. Zumindest stimmt die Regionseinstellung schon mal nicht (erlaubte Funkkanäle/Sendeleistung usw.), da die Sendeleistung das erlaubte Maß überschreitet.

Siehe iw - Regionseinstellung

Beachte dazu Welche Angaben zum System sind für ein neues Thema nötig?. Die Abfragen ab Punkt 6. und unter 7. die Abfrage des Syslog mit erweitertem Filter nach gescheitertem Verbindungsversuch.

WLAN-Scan etwas übersichtlicher:

sudo iwlist wlan0 scan | egrep -i 'cell|chan|essid|wpa|cipher|qual'

Auch direkt nach einem Versuch die letzten Einträge im Log:

tail -n 250 /var/log/syslog | grep -i net

nullmeridian

(Themenstarter)
Avatar von nullmeridian

Anmeldungsdatum:
3. Februar 2009

Beiträge: 616

Hallo Rainer,

sorry, für die späte Antwort. Hatte ich ganz vergessen. Hatte zunächst ein bisschen Hilfe auf askubuntu.com gefunden, allerdings löst das das Problem nur teilweise. Dabei habe ich die neueste Firmware installiert und die Regionseinstellungen auf DE gesetzt. Ich kann zwar wieder mit dem Netzwerk verbinden, aber immer wieder kommt es vor, dass ich nach Neustart des PCs keine Verbindung mehr bekomme, bzw. diese sofort wieder abbricht und ich immer wieder erneut nach dem Netzwekschlüssel gefragt werde, der aber richtig hinterlegt ist.

Hier nochmal die Ausgabe von 'tail -n 250 /var/log/syslog | grep -i net':

nunatak@zenbook:~$ tail -n 250 /var/log/syslog | grep -i net
Feb  8 17:00:00 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: disconnected -> scanning
Feb  8 17:00:00 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: scanning -> authenticating
Feb  8 17:00:00 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: authenticating -> associating
Feb  8 17:00:00 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: associating -> 4-way handshake
Feb  8 17:00:00 zenbook NetworkManager[688]: <warn>  Connection disconnected (reason -4)
Feb  8 17:00:00 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: 4-way handshake -> disconnected
Feb  8 17:00:00 zenbook NetworkManager[688]: <info>  (wlp2s0): Activation: (wifi) disconnected during association, asking for new key
Feb  8 17:00:00 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: activated -> need-auth (reason 'supplicant-disconnect') [100 60 8]
Feb  8 17:00:00 zenbook NetworkManager[688]: <info>  (wlp2s0): canceled DHCP transaction, DHCP client pid 2703
Feb  8 17:00:00 zenbook NetworkManager[688]: <info>  (wlp2s0): DHCPv4 state changed bound -> done
Feb  8 17:00:00 zenbook NetworkManager[688]: <info>  NetworkManager state is now CONNECTING
Feb  8 17:00:00 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: disconnected -> inactive
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): Activation: (wifi) connection 'FRITZ!Box 6360 Cable' has security, and secrets exist.  No new secrets needed.
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  Config: added 'ssid' value 'FRITZ!Box 6360 Cable'
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  Config: added 'scan_ssid' value '1'
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  Config: added 'psk' value '<omitted>'
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  Config: set interface ap_scan to 1
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: inactive -> scanning
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: scanning -> authenticating
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: authenticating -> associating
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: associating -> associated
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: associated -> 4-way handshake
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: 4-way handshake -> completed
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'FRITZ!Box 6360 Cable'.
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: config -> ip-config (reason 'none') [50 70 0]
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  dhclient started with pid 2847
Feb  8 17:00:30 zenbook NetworkManager[688]: <error> [1454947230.933568] [rdisc/nm-lndp-rdisc.c:68] send_rs(): (wlp2s0): cannot send router solicitation: -99.
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>    address 192.168.178.60
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>    plen 24 (255.255.255.0)
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>    gateway 192.168.178.1
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>    server identifier 192.168.178.1
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>    lease time 864000
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>    nameserver '192.168.178.1'
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>    domain name 'fritz.box'
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): DHCPv4 state changed unknown -> bound
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  NetworkManager state is now CONNECTED_SITE
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Feb  8 17:00:30 zenbook NetworkManager[688]: <info>  (wlp2s0): Activation: successful, device activated.
Feb  8 17:00:31 zenbook whoopsie[708]: [17:00:31] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/5
Feb  8 17:00:31 zenbook whoopsie[708]: [17:00:31] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/5
Feb  8 17:00:31 zenbook whoopsie[708]: [17:00:31] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/5
Feb  8 17:00:31 zenbook whoopsie[708]: [17:00:31] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/5
Feb  8 17:00:31 zenbook whoopsie[708]: [17:00:31] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/5
Feb  8 17:00:31 zenbook whoopsie[708]: [17:00:31] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/5
Feb  8 17:00:31 zenbook whoopsie[708]: [17:00:31] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/5
Feb  8 17:00:31 zenbook whoopsie[708]: [17:00:31] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/5
Feb  8 17:00:31 zenbook whoopsie[708]: [17:00:31] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/5
Feb  8 17:03:22 zenbook NetworkManager[688]: <warn>  Connection disconnected (reason 8)
Feb  8 17:03:22 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: completed -> disconnected
Feb  8 17:03:22 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: disconnected -> scanning
Feb  8 17:03:37 zenbook NetworkManager[688]: <warn>  (wlp2s0): link timed out.
Feb  8 17:03:37 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: activated -> failed (reason 'ssid-not-found') [100 120 53]
Feb  8 17:03:37 zenbook NetworkManager[688]: <info>  NetworkManager state is now CONNECTED_LOCAL
Feb  8 17:03:37 zenbook NetworkManager[688]: <info>  NetworkManager state is now DISCONNECTED
Feb  8 17:03:37 zenbook NetworkManager[688]: <info>  Connection 'FRITZ!Box 6360 Cable' failed to autoconnect; 4 tries left
Feb  8 17:03:37 zenbook NetworkManager[688]: <warn>  (wlp2s0): Activation: failed for connection 'FRITZ!Box 6360 Cable'
Feb  8 17:03:37 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Feb  8 17:03:37 zenbook kernel: [  785.485965] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb  8 17:03:37 zenbook systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb  8 17:03:37 zenbook systemd[1]: Started Network Manager Script Dispatcher Service.
Feb  8 17:03:37 zenbook NetworkManager[688]: <info>  (wlp2s0): canceled DHCP transaction, DHCP client pid 2847
Feb  8 17:03:37 zenbook NetworkManager[688]: <info>  (wlp2s0): DHCPv4 state changed bound -> done
Feb  8 17:03:37 zenbook NetworkManager[688]: <info>  Writing DNS information to /sbin/resolvconf
Feb  8 17:03:37 zenbook NetworkManager[688]: <info>  Device 'wlp2s0' has no connection; scheduling activate_check in 0 seconds.
Feb  8 17:03:37 zenbook NetworkManager[688]: <warn>  Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
Feb  8 17:03:40 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: scanning -> inactive
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: inactive -> scanning
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  Auto-activating connection 'FRITZ!Box 6360 Cable'.
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): Activation: starting connection 'FRITZ!Box 6360 Cable' (df311c4f-c894-4dda-974a-3e1ab1176a49)
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  NetworkManager state is now CONNECTING
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): Activation: (wifi) access point 'FRITZ!Box 6360 Cable' has security, but secrets are required.
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: config -> need-auth (reason 'none') [50 60 0]
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): Activation: (wifi) connection 'FRITZ!Box 6360 Cable' has security, and secrets exist.  No new secrets needed.
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  Config: added 'ssid' value 'FRITZ!Box 6360 Cable'
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  Config: added 'scan_ssid' value '1'
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  Config: added 'psk' value '<omitted>'
Feb  8 17:03:41 zenbook NetworkManager[688]: <warn>  Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
Feb  8 17:03:41 zenbook NetworkManager[688]: <warn>  Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  Config: set interface ap_scan to 1
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: scanning -> authenticating
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: authenticating -> associating
Feb  8 17:03:41 zenbook kernel: [  789.286404] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: associating -> associated
Feb  8 17:03:41 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: associated -> 4-way handshake
Feb  8 17:03:42 zenbook NetworkManager[688]: <warn>  Connection disconnected (reason -4)
Feb  8 17:03:42 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: 4-way handshake -> disconnected
Feb  8 17:03:42 zenbook NetworkManager[688]: <info>  (wlp2s0): Activation: (wifi) disconnected during association, asking for new key
Feb  8 17:03:42 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: config -> need-auth (reason 'supplicant-disconnect') [50 60 8]
Feb  8 17:03:42 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: disconnected -> inactive
Feb  8 17:04:27 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb  8 17:04:27 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
Feb  8 17:04:27 zenbook NetworkManager[688]: <info>  (wlp2s0): Activation: (wifi) connection 'FRITZ!Box 6360 Cable' has security, and secrets exist.  No new secrets needed.
Feb  8 17:04:27 zenbook NetworkManager[688]: <info>  Config: added 'ssid' value 'FRITZ!Box 6360 Cable'
Feb  8 17:04:27 zenbook NetworkManager[688]: <info>  Config: added 'scan_ssid' value '1'
Feb  8 17:04:27 zenbook NetworkManager[688]: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Feb  8 17:04:27 zenbook NetworkManager[688]: <info>  Config: added 'psk' value '<omitted>'
Feb  8 17:04:27 zenbook NetworkManager[688]: <info>  Config: set interface ap_scan to 1
Feb  8 17:04:27 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: inactive -> scanning
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: scanning -> authenticating
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: authenticating -> associating
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: associating -> associated
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: associated -> 4-way handshake
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): supplicant interface state: 4-way handshake -> completed
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'FRITZ!Box 6360 Cable'.
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: config -> ip-config (reason 'none') [50 70 0]
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  dhclient started with pid 3038
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>    address 192.168.178.60
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>    plen 24 (255.255.255.0)
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>    gateway 192.168.178.1
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>    server identifier 192.168.178.1
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>    lease time 864000
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>    nameserver '192.168.178.1'
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>    domain name 'fritz.box'
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): DHCPv4 state changed unknown -> bound
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  NetworkManager state is now CONNECTED_LOCAL
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): roamed from BSSID 08:96:D7:62:4C:3B (FRITZ!Box 6360 Cable) to 08:96:D7:63:34:C5 (FRITZ!Box 6360 Cable)
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  Policy set 'FRITZ!Box 6360 Cable' (wlp2s0) as default for IPv4 routing and DNS.
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  Writing DNS information to /sbin/resolvconf
Feb  8 17:04:28 zenbook NetworkManager[688]: <info>  (wlp2s0): Activation: successful, device activated.
Feb  8 17:04:28 zenbook systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb  8 17:04:28 zenbook whoopsie[708]: [17:04:28] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/6
Feb  8 17:04:28 zenbook whoopsie[708]: [17:04:28] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/6
Feb  8 17:04:28 zenbook whoopsie[708]: [17:04:28] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/6
Feb  8 17:04:28 zenbook systemd[1]: Started Network Manager Script Dispatcher Service.

'wlan0 scan' brachte nur die Meldung 'Interface doesn't support scanning'

In den Fritzbox Settings ist das zenbook mit 300 MBit/s eingetragen. Als Eigenschaften werden WPA2, WMM, STBC genannt. Mein Thinkpad, das mittlerweile keinerlei Probleme mehr bei der Netzwerk-Verbindung macht steht 65 Mbit/s und nur WPA2, WMM. Kann das 'Space Time Block Coding' etwas mit dem Problem zu tun haben? Allerdings werden auch andere Geräte in unserem Netzwerk mit dieser Eigentschaft angezeigt. Ich habe mal bei den Kanälen nachgesehen. Dieser wird standardmäßig automatisch zugeordnet. Anscheinend jedoch immer auf den Kanal der in der Umgebung ohnehin am öftesten genutzt wird. Aber das ist nicht immer der Gleiche. Da es sehr viele Netzwerke in der Umgebung gibt steht der Wert hier immer auf >8. Kann man den Router dazu veranlassen einen weniger genutzten Kanal auszuwählen? Oder muss ich dann einen Kanal fest bestimmen? Und kann das eine mögliche Ursache der Probleme sein? Allerdings haben ja alle anderen Geräte keine Verbindungsprobleme.

elektronenblitz63

Avatar von elektronenblitz63

Anmeldungsdatum:
16. Januar 2007

Beiträge: 29307

Man muss den geeigneten Funkkanal schon selbst auswählen und fest einstellen. Die Ausgabe des Scans fehlt um das besser beurteilen zu können. Im 2,4GHz-Band können nur drei Netze störungsfrei parallel nebeneinander senden, bei 40MHz Bandbreite (N-Modus) sogar nur zwei, da sich die verwendeten Frequenzbereiche überlappen.

Anzahl der Verbindungsversuche & Zeitintervall erhöhen:

echo "options mac80211 max_nullfunc_tries=30 max_probe_tries=30 probe_wait_ms=1500" | sudo tee /etc/modprobe.d/mac80211_options.conf

Treiber antladen/laden oder neu starten.

Sieht nach Störungen durch andere Netze aus, die auf dem selben oder einem benachbarten Funkkanal senden und zwischendurch das eigene Signal überdecken:

Feb  8 17:03:37 zenbook NetworkManager[688]: <info>  (wlp2s0): device state change: activated -> failed (reason 'ssid-not-found') [100 120 53]

Die SSID "FRITZ!Box 6360 Cable" ist auch noch auf Werkseinstellung. MMC kan man in der FB probeweise abschalten.

Siehe WLAN - Abschnitt Konfiguration

nullmeridian

(Themenstarter)
Avatar von nullmeridian

Anmeldungsdatum:
3. Februar 2009

Beiträge: 616

Danke für die Tipps! Werde das mal ausprobieren. Momentan läuft es wieder relativ stabil.

Antworten |