FunkNetzwerkkonfiguration

Begonnen von susa, 2014/08/25, 17:47:46

Vorheriges Thema - Nächstes Thema

susa

Hallo,
ich bin gerade dabei mich mit dem Laptop vom Kabelnetzwerk zu lösen, nur leider wird die  Funknetzwerkkarte leider nicht gefunden
ifconfig
eth0      Link encap:Ethernet  Hardware Adresse 00:02:3f:18:db:e6 
          inet Adresse:192.168.178.21  Bcast:192.168.178.255  Maske:255.255.255.0
          inet6-Adresse: fe80::202:3fff:fe18:dbe6/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX Pakets:149867 errors:0 dropped:0 overruns:0 frame:0
          TX packets:85460 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:215622288 (205.6 MiB)  TX bytes:6209533 (5.9 MiB)i

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 packets:74 errors:0 dropped:0 overruns:0 frame:0
          TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:5956 (5.8 KiB)  TX bytes:5956 (5.8 KiB)

root@siductionbox:/home/mgtd# inxi -AG
Graphics:  Card: Advanced Micro Devices [AMD/ATI] RV350/M10 [Mobility Radeon 9600 PRO Turbo]
           Display Server: X.org 1.16.0 drivers: ati,radeon (unloaded: fbdev,vesa)
           tty size: 128x21 Advanced Data: N/A for root
Audio:     Card Intel 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller driver: snd_intel8x0
           Sound: Advanced Linux Sound Architecture v: k3.16-1.towo-siduction-686
root@siduct

[code]
ich habe auch schon
[code]apt-get install firmware-linux firmware-linux-free firmware-linux-nonfree
[code]installiert

ayla

Was sagt denn inxi -n oder inxi -v2?

Wenn da nix vom Netzwerkchip kommt: lsusb oder lspci?

susa


root@siductionbox:/home/mgtd# inxi -n
Network:   Card-1: Realtek RTL-8139/8139C/8139C+ driver: 8139too
           IF: eth0 state: unknown speed: 100 Mbps duplex: full mac: 00:02:3f:18:db:e6
           Card-2: Intel PRO/Wireless 2200BG [Calexico2] Network Connection
           IF: N/A state: N/A mac: N/A
root@siductionbox:/home/mgtd# inxi -v2
System:    Host: siductionbox Kernel: 3.16-1.towo-siduction-686 i686 (32 bit) Desktop: LXDE (Openbox 3.5.2)
           Distro: siduction 12.1.6 Razor-qt LU-Edition - rqt - (201206250126)
Machine:   System: Acer product: TravelMate 290
           Mobo: N/A model: N/A Bios: ACER v: Version 1.40.T2 date: 05/31/2004
CPU:       Single core Intel Pentium M (-UP-) clocked at 1500 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] RV350/M10 [Mobility Radeon 9600 PRO Turbo]
           Display Server: X.org 1.16.0 drivers: ati,radeon (unloaded: fbdev,vesa)
           tty size: 128x23 Advanced Data: N/A for root
Network:   Card-1: Realtek RTL-8139/8139C/8139C+ driver: 8139too
           Card-2: Intel PRO/Wireless 2200BG [Calexico2] Network Connection
Drives:    HDD Total Size: 60.0GB (33.6% used) ID-1: model: HITACHI_DK23EA
Info:      Processes: 131 Uptime: 16 min Memory: 308.9/501.8MB Client: Shell (bash) inxi: 2.2.1
root@siductionbox:/home/mgtd#

susa

und eben schnell nachreich
root@siductionbox:/home/mgtd# lsusb
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@siductionbox:/home/mgtd# lspci
00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 21)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 21)
00:1d.0 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV350/M10 [Mobility Radeon 9600 PRO Turbo]
02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 80)
02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
02:03.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller (rev 01)
root@siductionbox:/home/mgtd#

ich hoffe, es ist hilfreich.

ayla

apt-get install firmware-ipw2x00
reboot


