staging.inyokaproject.org

WLAN mit Netis 2123

Status: Gelöst | Ubuntu-Version: Lubuntu 18.04 (Bionic Beaver)
Antworten |

Rosika

(Themenstarter)

Anmeldungsdatum:
26. Februar 2016

Beiträge: 1359

Ergänzung:

lsusb findet ihn nicht mehr:

lsusb | grep -i wlan

gibt nichts aus. Vorher war es:

Bus 001 Device 005: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter

Rosika

(Themenstarter)

Anmeldungsdatum:
26. Februar 2016

Beiträge: 1359

Folgendes:

ich habe den WLAN-Stick von der USB-Buchse abgezogen und neu angesteckt: Sofort wurde er erkannt und die Verbindung hergestellt.

Nur wenn er schon angesteckt ist und das System gestartet wird, wird er nicht erkannt.

kB Team-Icon

Supporter, Wikiteam
Avatar von kB

Anmeldungsdatum:
4. Oktober 2007

Beiträge: 9837

Rosika schrieb:

[…] Ein Unterschied zwischen den zwei Szenarien ist mir aufgefallen:

Wenn der WLAN-Dongle erkannt wird, wird meine Festplatte als /dev/sdb einegbunden. Wenn er nicht erkannt wird, als /dev/sdc.

Dann hat das Ding möglicherweise einen Massenspeicher, der nicht zuverlässig abgeschaltet wird. Was zeigen diese Befehle, wenn der Dongle als WLAN erkannt wird und was, wenn er nicht erkannt wird:

lsusb ; lsblk -lf 

Rosika

(Themenstarter)

Anmeldungsdatum:
26. Februar 2016

Beiträge: 1359

Hi,

Dann hat das Ding möglicherweise einen Massenspeicher

Das wäre mir aber neu...... 🙄

Im Moment wird er erkannt, da ich ihn ja im laufenden Betrieb angesteckt habe:

lsblk -lf 
NAME FSTYPE LABEL       UUID                                 MOUNTPOINT
sda                                                          
sda1 ntfs   WINRE_DRV   B4BE6282BE623CCC                     
sda2 vfat   SYSTEM_DRV  FC63-685C                            
sda3 vfat   LRS_ESP     B064-B41C                            
sda4                                                         
sda5 ntfs   Windows8_OS 588868DA8868B7E0                     
sda6 ntfs               C08495F68495EEE2                     
sda7 ntfs   PBR_DRV     9E2A60582A603007                     
sdb                                                          
sdb1 vfat               28BC-DAFC                            /media/rosika/28BC-DAFC
sdc                                                          
sdc1 ext2               d59df3ee-6785-415b-8c1f-50059dabec2c /
sdc2 ext2               f1b9eb35-0d28-40ba-999d-3ac8a8b9dff5 /home
sdc3 ext2               f14a27c2-0b49-4607-94ea-2e56bbf76fe1 /media/rosika/f14a27c2-0
sde                                                          
sde1 vfat               A492-CD29                            /media/rosika/A492-CD29
sdf  vfat               74C1-30C7                            /media/rosika/74C1-30C7
sr0                                                          
sr1                                         
lsusb
Bus 002 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 002 Device 003: ID 0458:0185 KYE Systems Corp. (Mouse Systems) 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 018: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
Bus 001 Device 016: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 012: ID 045e:0779 Microsoft Corp. LifeCam HD-3000
Bus 001 Device 015: ID 1113:3163 Medion AG 
Bus 001 Device 014: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer
Bus 001 Device 013: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 001 Device 011: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 010: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 009: ID 1058:25a2 Western Digital Technologies, Inc. 
Bus 001 Device 019: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 001 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Ich muß jetzt erst einen Neustart versuchen, damit er evtl. nicht erkannt wird.

Rosika

(Themenstarter)

Anmeldungsdatum:
26. Februar 2016

Beiträge: 1359

So, ich habe jetzt neu gestartet. Und der WLAN-Stick wird nicht erkennt.

Hier die Ausgaben:

lsblk -lf 
NAME FSTYPE LABEL       UUID                                 MOUNTPOINT
sda                                                          
sda1 ntfs   WINRE_DRV   B4BE6282BE623CCC                     
sda2 vfat   SYSTEM_DRV  FC63-685C                            
sda3 vfat   LRS_ESP     B064-B41C                            
sda4                                                         
sda5 ntfs   Windows8_OS 588868DA8868B7E0                     
sda6 ntfs               C08495F68495EEE2                     
sda7 ntfs   PBR_DRV     9E2A60582A603007                     
sdb                                                          
sdb1 vfat               28BC-DAFC                            /media/rosika/28BC-DAFC
sdc                                                          
sdc1 ext2               d59df3ee-6785-415b-8c1f-50059dabec2c /
sdc2 ext2               f1b9eb35-0d28-40ba-999d-3ac8a8b9dff5 /home
sdc3 ext2               f14a27c2-0b49-4607-94ea-2e56bbf76fe1 /media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1
sde                                                          
sde1 vfat               A492-CD29                            /media/rosika/A492-CD29
sdf  vfat               74C1-30C7                            /media/rosika/74C1-30C7
sr0                                                          
sr1 

lsusb
Bus 002 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 002 Device 003: ID 0458:0185 KYE Systems Corp. (Mouse Systems) 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 015: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem
Bus 001 Device 013: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 009: ID 045e:0779 Microsoft Corp. LifeCam HD-3000
Bus 001 Device 008: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 001 Device 012: ID 1113:3163 Medion AG 
Bus 001 Device 011: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer
Bus 001 Device 010: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 001 Device 007: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 1058:25a2 Western Digital Technologies, Inc. 
Bus 001 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Rosika

(Themenstarter)

Anmeldungsdatum:
26. Februar 2016

Beiträge: 1359

Komisch: jetzt wird mein System dennoch als /dev/sdc eingebunden......

Rosika

(Themenstarter)

Anmeldungsdatum:
26. Februar 2016

Beiträge: 1359

Hallo,

hab´ jetzt folgendes ausprobiert:

dmesg -T | grep -i wlan
[Do Mär 14 15:49:15 2019] usb 1-1.2.4.2: Product: 802.11n WLAN Adapter
[Do Mär 14 15:49:43 2019] usb 1-1.2.4.2: Product: 802.11n WLAN Adapter

, da ja lsusb den Stick zumindest anzeigt.

Danach:

echo '1-1.2.4.2' | sudo tee /sys/bus/usb/drivers/usb/bind
[sudo] Passwort für rosika: 
1-1.2.4.2
tee: /sys/bus/usb/drivers/usb/bind: Kein passendes Gerät gefunden

Merkwürdig!

Danach:

echo '1-1.2.4.2' | sudo tee /sys/bus/usb/drivers/usb/unbind
1-1.2.4.2
rosika@rosika-Lenovo-H520e ~> 
echo '1-1.2.4.2' | sudo tee /sys/bus/usb/drivers/usb/bind
1-1.2.4.2

Danach war´s WLAN wieder verfügbar. Keine Ahnung, ob das weiterhilft.

kB Team-Icon

Supporter, Wikiteam
Avatar von kB

Anmeldungsdatum:
4. Oktober 2007

Beiträge: 9837

Ja, ist seltsam. Ich kann jetzt nur vermuten, dass es doch am benötigten Strom liegt und die Hardware den nicht zuverlässig liefern kann.

  • Versuche mal, den WLAN-Stick am USB Bus 002 statt am Bus 001 zu betreiben. Vielleicht wird er da zuverlässiger erkannt.

  • Es könnte auch helfen, das HUAWEI-Modem zu entfernen. Das ist auch ein Stromfresser und die Kombination dieser beiden Geräte ist vielleicht zu viel. Jedenfalls solltest Du den WLAN-Stick und das HUAWEI-Modem nicht am selben BUS betreiben.

Rosika

(Themenstarter)

Anmeldungsdatum:
26. Februar 2016

Beiträge: 1359

Hi kB,

danke für Deine Antwort.

Ich habe schon versucht, einen anderen USB-Anschluß zu verwenden. Hat aber nichts gebracht, weil beide an demselben Hub sind.

Jedenfalls solltest Du den WLAN-Stick und das HUAWEI-Modem nicht am selben BUS betreiben.

Aha, da könnte ich evtl. etwas machen. Einen USB-Anschluß habe ich direkt am PC noch frei. Ich versuche es mal mit dem.

