Anzeige:
Ergebnis 1 bis 15 von 15

Thema: Wlan funktioniert nur ca. eine Minute

  1. #1
    eigentlich keine Blondine
    Registriert seit
    Mar 2010
    Beiträge
    931

    Wlan funktioniert nur ca. eine Minute

    Hallo!
    Das Problem habe ich zwar im Internet auch gefunden, aber keine für mich verständliche und praktikable Lösung. Ich habe SuSe11.3 und benutze den KNetworkmanager. Ich würde auch freiwillich die "traditionelle Methode mit ifup" benutzen, die in Yast bei den Netzwerkeinstellungen als Alternative angeboten wird - wenn ich wüsste, wie man damit überhaupt eine Internetverbindung herstellt.
    Normalerweise gehe ich über LAN-Kabel ins Internet, aber zur Zeit (und öfter mal) ist die Verbindung nicht verfügbar, deshalb möchte ich das Wlan nutzen. Wenn ich mich dort jedoch einwähle, kann ich gerade mal einmal meine Mail kontrollieren und zwei Seiten im Browser öffnen, und dann ist die verbindung wieder weg. Zuerst dachte ich, das Disconnect geschähe nach genau einer Minute. Aber manchmal auch schon nach 20 Sekunden.
    Wo gibt es ein Logfile oder so, dem man vielleicht entnehmen könnte, was hier passiert?

  2. #2
    Fieses Frettchen Avatar von DrunkenFreak
    Registriert seit
    Dec 2003
    Beiträge
    3.221
    Sortiere /var/log nach Datum und gucke, was in den unteren Logs drin steht. /var/log/messages und /var/log/syslog könnten hier was interessantes zeigen.

    Probier mal eine IP aus dem Netz zu pingen (z.B. 213.30.246.247 [linuxforen.de]), wenn die Verbindung weg ist. Eventuell ist dann nur der Nameserver nicht erreichbar.

  3. #3
    Registrierter Benutzer
    Registriert seit
    Sep 2003
    Beiträge
    2.990
    Zitat Zitat von rstuby Beitrag anzeigen
    Wo gibt es ein Logfile oder so, dem man vielleicht entnehmen könnte, was hier passiert?
    war bei mir auch...

    nachdem ich das modul getauscht habe, einen neuene wlanstick gekauft habe, hat sich herrausgestellt, das der wlan router defekt ist


    gruss Eddi

  4. #4
    eigentlich keine Blondine
    Registriert seit
    Mar 2010
    Beiträge
    931
    Beim ping-Versuch kommt:
    connect: Network is unreachable
    Da gibt es eine lange wpa_supplicant.log, deren unterste Zeilen sehen so aus:
    Code:
    Associated with 1c:af:f7:72:71:3b
    Associated with 1c:af:f7:72:71:3b
    Associated with 1c:af:f7:72:71:3b
    Associated with 1c:af:f7:72:71:3b
    Associated with 1c:af:f7:72:71:3b
    Associated with 1c:af:f7:72:71:3b
    Associated with 1c:af:f7:72:71:3b
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    Authentication with 00:00:00:00:00:00 timed out.
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    Associated with 1c:af:f7:72:71:33
    Trying to associate with 1c:af:f7:72:71:3b (SSID='students' freq=2437 MHz)
    Association request to the driver failed
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    Associated with 1c:af:f7:72:71:3b
    WPA: Key negotiation completed with 1c:af:f7:72:71:3b [PTK=CCMP GTK=TKIP]
    CTRL-EVENT-CONNECTED - Connection to 1c:af:f7:72:71:3b completed (reauth) [id=0 id_str=]
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    No network configuration found for the current AP
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    Trying to associate with 1c:af:f7:72:71:3b (SSID='students' freq=2437 MHz)
    Association request to the driver failed
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    Associated with 1c:af:f7:72:71:3b
    WPA: Key negotiation completed with 1c:af:f7:72:71:3b [PTK=CCMP GTK=TKIP]
    CTRL-EVENT-CONNECTED - Connection to 1c:af:f7:72:71:3b completed (auth) [id=0 id_str=]
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    Trying to associate with 1c:af:f7:72:71:3b (SSID='students' freq=2437 MHz)
    Association request to the driver failed
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    Associated with 1c:af:f7:72:71:3b
    WPA: Key negotiation completed with 1c:af:f7:72:71:3b [PTK=CCMP GTK=TKIP]
    CTRL-EVENT-CONNECTED - Connection to 1c:af:f7:72:71:3b completed (auth) [id=0 id_str=]
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    Trying to associate with 1c:af:f7:72:71:3b (SSID='students' freq=2437 MHz)
    Association request to the driver failed
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    Associated with 1c:af:f7:72:71:3b
    WPA: Key negotiation completed with 1c:af:f7:72:71:3b [PTK=CCMP GTK=TKIP]
    CTRL-EVENT-CONNECTED - Connection to 1c:af:f7:72:71:3b completed (auth) [id=0 id_str=]
    WPA: Group rekeying completed with 1c:af:f7:72:71:3b [GTK=TKIP]
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
    (students ist der Name des Netzwerks)
    messages endet folgendermaßen:
    Code:
    Feb 26 18:55:48 linux-ddqv kernel: [ 5648.249143] 
    
    Feb 26 18:56:11 linux-ddqv kernel: [ 5671.611122] TKIP: replay detected: STA=1c:af:f7:72:71:3b previous TSC 0002000214d3 received TSC 0000000215c5
    Feb 26 18:56:12 linux-ddqv kernel: [ 5672.360570] TKIP: replay detected: STA=1c:af:f7:72:71:3b previous TSC 0002000214d3 received TSC 0000000215c6
    Feb 26 18:56:12 linux-ddqv avahi-daemon[1899]: Withdrawing address record for 192.168.0.117 on wlan0.
    Feb 26 18:56:12 linux-ddqv avahi-daemon[1899]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.117.
    Feb 26 18:56:12 linux-ddqv avahi-daemon[1899]: Interface wlan0.IPv4 no longer relevant for mDNS.
    Feb 26 18:56:12 linux-ddqv kernel: [ 5672.473347] Linking with students: channel is 6
    Feb 26 18:56:19 linux-ddqv nmbd[11705]: [2011/02/26 18:56:19.606545,  0] nmbd/nmbd.c:332(reload_interfaces)
    Feb 26 18:56:19 linux-ddqv nmbd[11705]:   reload_interfaces: No subnets to listen to. Waiting..
    Feb 26 18:56:42 linux-ddqv smbd[2021]: [2011/02/26 18:56:42.785783,  0] smbd/server.c:281(remove_child_pid)
    Feb 26 18:56:42 linux-ddqv smbd[2021]:   Could not find child 12076 -- ignoring
    Feb 26 18:56:44 linux-ddqv kernel: [ 5704.875495] Linking with students: channel is 6
    Feb 26 18:56:44 linux-ddqv kernel: [ 5704.917453] Linking with students: channel is 6
    Feb 26 18:56:44 linux-ddqv kernel: [ 5704.940966] Associated successfully
    Feb 26 18:56:44 linux-ddqv kernel: [ 5704.940973] Using G rates
    Feb 26 18:56:45 linux-ddqv dhclient: Internet Systems Consortium DHCP Client 4.1-ESV-R1
    Feb 26 18:56:45 linux-ddqv dhclient: Copyright 2004-2011 Internet Systems Consortium.
    Feb 26 18:56:45 linux-ddqv dhclient: All rights reserved.
    Feb 26 18:56:45 linux-ddqv dhclient: For info, please visit https://www.isc.org/software/dhcp/
    Feb 26 18:56:45 linux-ddqv dhclient: 
    Feb 26 18:56:45 linux-ddqv dhclient: Listening on LPF/wlan0/00:24:21:4e:e4:11
    Feb 26 18:56:45 linux-ddqv dhclient: Sending on   LPF/wlan0/00:24:21:4e:e4:11
    Feb 26 18:56:45 linux-ddqv dhclient: Sending on   Socket/fallback
    Feb 26 18:56:45 linux-ddqv kernel: [ 5706.012436] TKIP: replay detected: STA=1c:af:f7:72:71:3b previous TSC 0002000215f7 received TSC 0000000215f8
    Feb 26 18:56:46 linux-ddqv dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Feb 26 18:56:46 linux-ddqv kernel: [ 5706.185837] CCMP: replay detected: STA=1c:af:f7:72:71:3b previous PN 000000000000 received PN 000000000000
    Feb 26 18:56:46 linux-ddqv kernel: [ 5706.977943] TKIP: replay detected: STA=1c:af:f7:72:71:3b previous TSC 0002000215f7 received TSC 0000000215fa
    Feb 26 18:56:47 linux-ddqv kernel: [ 5707.977685] TKIP: replay detected: STA=1c:af:f7:72:71:3b previous TSC 0002000215f7 received TSC 0000000215fc
    Feb 26 18:56:51 linux-ddqv dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
    Feb 26 18:56:51 linux-ddqv dhclient: DHCPACK from 192.168.0.1
    Feb 26 18:56:51 linux-ddqv avahi-daemon[1899]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.117.
    Feb 26 18:56:51 linux-ddqv avahi-daemon[1899]: New relevant interface wlan0.IPv4 for mDNS.
    Feb 26 18:56:51 linux-ddqv avahi-daemon[1899]: Registering new address record for 192.168.0.117 on wlan0.IPv4.
    Feb 26 18:56:51 linux-ddqv dhclient: bound to 192.168.0.117 -- renewal in 298603 seconds.
    Feb 26 18:56:52 linux-ddqv smbd[2021]: [2011/02/26 18:56:52.546703,  0] smbd/server.c:281(remove_child_pid)
    Feb 26 18:56:52 linux-ddqv smbd[2021]:   Could not find child 12229 -- ignoring
    Feb 26 18:56:52 linux-ddqv SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
    Feb 26 18:56:52 linux-ddqv SuSEfirewall2: batch committing...
    Feb 26 18:56:52 linux-ddqv SuSEfirewall2: Firewall rules successfully set
    Feb 26 18:57:07 linux-ddqv kernel: [ 5727.923436] TKIP: replay detected: STA=1c:af:f7:72:71:3b previous TSC 0002000215f7 received TSC 000000021631
    Feb 26 18:57:08 linux-ddqv kernel: [ 5728.674029] TKIP: replay detected: STA=1c:af:f7:72:71:3b previous TSC 0002000215f7 received TSC 000000021632
    Feb 26 18:57:09 linux-ddqv kernel: [ 5729.423019] TKIP: replay detected: STA=1c:af:f7:72:71:3b previous TSC 0002000215f7 received TSC 000000021633
    Feb 26 18:57:10 linux-ddqv kernel: [ 5730.476163] TKIP: replay detected: STA=1c:af:f7:72:71:3b previous TSC 0002000215f7 received TSC 000000021638
    Feb 26 18:57:11 linux-ddqv kernel: [ 5731.226511] TKIP: replay detected: STA=1c:af:f7:72:71:3b previous TSC 0002000215f7 received TSC 000000021639
    Feb 26 18:57:11 linux-ddqv kernel: [ 5731.976137] TKIP: replay detected: STA=1c:af:f7:72:71:3b previous TSC 0002000215f7 received TSC 00000002163a
    Feb 26 18:57:48 linux-ddqv kernel: [ 5768.180718] wpa_supplicant[11944]: segfault at bf587bb4 ip b739533a sp bfa3e2d0 error 4 in libc-2.11.2.so[b7327000+164000]
    Feb 26 18:57:48 linux-ddqv avahi-daemon[1899]: Withdrawing address record for 192.168.0.117 on wlan0.
    Feb 26 18:57:48 linux-ddqv avahi-daemon[1899]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.117.
    Feb 26 18:57:48 linux-ddqv avahi-daemon[1899]: Interface wlan0.IPv4 no longer relevant for mDNS.
    Feb 26 18:57:48 linux-ddqv kernel: [ 5768.534488] Linking with students: channel is 6
    Feb 26 18:58:08 linux-ddqv nmbd[12194]: [2011/02/26 18:58:08.541381,  0] libsmb/nmblib.c:839(send_udp)
    Feb 26 18:58:08 linux-ddqv nmbd[12194]:   Packet send failed to 192.168.0.255(138) ERRNO=Invalid argument
    Feb 26 18:58:09 linux-ddqv kernel: [ 5789.237069] Linking with students: channel is 6
    Feb 26 18:58:10 linux-ddqv kernel: [ 5790.819724] Associated successfully
    Feb 26 18:58:10 linux-ddqv kernel: [ 5790.819728] Using G rates
    Feb 26 18:58:10 linux-ddqv kernel: [ 5790.876798] Linking with students: channel is 6
    Feb 26 18:58:39 linux-ddqv kernel: [ 5819.211764] Linking with students: channel is 6
    Feb 26 18:58:40 linux-ddqv kernel: [ 5820.883384] Associated successfully
    Feb 26 18:58:40 linux-ddqv kernel: [ 5820.883390] Using G rates
    Feb 26 18:58:40 linux-ddqv kernel: [ 5820.944117] Linking with students: channel is 6
    Feb 26 18:59:08 linux-ddqv nmbd[12194]: [2011/02/26 18:59:08.601527,  0] nmbd/nmbd.c:332(reload_interfaces)
    Feb 26 18:59:08 linux-ddqv nmbd[12194]:   reload_interfaces: No subnets to listen to. Waiting..
    Feb 26 18:59:20 linux-ddqv kernel: [ 5860.477375] Linking with students: channel is 6
    Feb 26 18:59:23 linux-ddqv kernel: [ 5863.312036] Linking with students: channel is 6
    Feb 26 18:59:23 linux-ddqv kernel: [ 5863.347944] Associated successfully
    Feb 26 18:59:23 linux-ddqv kernel: [ 5863.347949] Using G rates
    Feb 26 18:59:23 linux-ddqv kernel: [ 5863.411663] Linking with students: channel is 6
    Feb 26 19:00:10 linux-ddqv kernel: [ 5910.551550] Linking with students: channel is 6
    Feb 26 19:00:13 linux-ddqv kernel: [ 5913.310064] Linking with students: channel is 6
    Feb 26 19:00:13 linux-ddqv kernel: [ 5913.332774] Associated successfully
    Feb 26 19:00:13 linux-ddqv kernel: [ 5913.332781] Using G rates
    Feb 26 19:00:13 linux-ddqv kernel: [ 5913.391793] Linking with students: channel is 6
    Feb 26 19:02:54 linux-ddqv su: (to root) ruth on /dev/pts/3
    Feb 26 19:02:54 linux-ddqv su: (to root) ruth on /dev/pts/3
    Feb 26 19:03:10 linux-ddqv kernel: [ 6090.573398] Linking with students: channel is 6
    Feb 26 19:03:13 linux-ddqv kernel: [ 6093.421077] Linking with students: channel is 6
    Feb 26 19:03:13 linux-ddqv kernel: [ 6093.458017] Associated successfully
    Feb 26 19:03:13 linux-ddqv kernel: [ 6093.458023] Using G rates
    Feb 26 19:03:13 linux-ddqv kernel: [ 6093.546127] Linking with students: channel is 6
    warn:
    Code:
    Feb 26 18:54:02 linux-ddqv kernel: [ 5542.488904] martian source 192.168.0.117 from 50.17.232.192, on dev wlan0
    Feb 26 18:54:02 linux-ddqv kernel: [ 5542.488909] ll header: 00:24:21:4e:e4:11:00:1e:58:c1:00:65:08:00
    Feb 26 18:54:02 linux-ddqv kernel: [ 5542.496745] martian source 192.168.0.117 from 204.236.131.36, on dev wlan0
    Feb 26 18:54:02 linux-ddqv kernel: [ 5542.496749] ll header: 00:24:21:4e:e4:11:00:1e:58:c1:00:65:08:00
    Feb 26 18:54:03 linux-ddqv nmbd[11140]: [2011/02/26 18:54:03.367326,  0] nmbd/nmbd.c:71(terminate)
    Feb 26 18:54:03 linux-ddqv nmbd[11140]:   Got SIGTERM: going down...
    Feb 26 18:54:03 linux-ddqv smbd[2021]: [2011/02/26 18:54:03.539880,  0] smbd/server.c:281(remove_child_pid)
    Feb 26 18:54:03 linux-ddqv smbd[2021]:   Could not find child 11718 -- ignoring
    Feb 26 18:56:09 linux-ddqv kernel: [ 5669.725163] net_ratelimit: 7 callbacks suppressed
    Feb 26 18:56:19 linux-ddqv nmbd[11705]: [2011/02/26 18:56:19.606545,  0] nmbd/nmbd.c:332(reload_interfaces)
    Feb 26 18:56:19 linux-ddqv nmbd[11705]:   reload_interfaces: No subnets to listen to. Waiting..
    Feb 26 18:56:42 linux-ddqv smbd[2021]: [2011/02/26 18:56:42.785783,  0] smbd/server.c:281(remove_child_pid)
    Feb 26 18:56:42 linux-ddqv smbd[2021]:   Could not find child 12076 -- ignoring
    Feb 26 18:56:52 linux-ddqv smbd[2021]: [2011/02/26 18:56:52.546703,  0] smbd/server.c:281(remove_child_pid)
    Feb 26 18:56:52 linux-ddqv smbd[2021]:   Could not find child 12229 -- ignoring
    Feb 26 18:58:08 linux-ddqv nmbd[12194]: [2011/02/26 18:58:08.541381,  0] libsmb/nmblib.c:839(send_udp)
    Feb 26 18:58:08 linux-ddqv nmbd[12194]:   Packet send failed to 192.168.0.255(138) ERRNO=Invalid argument
    Feb 26 18:59:08 linux-ddqv nmbd[12194]: [2011/02/26 18:59:08.601527,  0] nmbd/nmbd.c:332(reload_interfaces)
    Feb 26 18:59:08 linux-ddqv nmbd[12194]:   reload_interfaces: No subnets to listen to. Waiting..
    NetworkManager:
    Code:
    Feb 26 18:53:56 linux-ddqv NetworkManager: <info>  DHCP: device wlan0 state changed normal exit -> preinit
    Feb 26 18:54:02 linux-ddqv NetworkManager: <info>  DHCP: device wlan0 state changed preinit -> reboot
    Feb 26 18:54:02 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
    Feb 26 18:54:02 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
    Feb 26 18:54:02 linux-ddqv NetworkManager: <info>    address 192.168.0.117
    Feb 26 18:54:02 linux-ddqv NetworkManager: <info>    prefix 24 (255.255.255.0)
    Feb 26 18:54:02 linux-ddqv NetworkManager: <info>    gateway 192.168.0.1
    Feb 26 18:54:02 linux-ddqv NetworkManager: <info>    nameserver '192.168.0.1'
    Feb 26 18:54:02 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
    Feb 26 18:54:02 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
    Feb 26 18:54:02 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
    Feb 26 18:54:03 linux-ddqv NetworkManager: <debug> [1298735643.041610] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
    Feb 26 18:54:03 linux-ddqv NetworkManager: <debug> [1298735643.044133] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'#012
    Feb 26 18:54:03 linux-ddqv NetworkManager: <debug> [1298735643.044491] write_to_netconfig(): Writing to netconfig: DNSSERVERS='192.168.0.1'#012
    Feb 26 18:54:03 linux-ddqv NetworkManager: <info>  Clearing nscd hosts cache.
    Feb 26 18:54:03 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 7 -> 8 (reason 0)
    Feb 26 18:54:03 linux-ddqv NetworkManager: <debug> [1298735643.056459] periodic_update(): Roamed from BSSID 1C:AF:F7:72:71:33 (students) to 1C:AF:F7:72:71:3B (students)
    Feb 26 18:54:03 linux-ddqv NetworkManager: <debug> [1298735643.057158] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
    Feb 26 18:54:03 linux-ddqv NetworkManager: <debug> [1298735643.071906] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'#012
    Feb 26 18:54:03 linux-ddqv NetworkManager: <debug> [1298735643.072011] write_to_netconfig(): Writing to netconfig: DNSSERVERS='192.168.0.1'#012
    Feb 26 18:54:03 linux-ddqv NetworkManager: <info>  Clearing nscd hosts cache.
    Feb 26 18:54:03 linux-ddqv NetworkManager: <info>  Policy set 'students' (wlan0) as default for routing and DNS.
    Feb 26 18:54:03 linux-ddqv NetworkManager: <info>  Activation (wlan0) successful, device activated.
    Feb 26 18:54:03 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
    Feb 26 18:54:03 linux-ddqv nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
    Feb 26 18:56:12 linux-ddqv NetworkManager: <info>  (wlan0): supplicant manager state:  idle -> down
    Feb 26 18:56:12 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 8 -> 2 (reason 10)
    Feb 26 18:56:12 linux-ddqv NetworkManager: <info>  (wlan0): deactivating device (reason: 10).
    Feb 26 18:56:12 linux-ddqv NetworkManager: <info>  (wlan0): canceled DHCP transaction, dhcp client pid 11562
    Feb 26 18:56:12 linux-ddqv NetworkManager: <WARN>  check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess#012
    Feb 26 18:56:12 linux-ddqv NetworkManager: <debug> [1298735772.215213] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
    Feb 26 18:56:12 linux-ddqv NetworkManager: <debug> [1298735772.219706] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'#012
    Feb 26 18:56:12 linux-ddqv NetworkManager: <info>  Clearing nscd hosts cache.
    Feb 26 18:56:12 linux-ddqv NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
    Feb 26 18:56:12 linux-ddqv NetworkManager: <info>  Trying to start the supplicant...
    Feb 26 18:56:12 linux-ddqv NetworkManager: <info>  (wlan0): supplicant manager state:  down -> idle
    Feb 26 18:56:12 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 2 -> 3 (reason 0)
    Feb 26 18:56:12 linux-ddqv nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
    Feb 26 18:56:12 linux-ddqv NetworkManager: <info>  (wlan0): supplicant interface state:  starting -> ready
    Feb 26 18:56:37 linux-ddqv NetworkManager: <info>  Activation (wlan0) starting connection 'students'
    Feb 26 18:56:37 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 3 -> 4 (reason 0)
    Feb 26 18:56:37 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Feb 26 18:56:37 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Feb 26 18:56:37 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Feb 26 18:56:37 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Feb 26 18:56:37 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Feb 26 18:56:37 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
    Feb 26 18:56:37 linux-ddqv NetworkManager: <info>  Activation (wlan0/wireless): access point 'students' has security, but secrets are required.
    Feb 26 18:56:37 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 5 -> 6 (reason 0)
    Feb 26 18:56:37 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Feb 26 18:56:38 linux-ddqv NetworkManager: <WARN>  secrets_update_setting(): Failed to update connection secrets: 1 802-1x
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 6 -> 4 (reason 0)
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Activation (wlan0/wireless): connection 'students' has security, and secrets exist.  No new secrets needed.
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Config: added 'ssid' value 'students'
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Config: added 'scan_ssid' value '1'
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Config: added 'psk' value '<omitted>'
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  Config: set interface ap_scan to 1
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
    Feb 26 18:56:38 linux-ddqv NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
    Feb 26 18:56:44 linux-ddqv NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
    Feb 26 18:56:44 linux-ddqv NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
    Feb 26 18:56:44 linux-ddqv NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> associated
    Feb 26 18:56:44 linux-ddqv NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> group handshake
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'students'.
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 5 -> 7 (reason 0)
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction (timeout in 45 seconds)
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  dhclient started with pid 12077
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) scheduled...
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) started...
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) complete.
    Feb 26 18:56:45 linux-ddqv NetworkManager: <info>  DHCP: device wlan0 state changed normal exit -> preinit
    Feb 26 18:56:51 linux-ddqv NetworkManager: <info>  DHCP: device wlan0 state changed preinit -> reboot
    Feb 26 18:56:51 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
    Feb 26 18:56:51 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
    Feb 26 18:56:51 linux-ddqv NetworkManager: <info>    address 192.168.0.117
    Feb 26 18:56:51 linux-ddqv NetworkManager: <info>    prefix 24 (255.255.255.0)
    Feb 26 18:56:51 linux-ddqv NetworkManager: <info>    gateway 192.168.0.1
    Feb 26 18:56:51 linux-ddqv NetworkManager: <info>    nameserver '192.168.0.1'
    Feb 26 18:56:51 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
    Feb 26 18:56:51 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
    Feb 26 18:56:51 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
    Feb 26 18:56:52 linux-ddqv NetworkManager: <debug> [1298735812.024079] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
    Feb 26 18:56:52 linux-ddqv NetworkManager: <debug> [1298735812.028392] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'#012
    Feb 26 18:56:52 linux-ddqv NetworkManager: <debug> [1298735812.028486] write_to_netconfig(): Writing to netconfig: DNSSERVERS='192.168.0.1'#012
    Feb 26 18:56:52 linux-ddqv NetworkManager: <info>  Clearing nscd hosts cache.
    Feb 26 18:56:52 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 7 -> 8 (reason 0)
    Feb 26 18:56:52 linux-ddqv NetworkManager: <debug> [1298735812.036830] periodic_update(): Roamed from BSSID 1C:AF:F7:72:71:33 (students) to 1C:AF:F7:72:71:3B (students)
    Feb 26 18:56:52 linux-ddqv NetworkManager: <debug> [1298735812.037352] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
    Feb 26 18:56:52 linux-ddqv NetworkManager: <debug> [1298735812.052361] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'#012
    Feb 26 18:56:52 linux-ddqv NetworkManager: <debug> [1298735812.052448] write_to_netconfig(): Writing to netconfig: DNSSERVERS='192.168.0.1'#012
    Feb 26 18:56:52 linux-ddqv NetworkManager: <info>  Clearing nscd hosts cache.
    Feb 26 18:56:52 linux-ddqv NetworkManager: <info>  Policy set 'students' (wlan0) as default for routing and DNS.
    Feb 26 18:56:52 linux-ddqv NetworkManager: <info>  Activation (wlan0) successful, device activated.
    Feb 26 18:56:52 linux-ddqv NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
    Feb 26 18:56:52 linux-ddqv nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
    Feb 26 18:57:26 linux-ddqv NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> group handshake
    Feb 26 18:57:26 linux-ddqv NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
    Feb 26 18:57:48 linux-ddqv NetworkManager: <info>  (wlan0): supplicant manager state:  idle -> down
    Feb 26 18:57:48 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 8 -> 2 (reason 10)
    Feb 26 18:57:48 linux-ddqv NetworkManager: <info>  (wlan0): deactivating device (reason: 10).
    Feb 26 18:57:48 linux-ddqv NetworkManager: <info>  (wlan0): canceled DHCP transaction, dhcp client pid 12077
    Feb 26 18:57:48 linux-ddqv NetworkManager: <WARN>  check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess#012
    Feb 26 18:57:48 linux-ddqv NetworkManager: <debug> [1298735868.217010] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
    Feb 26 18:57:48 linux-ddqv NetworkManager: <debug> [1298735868.220138] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'#012
    Feb 26 18:57:48 linux-ddqv NetworkManager: <info>  Clearing nscd hosts cache.
    Feb 26 18:57:48 linux-ddqv NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
    Feb 26 18:57:48 linux-ddqv NetworkManager: <info>  Trying to start the supplicant...
    Feb 26 18:57:48 linux-ddqv NetworkManager: <WARN>  scan_results_cb(): could not get scan results: Method "scanResults" with signature "" on interface "fi.epitest.hostap.WPASupplicant.Interface" doesn't exist#012.
    Feb 26 18:57:48 linux-ddqv NetworkManager: <info>  (wlan0): supplicant manager state:  down -> idle
    Feb 26 18:57:48 linux-ddqv NetworkManager: <info>  (wlan0): device state change: 2 -> 3 (reason 0)
    Feb 26 18:57:48 linux-ddqv nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
    Feb 26 18:57:48 linux-ddqv NetworkManager: <info>  (wlan0): supplicant interface state:  starting -> ready
    firewall:
    Code:
    Feb 26 18:54:22 linux-ddqv kernel: [ 5562.452194] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.117 DST=62.53.230.177 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=60887 DF PROTO=TCP SPT=48478 DPT=80 WINDOW=272 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A00504C7462AB3E19) 
    Feb 26 18:54:22 linux-ddqv kernel: [ 5562.796188] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.117 DST=62.53.230.177 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=60888 DF PROTO=TCP SPT=48478 DPT=80 WINDOW=272 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A00504DCC62AB3E19) 
    Feb 26 18:54:23 linux-ddqv kernel: [ 5563.484175] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.117 DST=62.53.230.177 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=60889 DF PROTO=TCP SPT=48478 DPT=80 WINDOW=272 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A0050507C62AB3E19) 
    Feb 26 18:54:24 linux-ddqv kernel: [ 5564.241172] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.117 DST=62.53.230.177 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=21982 DF PROTO=TCP SPT=48479 DPT=80 WINDOW=272 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A0050537162AB3E19) 
    Feb 26 18:54:24 linux-ddqv kernel: [ 5564.599172] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.117 DST=62.53.230.177 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=21983 DF PROTO=TCP SPT=48479 DPT=80 WINDOW=272 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A005054D762AB3E19) 
    Feb 26 18:54:43 linux-ddqv kernel: [ 5584.124181] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.117 DST=62.53.230.177 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=60893 DF PROTO=TCP SPT=48478 DPT=80 WINDOW=272 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A0050A11C62AB3E19) 
    Feb 26 18:55:05 linux-ddqv kernel: [ 5606.140199] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.117 DST=62.53.230.177 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=60894 DF PROTO=TCP SPT=48478 DPT=80 WINDOW=272 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A0050F71C62AB3E19) 
    Feb 26 18:55:50 linux-ddqv kernel: [ 5650.172195] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.117 DST=62.53.230.177 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=60895 DF PROTO=TCP SPT=48478 DPT=80 WINDOW=272 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A0051A31C62AB3E19) 
    Feb 26 18:55:55 linux-ddqv kernel: [ 5655.531168] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.117 DST=62.53.230.177 LEN=52 TOS=0x00 PREC=0x00 TTL=64 ID=21990 DF PROTO=TCP SPT=48479 DPT=80 WINDOW=272 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080A0051B80B62AB3E19)

  5. #5
    eigentlich keine Blondine
    Registriert seit
    Mar 2010
    Beiträge
    931
    Was den Router angeht: andere Leute können sich einigermaßen einloggen.

  6. #6
    Registrierter Benutzer
    Registriert seit
    Aug 2007
    Ort
    Sauerland
    Beiträge
    1.291
    Was mich mal interessieren würde:
    Welcher Treiber da installiert ist?
    Code:
    /usr/sbin/hwinfo --wlan
    oder
    Code:
    /usr/sbin/hwinfo --netcard
    Bei zweitem Befehl nur die relevante Ausgabe zum Wlan.
    hwinfo evtl nachinstallieren.

  7. #7
    eigentlich keine Blondine
    Registriert seit
    Mar 2010
    Beiträge
    931
    Code:
    ruth@linux-ddqv:~> /usr/sbin/hwinfo --wlan
    13: PCI 200.0: 0282 WLAN controller                             
      [Created at pci.318]
      Unique ID: y9sn.QJ2twrkftL2
      Parent ID: H0_h.kwdMW5ykOE8
      SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:02:00.0
      SysFS BusID: 0000:02:00.0
      Hardware Class: network
      Model: "Realtek RTL8187SE Wireless LAN Controller"
      Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
      Device: pci 0x8199 "RTL8187SE Wireless LAN Controller"
      SubVendor: pci 0x1462 "Micro-Star International Co., Ltd."
      SubDevice: pci 0x6894 
      Revision: 0x22
      Driver: "r8180"
      Driver Modules: "r8187se"
      Device File: wlan0
      Features: WLAN
      I/O Ports: 0xec00-0xecff (rw)
      Memory Range: 0xfebfc000-0xfebfffff (rw,non-prefetchable)
      IRQ: 17 (no events)
      HW Address: 00:24:21:4e:e4:11
      Link detected: no
      WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13
      WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472
      WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54
      WLAN encryption modes: TKIP CCMP
      WLAN authentication modes: open wpa-psk wpa-eap
      Module Alias: "pci:v000010ECd00008199sv00001462sd00006894bc02sc80i00"
      Driver Info #0:
        Driver Status: r8187se is active
        Driver Activation Cmd: "modprobe r8187se"
      Config Status: cfg=no, avail=yes, need=no, active=unknown
      Attached to: #10 (PCI bridge)
    Auch für den zweiten Befehl poste ich mal lieber alles, weil da irgendwie zwei verschiedene Einträge zuv WLAN kommen:
    Code:
    ruth@linux-ddqv:~> /usr/sbin/hwinfo --wlan
    13: PCI 200.0: 0282 WLAN controller                             
      [Created at pci.318]
      Unique ID: y9sn.QJ2twrkftL2
      Parent ID: H0_h.kwdMW5ykOE8
      SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:02:00.0
      SysFS BusID: 0000:02:00.0
      Hardware Class: network
      Model: "Realtek RTL8187SE Wireless LAN Controller"
      Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
      Device: pci 0x8199 "RTL8187SE Wireless LAN Controller"
      SubVendor: pci 0x1462 "Micro-Star International Co., Ltd."
      SubDevice: pci 0x6894 
      Revision: 0x22
      Driver: "r8180"
      Driver Modules: "r8187se"
      Device File: wlan0
      Features: WLAN
      I/O Ports: 0xec00-0xecff (rw)
      Memory Range: 0xfebfc000-0xfebfffff (rw,non-prefetchable)
      IRQ: 17 (no events)
      HW Address: 00:24:21:4e:e4:11
      Link detected: no
      WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13
      WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472
      WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54
      WLAN encryption modes: TKIP CCMP
      WLAN authentication modes: open wpa-psk wpa-eap
      Module Alias: "pci:v000010ECd00008199sv00001462sd00006894bc02sc80i00"
      Driver Info #0:
        Driver Status: r8187se is active
        Driver Activation Cmd: "modprobe r8187se"
      Config Status: cfg=no, avail=yes, need=no, active=unknown
      Attached to: #10 (PCI bridge)
    ruth@linux-ddqv:~> /usr/sbin/hwinfo --netcard
    14: PCI 04.0: 0200 Ethernet controller                          
      [Created at pci.318]
      Unique ID: rBUF.MS0WWkp5xV2
      SysFS ID: /devices/pci0000:00/0000:00:04.0
      SysFS BusID: 0000:00:04.0                                                           
      Hardware Class: network                                                             
      Model: "Silicon Integrated 191 Gigabit Ethernet Adapter"                            
      Vendor: pci 0x1039 "Silicon Integrated Systems Corp."                               
      Device: pci 0x0191 "191 Gigabit Ethernet Adapter"                                   
      SubVendor: pci 0x1462 "Micro-Star International Co., Ltd."                          
      SubDevice: pci 0x63fa                                                               
      Revision: 0x02                                                                      
      Driver: "sis190"                                                                    
      Driver Modules: "sis190"                                                            
      Device File: eth0                                                                   
      Memory Range: 0xfe9fcc00-0xfe9fcc7f (rw,non-prefetchable)                           
      I/O Ports: 0xcc00-0xcc7f (rw)                                                       
      IRQ: 19 (114 events)
      HW Address: 00:24:21:6c:36:0b
      Link detected: no
      Module Alias: "pci:v00001039d00000191sv00001462sd000063FAbc02sc00i00"
      Driver Info #0:
        Driver Status: sis190 is active
        Driver Activation Cmd: "modprobe sis190"
      Config Status: cfg=new, avail=yes, need=no, active=unknown
    
    19: PCI 200.0: 0282 WLAN controller
      [Created at pci.318]
      Unique ID: y9sn.QJ2twrkftL2
      Parent ID: H0_h.kwdMW5ykOE8
      SysFS ID: /devices/pci0000:00/0000:00:06.0/0000:02:00.0
      SysFS BusID: 0000:02:00.0
      Hardware Class: network
      Model: "Realtek RTL8187SE Wireless LAN Controller"
      Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
      Device: pci 0x8199 "RTL8187SE Wireless LAN Controller"
      SubVendor: pci 0x1462 "Micro-Star International Co., Ltd."
      SubDevice: pci 0x6894 
      Revision: 0x22
      Driver: "r8180"
      Driver Modules: "r8187se"
      Device File: wlan0
      Features: WLAN
      I/O Ports: 0xec00-0xecff (rw)
      Memory Range: 0xfebfc000-0xfebfffff (rw,non-prefetchable)
      IRQ: 17 (13435 events)
      HW Address: 00:24:21:4e:e4:11
      Link detected: yes
      WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13
      WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472
      WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54
      WLAN encryption modes: TKIP CCMP
      WLAN authentication modes: open wpa-psk wpa-eap
      Module Alias: "pci:v000010ECd00008199sv00001462sd00006894bc02sc80i00"
      Driver Info #0:
        Driver Status: r8187se is active
        Driver Activation Cmd: "modprobe r8187se"
      Config Status: cfg=no, avail=yes, need=no, active=unknown
      Attached to: #16 (PCI bridge)
    ruth@linux-ddqv:~>

  8. #8
    Mod. FAQ/Howto/Emulation
    Registriert seit
    Sep 2000
    Beiträge
    17.341
    Zitat Zitat von rstuby Beitrag anzeigen
    Was den Router angeht: andere Leute können sich einigermaßen einloggen.
    Was bedeutet das denn? "Einigermaßen" hört sich eher negativ an, so, als ob es bei anderen 2 min geht.

  9. #9
    Registrierter Avatar von eule
    Registriert seit
    Mar 2000
    Ort
    Waierland
    Beiträge
    1.196
    Zitat Zitat von stefan.becker Beitrag anzeigen
    Was bedeutet das denn? "Einigermaßen" hört sich eher negativ an, so, als ob es bei anderen 2 min geht.
    Eben, aber auch:
    Zitat Zitat von rstuby Beitrag anzeigen
    Normalerweise gehe ich über LAN-Kabel ins Internet, aber zur Zeit (und öfter mal) ist die Verbindung nicht verfügbar,
    Geht beides ueber den gleichen Router?
    Eule

  10. #10
    eigentlich keine Blondine
    Registriert seit
    Mar 2010
    Beiträge
    931
    Also von ständigem "disconnect" habe ich bei den anderen noch nichts gehört. Nur dass die Geschwindigkeit schwach ist und auch mal der Empfang (worin äußert sich das? Muss ich noch mal nachfragen), auch in Abhängigkeit davon, wo im Gebäude man sich befindet.

    Das LAN ist nicht vom selben Router, sondern ein "Dozenten- und Mitarbeiter"-Netz, das kommt durch ein unterirdisches Kabel nur in die Bibliothek und in mein Zimmer und soll auch nicht von den Studenten genutzt werden, weil die sonst im Nullkommanix das Passwort für den "Server" geknackt hätten, wo auch Prüfungsfragen und so liegen. Der "Dozenten"-Router hat aber auch ein WLAN, ich kann also mal mein Notebook mit ins Büro nehmen und es da versuchen.

    Ich befürchte auch, dass ich bald auf das Studenten-WLAN angewiesen sein werde, da das Kabel zwischen den beiden Gebäuden die diesjährige Schneeschmelze wohl kaum übersteht. Nach der letzten hat der Computerspezialist noch mit "trial and error" zwei funktionierende Adern gefunden... und den Hof aufzubuddeln kommt auch nicht so schnell in Frage.

  11. #11
    eigentlich keine Blondine
    Registriert seit
    Mar 2010
    Beiträge
    931
    Vielleicht sollte ich mich auch einfach mal in den Flur oder in die Studentenküche setzen, näher an den Router. Ich habe jetzt gefunden, wo die Signalstärke angezeigt wird: sie ist zur Zeit 58% und es hält schon jedes Mal mehrere Minuten, deutlich besser als gestern.

    Das LAN ist aber auch erstmal wieder da :-)

  12. #12
    Mod. FAQ/Howto/Emulation
    Registriert seit
    Sep 2000
    Beiträge
    17.341
    Nun ja, dann ist es wohl eher ein physikalisches Problem.

    Da hilft entweder ein Repeater oder ein Boschhammer.

  13. #13
    eigentlich keine Blondine
    Registriert seit
    Mar 2010
    Beiträge
    931
    Sorry... hab gerade von einem Studenten erfahren, dass andere mit unserem WLAN im Moment das gleiche Problem haben...
    Also Entwarnung.

  14. #14
    eigentlich keine Blondine
    Registriert seit
    Mar 2010
    Beiträge
    931
    Hallo!
    Meine letzte Info hat sich als nicht ganz richtig herausgestellt. Die Studenten hatten zwar auch Probleme, aber nicht genau solche.
    Ich habe es jetzt geschafft, die Verbindung über die "traditionelle Methode mit ifup" ohne den NetworkManager einzurichten, und es läuft. Der war also wohl schuld. Schade, war ein bequemes Interface zum schnellen Umschalten zwischen Kabel und Wlan.

  15. #15
    Newbie and practicing Avatar von Newbie314
    Registriert seit
    Mar 2007
    Beiträge
    7.639
    .. wenn es darum geht schnell und einfach umzuschalten: du könntest dir die Befehle dazu in ein Skript gießen, deinem User mit der sudoers Liste das Recht geben die Skripte mit rootrechten auszuführen und diese Skripte mit Verknüpfungen auf dem Desktop sichtbar /startbar machen.

    Ist etwas Aufwand, aber deine Beschreibung klingt so als müsstest du ständig wechseln..
    Bei Konsolenausgaben / Fehlermeldungen bitte immer Code Tags verwenden: [code] -Text- [/code]
    "Überzeugungen sind gefährlichere Feinde der Wahrheit als Lügen" (H. Lesch)

Ähnliche Themen

  1. WLAN einrichten funktioniert nicht
    Von [SB]Benjamin im Forum Anbindung an die Aussenwelt
    Antworten: 11
    Letzter Beitrag: 26.03.07, 15:30
  2. WLAN funktioniert nicht
    Von Markus-MV6 im Forum Anbindung an die Aussenwelt
    Antworten: 2
    Letzter Beitrag: 19.03.07, 17:33
  3. wlan funktioniert nicht
    Von KITT im Forum Anbindung an die Aussenwelt
    Antworten: 18
    Letzter Beitrag: 29.06.06, 18:21
  4. Ubuntu WLAN mit WPA funktioniert nicht
    Von GambaJo im Forum Anbindung an die Aussenwelt
    Antworten: 0
    Letzter Beitrag: 27.06.06, 20:43
  5. Wlan funktioniert nur 1 minute lang
    Von TheDoctor im Forum Router und Netzaufbau
    Antworten: 6
    Letzter Beitrag: 16.12.03, 07:34

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •