Ein Versuch DWA-131E1 USB-WIFI Adapter am Pi B+ installieren

DWA-131E1 USB-WIFI Adapter am Pi B+ installieren

Ich denke das chipset ist RTL8192EU. Bitte korregieren, wenn ich falsch liege.

Im Folgenden versuche ich den Ablauf darzustellen:

pi@raspberrypi:~ $ uname -a

Linux raspberrypi 4.9.59+ #1047 Sun Oct 29 11:47:10 GMT 2017 armv6l GNU/Linux

pi@raspberrypi:/ $ lsusb

Bus 001 Device 006: ID 2001:3319 D-Link Corp.

Bus 001 Device 005: ID 413c:2003 Dell Computer Corp. Keyboard

Bus 001 Device 004: ID 046d:c001 Logitech, Inc. N48/M-BB48/M-UK96A [FirstMouse Plus]

Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter

Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pi@raspberrypi:/ $ sudo dmesg -T | grep usb

[Tue Feb 16 14:15:38 2021] usb 1-1.5: new high-speed USB device number 6 using dwc_otg

[Tue Feb 16 14:15:38 2021] usb 1-1.5: New USB device found, idVendor=2001, idProduct=3319

[Tue Feb 16 14:15:38 2021] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[Tue Feb 16 14:15:38 2021] usb 1-1.5: Product: Wireless N Nano USB Adapter

[Tue Feb 16 14:15:38 2021] usb 1-1.5: Manufacturer: Realtek

[Tue Feb 16 14:15:38 2021] usb 1-1.5: SerialNumber: 00e04c000001

[Tue Feb 16 14:15:39 2021] usbcore: registered new interface driver rtl8192eu

Bis hier denke ich wird der Adapter am USB erkannt und ein Treiber zugewiesen ?

Ja / Nein ?

pi@raspberrypi:/ $ apt-cache search rtl8192eu

firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters

pi@raspberrypi:/ $ lsmod

Module Size Used by

8192eu 1464640 0

bluetooth 375121 0

fuse 94600 3

cfg80211 527100 1 8192eu

rfkill 21373 4 bluetooth,cfg80211

spidev 7034 0

evdev 11746 4

snd_bcm2835 23131 1

snd_pcm 97825 1 snd_bcm2835

snd_timer 22706 1 snd_pcm

snd 68784 5 snd_timer,snd_bcm2835,snd_pcm

i2c_bcm2835 6433 0

spi_bcm2835 7424 0

bcm2835_gpiomem 3791 2

uio_pdrv_genirq 3718 0

uio 10166 1 uio_pdrv_genirq

fixed 3029 0

rtc_pcf8583 3060 0

i2c_dev 6642 0

ip_tables 12512 0

x_tables 20921 1 ip_tables

ipv6 384613 14

pi@raspberrypi:~ $ iwconfig

wlan0 unassociated Nickname:"<WIFI@REALTEK>"

Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated

Sensitivity:0/0

Retry:off RTS thr:off Fragment thr: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

lo no wireless extensions.

eth0 no wireless extensions.

An dieser Stelle vermute ich der WIFI Adapter ist erkannt und eingebunden.

Aber mit keinem Netzwerk verbunden, es gibt keine IP Adresse ?

pi@raspberrypi:/etc/network $ sudo cat interfaces

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd

# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:

source-directory /etc/network/interfaces.d

auto wlan0

auto lo

iface lo inet loopback

iface eth0 inet dhcp

allow-hotplug wlan0

iface wlan0 inet dhcp

wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

iface default inet dhcp

pi@raspberrypi:/etc/network $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev

country=GR

update_config=1

network={

ssid="**myName**"

psk="**myPSWD**"

proto=RSN

key_mgmt=WPA-PSK

pairwise=CCMP

auth_alg=OPEN

Reboot dauert nun länger, vermutlich wegen "auto wlan0" ??

Aber es hat sich nichts geändert:

pi@raspberrypi:~ $ iwconfig

wlan0 unassociated Nickname:"<WIFI@REALTEK>"

Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated

Sensitivity:0/0

Retry:off RTS thr:off Fragment thr: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

pi@raspberrypi:~ $ sudo ip link set wlan0 down

pi@raspberrypi:~ $ sudo ip link set wlan0 up

Ebenfalls nach diesen Befehlen keine Ändewrung im iwconfig zu sehen.

pi@raspberrypi:~ $ sudo ifdown wlan0

Killed old client process

Internet Systems Consortium DHCP Client 4.3.5

Copyright 2004-2016 Internet Systems Consortium.

All rights reserved.

For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/c4:e9:0a:08:01:6e

Sending on LPF/wlan0/c4:e9:0a:08:01:6e

Sending on Socket/fallback

pi@raspberrypi:~ $ sudo ifup wlan0

Internet Systems Consortium DHCP Client 4.3.5

Copyright 2004-2016 Internet Systems Consortium.

All rights reserved.

For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/c4:e9:0a:08:01:6e

Sending on LPF/wlan0/c4:e9:0a:08:01:6e

Sending on Socket/fallback

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9

No DHCPOFFERS received.

No working leases in persistent database - sleeping.

Auch mit verschiedenen Einstellungen in wpa_supplicant.conf und interfaces,

die ich im WEB fand, hatte ich keinen Erfolg.

Mein Ziel ist es den Pi über DHCP automatisch mit dem Netzwerk zu verbinden.

Hi, danke für den Tip. Heute habe ich einen Pi3 model B, mit integriertem Wlan, erfolgreich in mein Neztwerk eingebunden.

Auch all unsere Gäste haben, meist mit den Smartphones, kein Probelm unser wlan zu nutzten. Sollte OK sein.

Ich bin weiterhin ratlos, wo ich nach dem Problem suchen soll. Ist USB OK, ist der Treiber OK, oder sind die Dateien /etc/network/interfaces,

/etc/wpa_supplicant/wpa_supplicant.conf sowie /etc/dhcpcd.conf das Problem. Antworten auf oben gestellte Fragen könnten Klarheit schaffen.

"sudo services dhcpcd status" zeigt ,dass DHCP aktive ist. Was macht : sudo systemctl enable dhcpcd ??

LG

Hi, der Schlüssel zum Erfolg war .....

pi@raspberrypi:/ $ sudo service dhcpcd status

● dhcpcd.service - dhcpcd on all interfaces

Loaded: loaded (/lib/systemd/system/dhcpcd.service; enabled; vendor preset: enabled)

Active: failed (Result: exit-code) since Wed 2021-02-17 13:14:29 UTC; 2 days ago

Process: 211 ExecStart=/usr/lib/dhcpcd5/dhcpcd -q -b (code=exited, status=6)

Feb 17 13:14:28 raspberrypi systemd[1]: Starting dhcpcd on all interfaces...

Feb 17 13:14:29 raspberrypi dhcpcd[211]: Not running dhcpcd because /etc/network/interfaces

Feb 17 13:14:29 raspberrypi dhcpcd[211]: defines some interfaces that will use a

Feb 17 13:14:29 raspberrypi dhcpcd[211]: DHCP client or static address

Feb 17 13:14:29 raspberrypi systemd[1]: dhcpcd.service: Control process exited, code=exited status=6

Feb 17 13:14:29 raspberrypi systemd[1]: Failed to start dhcpcd on all interfaces.

Feb 17 13:14:29 raspberrypi systemd[1]: dhcpcd.service: Unit entered failed state.

Feb 17 13:14:29 raspberrypi systemd[1]: dhcpcd.service: Failed with result 'exit-code'.

die interfaces-Datei habe ich wie flogt geändert:

pi@raspberrypi:/ $ sudo cat /etc/network/interfaces

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd

# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:

source-directory /etc/network/interfaces.d

wpa_supplicant-Datei und dhcpcd.conf ebenfalls :

pi@raspberrypi:/ $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev

update_config=1

country=GR

network={

ssid="*mynet*"

psk="*mykey*"

proto=RSN

key_mgmt=NONE

pairwise=CCMP

auth_alg=OPEN

wep_key0="*mykey*"

pi@raspberrypi:/ $ sudo cat /etc/dhcpcd.conf

....

interface wlan0

static ip_address=192.168.2.101/24

static routers=192.168.2.1

static domain_name_servers=8.8.8.8 4.4.4.4

static domain_search=

noipv6

pi@raspberrypi:/ $ sudo service dhcpcd stop

pi@raspberrypi:/ $ sudo service dhcpcd start

pi@raspberrypi:/ $ sudo service dhcpcd status

● dhcpcd.service - dhcpcd on all interfaces

Loaded: loaded (/lib/systemd/system/dhcpcd.service; enabled; vendor preset: enabled)

Active: active (running) since Sat 2021-02-20 10:52:09 UTC; 3s ago

Process: 980 ExecStart=/usr/lib/dhcpcd5/dhcpcd -q -b (code=exited, status=0/SUCCESS)

Main PID: 982 (dhcpcd)

CGroup: /system.slice/dhcpcd.service

└─982 /sbin/dhcpcd -q -b

Feb 20 10:52:09 raspberrypi systemd[1]: Starting dhcpcd on all interfaces...

Feb 20 10:52:09 raspberrypi dhcpcd[980]: dev: loaded udev

Feb 20 10:52:09 raspberrypi dhcpcd[980]: forked to background, child pid 982

Feb 20 10:52:09 raspberrypi systemd[1]: Started dhcpcd on all interfaces.

Feb 20 10:52:10 raspberrypi dhcpcd[982]: eth0: waiting for carrier

Feb 20 10:52:10 raspberrypi dhcpcd[982]: wlan0: waiting for carrier

Sieh´ da eine IP!

pi@raspberrypi:/ $ ifconfig wlan0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 192.168.2.101 netmask 255.255.255.0 broadcast 192.168.2.255

inet6 fe80::c6e9:aff:fe08:16e prefixlen 64 scopeid 0x20<link>

ether c4:e9:0a:08:01:6e txqueuelen 1000 (Ethernet)

RX packets 4654 bytes 6101009 (5.8 MiB)

RX errors 0 dropped 2455 overruns 0 frame 0

TX packets 3743 bytes 408602 (399.0 KiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

LG