Aber viel Hoffnung habe ich nicht, denn der HUAWEI-stick war beim Booten ausgeschaltet (schaltbarer Hub). Deswegen konnte er eigentlich nicht verantwortlich sein......

Ich melde mich wieder, sobald ich etwas Neues berichten kann.

Schönen Abend noch. Rosika

Lidux

Anmeldungsdatum:
18. April 2007

Beiträge: 16801

Hallo Rosika,

Bitte poste mal:

iwconfig
ifconfig

wegen der Sendeleistung.

Gruss Lidux

Rosika

(Themenstarter)

Anmeldungsdatum:
26. Februar 2016

Beiträge: 1359

Hallo Lidux,

Ich habe jetzt folgendes gemacht:

Den Netis 2123 habe ich nun direkt in eine noch freie USB-Buchse am PC angesteckt, also nicht über einen Hub verbunden. Er ist jetzt sofort erkannt worden, und die Verbindung ins Internet war sofort da. Jetzt muß ich abwarten und beobachten, ob´s so bleibt.

Hier auf jeden Fall die gewünschten Angaben. Sie beziehen sich auf die Situation jetzt (also funktionierender Zustand):

iwconfig
lo        no wireless extensions.

enp2s0    no wireless extensions.

wlxe4beed63ad6d  IEEE 802.11  ESSID:"snet (repeater) "2""  
          Mode:Managed  Frequency:2.462 GHz  Access Point: 80:1F:02:98:37:38   
          Bit Rate=1 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Power Management:off
          Link Quality=50/70  Signal level=-60 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:54   Missed beacon:0