denn:
Zitat
apt-cache search intel 2200
firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915
firmware-iwlwifi - Binary firmware for Intel Wireless cards

apt-cache show firmware-ipw2x00 
firmware-ipw2x00                                         
Package: firmware-ipw2x00                                                                 
Source: firmware-nonfree                                                                 
Version: 0.43                                                                             
Installed-Size: 1226                                                                     
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>                           
Architecture: all                                                                         
Depends: debconf (>= 0.5) | debconf-2.0                                                   
Pre-Depends: debconf | debconf-2.0                                                       
Suggests: initramfs-tools                                                                 
Description-en: Binary firmware for Intel Pro Wireless 2100, 2200 and 2915               
This package contains the binary firmware for Intel Pro Wireless 2100,                   
2200 and 2915 cards supported by the ipw2100 and ipw2200 drivers.
.
Contents:
  * Intel Pro Wireless 2100 firmware (bootstrap), version 1.3
    (ipw2100-1.3.fw)
  * Intel Pro Wireless 2100 firmware (ibss mode), version 1.3
    (ipw2100-1.3-i.fw)
  * Intel Pro Wireless 2100 firmware (monitor mode), version 1.3
    (ipw2100-1.3-p.fw)
  * Intel Pro Wireless 2200/2915 firmware (bss), version 3.1
    (ipw2200-bss.fw)
  * Intel Pro Wireless 2200/2915 firmware (ibss), version 3.1
    (ipw2200-ibss.fw)
  * Intel Pro Wireless 2200/2915 firmware (snf), version 3.1
    (ipw2200-sniffer.fw)

susa


root@siductionbox:/home/mgtd# apt-cache policy firmware-ipw2x00 
firmware-ipw2x00:
  Installiert:           0.43
  Installationskandidat: 0.43
  Versionstabelle:
*** 0.43 0
        500 http://ftp2.de.debian.org/debian/ unstable/non-free i386 Packages
        500 http://ftp.us.debian.org/debian/ unstable/non-free i386 Packages
        500 http://ftp.us.debian.org/debian/ testing/non-free i386 Packages
        100 /var/lib/dpkg/status
     0.41 0
        500 http://http.debian.net/debian/ unstable/non-free i386 Packages
root@siductionbox:/home/mgtd#
[code] funzt immer noch nicht

towo

"Funzt nicht" hilft auch Keinem!
Hast DU nach der Installation der Firmware das Kernel-Modul neu geladen?
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

ayla

Wie towo sagt: Mit "funzt nicht" ist, außer in's Blaue raten, keine Hilfe möglich.

Was weiterhelfen könnte ist die Ausgabe von folgendem:

modprobe -rv ipw2200

modprobe -iv ipw2200

rfkill list

ifconfig

iwconfig


susa

# modprobe -rv ipw2200
rmmod ipw2200
rmmod libipw
rmmod lib80211
rmmod cfg80211
rmmod rfkill
root@siductionbox:/home/mgtd#
root@siductionbox:/home/mgtd# modprobe -iv ipw2200
insmod /lib/modules/3.16-1.towo-siduction-686/kernel/net/rfkill/rfkill.ko
insmod /lib/modules/3.16-1.towo-siduction-686/kernel/net/wireless/lib80211.ko
insmod /lib/modules/3.16-1.towo-siduction-686/kernel/net/wireless/cfg80211.ko
insmod /lib/modules/3.16-1.towo-siduction-686/kernel/drivers/net/wireless/ipw2x00/libipw.ko
insmod /lib/modules/3.16-1.towo-siduction-686/kernel/drivers/net/wireless/ipw2x00/ipw2200.ko
root@siductionbox:/home/mgtd#
root@siductionbox:/home/mgtd# rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
root@siductionbox:/home/mgtd#
root@siductionbox:/home/mgtd# ifconfig
eth0      Link encap:Ethernet  Hardware Adresse 00:02:3f:18:db:e6 
          inet Adresse:192.168.178.21  Bcast:192.168.178.255  Maske:255.255.255.0
          inet6-Adresse: fe80::202:3fff:fe18:dbe6/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:70985 errors:0 dropped:0 overruns:0 frame:0
          TX packets:43422 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:101022369 (96.3 MiB)  TX bytes:3430601 (3.2 MiB)

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 packets:1770 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1770 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:138740 (135.4 KiB)  TX bytes:138740 (135.4 KiB)

