wifi dongle

giuliomoro

Are the LEDs blinking as usual? Is the device showing up as a "BELABOOT" drive on your computer? Maybe try removing the WiFi dongle and reboot?

giuliomoro

I am wondering if the space in the SSID name is what is tripping it off? Can you try changing that name temporarily?
Hopefully you turned the actual psk to ************** only for the purpose of posting it here, but entered it correctly when you ran wpa_passphrase.

claudiopanariello

giuliomoro Yes, I put the stars in the password just for posting here 🙂
I thought something related to the Network name, I will give a try to this in a while!
Regarding the other questions, all yes: led blinking and BELABOOT shown on my computer.

giuliomoro

claudiopanariello So, I tried removing the wifi dongle

that may just have slowed down the network bringup process ...

claudiopanariello

I tried again with ifdown wlan0; ifup wlan0 and now I get this:

root@bela:~# ifdown wlan0; ifup 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/d0:37:45:89:72:63
Sending on   LPF/wlan0/d0:37:45:89:72:63
Sending on   Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
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/d0:37:45:89:72:63
Sending on   LPF/wlan0/d0:37:45:89:72:63
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

So at least I don't get the message Network is unreachable, but still no ip address.

giuliomoro

what does /etc/wpa_supplicant/wpa_supplicant.conf look like now?

claudiopanariello

giuliomoro I have changed my network name to a more straightforward "testcasa" and updated the network name and password (stars just for posting here):

network={
        ssid="testcasa"
        #psk="*****"
        psk=f4a8591d0a20844db373d3ca12a1172a05f4f69e54ad071dae73d76f50bff322
}

Running ifdown wlan0; ifup wlan0; I encounter the same problem as before:

root@bela:~# ifdown wlan0; ifup 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/d0:37:45:89:72:63
Sending on   LPF/wlan0/d0:37:45:89:72:63
Sending on   Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.
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/d0:37:45:89:72:63
Sending on   LPF/wlan0/d0:37:45:89:72:63
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 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

claudiopanariello

I am wondering if the problem might be with the dongle itself, although when running lsusb I can see it, and when running iwlist wlan0 scanning I can detect all the available networks, including "testcasa". Or this doesn't actually tell anything about the proper dongle functioning ?

giuliomoro

well the fact that the network is recognised with iwlist surely shows that something does work.

I see that one of the lines output by ifdown wlan0 is :

DHCPRELEASE on wlan0 to 192.168.1.1 port 67

which means that it somehow knows that the DHCP is on 192.168.1.1 . I am wondering at what point it found out about it ...

however, these:

send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.

don't look particularly good ...

Also, did you modify the /etc/network/interfaces file at all? The default one assumes that your router will have a running DHCP server, which would be expected of any home router ... is that the case? You could also try to set it up with a static IP in /etc/network/interfaces ... does the device ever show up in your router's control panel?

A few shots in the dark:
- run ifup with --verbose to see if it prints something else
- see if dmesg shows some useful error message while you are trying this
- did you google the name of your device (as returned by lsusb or dmesg, not necessarily its commercial name) along with the issue? Sometimes Linux drivers are just broken ...

claudiopanariello

Ok, so: I tried modifying /etc/network/interfaces with a static IP, failed, went back to DHCP and now I get this:

root@bela:~# ifdown wlan0; ifup 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/d0:37:45:89:72:63
Sending on   LPF/wlan0/d0:37:45:89:72:63
Sending on   Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
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/d0:37:45:89:72:63
Sending on   LPF/wlan0/d0:37:45:89:72:63
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

so at least not "Network is unreachable" anymore.
The --verbose gives me:

root@bela:~# ifup wlan0 --verbose
ifup: interface wlan0 already configured

Now checking again about possible issues with the device, drivers and so on.

giuliomoro

claudiopanariello The --verbose gives me:

you also need ifdown wlan0 before that!

giuliomoro

claudiopanariello to DHCP and now I get this:

it seems the same as before, right?

claudiopanariello

giuliomoro Yes, sorry, but even with ifdown wlan0; ifup wlan0 --verbose the outputs seems the same same as before:

root@bela:~# ifdown wlan0; ifup wlan0 --verbose
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/d0:37:45:89:72:63
Sending on   LPF/wlan0/d0:37:45:89:72:63
Sending on   Socket/fallback
DHCPRELEASE on wlan0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
dhclient.c:2733: Failed to send 300 byte long packet over fallback interface.

ifup: configuring interface wlan0=wlan0 (inet)
/bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/hostapd
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver nl80211,wext (default)
wpa_supplicant: /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlan0.pid -i wlan0 -D nl80211,wext -c /etc/wpa_supplicant/wpa_supplicant.conf -C /run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: creating sendsigs omission pidfile: /run/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlan0.pid
wpa_supplicant: ctrl_interface socket located at /run/wpa_supplicant/wlan0

/sbin/dhclient -4 -v -pf /run/dhclient.wlan0.pid -lf /var/lib/dhcp/dhclient.wlan0.leases -I -df /var/lib/dhcp/dhclient6.wlan0.leases 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/d0:37:45:89:72:63
Sending on   LPF/wlan0/d0:37:45:89:72:63
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 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
/bin/run-parts --exit-on-error --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/upstart
run-parts: executing /etc/network/if-up.d/wpasupplicant

claudiopanariello

giuliomoro Totally the same, yeah, the only thing missing was "Network is unreachable", that now is back tho

claudiopanariello

giuliomoro Hello again. I made some attempts to make it work, failing; today, without literally doing anything, the wifi device seems to properly work:

root@bela:~# lsusb
Bus 001 Device 002: ID 2357:0109 TP-Link TL WN823N RTL8192EU
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@bela:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:35:ff:8c:c8:4f brd ff:ff:ff:ff:ff:ff
3: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether be:1a:ff:8c:c8:51 brd ff:ff:ff:ff:ff:ff
    inet 192.168.6.2/24 brd 192.168.6.255 scope global usb0
       valid_lft forever preferred_lft forever
    inet6 fe80::bc1a:ffff:fe8c:c851/64 scope link 
       valid_lft forever preferred_lft forever
4: usb1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether be:1a:ff:8c:c8:54 brd ff:ff:ff:ff:ff:ff
    inet 192.168.7.2/24 brd 192.168.7.255 scope global usb1
       valid_lft forever preferred_lft forever
    inet6 fe80::bc1a:ffff:fe8c:c854/64 scope link 
       valid_lft forever preferred_lft forever
5: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d0:37:45:89:72:63 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.19/24 brd 192.168.1.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::d237:45ff:fe89:7263/64 scope link 
       valid_lft forever preferred_lft forever
```
I will just accept they mystery.

giuliomoro

🤷