ifconfig
enp2s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c0:3f:d5:06:bf:be  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 330  bytes 28305 (28.3 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 330  bytes 28305 (28.3 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlxe4beed63ad6d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.113  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 fe80::2089:321b:4357:334e  prefixlen 64  scopeid 0x20<link>
        ether e4:be:ed:63:ad:6d  txqueuelen 1000  (Ethernet)
        RX packets 2673  bytes 2452530 (2.4 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1977  bytes 238348 (238.3 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

LG. Rosika

Rosika

(Themenstarter)

Anmeldungsdatum:
26. Februar 2016

Beiträge: 1359

Hallo,

im Moment funktioniert der WLAN-Stick, wie oben beschrieben, dachte ich zumindest. Aber innerhalb kürzester Zeit hat er sich schon zweimal getrennt. Nicht nur die Verbindung war weg, sondern es war gar kein Funknetzwerk mehr verfügbar. Innerhalb von einer Minute meldete er sich wieder an.

Hier zur Info die Logs:

Mar 15 13:54:51 rosika-Lenovo-H520e indicator-appli[1312]: message repeated 1145 times: [ Application already exists, re-requesting properties.]
Mar 15 13:54:51 rosika-Lenovo-H520e wpa_supplicant[631]: wlxe4beed63ad6d: CTRL-EVENT-DISCONNECTED bssid=80:1f:02:98:37:38 reason=4 locally_generated=1
Mar 15 13:54:51 rosika-Lenovo-H520e NetworkManager[632]: <warn>  [1552654491.8650] sup-iface[0x558dc79e7240,wlxe4beed63ad6d]: connection disconnected (reason -4)
Mar 15 13:54:51 rosika-Lenovo-H520e wpa_supplicant[631]: wlxe4beed63ad6d: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar 15 13:54:51 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654491.8956] device (wlxe4beed63ad6d): supplicant interface state: completed -> disconnected
Mar 15 13:54:51 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654491.9703] device (wlxe4beed63ad6d): supplicant interface state: disconnected -> scanning
Mar 15 13:54:51 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.
Mar 15 13:55:07 rosika-Lenovo-H520e indicator-appli[1312]: message repeated 61 times: [ Application already exists, re-requesting properties.]
Mar 15 13:55:07 rosika-Lenovo-H520e NetworkManager[632]: <warn>  [1552654507.4325] device (wlxe4beed63ad6d): link timed out.
Mar 15 13:55:07 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654507.4330] device (wlxe4beed63ad6d): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Mar 15 13:55:07 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654507.4335] manager: NetworkManager state is now DISCONNECTED
Mar 15 13:55:07 rosika-Lenovo-H520e NetworkManager[632]: <warn>  [1552654507.4358] device (wlxe4beed63ad6d): Activation: failed for connection 'snet (repeater) "2"'
Mar 15 13:55:07 rosika-Lenovo-H520e dbus-daemon[611]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=632 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Mar 15 13:55:07 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654507.4380] device (wlxe4beed63ad6d): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Mar 15 13:55:07 rosika-Lenovo-H520e avahi-daemon[640]: Withdrawing address record for fe80::2089:321b:4357:334e on wlxe4beed63ad6d.
Mar 15 13:55:07 rosika-Lenovo-H520e avahi-daemon[640]: Leaving mDNS multicast group on interface wlxe4beed63ad6d.IPv6 with address fe80::2089:321b:4357:334e.
Mar 15 13:55:07 rosika-Lenovo-H520e avahi-daemon[640]: Interface wlxe4beed63ad6d.IPv6 no longer relevant for mDNS.
Mar 15 13:55:07 rosika-Lenovo-H520e systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 15 13:55:07 rosika-Lenovo-H520e kernel: [ 3148.010554] IPv6: ADDRCONF(NETDEV_UP): wlxe4beed63ad6d: link is not ready
Mar 15 13:55:07 rosika-Lenovo-H520e dbus-daemon[611]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mar 15 13:55:07 rosika-Lenovo-H520e systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 15 13:55:07 rosika-Lenovo-H520e nm-dispatcher: req:1 'down' [wlxe4beed63ad6d]: new request (1 scripts)
Mar 15 13:55:07 rosika-Lenovo-H520e nm-dispatcher: req:1 'down' [wlxe4beed63ad6d]: start running ordered scripts...
Mar 15 13:55:07 rosika-Lenovo-H520e nm-dispatcher: req:2 'connectivity-change': new request (1 scripts)
Mar 15 13:55:07 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654507.4748] dhcp4 (wlxe4beed63ad6d): canceled DHCP transaction, DHCP client pid 740
Mar 15 13:55:07 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654507.4749] dhcp4 (wlxe4beed63ad6d): state changed bound -> done
Mar 15 13:55:07 rosika-Lenovo-H520e avahi-daemon[640]: Withdrawing address record for 192.168.2.113 on wlxe4beed63ad6d.
Mar 15 13:55:07 rosika-Lenovo-H520e avahi-daemon[640]: Leaving mDNS multicast group on interface wlxe4beed63ad6d.IPv4 with address 192.168.2.113.
Mar 15 13:55:07 rosika-Lenovo-H520e avahi-daemon[640]: Interface wlxe4beed63ad6d.IPv4 no longer relevant for mDNS.
Mar 15 13:55:07 rosika-Lenovo-H520e nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...
Mar 15 13:55:07 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.
Mar 15 13:55:12 rosika-Lenovo-H520e indicator-appli[1312]: message repeated 19 times: [ Application already exists, re-requesting properties.]
Mar 15 13:55:12 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654512.4417] device (wlxe4beed63ad6d): supplicant interface state: scanning -> inactive
Mar 15 13:55:12 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.
Mar 15 13:55:46 rosika-Lenovo-H520e indicator-appli[1312]: message repeated 137 times: [ Application already exists, re-requesting properties.]
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6174] policy: auto-activating connection 'snet (repeater) "2"'
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6185] device (wlxe4beed63ad6d): Activation: starting connection 'snet (repeater) "2"' (3e8723d9-8bd6-4130-82ed-7a434847bf71)
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6188] device (wlxe4beed63ad6d): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6190] manager: NetworkManager state is now CONNECTING
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6195] device (wlxe4beed63ad6d): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6197] device (wlxe4beed63ad6d): Activation: (wifi) access point 'snet (repeater) "2"' has security, but secrets are required.
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6197] device (wlxe4beed63ad6d): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6199] sup-iface[0x558dc79e7240,wlxe4beed63ad6d]: wps: type pbc start...
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6242] device (wlxe4beed63ad6d): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6248] device (wlxe4beed63ad6d): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6251] device (wlxe4beed63ad6d): Activation: (wifi) connection 'snet (repeater) "2"' has security, and secrets exist.  No new secrets needed.
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6251] Config: added 'ssid' value 'snet (repeater) "2"'
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6252] Config: added 'scan_ssid' value '1'
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6252] Config: added 'bgscan' value 'simple:30:-80:86400'
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6252] Config: added 'key_mgmt' value 'WPA-PSK'
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6252] Config: added 'psk' value '<hidden>'
Mar 15 13:55:46 rosika-Lenovo-H520e wpa_supplicant[631]: wlxe4beed63ad6d: SME: Trying to authenticate with 80:1f:02:98:37:38 (SSID='snet (repeater) \"2\"' freq=2462 MHz)
Mar 15 13:55:46 rosika-Lenovo-H520e kernel: [ 3187.204508] wlxe4beed63ad6d: authenticate with 80:1f:02:98:37:38
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6448] device (wlxe4beed63ad6d): supplicant interface state: inactive -> authenticating
Mar 15 13:55:46 rosika-Lenovo-H520e kernel: [ 3187.214740] wlxe4beed63ad6d: send auth to 80:1f:02:98:37:38 (try 1/3)
Mar 15 13:55:46 rosika-Lenovo-H520e wpa_supplicant[631]: wlxe4beed63ad6d: Trying to associate with 80:1f:02:98:37:38 (SSID='snet (repeater) \"2\"' freq=2462 MHz)
Mar 15 13:55:46 rosika-Lenovo-H520e kernel: [ 3187.216218] wlxe4beed63ad6d: authenticated
Mar 15 13:55:46 rosika-Lenovo-H520e kernel: [ 3187.216431] rtl8xxxu 2-1.1:1.0 wlxe4beed63ad6d: disabling HT/VHT due to WEP/TKIP use
Mar 15 13:55:46 rosika-Lenovo-H520e kernel: [ 3187.216433] rtl8xxxu 2-1.1:1.0 wlxe4beed63ad6d: disabling HT as WMM/QoS is not supported by the AP
Mar 15 13:55:46 rosika-Lenovo-H520e kernel: [ 3187.216435] rtl8xxxu 2-1.1:1.0 wlxe4beed63ad6d: disabling VHT as WMM/QoS is not supported by the AP
Mar 15 13:55:46 rosika-Lenovo-H520e kernel: [ 3187.220037] wlxe4beed63ad6d: associate with 80:1f:02:98:37:38 (try 1/3)
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6517] device (wlxe4beed63ad6d): supplicant interface state: authenticating -> associating
Mar 15 13:55:46 rosika-Lenovo-H520e kernel: [ 3187.223869] wlxe4beed63ad6d: RX AssocResp from 80:1f:02:98:37:38 (capab=0x411 status=0 aid=2)
Mar 15 13:55:46 rosika-Lenovo-H520e kernel: [ 3187.227464] wlxe4beed63ad6d: associated
Mar 15 13:55:46 rosika-Lenovo-H520e wpa_supplicant[631]: wlxe4beed63ad6d: Associated with 80:1f:02:98:37:38
Mar 15 13:55:46 rosika-Lenovo-H520e wpa_supplicant[631]: wlxe4beed63ad6d: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6628] device (wlxe4beed63ad6d): supplicant interface state: associating -> group handshake
Mar 15 13:55:46 rosika-Lenovo-H520e wpa_supplicant[631]: wlxe4beed63ad6d: WPA: Key negotiation completed with 80:1f:02:98:37:38 [PTK=TKIP GTK=TKIP]
Mar 15 13:55:46 rosika-Lenovo-H520e kernel: [ 3187.235915] IPv6: ADDRCONF(NETDEV_CHANGE): wlxe4beed63ad6d: link becomes ready
Mar 15 13:55:46 rosika-Lenovo-H520e wpa_supplicant[631]: wlxe4beed63ad6d: CTRL-EVENT-CONNECTED - Connection to 80:1f:02:98:37:38 completed [id=0 id_str=]
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6713] device (wlxe4beed63ad6d): supplicant interface state: group handshake -> completed
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6714] device (wlxe4beed63ad6d): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'snet (repeater) "2"'.
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6716] device (wlxe4beed63ad6d): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6720] dhcp4 (wlxe4beed63ad6d): activation: beginning transaction (timeout in 45 seconds)
Mar 15 13:55:46 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654546.6741] dhcp4 (wlxe4beed63ad6d): dhclient started with pid 4263
Mar 15 13:55:46 rosika-Lenovo-H520e dhclient[4263]: DHCPREQUEST of 192.168.2.113 on wlxe4beed63ad6d to 255.255.255.255 port 67 (xid=0x2e90e807)
Mar 15 13:55:47 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.
Mar 15 13:55:47 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.
Mar 15 13:55:47 rosika-Lenovo-H520e wpa_supplicant[631]: wlxe4beed63ad6d: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=1000
Mar 15 13:55:47 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.
Mar 15 13:55:48 rosika-Lenovo-H520e indicator-appli[1312]: message repeated 3 times: [ Application already exists, re-requesting properties.]
Mar 15 13:55:48 rosika-Lenovo-H520e avahi-daemon[640]: Joining mDNS multicast group on interface wlxe4beed63ad6d.IPv6 with address fe80::2089:321b:4357:334e.
Mar 15 13:55:48 rosika-Lenovo-H520e avahi-daemon[640]: New relevant interface wlxe4beed63ad6d.IPv6 for mDNS.
Mar 15 13:55:48 rosika-Lenovo-H520e avahi-daemon[640]: Registering new address record for fe80::2089:321b:4357:334e on wlxe4beed63ad6d.*.
Mar 15 13:55:48 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.
Mar 15 13:55:49 rosika-Lenovo-H520e indicator-appli[1312]: message repeated 5 times: [ Application already exists, re-requesting properties.]
Mar 15 13:55:49 rosika-Lenovo-H520e dhclient[4263]: DHCPREQUEST of 192.168.2.113 on wlxe4beed63ad6d to 255.255.255.255 port 67 (xid=0x2e90e807)
Mar 15 13:55:49 rosika-Lenovo-H520e dhclient[4263]: DHCPACK of 192.168.2.113 from 192.168.2.1
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6812] dhcp4 (wlxe4beed63ad6d):   address 192.168.2.113
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6812] dhcp4 (wlxe4beed63ad6d):   plen 24 (255.255.255.0)
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6812] dhcp4 (wlxe4beed63ad6d):   gateway 192.168.2.1
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6813] dhcp4 (wlxe4beed63ad6d):   lease time 1814400
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6813] dhcp4 (wlxe4beed63ad6d):   nameserver '192.168.2.1'
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6813] dhcp4 (wlxe4beed63ad6d):   domain name 'Speedport_W_921V_1_45_000'
Mar 15 13:55:49 rosika-Lenovo-H520e avahi-daemon[640]: Joining mDNS multicast group on interface wlxe4beed63ad6d.IPv4 with address 192.168.2.113.
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6813] dhcp4 (wlxe4beed63ad6d): state changed unknown -> bound
Mar 15 13:55:49 rosika-Lenovo-H520e avahi-daemon[640]: New relevant interface wlxe4beed63ad6d.IPv4 for mDNS.
Mar 15 13:55:49 rosika-Lenovo-H520e avahi-daemon[640]: Registering new address record for 192.168.2.113 on wlxe4beed63ad6d.IPv4.
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6850] device (wlxe4beed63ad6d): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 15 13:55:49 rosika-Lenovo-H520e dhclient[4263]: bound to 192.168.2.113 -- renewal in 863110 seconds.
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6864] device (wlxe4beed63ad6d): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6868] device (wlxe4beed63ad6d): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6871] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6896] manager: NetworkManager state is now CONNECTED_SITE
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6898] policy: set 'snet (repeater) "2"' (wlxe4beed63ad6d) as default for IPv4 routing and DNS
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6901] device (wlxe4beed63ad6d): Activation: successful, device activated.
Mar 15 13:55:49 rosika-Lenovo-H520e dbus-daemon[611]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=632 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Mar 15 13:55:49 rosika-Lenovo-H520e NetworkManager[632]: <info>  [1552654549.6911] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 15 13:55:49 rosika-Lenovo-H520e systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 15 13:55:49 rosika-Lenovo-H520e dbus-daemon[611]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mar 15 13:55:49 rosika-Lenovo-H520e systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 15 13:55:49 rosika-Lenovo-H520e nm-dispatcher: req:1 'up' [wlxe4beed63ad6d]: new request (1 scripts)
Mar 15 13:55:49 rosika-Lenovo-H520e nm-dispatcher: req:1 'up' [wlxe4beed63ad6d]: start running ordered scripts...
Mar 15 13:55:49 rosika-Lenovo-H520e nm-dispatcher: req:2 'connectivity-change': new request (1 scripts)
Mar 15 13:55:49 rosika-Lenovo-H520e nm-dispatcher[4275]: postconf: fatal: open /etc/postfix/main.cf: No such file or directory
Mar 15 13:55:50 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.
Mar 15 13:55:50 rosika-Lenovo-H520e indicator-appli[1312]: message repeated 3 times: [ Application already exists, re-requesting properties.]
Mar 15 13:55:50 rosika-Lenovo-H520e nm-dispatcher[4275]: postconf: fatal: open /etc/postfix/main.cf: No such file or directory
Mar 15 13:55:51 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.
Mar 15 13:55:51 rosika-Lenovo-H520e indicator-appli[1312]: message repeated 3 times: [ Application already exists, re-requesting properties.]
Mar 15 13:55:51 rosika-Lenovo-H520e nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...
Mar 15 13:55:52 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.
Mar 15 13:55:52 rosika-Lenovo-H520e indicator-appli[1312]: message repeated 3 times: [ Application already exists, re-requesting properties.]
Mar 15 13:55:52 rosika-Lenovo-H520e systemd-resolved[544]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Mar 15 13:55:52 rosika-Lenovo-H520e systemd-resolved[544]: message repeated 2 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.]
Mar 15 13:55:53 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.
Mar 15 13:55:55 rosika-Lenovo-H520e indicator-appli[1312]: message repeated 9 times: [ Application already exists, re-requesting properties.]
Mar 15 13:55:55 rosika-Lenovo-H520e systemd-resolved[544]: Using degraded feature set (UDP) for DNS server 192.168.2.1.
Mar 15 13:55:55 rosika-Lenovo-H520e indicator-appli[1312]: Application already exists, re-requesting properties.