root@siductionbox:/home/mgtd#
root@siductionbox:/home/mgtd# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

eth1      IEEE 802.11bg  ESSID:off/any 
          Mode:Managed  Channel:0  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power=20 dBm   Sensitivity=8/0 
          Retry limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@siductionbox:/home/mgtd#

ayla

Dein Chip ist als eth1 da, sollte aber AFAIK wlan0 sein damit es funktioniert.

Zeig mal bitte die Ausgabe von cat /etc/udev/rules.d/70-persistent-net.rules

susa

cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x10ec:/sys/devices/pci0000:00/0000:00:1e.0/0000:02:01.0 (8139too)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:3f:18:db:e6", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x4220 (ipw2200)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:35:35:fa:5f", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
mgtd@siductionbox:~$

ayla

Öffne die Datei als root mit dem Editor Deiner Wahl und änder sie so ab:


Zitat# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x10ec:/sys/devices/pci0000:00/0000:00:1e.0/0000:02:01.0 (8139too)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:3f:18:db:e6", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x4220 (ipw2200)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:35:35:fa:5f", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
Speichern/Schließen
Dann entweder ein udevadm triggeroder ein reboot und schau dann mal ob Du mit ceni oder Networkmanager was bekommst.

Wenn nicht nochmal die Ausgabe von rfkill list, ifconfig, iwconfig. Eventuell auch noch ein iwlist scan aber nimm dort die Zeilen raus die mit
ZitatIE: Unknown
beginnen, ich bin mir nicht sicher ob da nicht der Schlüssel mit bei ist.

susa

iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

eth1      IEEE 802.11bg  ESSID:off/any 
          Mode:Managed  Channel:0  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power=20 dBm   Sensitivity=8/0 
          Retry limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

root@siductionbox:/home/mgtd# iwlist scan
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

eth1      Scan completed :
          Cell 01 - Address: 08:96:D7:84:9E:06
                    ESSID:"FritzBox!"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.412 GHz (Channel 1)
                    Encryption key:on
                    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; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=96/100  Signal level=-30 dBm 
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    Extra: Last beacon: 150ms ago
          Cell 02 - Address: 2A:65:11:99:92:C3
                    ESSID:"MANNI_HOME"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.437 GHz (Channel 6)
                    Encryption key:on
                    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; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=53/100  Signal level=-69 dBm 
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    Extra: Last beacon: 93ms ago
          Cell 03 - Address: 08:96:D7:E5:1A:8D
                    ESSID:"Netz"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.412 GHz (Channel 1)
                    Encryption key:on
                    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; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=39/100  Signal level=-77 dBm 
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK
                    Extra: Last beacon: 213ms ago


susa

wo steht das mit dem
IE: Unknown
ayla

ayla

Hi,

ich hab hier gerade das Läppi eines Bekannten mit dem gleichen WLAN-Chip in die Finger bekommen.

Das WLAN funktioniert nach Installation der firmware und Einschalten per Hardwareschalter auch ohne die udev-rules zu ändern. Also mach die Änderungen in den 70-persistent-net.rules bitte rückgängig -lt einigem gegoogel funktioniert das sowieso nicht (mehr).

Allerdings: Sobald Du Dein Laptop ohne Kabelverbindung bootest ändert sich Dein wlan-Interface von eth1 auf eth0, das kann etwas umständlich sein wenn Du was anderes als den NetworkManager benutzt.!

Wie -mit welcher app- verbindest Du Dich mit dem Router? NM, ceni, oder wicd?
Was sagt rfkill list nach einem Verbindungsversuch?