Was kann denn jetzt wieder los sein?

Lidux

Anmeldungsdatum:
18. April 2007

Beiträge: 16801

Hallo Rosika,

Trage mal im Netzwerkmanager unter BSSID die MAC Adresse des Repeater ein.

Mache mal einen Scan der Netzwerkumgebung:

sudo iwlist scan
sudo iwlist chan

und kennzeichne das Netz der Verbindung.

Das erste ist auch nicht gut:

Bit Rate=1 Mb/s   Tx-Power=20 dBm

Ausgabe von lsmod ...

Gruss Lidux

Rosika

(Themenstarter)

Anmeldungsdatum:
26. Februar 2016

Beiträge: 1359

Hallo Lidux,

vielen Dank.

Trage mal im Netzwerkmanager unter BSSID die MAC Adresse des Repeater ein.

Hab´ ich jetzt gemacht.

sudo iwlist scan

lo        Interface doesn't support scanning.

enp2s0    Interface doesn't support scanning.

wlxe4beed63ad6d  Scan completed :
          Cell 01 - Address: 80:1F:02:98:37:38
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=52/70  Signal level=-58 dBm  
                    Encryption key:on
                    ESSID:"snet (repeater) "2""
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=00000000dc6be588
                    Extra: Last beacon: 84ms ago
                    IE: Unknown: 0013736E6574202872657065617465722920223222
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 03010B
                    IE: Unknown: 2A0100
                    IE: Unknown: 32043048606C
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD800050F204104A0001101044000102103B0001031047001063041253101920061228801F02983738102100064D6564696F6E102300064D6564696F6E1024000D45562D323030392D30322D30361042000F3132333435363738393031323334371054000800060050F20400011011000B576972656C657373204150100800020086
                    IE: Unknown: DD0600E04C0201E0

sudo iwlist chan

lo        no frequency information.

enp2s0    no frequency information.

wlxe4beed63ad6d  14 channels in total; available frequencies :
          Channel 01 : 2.412 GHz
          Channel 02 : 2.417 GHz
          Channel 03 : 2.422 GHz
          Channel 04 : 2.427 GHz
          Channel 05 : 2.432 GHz
          Channel 06 : 2.437 GHz
          Channel 07 : 2.442 GHz
          Channel 08 : 2.447 GHz
          Channel 09 : 2.452 GHz
          Channel 10 : 2.457 GHz
          Channel 11 : 2.462 GHz
          Channel 12 : 2.467 GHz
          Channel 13 : 2.472 GHz
          Channel 14 : 2.484 GHz
          Current Frequency=2.462 GHz (Channel 11)

Darüberhinaus habe ich auf der Seite https://debianforum.de/forum/viewtopic.php?t=152554 als Info gefunden, daß es evtl. Probleme mit 2,4 GHz und 5 GHz geben kann. Auf jeden Fall habe ich nun im Netzwerkmanager als Band B/G 2,4 GHz eingestellt. Kann ja nicht schaden, denke ich.

LG. Rosika

Rosika

(Themenstarter)

Anmeldungsdatum:
26. Februar 2016

Beiträge: 1359

Ach, ich vergaß:

lsmod

Module                  Size  Used by
nls_iso8859_1          16384  3
arc4                   16384  2
rtl8xxxu              122880  0
mac80211              778240  1 rtl8xxxu
snd_hda_codec_realtek   106496  1
snd_hda_codec_generic    73728  1 snd_hda_codec_realtek
rtsx_usb_ms            20480  0
memstick               16384  1 rtsx_usb_ms
cfg80211              622592  1 mac80211
uvcvideo               86016  0
videobuf2_vmalloc      16384  1 uvcvideo
videobuf2_memops       16384  1 videobuf2_vmalloc
videobuf2_v4l2         24576  1 uvcvideo
videobuf2_core         40960  2 videobuf2_v4l2,uvcvideo
videodev              184320  3 videobuf2_core,videobuf2_v4l2,uvcvideo
joydev                 24576  0
snd_usb_audio         204800  2
input_leds             16384  0
snd_usbmidi_lib        32768  1 snd_usb_audio
snd_rawmidi            32768  1 snd_usbmidi_lib
media                  40960  2 videodev,uvcvideo
snd_seq_device         16384  1 snd_rawmidi
i915                 1617920  8
intel_rapl             20480  0
x86_pkg_temp_thermal    16384  0
intel_powerclamp       16384  0
coretemp               16384  0
kvm_intel             212992  0
kvm                   598016  1 kvm_intel
snd_hda_intel          40960  6
snd_hda_codec         126976  3 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec_realtek
drm_kms_helper        172032  1 i915
drm                   401408  6 drm_kms_helper,i915
irqbypass              16384  1 kvm
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
ghash_clmulni_intel    16384  0
cryptd                 24576  1 ghash_clmulni_intel
intel_cstate           20480  0
intel_rapl_perf        16384  0
snd_hda_core           81920  4 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_hwdep              20480  2 snd_usb_audio,snd_hda_codec
snd_pcm                98304  4 snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core
snd_timer              32768  1 snd_pcm
snd                    81920  27 snd_hda_codec_generic,snd_seq_device,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi
mei_me                 40960  0
mei                    90112  1 mei_me
shpchp                 36864  0
soundcore              16384  1 snd
lpc_ich                24576  0
video                  45056  1 i915
mac_hid                16384  0
ie31200_edac           16384  0
i2c_algo_bit           16384  1 i915
fb_sys_fops            16384  1 drm_kms_helper
syscopyarea            16384  1 drm_kms_helper
sysfillrect            16384  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
sch_fq_codel           20480  6
parport_pc             36864  0
ppdev                  20480  0
lp                     20480  0
parport                49152  3 parport_pc,lp,ppdev
ip_tables              28672  0
x_tables               40960  1 ip_tables
autofs4                40960  2
hid_generic            16384  0
usbhid                 49152  0
uas                    24576  0
hid                   118784  2 usbhid,hid_generic
usb_storage            69632  7 uas
rtsx_usb_sdmmc         28672  0
ahci                   40960  0
rtsx_usb               20480  2 rtsx_usb_sdmmc,rtsx_usb_ms
r8169                  86016  0
libahci                32768  1 ahci
mii                    16384  1 r8169